Sunday, March 11, 2012

Error 53, Cannot generate SSPI Context

SQLserveragent service for SQL2K does not start and returns the following er
ror in the agent out file.
Error 53, Cannot generate SSPI Context
We have researched this error on Microsoft and several news groups and none
of the stuff we read seems to work.
We CAN connect to the DB using the full DNS name or IP. But when trying to
use (local), the error appears. It just seems like SQL/Windows lost how to
find or resolve (local).
How does (local) work? This is happening on two servers in the same Active
Directory Win2k server domain. Could it be a domain level policy that is go
ofed?
Thanks for any help.'local' used to mean a local pipe as opposed to a Named Pipe. With 2000 we
use Shared Memory.
Check the servername to make sure it is right. Run sp_helpserver and
review the results
the netbios name should have an id of 0 (zero).
Also check the registry on the server itself to make sure the default
netlib is set to DBNETLIB
There should be no aliases for (local) as well.
Check this key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\Client\ConnectTo
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

No comments:

Post a Comment