Login failed for user ''NT AUTHORITY\ANONYMOUS LOGON

Hello Guys,

I have two machines that i want to use for merge replication :

Laptop ( Publisher + Distributor )

VPS90 ( Subscriber )

Both connected via the internet

NO DOMAIN

Need to implement merge replication ,after initializing the snapshot I get the following error on both machines :

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 192.168.1.1]

I created a new user "Repuser" (admin)with the same password on both machines and configured the Agent proccess to run under that account ,now i get this error :

Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.1]

Please note that :

· Mixed mode authentication IS ENABLED ON BOTH MACHINES

· BOTH MACHINES CAN PING AND ACCESS EACH OTHER ,BOTH COMPLEETELY VISIBLE.

· CONFIGURED ALIASES ON BOTH MACHINES.

· Both configured to use Sa account .

* I have NO DOMAIN

what does this mean?

It simply means that the SQL Server Agent process account is the one that’s being authenticated to connect to the other machine and NOT the Sa account ,WHY?

do i have to use Web Synch in my case?

hi,

replication uses the sql server agent services

your sql services should be running on an account that has

access to replication resources such as the snapshot folder or the replication folder.

the sql server services should be able to access both machine

regards,

joey

|||how can i make the SQL Server Agent account access the other machine ? supposing that i have no domain? please clarify|||Hello?!! Any 1 there?!|||

how are the machine connected in the internet anyway?

are the IPs exposed over the web? Are you using VPN's?

192.168.1.1 seems to be a local IP

anyway...

I think it is not possible to do replication without domain

maybe some other solution would be better in the scenario

like

the SQL SERVER integration services (SSIS)

|||

thanks for the reply joeydj

both machines are exposed to the internet openely ,no VPNs ,first 1 with a static IP (in USA) and the other is via a DSL modem via NAT (thats y u saw 192.168.1.1) ,they can both connect to each other via SQL server Management Studio with out any problems ,i think microsoft made it nearly impossible to do anything with out Domain ,which is really stupid ,as for merge replication (which is my case) ,they are suggesting Web Synchronization if no domain was present ,which is even much harder to configure.

|||

Good Morning (its morning here)!
FINALLY I DID IT!...ITS WORKING NOW..>WOWWWWWWWWW..
well after cleaning up the whole mess and starting over from scratch ,i figured out the following mistake:
i made TWO Aliases on the publisher one for the publisher itself and the other for the subscriber ,the publisher Alias was causing the connection to fail when initializing the snapshot ,thats why i got the error message ,although i could connect to my own machine using that alias ,which make things strange ,but it was causing connection problems with the agent.

|||

Hi

Can you describe your setup a bit more in details, I'm having the exact same problem.

I get no errors other than the Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON error.

The two servers seem to connect just fine, and I can connect to them from sql server managemen studio just fine. But the Snapshot is not created.

On the subscriber machine the only indication that its not working is a message that the replication could not finish because no snapshot exists.

|||

ali_khankan wrote:

Good Morning (its morning here)!
FINALLY I DID IT!...ITS WORKING NOW..>WOWWWWWWWWW..
well after cleaning up the whole mess and starting over from scratch ,i figured out the following mistake:
i made TWO Aliases on the publisher one for the publisher itself and the other for the subscriber ,the publisher Alias was causing the connection to fail when initializing the snapshot ,thats why i got the error message ,although i could connect to my own machine using that alias ,which make things strange ,but it was causing connection problems with the agent.

that's a good news.

to sparrez just make sure that the sql server agent service is running on an account that have access to the replication folder.

usually it is a network share.

you can check it in the publication properties-snapshot location

|||

Why does it need to be a network share ? The publishing machine is isolated and not part of a "network", with shares, so to speak. Why won't the default folder be ok?

Also the two servers are in completely different locations so the replication must occur over the internet. With the subscribing machine actually beeing a Domain Controller, but the publishing not beeing a member of a domain a all.

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON

Hello Guys,

I have two machines that i want to use for merge replication :

Laptop ( Publisher + Distributor )

VPS90 ( Subscriber )

Both connected via the internet

NO DOMAIN

Need to implement merge replication ,after initializing the snapshot I get the following error on both machines :

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 192.168.1.1]

I created a new user "Repuser" (admin)with the same password on both machines and configured the Agent proccess to run under that account ,now i get this error :

Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.1]

Please note that :

· Mixed mode authentication IS ENABLED ON BOTH MACHINES

· BOTH MACHINES CAN PING AND ACCESS EACH OTHER ,BOTH COMPLEETELY VISIBLE.

· CONFIGURED ALIASES ON BOTH MACHINES.

· Both configured to use Sa account .

* I have NO DOMAIN

what does this mean?

It simply means that the SQL Server Agent process account is the one that’s being authenticated to connect to the other machine and NOT the Sa account ,WHY?

do i have to use Web Synch in my case?

hi,

replication uses the sql server agent services

your sql services should be running on an account that has

access to replication resources such as the snapshot folder or the replication folder.

the sql server services should be able to access both machine

regards,

joey

|||how can i make the SQL Server Agent account access the other machine ? supposing that i have no domain? please clarify|||Hello?!! Any 1 there?!|||

how are the machine connected in the internet anyway?

are the IPs exposed over the web? Are you using VPN's?

192.168.1.1 seems to be a local IP

anyway...

I think it is not possible to do replication without domain

maybe some other solution would be better in the scenario

like

the SQL SERVER integration services (SSIS)

|||

thanks for the reply joeydj

both machines are exposed to the internet openely ,no VPNs ,first 1 with a static IP (in USA) and the other is via a DSL modem via NAT (thats y u saw 192.168.1.1) ,they can both connect to each other via SQL server Management Studio with out any problems ,i think microsoft made it nearly impossible to do anything with out Domain ,which is really stupid ,as for merge replication (which is my case) ,they are suggesting Web Synchronization if no domain was present ,which is even much harder to configure.

|||

Good Morning (its morning here)!
FINALLY I DID IT!...ITS WORKING NOW..>WOWWWWWWWWW..
well after cleaning up the whole mess and starting over from scratch ,i figured out the following mistake:
i made TWO Aliases on the publisher one for the publisher itself and the other for the subscriber ,the publisher Alias was causing the connection to fail when initializing the snapshot ,thats why i got the error message ,although i could connect to my own machine using that alias ,which make things strange ,but it was causing connection problems with the agent.

|||

Hi

Can you describe your setup a bit more in details, I'm having the exact same problem.

I get no errors other than the Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON error.

The two servers seem to connect just fine, and I can connect to them from sql server managemen studio just fine. But the Snapshot is not created.

On the subscriber machine the only indication that its not working is a message that the replication could not finish because no snapshot exists.

|||

ali_khankan wrote:

Good Morning (its morning here)!
FINALLY I DID IT!...ITS WORKING NOW..>WOWWWWWWWWW..
well after cleaning up the whole mess and starting over from scratch ,i figured out the following mistake:
i made TWO Aliases on the publisher one for the publisher itself and the other for the subscriber ,the publisher Alias was causing the connection to fail when initializing the snapshot ,thats why i got the error message ,although i could connect to my own machine using that alias ,which make things strange ,but it was causing connection problems with the agent.

that's a good news.

to sparrez just make sure that the sql server agent service is running on an account that have access to the replication folder.

usually it is a network share.

you can check it in the publication properties-snapshot location

|||

Why does it need to be a network share ? The publishing machine is isolated and not part of a "network", with shares, so to speak. Why won't the default folder be ok?

Also the two servers are in completely different locations so the replication must occur over the internet. With the subscribing machine actually beeing a Domain Controller, but the publishing not beeing a member of a domain a all.

Login failed for user '(null)'. Reason: Not associated with a trusted SQL server....

Hi guys,

I have a problem:

I have a created a vb.net app.

From this vb.net App (in server A) I connect to the SQL server SP4 (in serverA) and to a SQLServer 2000 SP4 in another server (server B).
All connection are with trusted_connection = true. Server A and B are in a domain.

After pressed a button, (when I run the button I am logged as a domain administrator) some store procedures and table are created in SQL server A and B.

During this phase everything is OK, I mean tables and store procs are installed correctly, and Linked server are installed.

The problem is that:at the end of this job a store aprocedure (in server B) is called form which has a sql statement (SQL select ...inner join from table in different sql server A,B),
the vb.net app show an error:

"System.Data.SQLClient.SqlExcemption: Login failed for user '(null)'. Reason: Not associated with a trusted SQL server connection"

Linked server is:

Local Login: domain\administrator
Impersonate: true
RMUser and Pw are null
Selected: Be made using the login's current security context

SQL server is win + SQL auth mode.

and account: System Account

Do you know how to solve the problem.

I tried to modify option in Linked server but is the same.

I replaced the conn string in vb.net with user and pass and everything work.
So, it looks like that using windows account credential used are lost.

Any help will be very appreciated

For .NET related questions, please see the Data Access forum in the .NET group.

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Hi,
I'm new here guys.
I'm developing a web application that's using a separate component to access data from SQL Server 2000. This component uses DAAB of EL June 2005. This data access component resides on a different server from the database server. I would just like to ask if what's the cause of this error. I wonder why it doesn't get the actual user I'm passing?

"Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
Our database admin had the database server in mixed mode authentication already.
I don't know if this will help but I'll share the contents of my config files.
web.config contains:
<enterpriselibrary.configurationSettings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" applicationName="Application" xmlns="http://www.microsoft.com/practices/enterpriselibrary/08-31-2004/configuration">
<configurationSections>
<configurationSection xsi:type="ReadOnlyConfigurationSectionData" name="dataConfiguration" encrypt="false">
<storageProvider xsi:type="XmlFileStorageProviderData" name="XML File Storage Provider" path="dataConfiguration.config" />
<dataTransformer xsi:type="XmlSerializerTransformerData" name="Xml Serializer Transformer">
<includeTypes />
</dataTransformer>
</configurationSection>
</configurationSections>
<keyAlgorithmStorageProvider xsi:nil="true" />
<includeTypes />
</enterpriselibrary.configurationSettings>

dataconfiguration.config contains
<?xml version="1.0" encoding="utf-8"?>
<dataConfiguration>
<xmlSerializerSection type="Microsoft.Practices.EnterpriseLibrary.Data.Configuration.DatabaseSettings, Microsoft.Practices.EnterpriseLibrary.Data, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null">
<enterpriseLibrary.databaseSettings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" defaultInstance="something" xmlns="http://www.microsoft.com/practices/enterpriselibrary/08-31-2004/data">
<databaseTypes>
<databaseType name="Sql Server" type="Microsoft.Practices.EnterpriseLibrary.Data.Sql.SqlDatabase, Microsoft.Practices.EnterpriseLibrary.Data, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null" />
</databaseTypes>
<instances>
<instance name="something" type="Sql Server" connectionString="something" />
</instances>
<connectionStrings>
<connectionString name="something">
<parameters>
<parameter name="data source" value="dbserver" isSensitive="false" />
<parameter name="initial catalog" value="dbname" isSensitive="false" />
<parameter name="Integrated Security" value="SSPI" isSensitive="false" />
<parameter name="password" value="password" isSensitive="true" />
<parameter name="user id" value="userid" isSensitive="false" />
</parameters>
</connectionString>
</connectionStrings>
</enterpriseLibrary.databaseSettings>
</xmlSerializerSection>
</dataConfiguration>

Also, do I need to create an app.config and another dataconfiguration.config files in my data access component?

Hoping for your replies guys. Thanks in advance!

This KB can help you.

http://support.microsoft.com/default.aspx/kb/307002.

Login & owner of object

Hi Guys,
When I'm creating login and assinging to DBO role it is still creating
object name with login.objectname instead of dbo.object name..
Am I doing anything wrong or I have to do anything else to do this.
Thanks
- NT
Hi NT
There is no DBO role.
There is a user DBO and role called db_owner. Although the DBO user is in
the db_owner, other users can be in the db_owner role as well.
Every login has a user name in every database. User names can be members of
database roles.
When using Query Analyzer you can see the current user's name by running
this command:
SELECT user_name()
Only the user DBO will have all the objects she creates owned by DBO, by
default. However, a user in the db_owner role may create objects owned by
the DBO user, if the owner is stated explicitly:
CREATE TABLE dbo.new_table
(col1 ...
col2...
)
etc.
Please read about users and database roles in the Books Online for more
information.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"NT" <NT@.discussions.microsoft.com> wrote in message
news:205A1292-BCEE-467F-99BA-D1856C81737F@.microsoft.com...
> Hi Guys,
> When I'm creating login and assinging to DBO role it is still creating
> object name with login.objectname instead of dbo.object name..
> Am I doing anything wrong or I have to do anything else to do this.
> Thanks
>
> - NT

Login & owner of object

Hi Guys,
When I'm creating login and assinging to DBO role it is still creating
object name with login.objectname instead of dbo.object name..
Am I doing anything wrong or I have to do anything else to do this.
Thanks
- NTHi NT
There is no DBO role.
There is a user DBO and role called db_owner. Although the DBO user is in
the db_owner, other users can be in the db_owner role as well.
Every login has a user name in every database. User names can be members of
database roles.
When using Query Analyzer you can see the current user's name by running
this command:
SELECT user_name()
Only the user DBO will have all the objects she creates owned by DBO, by
default. However, a user in the db_owner role may create objects owned by
the DBO user, if the owner is stated explicitly:
CREATE TABLE dbo.new_table
(col1 ...
col2...
)
etc.
Please read about users and database roles in the Books Online for more
information.
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"NT" <NT@.discussions.microsoft.com> wrote in message
news:205A1292-BCEE-467F-99BA-D1856C81737F@.microsoft.com...
> Hi Guys,
> When I'm creating login and assinging to DBO role it is still creating
> object name with login.objectname instead of dbo.object name..
> Am I doing anything wrong or I have to do anything else to do this.
> Thanks
>
> - NT

Login & owner of object

Hi Guys,
When I'm creating login and assinging to DBO role it is still creating
object name with login.objectname instead of dbo.object name..
Am I doing anything wrong or I have to do anything else to do this.
Thanks
- NTHi NT
There is no DBO role.
There is a user DBO and role called db_owner. Although the DBO user is in
the db_owner, other users can be in the db_owner role as well.
Every login has a user name in every database. User names can be members of
database roles.
When using Query Analyzer you can see the current user's name by running
this command:
SELECT user_name()
Only the user DBO will have all the objects she creates owned by DBO, by
default. However, a user in the db_owner role may create objects owned by
the DBO user, if the owner is stated explicitly:
CREATE TABLE dbo.new_table
(col1 ...
col2...
)
etc.
Please read about users and database roles in the Books Online for more
information.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"NT" <NT@.discussions.microsoft.com> wrote in message
news:205A1292-BCEE-467F-99BA-D1856C81737F@.microsoft.com...
> Hi Guys,
> When I'm creating login and assinging to DBO role it is still creating
> object name with login.objectname instead of dbo.object name..
> Am I doing anything wrong or I have to do anything else to do this.
> Thanks
>
> - NT

Logic in format?

Hello,
This might be a simple questions for you guys.
Can you put logic withing the format of each cell; for example if i have a
number column and i want all numbers > 0 to be red and numbers<=0 to be blue.
Can this be done?
Thanks.Click on your field and go to properties box Go to properties box. Find color
property and and in the drop down box select <expression>. Use an IIF clause
in place of black. IE:
=IIF(Fields!fieldname.value <= 0,"Blue","Red")
"Ash" wrote:
> Hello,
> This might be a simple questions for you guys.
> Can you put logic withing the format of each cell; for example if i have a
> number column and i want all numbers > 0 to be red and numbers<=0 to be blue.
> Can this be done?
> Thanks.|||Actually you can code for most of the field properties. If your report is
going to be printed and you only have a black laser, changing the font to
bold makes it stand out. I had this issue come up earlier today.|||Do you do that in the one click report builder (that you can launch from the
web) or from within the VS2005 editor?
because i tried it from the report builder and when i right click a field i
get 'Format', 'Edit Formula' and 'Delete' only.
I think i'm missing somthing..
"William" wrote:
> Actually you can code for most of the field properties. If your report is
> going to be printed and you only have a black laser, changing the font to
> bold makes it stand out. I had this issue come up earlier today.|||I was describing the process in RS designing in the MSDE designer within VS
.Net 2003. I know there is a Report Builder in 2005, but I have not tried
it yet.