Login failed for user 'NT Authority\Anonymous

I have a Merge Replication configuration in which one Publisher replicates
with 20 subscribers.
Currently, we use Windows Integrated security.
I get the following error when attempting to access tables in a remote
server from the publisher.
In Query Analyzer window, logged into publisher, I type
SELECT * FROM <subscriber1>.<databasename>..<tablename>
And get the following error message:
Login failed for user 'NTAUTHORITY\ANONYMOUS LOGON'
1) From everything I’ve read, including article 827422, it is necessary to
go to Mixed Security in order to overcome this security issue. Is this true?
2) Will changing the security mode on the Publisher and all 20 subscribers
cause any problems with replication?1) That's a major over-generalization to say that changing it to SQL
Authentication (Mixed Mode) will allow you to over come this. It's working
around the issue entirely. You will still have issues with Windows
authentication, and should deal with those.
When you set up the merge subscribers, are they anonymous? Did you specify
for the merge agent to connect to the subscriber (if push) or publisher (if
pull) under the credentials of the SQL Agent account? What is that account?
Can you log onto each server (pub and sub) as their respective SQL Agent
accounts, then try to open Query Analyzer and point to the other server usin
g
windows authentication? Do you get the same "Anonymous error"? Are they th
e
same account? If not, are they in the same domain? Make sure they both have
the correct rights to each other's machine. If not in the same domain, you
need to look at trust issues. If there is no trust, then you will either
have to set one up, or use mixed mode and SQL accounts.
2) No, unless you consider the time to restart SQL an issue.
Donna Lambert
"elpepe" wrote:

> I have a Merge Replication configuration in which one Publisher replicates
> with 20 subscribers.
> Currently, we use Windows Integrated security.
> I get the following error when attempting to access tables in a remote
> server from the publisher.
> In Query Analyzer window, logged into publisher, I type
> SELECT * FROM <subscriber1>.<databasename>..<tablename>
> And get the following error message:
> Login failed for user 'NTAUTHORITY\ANONYMOUS LOGON'
> 1) From everything I’ve read, including article 827422, it is necessary
to
> go to Mixed Security in order to overcome this security issue. Is this tru
e?
> 2) Will changing the security mode on the Publisher and all 20 subscribers
> cause any problems with replication?
>
>

Login error after automatic failover

I have setup a mirror configuration with a witness to be able to use the automatic failover. The principal is DBSP01, the mirror is DBSP02 and the witness is DBSP03. I have an application running an DBCP01. When the mirroring is working, the application can connect to the database on DBSP01. I disconnect dbsp01 from the network, so that DBSP02 becomes the principal. When I try to connect the application to the database on DBSP02, the login fails. Whithout the mirroring I was able to logon to DBSP02, but as soon as it is part of the mirroring, I'm not able to connect to it anymore, whatever the state of the database is. What could be the problem? Can anybody help?

Remco

I hope you are running with safety FULL. Please confirm.

Before you disconnect DBSP01, what is the status of the DBM session? is it SYNCHRONIZED?

After you disconnect DBSP01, are you sure the failover is taking place, and the database DBSP02 has become principal? Please check the role and status.

|||

I found the problem. The services of SQL were not running under the same accounts on the different boxes. One service was running under local account, while the same service was running under the network service account on the other box. When I changed it, it works properly.

Thanks

logging server configuration changes

Hi,
Does anyone know if SQL Server 2000 sp3a log server configuration
changes. I am acting as a dba for a client and the old DBA added Named
Pipes as a protocol to a production database without following
protocol.
My supervisor wants me to track down when this was done. I am not sure
if it even possible unless the change is logged somehow. I checked the
SQL server logs but there seems to be no entry.
Can someone point me in the right direction or at least verify that
this change was never logged.
Thanks
Mike.Hi
There is no specific logging of these events, you may want to check the SQL
Server log and the Windows Event Log for Names pipes starting, although if
this was done some time ago the original change may not be there. SQL 2005
logs Event ids 26028 and 26048 in the Windows Application Event log when
named pipes are started.
John
"MD" <miked1119@.gmail.com> wrote in message
news:1145301860.104228.88070@.e56g2000cwe.googlegroups.com...
> Hi,
> Does anyone know if SQL Server 2000 sp3a log server configuration
> changes. I am acting as a dba for a client and the old DBA added Named
> Pipes as a protocol to a production database without following
> protocol.
> My supervisor wants me to track down when this was done. I am not sure
> if it even possible unless the change is logged somehow. I checked the
> SQL server logs but there seems to be no entry.
> Can someone point me in the right direction or at least verify that
> this change was never logged.
> Thanks
> Mike.
>|||If you have the backp of old SQL Server log files may be you can find the
following entry:
SQL server listening on TCP, Shared Memory, Named Pipes.
This part in the error log indicates what all protocols have enabled for the
SQL Server.
jAj
"MD" <miked1119@.gmail.com> wrote in message
news:1145301860.104228.88070@.e56g2000cwe.googlegroups.com...
> Hi,
> Does anyone know if SQL Server 2000 sp3a log server configuration
> changes. I am acting as a dba for a client and the old DBA added Named
> Pipes as a protocol to a production database without following
> protocol.
> My supervisor wants me to track down when this was done. I am not sure
> if it even possible unless the change is logged somehow. I checked the
> SQL server logs but there seems to be no entry.
> Can someone point me in the right direction or at least verify that
> this change was never logged.
> Thanks
> Mike.
>

logging server configuration changes

Hi,
Does anyone know if SQL Server 2000 sp3a log server configuration
changes. I am acting as a dba for a client and the old DBA added Named
Pipes as a protocol to a production database without following
protocol.
My supervisor wants me to track down when this was done. I am not sure
if it even possible unless the change is logged somehow. I checked the
SQL server logs but there seems to be no entry.
Can someone point me in the right direction or at least verify that
this change was never logged.
Thanks
Mike.Hi
There is no specific logging of these events, you may want to check the SQL
Server log and the Windows Event Log for Names pipes starting, although if
this was done some time ago the original change may not be there. SQL 2005
logs Event ids 26028 and 26048 in the Windows Application Event log when
named pipes are started.
John
"MD" <miked1119@.gmail.com> wrote in message
news:1145301860.104228.88070@.e56g2000cwe.googlegroups.com...
> Hi,
> Does anyone know if SQL Server 2000 sp3a log server configuration
> changes. I am acting as a dba for a client and the old DBA added Named
> Pipes as a protocol to a production database without following
> protocol.
> My supervisor wants me to track down when this was done. I am not sure
> if it even possible unless the change is logged somehow. I checked the
> SQL server logs but there seems to be no entry.
> Can someone point me in the right direction or at least verify that
> this change was never logged.
> Thanks
> Mike.
>|||If you have the backp of old SQL Server log files may be you can find the
following entry:
SQL server listening on TCP, Shared Memory, Named Pipes.
This part in the error log indicates what all protocols have enabled for the
SQL Server.
jAj
"MD" <miked1119@.gmail.com> wrote in message
news:1145301860.104228.88070@.e56g2000cwe.googlegroups.com...
> Hi,
> Does anyone know if SQL Server 2000 sp3a log server configuration
> changes. I am acting as a dba for a client and the old DBA added Named
> Pipes as a protocol to a production database without following
> protocol.
> My supervisor wants me to track down when this was done. I am not sure
> if it even possible unless the change is logged somehow. I checked the
> SQL server logs but there seems to be no entry.
> Can someone point me in the right direction or at least verify that
> this change was never logged.
> Thanks
> Mike.
>