SQLserveragent service for SQL2K does not start and returns the following
error in the agent out file.
Error 53, Cannot generate SSPI Context
The agent was working until last week.
We have researched this error on Microsoft knowldge base 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
goofed?
Thanks for any help.
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.
|||need to try to connect to sqlagent using sa account and password. you can do
that with the
sqlagen manager, change authentication and ener account and password, then
restart sqlserver agent. (there is a known kba for this problem sorry I
cannot find it now)
I will then suggest re-booting the server.
I vaguely remember it being something to do with the sqlagent service
accounts not being able to communicate with the domain controller and there
fore not being authenticated,causing the error.
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.
|||Hi Kenwu,
Look at this kbs:
http://support.microsoft.com/?id=814401
http://support.microsoft.com/?id=811889
http://dotnetjunkies.com/WebLog/pete...2/25/7897.aspx
Good Luck !
Rodrigo Fernandes
MCSE/MCDBA
"kenwu" wrote:
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.
|||What changes you did last week?
Regards,
Daniel
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.
Showing posts with label context. Show all posts
Showing posts with label context. Show all posts
Sunday, March 11, 2012
Error 53: Cannot generate SSPI Context
Error 53: Cannot generate SSPI Context
SQLserveragent service for SQL2K does not start and returns the following
error in the agent out file.
Error 53, Cannot generate SSPI Context
The agent was working until last week.
We have researched this error on Microsoft knowldge base 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
goofed?
Thanks for any help."kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.|||need to try to connect to sqlagent using sa account and password. you can do
that with the
sqlagen manager, change authentication and ener account and password, then
restart sqlserver agent. (there is a known kba for this problem sorry I
cannot find it now)
I will then suggest re-booting the server.
I vaguely remember it being something to do with the sqlagent service
accounts not being able to communicate with the domain controller and there
fore not being authenticated,causing the error.
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.|||Hi Kenwu,
Look at this kbs:
http://support.microsoft.com/?id=814401
http://support.microsoft.com/?id=811889
http://dotnetjunkies.com/WebLog/pet...02/25/7897.aspx
Good Luck !
Rodrigo Fernandes
MCSE/MCDBA
"kenwu" wrote:
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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 t
o
> use (local), the error appears. It just seems like SQL/Windows lost how t
o
> find or resolve (local).
> How does (local) work? This is happening on two servers in the same Activ
e
> Directory Win2k server domain. Could it be a domain level policy that is
> goofed?
> Thanks for any help.|||What changes you did last week?
Regards,
Daniel
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.
error in the agent out file.
Error 53, Cannot generate SSPI Context
The agent was working until last week.
We have researched this error on Microsoft knowldge base 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
goofed?
Thanks for any help."kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.|||need to try to connect to sqlagent using sa account and password. you can do
that with the
sqlagen manager, change authentication and ener account and password, then
restart sqlserver agent. (there is a known kba for this problem sorry I
cannot find it now)
I will then suggest re-booting the server.
I vaguely remember it being something to do with the sqlagent service
accounts not being able to communicate with the domain controller and there
fore not being authenticated,causing the error.
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.|||Hi Kenwu,
Look at this kbs:
http://support.microsoft.com/?id=814401
http://support.microsoft.com/?id=811889
http://dotnetjunkies.com/WebLog/pet...02/25/7897.aspx
Good Luck !
Rodrigo Fernandes
MCSE/MCDBA
"kenwu" wrote:
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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 t
o
> use (local), the error appears. It just seems like SQL/Windows lost how t
o
> find or resolve (local).
> How does (local) work? This is happening on two servers in the same Activ
e
> Directory Win2k server domain. Could it be a domain level policy that is
> goofed?
> Thanks for any help.|||What changes you did last week?
Regards,
Daniel
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.
Error 53: Cannot generate SSPI Context
SQLserveragent service for SQL2K does not start and returns the following
error in the agent out file.
Error 53, Cannot generate SSPI Context
The agent was working until last week.
We have researched this error on Microsoft knowldge base 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
goofed?
Thanks for any help."kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.|||need to try to connect to sqlagent using sa account and password. you can do
that with the
sqlagen manager, change authentication and ener account and password, then
restart sqlserver agent. (there is a known kba for this problem sorry I
cannot find it now)
I will then suggest re-booting the server.
I vaguely remember it being something to do with the sqlagent service
accounts not being able to communicate with the domain controller and there
fore not being authenticated,causing the error.
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.|||Hi Kenwu,
Look at this kbs:
http://support.microsoft.com/?id=814401
http://support.microsoft.com/?id=811889
http://dotnetjunkies.com/WebLog/petergekko/archive/2004/02/25/7897.aspx
Good Luck !
Rodrigo Fernandes
MCSE/MCDBA
"kenwu" wrote:
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.|||What changes you did last week?
Regards,
Daniel
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.
error in the agent out file.
Error 53, Cannot generate SSPI Context
The agent was working until last week.
We have researched this error on Microsoft knowldge base 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
goofed?
Thanks for any help."kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.|||need to try to connect to sqlagent using sa account and password. you can do
that with the
sqlagen manager, change authentication and ener account and password, then
restart sqlserver agent. (there is a known kba for this problem sorry I
cannot find it now)
I will then suggest re-booting the server.
I vaguely remember it being something to do with the sqlagent service
accounts not being able to communicate with the domain controller and there
fore not being authenticated,causing the error.
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.|||Hi Kenwu,
Look at this kbs:
http://support.microsoft.com/?id=814401
http://support.microsoft.com/?id=811889
http://dotnetjunkies.com/WebLog/petergekko/archive/2004/02/25/7897.aspx
Good Luck !
Rodrigo Fernandes
MCSE/MCDBA
"kenwu" wrote:
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.|||What changes you did last week?
Regards,
Daniel
"kenwu" <kenwu@.discussions.microsoft.com> wrote in message
news:61B5A8F9-AB41-4192-80D6-F9B96224DBF4@.microsoft.com...
> SQLserveragent service for SQL2K does not start and returns the following
> error in the agent out file.
> Error 53, Cannot generate SSPI Context
> The agent was working until last week.
> We have researched this error on Microsoft knowldge base 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
> goofed?
> Thanks for any help.
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.
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.
Subscribe to:
Posts (Atom)