Cannot Generate SSPI Context

hi @.all,
when rebooting the sbs 2k3 server, first the service sqlagent$sbsmonitoring
failes to start and then the sqlserveragent. both events are record with the
event id 103:
sqlagent$sbsmonitoring:
SQLServerAgent could not be started (reason: Unable to connect to server
"(sbs\sbsmonitoring)"; SQLServerAgent
cannot start).
sqlserveragent:
SQLServerAgent could not be started (reason: Unable to connect to server
"(local)"; SQLServerAgent
cannot start).
after searching the web i found an articel describing to look for the
sqlagent.out file. i found two files in "microsoft sql server\mssql\log" and
"microsoft sql server\mssql$sbsmonitoring". both have the error "Cannot
Generate SSPI Context".
when i start the services manually it works fine, but NOT on startup... i
even searched the kb from ms, but didn′t find anything that helped me.
even if i set the services to start over if an error occure, it doesn′t
work. only if i start the services manually...
the services are set to start with the local system account.
i don′t have any knowledge from a sql server. can somebody please help me!
kind regards / liebe grüsse
dominique
Hi
This sounds like it can not authenticate the service account in the AD, have
you tried setting it to the system account or to a different domain one?
John
"dominique" wrote:

> hi @.all,
> when rebooting the sbs 2k3 server, first the service sqlagent$sbsmonitoring
> failes to start and then the sqlserveragent. both events are record with the
> event id 103:
> sqlagent$sbsmonitoring:
> SQLServerAgent could not be started (reason: Unable to connect to server
> "(sbs\sbsmonitoring)"; SQLServerAgent
> cannot start).
> sqlserveragent:
> SQLServerAgent could not be started (reason: Unable to connect to server
> "(local)"; SQLServerAgent
> cannot start).
> after searching the web i found an articel describing to look for the
> sqlagent.out file. i found two files in "microsoft sql server\mssql\log" and
> "microsoft sql server\mssql$sbsmonitoring". both have the error "Cannot
> Generate SSPI Context".
> when i start the services manually it works fine, but NOT on startup... i
> even searched the kb from ms, but didn′t find anything that helped me.
> even if i set the services to start over if an error occure, it doesn′t
> work. only if i start the services manually...
> the services are set to start with the local system account.
> i don′t have any knowledge from a sql server. can somebody please help me!
> --
> kind regards / liebe grüsse
> dominique
|||hi john,
first of all, thank you for your answer.
i′m using the system account all the time.
i just tried your suggestion using a domain account for starting the two
services and rebooted the server. now the events 103 are gone, but i′m
getting two events 7000 service control manager:
(translation from german)
the "SQLAgent$SBSMONITORING" / "SQLSERVERAGENT" service failed to start due
to the following error:
the accountname is incorrect or not existent, or the password for the
accountname is incorrect.
the account is a domain-admin account.
when i tried to start the service manually it was successfull again... ://
i don′t understand it...
any ideas?
kind regards / liebe grüsse
dominique
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This sounds like it can not authenticate the service account in the AD, have
> you tried setting it to the system account or to a different domain one?
> John
> "dominique" wrote:
|||Hi
Is this only happening occuring when you reboot the server, or when you
stop/start SQL Server once the server is running?
John
"dominique" wrote:
[vbcol=seagreen]
> hi john,
> first of all, thank you for your answer.
> i′m using the system account all the time.
> i just tried your suggestion using a domain account for starting the two
> services and rebooted the server. now the events 103 are gone, but i′m
> getting two events 7000 service control manager:
> (translation from german)
> the "SQLAgent$SBSMONITORING" / "SQLSERVERAGENT" service failed to start due
> to the following error:
> the accountname is incorrect or not existent, or the password for the
> accountname is incorrect.
> the account is a domain-admin account.
> when i tried to start the service manually it was successfull again... ://
> i don′t understand it...
> any ideas?
> --
> kind regards / liebe grüsse
> dominique
>
> "John Bell" wrote:
|||hi,
no only on reboot, that′s why it′s so strange...
i just tested it again. when i stop the sql server the sqlserveragent is
stopping too. when i start the sql server i′m able to start the
sqlserveragent (right now with the domain account). but i′m able to start the
sqlserveragent with the system account too.
only on reboot / startup the services are not starting with the below events.
i′m desperate
kind regards / liebe grüsse
dominique
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Is this only happening occuring when you reboot the server, or when you
> stop/start SQL Server once the server is running?
> John
> "dominique" wrote:
|||Hi dominique
If this is only on re-boot then it sounds like SQL Server service is
starting too early. You may want to check to see if the network services are
taking too long to start or possibly there may be a problem with the network
card. If you can make SQLServer dependent another service (say computer
browser) then it may delay things for long enough. If you have a software
firewall running, check to see how long this takes to start up.
John
"dominique" wrote:
[vbcol=seagreen]
> hi,
> no only on reboot, that′s why it′s so strange...
> i just tested it again. when i stop the sql server the sqlserveragent is
> stopping too. when i start the sql server i′m able to start the
> sqlserveragent (right now with the domain account). but i′m able to start the
> sqlserveragent with the system account too.
> only on reboot / startup the services are not starting with the below events.
> i′m desperate
> --
> kind regards / liebe grüsse
> dominique
>
> "John Bell" wrote:
|||hi john,
thanks for trying to resolve my problem, i really apreciate this )
hm... is the sql server service starting too early or too late? remember the
event:
could not be started (reason: Unable to connect to server "(local)";
SQLServerAgent
how can i check to see if the network services are taking too long to start?
the network card is working fine, no problems or events here.
the server needs a pretty long time to boot, but it is a sbs, so he′s got a
lot of work to do, when booting :/ i thought this is "normal".
how can i make the SQLServer dependent on another service?
i don′t have any software firewall running... isa is running only as a proxy.
kind regards / liebe grüsse
dominique
"John Bell" wrote:
[vbcol=seagreen]
> Hi dominique
> If this is only on re-boot then it sounds like SQL Server service is
> starting too early. You may want to check to see if the network services are
> taking too long to start or possibly there may be a problem with the network
> card. If you can make SQLServer dependent another service (say computer
> browser) then it may delay things for long enough. If you have a software
> firewall running, check to see how long this takes to start up.
> John
> "dominique" wrote:
|||Hi
Make sure that the SQLServerAgent service is dependent on the SQL
Server service in the Services Applet.
Also you may want to check out http://support.microsoft.com/kb/811889/
"Cannot Generate SSPI Context" is an issue authenticating the service
account with AD not SQL Server, but as this seems to work once you are
allowed to log in, it would indicate that either something has started
at the time the service wishes to authenticate or something is stopping
the authentication happening, which is resolved by the time you can log
in.
John
dominique wrote:
> hi john,
> thanks for trying to resolve my problem, i really apreciate this )
> hm... is the sql server service starting too early or too late? remember =
the
> event:
> could not be started (reason: Unable to connect to server "(local)";
> SQLServerAgent
> how can i check to see if the network services are taking too long to sta=
rt?
> the network card is working fine, no problems or events here.
> the server needs a pretty long time to boot, but it is a sbs, so he=B4s g=
ot a
> lot of work to do, when booting :/ i thought this is "normal".
> how can i make the SQLServer dependent on another service?
> i don=B4t have any software firewall running... isa is running only as a =
proxy.[vbcol=seagreen]
> --
> kind regards / liebe gr=FCsse
> dominique
>
> "John Bell" wrote:
s are[vbcol=seagreen]
twork[vbcol=seagreen]
re[vbcol=seagreen]
is[vbcol=seagreen]
start the[vbcol=seagreen]
events.[vbcol=seagreen]
you[vbcol=seagreen]
the two[vbcol=seagreen]
t i=B4m[vbcol=seagreen]
start due[vbcol=seagreen]
the[vbcol=seagreen]
in... ://[vbcol=seagreen]
the AD, have[vbcol=seagreen]
main one?[vbcol=seagreen]
$sbsmonitoring[vbcol=seagreen]
record with the[vbcol=seagreen]
t to server[vbcol=seagreen]
t to server[vbcol=seagreen]
for the[vbcol=seagreen]
\mssql\log" and[vbcol=seagreen]
or "Cannot[vbcol=seagreen]
startup... i[vbcol=seagreen]
helped me.[vbcol=seagreen]
it doesn=B4t[vbcol=seagreen]
please help me![vbcol=seagreen]
|||hi john,
i tried the following now:
after reading the kb i changed the authentification for the sqlserveragent
(local) to sql authentification and that worked!
now the sqlserveragent (local) is starting, but i′m still getting the event
103 on sqlagent$sbsmonitoring. i changed the authentification for the
sqlserveragent too, but that didn′t worked. i′m only able to start the
sqlserveragent when windows authentification is enabled...
any other suggestions? ://
kind regards / liebe grüsse
dominique
"John Bell" wrote:

> Hi
> Make sure that the SQLServerAgent service is dependent on the SQL
> Server service in the Services Applet.
> Also you may want to check out http://support.microsoft.com/kb/811889/
> "Cannot Generate SSPI Context" is an issue authenticating the service
> account with AD not SQL Server, but as this seems to work once you are
> allowed to log in, it would indicate that either something has started
> at the time the service wishes to authenticate or something is stopping
> the authentication happening, which is resolved by the time you can log
> in.
> John
> dominique wrote:
>