August 19, 2008 at 11:09 pm
Hello
We are running a SQL Server 2005 instance on SBS 2003. One computer (and only one computer) in the network tries to log into a specific database (WinNT authentication) on the server and the error 'cannot generate an SSPI Context' appears. Sometimes the user can get in a little while, but eventually the error will reappear!! I have tried several fixes from KB articles on the Web, mainly related to DNS caching but none of these persist.
The user has all the appropriate permissions for both the server instance and the network so I am totally baffled. Hoping one of you DBA's may have an answer and thanking you in advance 🙂
Richard
August 20, 2008 at 6:32 am
do the sql services start as local system or a user account.
we had this recently on one of our clients, i re registered all the SPN's for the 8 sql instances and it was ok after that
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 20, 2008 at 6:46 am
Dear Richard
Check Whether Named pipes is enabled on both server and Client.
Do check the following KB
http://support.microsoft.com/kb/909801
Restarting the server will fix the issue temporarily
Thanks
Kokila K
August 20, 2008 at 9:41 am
did you ever change the server name? make sure to delete the old one
August 20, 2008 at 9:53 pm
Thank you all for your responses :D. I found I was able to default to using Named Pipes on that client rather than TCP/IP and all appears OK so far.
Regards
Richard
August 21, 2008 at 4:11 am
a sticky plaster rather than a cure. TCP/IP is more secure, check the SPN's i'm sure they'll be the source of your problem. Do the sql services run as a user account or local system?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 21, 2008 at 5:08 am
Hi Perry
SQL runs as LocalSystem on the server. Unfortunately too, the database the user has tried unsuccessfully (for the most part) to access forms the backend for our accounting application, and is actually our company accounts so I had to come up with a solution pronto!! Other users of the database use Named Pipes without incident so I thought this was the most logical check. The user has been able to run the database for several hours today without incident, something which has been impossible for the past fortnight!
Once again, thanks so much for your help, I'm sure I will have more queries to post to this site as I am a bit of a newbie to SQL administration, I usually am involved in .NET development, T-SQL etc.
Regards
Richard
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply