SQLAGENT will not start in a timely fashion

  • I have read just about every post for this but I cannot find a solution. here is my issue.

    to be clear every program and service seems to be working as expected. The server works perfectly except for sqlagent.

    We are running Server 2008R2 and have SQL Server 2008R2 SP2 (stand-alone), there was an unexpected crash of our server and ever since the recovery, SQLAGENT will not start. The crash was not due to server but the VM environment. after recovering all programs/ services were verified as working, including SQL Server (SQL Server service is running without issues and the DB is functioning as designed).

    The error I am getting in the windows event log: the SQL Server Agent (instance) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

    Starting SQLAGENT from SSMS reveals this error:

    ===================================

    Unable to start service SQLSERVERAGENT on server xxxxxxxxx. (mscorlib)

    ------------------------------

    Program Location:

    Server stack trace:

    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Service.Start()

    at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

    at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

    at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

    Exception rethrown at [0]:

    at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)

    at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)

    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ServiceActionHandler.EndInvoke(IAsyncResult result)

    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ServiceControlProgress.ActionCompletedHandler(IAsyncResult result)

    ===================================

    Service Request Timeout (ObjectExplorer)

    ------------------------------

    Program Location:

    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Service.CheckServiceActionReturnValueSuccess(UInt32 returnValue)

    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Service.Start()

    Checking the SQLAGENT.OUT log does not reveal anything. In fact no entries have been made since the crash. SQLAGENT is not updating/writing to the log. I know when SQLSERVERAGENT quit working because my job history shows the last day my daily job ran. I even checked the sql logs and nothing stuck out with slqagent.

    These are the things I have done to try and correct:

    1) I have verified the authentication (NT Authority/system) and tried different users for authentication but everything I try fails to start the service. of Note "SQL Server" service is using the same authentication. So i do not think its an authentication issue.

    2) verified that the BUILTIN\Adminsitrators account did not drop out of sql logins.

    3) I have verified the log path in the registry and it is correct. in registry and in SSMS sql server agent properties

    4) I tried running SQLAGENT.exe in privileged cmd with verbose logging: "SQLAGENT.exe -c -v". A dialog box opens and states "SQLAGENT - SQL ServerAgent has stopped working. a problem caused the program to stop working correctly. Please close program." Hit close and an error box opens: "SQLAGENT - Application Error. the application was unable to start correctly (0xc06d007e). Click ok to close." this is the application event log after running:

    Faulting application name: SQLAGENT.EXE, version: 2009.100.1617.0, time stamp: 0x4db245ad

    Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a

    Exception code: 0xc06d007e

    Fault offset: 0x000000000000940d

    Faulting process id: 0x1208

    Faulting application start time: 0x01d0035dcf4bc528

    Faulting application path: E:\xxxxxxx\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SQLAGENT.EXE

    Faulting module path: C:\windows\system32\KERNELBASE.dll

    Report Id: 0d55e640-6f51-11e4-866e-0050568607b0

    5) I thought maybe sqlagent.exe file was corrupt so i copied the file from another sql server and placed it on my broken server and

    tried running, I got the same results as before.

    6) increased timeout in registry

    7) ran "sfc /scannow"

    8) made sure correct host names was in: SQL Server Agent -> Properties ->Connection->Alias local host server and verified in registry

    9) I tried deleting SQLAGENT.OUT log file in hope it would recreate, but never did. the file was never recreated. I do have SQLAGENT.1-9, but none of the have any entries that are even close the the crash event. the last entry in this log is: Job syspolicy_purge_history reported: The process could not be created for step 3 of job 0xA9E7005F8FBB4349BD63721B4F78AFD8 (reason: Access is denied). for this job to run SQLAGENT had to be running.

    I am fresh out of clues. any help or pointing in the right direction to look would be helpful.

    thx,

    curtis

  • well after a full week of troubleshooting I found out what was my problem. We have McAfee Host Intrusion Protection System (HIPS) on our network and I discovered it was blocking SQLAGENT from running. HIPS is not suppose to installed on my server but was recently pushed unbeknownst to me. so now SQL is running as it should be.

  • That's an interesting one, and might help somebody else in the future!

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply