If you have worked on SQL Server migration then its likely that you have come across this error message.I recently migrated a server from SQL Server 2005 to SQL Server 2008.Everything seemed to go well except that I started seeing this error message in the SQL Server Log,Event viewer.
After searching the internet for the causes and trying the fixes, the issue wasn't fixed.Some of the checks I did were to recreate the SPN's,Set the DisableLoopbackCheck registry entry to 1 (Note this fix worked for another server) ,verify NTLM or KERBEROS authentication and so on.
So I decided to contact our DBA and it took 5 minutes to figure out the issue.
First thing was to figure out the offending application.So he ran a trace on Audit Login Events in SQL Profiler
The account to connect to the report server was not configured correctly and that was causing the error.Once the Report Server was configured the error disappeared.
Open Report Server Configuration Manager
Configure Report Server Service Account and provide the correct credentials
The trace now correctly shows that the account login was successful.
SQL Profiler Rocks !!! Hope this helps.
After searching the internet for the causes and trying the fixes, the issue wasn't fixed.Some of the checks I did were to recreate the SPN's,Set the DisableLoopbackCheck registry entry to 1 (Note this fix worked for another server) ,verify NTLM or KERBEROS authentication and so on.
So I decided to contact our DBA and it took 5 minutes to figure out the issue.
First thing was to figure out the offending application.So he ran a trace on Audit Login Events in SQL Profiler
The account to connect to the report server was not configured correctly and that was causing the error.Once the Report Server was configured the error disappeared.
Open Report Server Configuration Manager
Configure Report Server Service Account and provide the correct credentials
Restart the Report Server and now SQL Server Log does not show the SSPI handshake failed error
No comments:
Post a Comment