Cannot Generate SSPI Context

[Bill]

I have an adp that just up and quit for no apparent reason the other
day. All of a sudden I am getting the following error, "Cannot Generate
SSPI Context." I found out that the network admins changed the password
for the useraccount that the SQLServer Service and Agent use. They did
change the account on the services startup too but not until later on.
The server has not been rebooted yet and I can't do that until tonight.
I kind of suspect that it might be a case of the password change but
here's the catch which makes me second guess that. Everyone that runs
XP Pro cannot get onto it. But those that connect through a Citrix
server, which is hosted on Win2k Server, can connect without problem.
And if the XP clients are in it, they can stay in it and work fine, but
if they leave, they can't reconnect.

If I make a brand new adp and go to the connection menu I can select the
server, select the integrated windows authentication and then when I go
to choose the database I want to connect to via the drop down, I get the
same error with a second error, "Login Failed. Catalog information
cannot be retrieved." I've also tried admin accounts and I get the same
error. If I instead just type in the name in the combo box for which
database I want and then click on test connection I get the error, "Test
connection failed because of an error initializing the provider."
Anyone have any thoughts on what could cause this, will a reboot tonight
simply fix this?

Thanks,
Bill

 

[Vadim Rapp]

B> I have an adp that just up and quit for no apparent reason the other
B> day. All of a sudden I am getting the following error, "Cannot Generate
B> SSPI Context."

Search for this exact phrase on support.microsoft.com , also on google -
there's quite a number of results, hopefully some will help.

Vadim

 

[Bill]

Oh boy, did I ever search with that phrase. The funny thing is, not one
of the answers I found suggested what actually needed to be done, reboot
the server. Which has always been the first rule of computing in my
book especially when dealing with MS products (but which I couldn't do
in the middle of the day). So the lesson learned here is, if you change
a password for the service account that SQL is running under, reboot the
server so that stuff will work again. I guess a caveat would be, don't
change the password unless you can reboot the server immediately.

Thanks,
Bill

 

[Peter Kaufman]

Probably if you just logged off and on again it would have
accomplished the same thing.

Peter