dbTalk Databases Forums  

Agent does not start after moving SQL to other node

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss Agent does not start after moving SQL to other node in the microsoft.public.sqlserver.clustering forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Gunno
 
Posts: n/a

Default Agent does not start after moving SQL to other node - 09-10-2009 , 01:49 AM






Hi,

I have an issues where the sql agent does not automatically when sql server
is moved (failover) from one node to the other. If I wait 5-10 seconds the
agent can be started manually.

Has anyone seen this before?

I also have a error message in the log saying:

[298] SQLServer Error: 18401, Login failed for user 'Contoso\sqlaccount'.
Reason: Server is in script upgrade mode. Only administrator can connect at
this time. [SQLSTATE 42000]
[000] Unable to connect to server 'sqlserver1\db1'; SQLServerAgent cannot
start
[298] SQLServer Error: 18401, Login failed for user 'Contoso\sqlaccount'.
Reason: Server is in script upgrade mode. Only administrator can connect at
this time. [SQLSTATE 42000]
[382] Logon to server 'sqlserver1\db1' failed (DisableAgentXPs)
[098] SQLServerAgent terminated (normally)

Thanks
Gunno

Reply With Quote
  #2  
Old   
LaRoux
 
Posts: n/a

Default Re: Agent does not start after moving SQL to other node - 09-10-2009 , 01:54 PM






It sounds as if your SQLAgent resource isn't dependent on the SQL Server
service, causing it to try to start up too quickly.

In Cluster Administrator, rt-click on the Agent resource and under
properties\dependencies, be sure that the SQL Server resource is listed.

"Gunno" <Gunno (AT) discussions (DOT) microsoft.com> wrote

Quote:
Hi,

I have an issues where the sql agent does not automatically when sql
server
is moved (failover) from one node to the other. If I wait 5-10 seconds the
agent can be started manually.

Has anyone seen this before?

I also have a error message in the log saying:

[298] SQLServer Error: 18401, Login failed for user 'Contoso\sqlaccount'.
Reason: Server is in script upgrade mode. Only administrator can connect
at
this time. [SQLSTATE 42000]
[000] Unable to connect to server 'sqlserver1\db1'; SQLServerAgent cannot
start
[298] SQLServer Error: 18401, Login failed for user 'Contoso\sqlaccount'.
Reason: Server is in script upgrade mode. Only administrator can connect
at
this time. [SQLSTATE 42000]
[382] Logon to server 'sqlserver1\db1' failed (DisableAgentXPs)
[098] SQLServerAgent terminated (normally)

Thanks
Gunno

Reply With Quote
  #3  
Old   
Linchi Shea
 
Posts: n/a

Default RE: Agent does not start after moving SQL to other node - 09-10-2009 , 02:13 PM



Perhaps, you had an unfinished upgrade/patch on the other node. Was it a
one-off occurrence?

Linchi

"Gunno" wrote:

Quote:
Hi,

I have an issues where the sql agent does not automatically when sql server
is moved (failover) from one node to the other. If I wait 5-10 seconds the
agent can be started manually.

Has anyone seen this before?

I also have a error message in the log saying:

[298] SQLServer Error: 18401, Login failed for user 'Contoso\sqlaccount'.
Reason: Server is in script upgrade mode. Only administrator can connect at
this time. [SQLSTATE 42000]
[000] Unable to connect to server 'sqlserver1\db1'; SQLServerAgent cannot
start
[298] SQLServer Error: 18401, Login failed for user 'Contoso\sqlaccount'.
Reason: Server is in script upgrade mode. Only administrator can connect at
this time. [SQLSTATE 42000]
[382] Logon to server 'sqlserver1\db1' failed (DisableAgentXPs)
[098] SQLServerAgent terminated (normally)

Thanks
Gunno

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.