December 4, 2003 at 5:08 am
Hi There,
I'm a rookie to SQL and cluster. Please help me.
I've a problem with starting SQL Agent on our Cluster. Hence, no failover. SQL#1 start SQL Agent no problem but SQL#2 have problem starting SQLAgent.
Information:-
*It's a Windows 2000 cluster
*It's a Windows SQL Server Cluster
*It's a Active/Passive (or failover) cluster
*In SQL#2 event log. Event ID:103 - SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
*In SQL Log. SQLServer Error: 18456, Login failed for user 'sa'. [SQLSTATE 28000]
Pretty sure the SA password is correct. Orderwise, SQL#1 wouldn't start.
Many Thanks In Advance.
Alvin
December 4, 2003 at 12:23 pm
Check a couple of things. One the account that sql server and the agent are set two run under have enough permissions to start i.e. usually a domain acount with local admin rights on each node. Two, check your dependancies in cluster admin and make sure that sql owns everything it needs to fail over with.
Wes
December 5, 2003 at 2:59 am
I've also seen problems where the account your running the cluster services under needs to have a login to the Master database as the cluster services perform a login to check that SQL has started correctly.
December 5, 2003 at 10:07 am
My guess...SQL Server Agent is connecting with a local system account.
Check who owns the SQL Server Agent Service, and what account is used by SQL Server Agent to connect to the database. Right click on the SQL Server Agent properties and tab to the left.
Quick question...What version of SQL Server are you using. You mentioned Windows 2000 clustering which suggests possibly SQL Server 7.0.
"Keep Your Stick On the Ice" ..Red Green
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply