Cannot find mdf files: sbs

Showing posts with label sbs. Show all posts

Sunday, March 25, 2012

Cannot rebuild full text catalogs

Recently moved database and full text catalogs to new server with SQL Server
2000 sp3a/SBS 2003 sp1
I am having problems rebuilding and repopulating the fulltext catalogs
restored to the new server.
The message I encounter is "Error 7635: The Microsoft Search cannot be
administered under the present user account".
I understand from the link I have been referred to
"http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states that
the service logon was changed through the control panel instead of the
Enterprise Manager therefore the service login for SQL Server does not have
administrative priviledges over the MSSearch service.
None of the service logins were changed through the control panel
I have tried the workround as suggested in the link but I still get the same
error message when I try to rebuild the full text catalog.
Any of you MVP's with another approach or suggestions to solve this problem?What account is MSSearch running under? It must be running under the local
system account. If it is not change it, you can change it through the
services applet in Control panel - Administrative Tasks.
Check that the builtin\Admins group is in the sysadmin role, and if not do
the following
use master
go
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
goThen change the SQL Server account to a the local system account in
Enterprise manger, right click on it and select properties and then select
the security tab and make the modifcation here, bounce it and the repeat the
process to have it run under a local adminstrators account.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> Recently moved database and full text catalogs to new server with SQL
> Server
> 2000 sp3a/SBS 2003 sp1
> I am having problems rebuilding and repopulating the fulltext catalogs
> restored to the new server.
> The message I encounter is "Error 7635: The Microsoft Search cannot be
> administered under the present user account".
> I understand from the link I have been referred to
> "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> that
> the service logon was changed through the control panel instead of the
> Enterprise Manager therefore the service login for SQL Server does not
> have
> administrative priviledges over the MSSearch service.
> None of the service logins were changed through the control panel
> I have tried the workround as suggested in the link but I still get the
> same
> error message when I try to rebuild the full text catalog.
> Any of you MVP's with another approach or suggestions to solve this
> problem?|||"Hilary Cotter" wrote:
> What account is MSSearch running under? It must be running under the local
> system account. If it is not change it, you can change it through the
> services applet in Control panel - Administrative Tasks.
> Check that the builtin\Admins group is in the sysadmin role, and if not do
> the following
> use master
> go
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> goThen change the SQL Server account to a the local system account in
> Enterprise manger, right click on it and select properties and then select
> the security tab and make the modifcation here, bounce it and the repeat the
> process to have it run under a local adminstrators account.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > Recently moved database and full text catalogs to new server with SQL
> > Server
> > 2000 sp3a/SBS 2003 sp1
> > I am having problems rebuilding and repopulating the fulltext catalogs
> > restored to the new server.
> > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > administered under the present user account".
> >
> > I understand from the link I have been referred to
> > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > that
> > the service logon was changed through the control panel instead of the
> > Enterprise Manager therefore the service login for SQL Server does not
> > have
> > administrative priviledges over the MSSearch service.
> > None of the service logins were changed through the control panel
> >
> > I have tried the workround as suggested in the link but I still get the
> > same
> > error message when I try to rebuild the full text catalog.
> >
> > Any of you MVP's with another approach or suggestions to solve this
> > problem?
> Thank you for your reply Hilary
The MS Search service is using the local system logon and built in admin has
the role of sydadmin.
I followed your instructions which was similiar to the instruction I
followed in the link i was reffered to inmy original message.
Unfortunately the your instructions I followed failed to cure the 7635 error
(cannot administer MS Search service under present user account).
Are ther any other slutions to try?
>|||"Jarvis Allen" wrote:
I have tried suggestions by Hilary and the problem still persists.
The MS Search is running under the local system account as it should which
seems to be the problem.
The problem seems to be getting the administer rights over the MS Search
service.
The SQL Server does start with the Domain Admin user.
For some reason the Domain Admin user can administer the MS Search service
even though I have used the suggested way to gain admin rights over the MS
Search!
Any other ideas from you SQL experts?
>
> "Hilary Cotter" wrote:
> > What account is MSSearch running under? It must be running under the local
> > system account. If it is not change it, you can change it through the
> > services applet in Control panel - Administrative Tasks.
> >
> > Check that the builtin\Admins group is in the sysadmin role, and if not do
> > the following
> >
> > use master
> > go
> > exec sp_grantlogin N'NT Authority\System'
> > exec sp_defaultdb N'NT Authority\System', N'master'
> > exec sp_defaultlanguage N'NT Authority\System','us_english'
> > exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> > goThen change the SQL Server account to a the local system account in
> > Enterprise manger, right click on it and select properties and then select
> > the security tab and make the modifcation here, bounce it and the repeat the
> > process to have it run under a local adminstrators account.
> >
> >
> >
> > --
> > Hilary Cotter
> > Director of Text Mining and Database Strategy
> > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> >
> > This posting is my own and doesn't necessarily represent RelevantNoise's
> > positions, strategies or opinions.
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> > Looking for a FAQ on Indexing Services/SQL FTS
> > http://www.indexserverfaq.com
> >
> >
> >
> > "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> > news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > > Recently moved database and full text catalogs to new server with SQL
> > > Server
> > > 2000 sp3a/SBS 2003 sp1
> > > I am having problems rebuilding and repopulating the fulltext catalogs
> > > restored to the new server.
> > > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > > administered under the present user account".
> > >
> > > I understand from the link I have been referred to
> > > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > > that
> > > the service logon was changed through the control panel instead of the
> > > Enterprise Manager therefore the service login for SQL Server does not
> > > have
> > > administrative priviledges over the MSSearch service.
> > > None of the service logins were changed through the control panel
> > >
> > > I have tried the workround as suggested in the link but I still get the
> > > same
> > > error message when I try to rebuild the full text catalog.
> > >
> > > Any of you MVP's with another approach or suggestions to solve this
> > > problem?
> >
> > Thank you for your reply Hilary
> The MS Search service is using the local system logon and built in admin has
> the role of sydadmin.
> I followed your instructions which was similiar to the instruction I
> followed in the link i was reffered to inmy original message.
> Unfortunately the your instructions I followed failed to cure the 7635 error
> (cannot administer MS Search service under present user account).
> Are ther any other slutions to try?
> >|||>
> "Jarvis Allen" wrote:
> I have tried suggestions by Hilary and the problem still persists.
> The MS Search is running under the local system account as it should which
> seems to be the problem.
> The problem seems to be getting the administer rights over the MS Search
> service.
> The SQL Server does start with the Domain Admin user.
> For some reason the Domain Admin user cannot administer the MS Search service
> even though I have used the suggested way to gain admin rights over the MS
> Search!
> Any other ideas from you SQL experts?
> >
> >
> > "Hilary Cotter" wrote:
> >
> > > What account is MSSearch running under? It must be running under the local
> > > system account. If it is not change it, you can change it through the
> > > services applet in Control panel - Administrative Tasks.
> > >
> > > Check that the builtin\Admins group is in the sysadmin role, and if not do
> > > the following
> > >
> > > use master
> > > go
> > > exec sp_grantlogin N'NT Authority\System'
> > > exec sp_defaultdb N'NT Authority\System', N'master'
> > > exec sp_defaultlanguage N'NT Authority\System','us_english'
> > > exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> > > goThen change the SQL Server account to a the local system account in
> > > Enterprise manger, right click on it and select properties and then select
> > > the security tab and make the modifcation here, bounce it and the repeat the
> > > process to have it run under a local adminstrators account.
> > >
> > >
> > >
> > > --
> > > Hilary Cotter
> > > Director of Text Mining and Database Strategy
> > > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> > >
> > > This posting is my own and doesn't necessarily represent RelevantNoise's
> > > positions, strategies or opinions.
> > >
> > > Looking for a SQL Server replication book?
> > > http://www.nwsu.com/0974973602.html
> > >
> > > Looking for a FAQ on Indexing Services/SQL FTS
> > > http://www.indexserverfaq.com
> > >
> > >
> > >
> > > "Jarvis Allen" <JarvisAllen@.discussions.microsoft.com> wrote in message
> > > news:DA108BC7-E94F-4391-A71F-505CF6D42E0A@.microsoft.com...
> > > > Recently moved database and full text catalogs to new server with SQL
> > > > Server
> > > > 2000 sp3a/SBS 2003 sp1
> > > > I am having problems rebuilding and repopulating the fulltext catalogs
> > > > restored to the new server.
> > > > The message I encounter is "Error 7635: The Microsoft Search cannot be
> > > > administered under the present user account".
> > > >
> > > > I understand from the link I have been referred to
> > > > "http://support.microsoft.com/default.aspx?scid=kb;en-us;277549" states
> > > > that
> > > > the service logon was changed through the control panel instead of the
> > > > Enterprise Manager therefore the service login for SQL Server does not
> > > > have
> > > > administrative priviledges over the MSSearch service.
> > > > None of the service logins were changed through the control panel
> > > >
> > > > I have tried the workround as suggested in the link but I still get the
> > > > same
> > > > error message when I try to rebuild the full text catalog.
> > > >
> > > > Any of you MVP's with another approach or suggestions to solve this
> > > > problem?
> > >
> > > Thank you for your reply Hilary
> > The MS Search service is using the local system logon and built in admin has
> > the role of sydadmin.
> > I followed your instructions which was similiar to the instruction I
> > followed in the link i was reffered to inmy original message.
> > Unfortunately the your instructions I followed failed to cure the 7635 error
> > (cannot administer MS Search service under present user account).
> > Are ther any other slutions to try?
> > >

Cannot rebuild full text catalogs

Tuesday, February 14, 2012

Cannot Generate SSPI Context

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...

Sunday, February 12, 2012

Cannot Generate SSPI Context

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
dominiqueHi
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$sbsmonitorin
g
> failes to start and then the sqlserveragent. both events are record with t
he
> 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" a
nd
> "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, ha
ve
> 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 du
e
> 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 t
he
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 even
ts.
> 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 prox
y.
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 a
re
> taking too long to start or possibly there may be a problem with the netwo
rk
> 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!

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:
>|||Hi
Are you running two copies of SQL Server on this server? If this instance is
the default then it would be the same as (local).
John
"dominique" <dominique@.discussions.microsoft.com> wrote in message
news:E0C60EA7-62C6-4146-90A8-21E76083B9AD@.microsoft.com...[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 im still getting the
> event
> 103 on sqlagent$sbsmonitoring. i changed the authentification for the
> sqlserveragent too, but that didnt worked. im only able to start the
> sqlserveragent when windows authentification is enabled...

> any other suggestions? ://
> --
> kind regards / liebe grsse
> dominique
>
> "John Bell" wrote:
>

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
dominiqueHi
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:
> 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
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 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
> >
> > 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,
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
> 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 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
> > >
> > > 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 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,
> 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
> >
> > 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 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
> > > >
> > > > 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,
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:
> 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,
> >
> > 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
> > >
> > > 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 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
> > > > >
> > > > > 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
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.
> --
> kind regards / liebe gr=FCsse
> dominique
>
> "John Bell" 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 service=s are
> > taking too long to start or possibly there may be a problem with the ne=twork
> > card. If you can make SQLServer dependent another service (say computer
> > browser) then it may delay things for long enough. If you have a softwa=re
> > firewall running, check to see how long this takes to start up.
> >
> > John
> >
> > "dominique" wrote:
> >
> > > hi,
> > >
> > > no only on reboot, that=B4s why it=B4s 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=B4m able to start the
> > > sqlserveragent (right now with the domain account). but i=B4m able to= start the
> > > sqlserveragent with the system account too.
> > >
> > > only on reboot / startup the services are not starting with the below= events.
> > >
> > > i=B4m desperate :(
> > >
> > > --
> > > kind regards / liebe gr=FCsse
> > > dominique
> > >
> > >
> > > "John Bell" 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:
> > > >
> > > > > hi john,
> > > > >
> > > > > first of all, thank you for your answer.
> > > > > i=B4m 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, bu=t i=B4m
> > > > > 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 aga=in... ://
> > > > >
> > > > > i don=B4t understand it... :(
> > > > >
> > > > > any ideas?
> > > > >
> > > > > --
> > > > > kind regards / liebe gr=FCsse
> > > > > dominique
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > 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 do=main 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 connec=t to server
> > > > > > > "(sbs\sbsmonitoring)"; SQLServerAgent
> > > > > > > cannot start).
> > > > > > > sqlserveragent:
> > > > > > > SQLServerAgent could not be started (reason: Unable to connec=t 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 err=or "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=B4t find anything that= helped me.
> > > > > > >
> > > > > > > even if i set the services to start over if an error occure, =it doesn=B4t
> > > > > > > work. only if i start the services manually... :(
> > > > > > > the services are set to start with the local system account.
> > > > > > >
> > > > > > > i don=B4t have any knowledge from a sql server. can somebody =please help me!
> > > > > > >
> > > > > > > --
> > > > > > > kind regards / liebe gr=FCsse
> > > > > > > dominique|||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:
> > 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:
> >
> > > 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,
> > > >
> > > > 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
> > > > >
> > > > > 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 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
> > > > > > >
> > > > > > > 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
Are you running two copies of SQL Server on this server? If this instance is
the default then it would be the same as (local).
John
"dominique" <dominique@.discussions.microsoft.com> wrote in message
news:E0C60EA7-62C6-4146-90A8-21E76083B9AD@.microsoft.com...
> 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:
>> > 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:
>> >
>> > > 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,
>> > > >
>> > > > 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
>> > > > >
>> > > > > 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 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
>> > > > > > >
>> > > > > > > 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,
no, not that i know. iÂ´m running only one sql server.
iÂ´m sorry, but i donÂ´t understand your question. what instance do you mean?
the sbsmonitoring?
--
kind regards / liebe grÃ¼sse
dominique
"John Bell" wrote:
> Hi
> Are you running two copies of SQL Server on this server? If this instance is
> the default then it would be the same as (local).
> John
> "dominique" <dominique@.discussions.microsoft.com> wrote in message
> news:E0C60EA7-62C6-4146-90A8-21E76083B9AD@.microsoft.com...
> > 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:
> >> > 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:
> >> >
> >> > > 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,
> >> > > >
> >> > > > 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
> >> > > > >
> >> > > > > 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 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
> >> > > > > > >
> >> > > > > > > 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
You can install multiple instances on a single server, if you run the
command NET START from a command prompt you may have multiple instances that
are either like MSSQLSERVER or MSQL$INSTANCE.
John
"dominique" wrote:
> hi john,
> no, not that i know. iÂ´m running only one sql server.
> iÂ´m sorry, but i donÂ´t understand your question. what instance do you mean?
> the sbsmonitoring?
> --
> kind regards / liebe grÃ¼sse
> dominique
>
> "John Bell" wrote:
> > Hi
> >
> > Are you running two copies of SQL Server on this server? If this instance is
> > the default then it would be the same as (local).
> >
> > John
> >
> > "dominique" <dominique@.discussions.microsoft.com> wrote in message
> > news:E0C60EA7-62C6-4146-90A8-21E76083B9AD@.microsoft.com...
> > > 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:
> > >> > 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:
> > >> >
> > >> > > 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,
> > >> > > >
> > >> > > > 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
> > >> > > > >
> > >> > > > > 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 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
> > >> > > > > > >
> > >> > > > > > > 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,
there are multiple instances running.
backup exec, msfw (isa), sbsmonitoring and sharepoint. but the
sqlserveragent is only needed for sbsmonitoring and local.
Did that answer your question? :/
thanks again for your help :)
--
kind regards / liebe grÃ¼sse
dominique
"John Bell" wrote:
> Hi
> You can install multiple instances on a single server, if you run the
> command NET START from a command prompt you may have multiple instances that
> are either like MSSQLSERVER or MSQL$INSTANCE.
> John
> "dominique" wrote:
> > hi john,
> >
> > no, not that i know. iÂ´m running only one sql server.
> >
> > iÂ´m sorry, but i donÂ´t understand your question. what instance do you mean?
> > the sbsmonitoring?
> > --
> > kind regards / liebe grÃ¼sse
> > dominique
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Are you running two copies of SQL Server on this server? If this instance is
> > > the default then it would be the same as (local).
> > >
> > > John
> > >
> > > "dominique" <dominique@.discussions.microsoft.com> wrote in message
> > > news:E0C60EA7-62C6-4146-90A8-21E76083B9AD@.microsoft.com...
> > > > 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:
> > > >> > 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:
> > > >> >
> > > >> > > 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,
> > > >> > > >
> > > >> > > > 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
> > > >> > > > >
> > > >> > > > > 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 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
> > > >> > > > > > >
> > > >> > > > > > > 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
Have you stopped the SQL Server Agent service for the instances where you
don't want it to run? Try changing the start up type to manual.
John
"dominique" wrote:
> hi john,
> there are multiple instances running.
> backup exec, msfw (isa), sbsmonitoring and sharepoint. but the
> sqlserveragent is only needed for sbsmonitoring and local.
> Did that answer your question? :/
> thanks again for your help :)
> --
> kind regards / liebe grÃ¼sse
> dominique
>
> "John Bell" wrote:
> > Hi
> >
> > You can install multiple instances on a single server, if you run the
> > command NET START from a command prompt you may have multiple instances that
> > are either like MSSQLSERVER or MSQL$INSTANCE.
> >
> > John
> >
> > "dominique" wrote:
> >
> > > hi john,
> > >
> > > no, not that i know. iÂ´m running only one sql server.
> > >
> > > iÂ´m sorry, but i donÂ´t understand your question. what instance do you mean?
> > > the sbsmonitoring?
> > > --
> > > kind regards / liebe grÃ¼sse
> > > dominique
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > Are you running two copies of SQL Server on this server? If this instance is
> > > > the default then it would be the same as (local).
> > > >
> > > > John
> > > >
> > > > "dominique" <dominique@.discussions.microsoft.com> wrote in message
> > > > news:E0C60EA7-62C6-4146-90A8-21E76083B9AD@.microsoft.com...
> > > > > 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:
> > > > >> > 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:
> > > > >> >
> > > > >> > > 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,
> > > > >> > > >
> > > > >> > > > 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
> > > > >> > > > >
> > > > >> > > > > 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 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
> > > > >> > > > > > >
> > > > >> > > > > > > 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,
sorry my fault. the sql server agent service is running only on the two
instances (sbsmonitoring and local) and the start up type for the other
instances is allready manual.
--
kind regards / liebe grÃ¼sse
dominique
"John Bell" wrote:
> Hi
> Have you stopped the SQL Server Agent service for the instances where you
> don't want it to run? Try changing the start up type to manual.
> John
>
> "dominique" wrote:
> > hi john,
> >
> > there are multiple instances running.
> > backup exec, msfw (isa), sbsmonitoring and sharepoint. but the
> > sqlserveragent is only needed for sbsmonitoring and local.
> >
> > Did that answer your question? :/
> >
> > thanks again for your help :)
> >
> > --
> > kind regards / liebe grÃ¼sse
> > dominique
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > You can install multiple instances on a single server, if you run the
> > > command NET START from a command prompt you may have multiple instances that
> > > are either like MSSQLSERVER or MSQL$INSTANCE.
> > >
> > > John
> > >
> > > "dominique" wrote:
> > >
> > > > hi john,
> > > >
> > > > no, not that i know. iÂ´m running only one sql server.
> > > >
> > > > iÂ´m sorry, but i donÂ´t understand your question. what instance do you mean?
> > > > the sbsmonitoring?
> > > > --
> > > > kind regards / liebe grÃ¼sse
> > > > dominique
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > Are you running two copies of SQL Server on this server? If this instance is
> > > > > the default then it would be the same as (local).
> > > > >
> > > > > John
> > > > >
> > > > > "dominique" <dominique@.discussions.microsoft.com> wrote in message
> > > > > news:E0C60EA7-62C6-4146-90A8-21E76083B9AD@.microsoft.com...
> > > > > > 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:
> > > > > >> > 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:
> > > > > >> >
> > > > > >> > > 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,
> > > > > >> > > >
> > > > > >> > > > 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
> > > > > >> > > > >
> > > > > >> > > > > 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 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
> > > > > >> > > > > > >
> > > > > >> > > > > > > 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
Are these two services running under the same user? If they are then try
changing them to a different one.
John
"dominique" wrote:
> hi john,
> sorry my fault. the sql server agent service is running only on the two
> instances (sbsmonitoring and local) and the start up type for the other
> instances is allready manual.
> --
> kind regards / liebe grÃ¼sse
> dominique
>
> "John Bell" wrote:
> > Hi
> >
> > Have you stopped the SQL Server Agent service for the instances where you
> > don't want it to run? Try changing the start up type to manual.
> >
> > John
> >
> >
> > "dominique" wrote:
> >
> > > hi john,
> > >
> > > there are multiple instances running.
> > > backup exec, msfw (isa), sbsmonitoring and sharepoint. but the
> > > sqlserveragent is only needed for sbsmonitoring and local.
> > >
> > > Did that answer your question? :/
> > >
> > > thanks again for your help :)
> > >
> > > --
> > > kind regards / liebe grÃ¼sse
> > > dominique
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > You can install multiple instances on a single server, if you run the
> > > > command NET START from a command prompt you may have multiple instances that
> > > > are either like MSSQLSERVER or MSQL$INSTANCE.
> > > >
> > > > John
> > > >
> > > > "dominique" wrote:
> > > >
> > > > > hi john,
> > > > >
> > > > > no, not that i know. iÂ´m running only one sql server.
> > > > >
> > > > > iÂ´m sorry, but i donÂ´t understand your question. what instance do you mean?
> > > > > the sbsmonitoring?
> > > > > --
> > > > > kind regards / liebe grÃ¼sse
> > > > > dominique
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > Are you running two copies of SQL Server on this server? If this instance is
> > > > > > the default then it would be the same as (local).
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "dominique" <dominique@.discussions.microsoft.com> wrote in message
> > > > > > news:E0C60EA7-62C6-4146-90A8-21E76083B9AD@.microsoft.com...
> > > > > > > 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:
> > > > > > >> > 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:
> > > > > > >> >
> > > > > > >> > > 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,
> > > > > > >> > > >
> > > > > > >> > > > 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
> > > > > > >> > > > >
> > > > > > >> > > > > 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 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
> > > > > > >> > > > > > >
> > > > > > >> > > > > > > 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,
well they are running both under the local system. i think i tried changing
it to an (admin)user and the result was the same. service is not able to
start. but iÂ´m gonna test it next week and tell you.
thank you for your help so far :) thank you, thank you, thank you :)
--
kind regards / liebe grÃ¼sse
dominique
"John Bell" wrote:
> Hi
> Are these two services running under the same user? If they are then try
> changing them to a different one.
> John
> "dominique" wrote:
> > hi john,
> >
> > sorry my fault. the sql server agent service is running only on the two
> > instances (sbsmonitoring and local) and the start up type for the other
> > instances is allready manual.
> >
> > --
> > kind regards / liebe grÃ¼sse
> > dominique
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Have you stopped the SQL Server Agent service for the instances where you
> > > don't want it to run? Try changing the start up type to manual.
> > >
> > > John
> > >
> > >
> > > "dominique" wrote:
> > >
> > > > hi john,
> > > >
> > > > there are multiple instances running.
> > > > backup exec, msfw (isa), sbsmonitoring and sharepoint. but the
> > > > sqlserveragent is only needed for sbsmonitoring and local.
> > > >
> > > > Did that answer your question? :/
> > > >
> > > > thanks again for your help :)
> > > >
> > > > --
> > > > kind regards / liebe grÃ¼sse
> > > > dominique
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > You can install multiple instances on a single server, if you run the
> > > > > command NET START from a command prompt you may have multiple instances that
> > > > > are either like MSSQLSERVER or MSQL$INSTANCE.
> > > > >
> > > > > John
> > > > >
> > > > > "dominique" wrote:
> > > > >
> > > > > > hi john,
> > > > > >
> > > > > > no, not that i know. iÂ´m running only one sql server.
> > > > > >
> > > > > > iÂ´m sorry, but i donÂ´t understand your question. what instance do you mean?
> > > > > > the sbsmonitoring?
> > > > > > --
> > > > > > kind regards / liebe grÃ¼sse
> > > > > > dominique
> > > > > >
> > > > > >
> > > > > > "John Bell" wrote:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > Are you running two copies of SQL Server on this server? If this instance is
> > > > > > > the default then it would be the same as (local).
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > > "dominique" <dominique@.discussions.microsoft.com> wrote in message
> > > > > > > news:E0C60EA7-62C6-4146-90A8-21E76083B9AD@.microsoft.com...
> > > > > > > > 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:
> > > > > > > >> > 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:
> > > > > > > >> >
> > > > > > > >> > > 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,
> > > > > > > >> > > >
> > > > > > > >> > > > 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
> > > > > > > >> > > > >
> > > > > > > >> > > > > 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 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
> > > > > > > >> > > > > > >
> > > > > > > >> > > > > > > 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
Looking back through the thread I realise I have already suggested to change
the account. I did find
http://tinyurl.com/g3jly and http://tinyurl.com/g8k4c
John
"dominique" wrote:
> hi john,
> well they are running both under the local system. i think i tried changing
> it to an (admin)user and the result was the same. service is not able to
> start. but iÂ´m gonna test it next week and tell you.
> thank you for your help so far :) thank you, thank you, thank you :)
> --
> kind regards / liebe grÃ¼sse
> dominique
>
> "John Bell" wrote:
> > Hi
> >
> > Are these two services running under the same user? If they are then try
> > changing them to a different one.
> >
> > John
> >
> > "dominique" wrote:
> >
> > > hi john,
> > >
> > > sorry my fault. the sql server agent service is running only on the two
> > > instances (sbsmonitoring and local) and the start up type for the other
> > > instances is allready manual.
> > >
> > > --
> > > kind regards / liebe grÃ¼sse
> > > dominique
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi
> > > >
> > > > Have you stopped the SQL Server Agent service for the instances where you
> > > > don't want it to run? Try changing the start up type to manual.
> > > >
> > > > John
> > > >
> > > >
> > > > "dominique" wrote:
> > > >
> > > > > hi john,
> > > > >
> > > > > there are multiple instances running.
> > > > > backup exec, msfw (isa), sbsmonitoring and sharepoint. but the
> > > > > sqlserveragent is only needed for sbsmonitoring and local.
> > > > >
> > > > > Did that answer your question? :/
> > > > >
> > > > > thanks again for your help :)
> > > > >
> > > > > --
> > > > > kind regards / liebe grÃ¼sse
> > > > > dominique
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > You can install multiple instances on a single server, if you run the
> > > > > > command NET START from a command prompt you may have multiple instances that
> > > > > > are either like MSSQLSERVER or MSQL$INSTANCE.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "dominique" wrote:
> > > > > >
> > > > > > > hi john,
> > > > > > >
> > > > > > > no, not that i know. iÂ´m running only one sql server.
> > > > > > >
> > > > > > > iÂ´m sorry, but i donÂ´t understand your question. what instance do you mean?
> > > > > > > the sbsmonitoring?
> > > > > > > --
> > > > > > > kind regards / liebe grÃ¼sse
> > > > > > > dominique
> > > > > > >
> > > > > > >
> > > > > > > "John Bell" wrote:
> > > > > > >
> > > > > > > > Hi
> > > > > > > >
> > > > > > > > Are you running two copies of SQL Server on this server? If this instance is
> > > > > > > > the default then it would be the same as (local).
> > > > > > > >
> > > > > > > > John
> > > > > > > >
> > > > > > > > "dominique" <dominique@.discussions.microsoft.com> wrote in message
> > > > > > > > news:E0C60EA7-62C6-4146-90A8-21E76083B9AD@.microsoft.com...
> > > > > > > > > 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:
> > > > > > > > >> > 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:
> > > > > > > > >> >
> > > > > > > > >> > > 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,
> > > > > > > > >> > > >
> > > > > > > > >> > > > 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
> > > > > > > > >> > > > >
> > > > > > > > >> > > > > 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 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
> > > > > > > > >> > > > > > >
> > > > > > > > >> > > > > > > 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

Sunday, March 25, 2012

Cannot rebuild full text catalogs

Cannot rebuild full text catalogs

Cannot rebuild full text catalogs

Tuesday, February 14, 2012

Cannot Generate SSPI Context

Sunday, February 12, 2012

Cannot Generate SSPI Context

Cannot Generate SSPI Context

Cannot find mdf files

Blog Archive

About Me