August 3, 2009 at 10:15 am
Background:
We built a server to replace 'ServerA' a production server, while we were getting 'ServerB' ready we had it on the domain. We could connect to the server using Window Auth. with no problem.
To do the production switch we took 'ServerB' and renamed it to 'ServerA'. We then did the sp_dropserver and sp_addserver name changes for SQL Server that worked and I can connect to the server with the sa account.
I am guessing that something more needs to be done to allow the windows groups that are created during the SQL Server install to talk to the DNS server?
The error I am getting when trying to connect with my domain account:
Cannot generate SSPI context. (.Net SqlClient Data Provider)
Any suggestions would be helpful.
August 3, 2009 at 10:33 am
SQL_Easy_btn? (8/3/2009)
Background:We built a server to replace 'ServerA' a production server, while we were getting 'ServerB' ready we had it on the domain. We could connect to the server using Window Auth. with no problem.
To do the production switch we took 'ServerB' and renamed it to 'ServerA'. We then did the sp_dropserver and sp_addserver name changes for SQL Server that worked and I can connect to the server with the sa account.
I am guessing that something more needs to be done to allow the windows groups that are created during the SQL Server install to talk to the DNS server?
The error I am getting when trying to connect with my domain account:
Cannot generate SSPI context. (.Net SqlClient Data Provider)
Any suggestions would be helpful.
These site look like they may be helpful to you:
http://sqlblogcasts.com/blogs/grumpyolddba/archive/2008/07/19/cannot-generate-sspi-context.aspx
http://www.sqlservercentral.com/articles/Installation/cannotgeneratesspicontext/929/
August 3, 2009 at 11:49 am
Check the SPN records that were created - you probably need to remove the old ones and create new ones that point to the correct server instance.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 4, 2009 at 10:35 am
For more information:
There are two other instances on this server (3 total), both of which I have no problem connecting.
I had just come across the kb article that pointed out the SPN numbers which are generated when the SQL Server starts and was going to look into that next. But, what I dont see is how to view what the current SPN number is.
August 4, 2009 at 10:41 am
It is not an SPN number - SPN stands for Service Principal Name and is a DNS type of entry. You need to download and install the SetSPN utility that comes with the Admin Kit for Windows 2003.
Using the SetSPN utility from the command line, you would do the following:
C:\SetSPN.exe -L {account}
If you have a Windows Server 2008 box, you can log into that machine, launch Powershell and run the following:
PS> SetSPN -Q MSSqlSvc/{server name}*
Where {server name} is a prefix for the servers you want to find.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply