Skip to main content

SQLServerAgent could not be started (reason: Unable to connect to server 'ServerName\Instancename'; SQLServerAgent cannot start).

Hello,

At one of the environments i faced a very strange issue, i was working on SQL Server cluster that was working fine, but for some reason i have to perform a failover, all the resources and services were restarted successfully except for the SQL Server Agent service... looking at the system logs of the vent viewer i found the following error, Event ID 103 "
SQLServerAgent could not be started (reason: Unable to connect to server 'ServerName\Instancename'; SQLServerAgent cannot start)."

Log Name:      Application
Source:        SQLAgent$InstaceName
Date:          3/20/2013 3:29:58 PM
Event ID:      103
Task Category: Service Control
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ServerName
Description:
SQLServerAgent could not be started (reason: Unable to connect to server 'ServerName\InstanceName'; SQLServerAgent cannot start).
Event Xml:
http://schemas.microsoft.com/win/2004/08/events/event
">
 
   
    103
    2
    2
    0x80000000000000
   
    22958
    Application
    ServeraName
   
 
 
    Unable to connect to server 'ServerName\InstanceName'; SQLServerAgent cannot start
 
A quick search on the Internet yielded some forum posts that talk about permission on the SQL drives, and this was not my case.
After some troubleshooting i looked at the account used by the SQL Server Agent Service, the account was OK, but looking at SQL server logs i fount the root cause !
Login failed for user 'Domain\ServiceAccount'. Reason: The account is disabled. [CLIENT: IP Address]
looking at the SQL logins I found out that the login for this account has been disabled by the DBA !!! :(

enabling the account solved the  problem and the service can start successfully

Regards
Amr

Comments

Post a Comment

Popular posts from this blog

Upgrade from Lync Evaluation edition to Lync RTM.

If you have installed Lync Server using the 180 Day  trial bits  you can upgrade to the RTM bits nsing the following easy steps: Run setup.exe on your Lync server Volume License media. Click on "Install or Update Lync server system" Click on "Setup or remove Lync server components" Open CMD and  navigate to \Setup\amd64\setup and then run msiexec.exe /fvomus server.msi EVALTOFULL=1 /qb  Open Lync Server Management Shell and then run Enable-CSComputer and then you are done !
7 comments
Read more

Exchange 2010 - EMC "RBAC authorization returns Access Denied"

I was doing an Upgrade for Exchange 2003 to Exchange 2010 and after i installed the first CAS server and opened the EMC an error appeared that i have no permissions... while i was logged in with the setup account and it was a memeber of the Organization Managemnet Group. and i founbd this in the Applicaiton Log  "(Process w3wp.exe, PID 6716) "RBAC authorization returns Access Denied for user Udomain.Local/Users/AccountName. Reason: No role assignments associated with the specified user were found on Domain Controller XXXXX" " After alot of searches i was pulling my remaining hair out :)  I  found this post ( http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/fc568cc6-8691-4127-b70b-bcc82f9b1f7f?prof=required ) The issue was with 2 things : Allow inheritable permissions check Box was not enabled on the Exchange  Microsoft Exchange Organzaiton container inside the Configuration partition. The value for the attributes msExchRoleLink ...
Post a Comment
Read more

the networkmanager has not yet been initialized

I faced a very strange case with Exchange DAG, I was doing a site resiliency test I failed over to the DR site successfully and then I failed back to the main site, after failing back I found that the DAG was in a state that looks like split brain syndrome although the DAG was running in DAC mode. the symptoms were as follows: From the DR mailbox server: Cluster Console only showed this node while the active nodes were not present. From EMC the copies on the DR server were healthy. From the Main site mailbox servers: Cluster console showed the three nodes but the DR node was stopped, and the option to start it was grayed out. From EMC the copies on the DR server were failed. The fix was as follows:  run the following command: Cluster       /forcecleanup Then run the following: Start-DatabaseAvailabilityGroup "DAGname" -MailboxServer  "DRNodeName" After the first command you will find that the DR node can see the oth...
Post a Comment
Read more