![]() for this job to run SQLAGENT had to be running. 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). I do have SQLAGENT.1-9, but none of the have any entries that are even close the the crash event. Tried running, I got the same results as before.Ĩ) made sure correct host names was in: SQL Server Agent -> Properties ->Connection->Alias local host server and verified in registryĩ) I tried deleting SQLAGENT.OUT log file in hope it would recreate, but never did. Report Id: 0d55e640-6f51-11e4-866e-0050568607b0ĥ) 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 18409, time stamp: 0x5315a05aįaulting application start time: 0x01d0035dcf4bc528įaulting application path: E:\xxxxxxx\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SQLAGENT.EXEįaulting module path: C:\windows\system32\KERNELBASE.dll Click ok to close." this is the application event log after running:įaulting application name: SQLAGENT.EXE, version: 2009.100.1617.0, time stamp: 0x4db245adįaulting module name: KERNELBASE.dll, version. the application was unable to start correctly (0xc06d007e). Please close program." Hit close and an error box opens: "SQLAGENT - Application Error. a problem caused the program to stop working correctly. A dialog box opens and states "SQLAGENT - SQL ServerAgent has stopped working. in registry and in SSMS sql server agent propertiesĤ) I tried running SQLAGENT.exe in privileged cmd with verbose logging: "SQLAGENT.exe -c -v". So i do not think its an authentication issue.Ģ) verified that the BUILTIN\Adminsitrators account did not drop out of sql logins.ģ) I have verified the log path in the registry and it is correct. of Note "SQL Server" service is using the same authentication. These are the things I have done to try and correct:ġ) I have verified the authentication (NT Authority/system) and tried different users for authentication but everything I try fails to start the service. I even checked the sql logs and nothing stuck out with slqagent. I know when SQLSERVERAGENT quit working because my job history shows the last day my daily job ran. SQLAGENT is not updating/writing to the log. In fact no entries have been made since the crash. (mscorlib)Īt .()Īt .StackBuilderSink._PrivateProcessMessage(IntPtr md, Object args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object& outArgs)Īt .StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object& outArgs)Īt .StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)Īt .RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProx圜ase)Īt .RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)Īt .(IAsyncResult result)Īt .(IAsyncResult result)Īt .(UInt32 returnValue)Ĭhecking the SQLAGENT.OUT log does not reveal anything. Unable to start service SQLSERVERAGENT on server xxxxxxxxx. Starting SQLAGENT from SSMS reveals this error: 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. 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 crash was not due to server but the VM environment. ![]() 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 server works perfectly except for sqlagent. To be clear every program and service seems to be working as expected. I have read just about every post for this but I cannot find a solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |