Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
influent
Constraint Violating Yak Guru
367 Posts |
 Posted - 2012-01-31 : 15:21:26
|
| I'm posting this to help people but I also am confused by it so I'm looking for some enlightenment. I had a linked server set up on my old reporting SQL server and it was working fine. I migrated to a new reporting server and set up the linked server with the exact same settings, which worked when I ran queries in Mgmt Studio but when I executed the report containing the same query from the SSRS Report Manager it said: System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. I was using SQL Server for the linked server type and using "Be made using this security context." I don't know why anything would have changed regarding NTLM vs Kerberos, if that's the problem, but I was able to fix it by copying the SQL login's username and password into the Remote User and Remote Password boxes at the top of the linked server setup screen (Security tab). Why did that work? Did something change because the new server is part of a failover cluster? |
|
|
|
|
|
linked server funkiness