SQL SERVER – Unable to Start Jobs – Error: Enumerate Target Servers Failed for Job

SQL
No Comments

SQL SERVER - Unable to Start Jobs - Error: Enumerate Target Servers Failed for Job failicon One of my clients contacted me for quick On-Demand consulting. When I joined GoToMeeting with them they showed me below error when they were trying to run a job. Let us see how we can fix the error Enumerate Target Servers Failed for Job.

Cannot perform this operation while SQLServerAgent is starting. Try again later. (Microsoft SQL Server, Error: 14258)

I asked them to check SQL Server Agent logs (SQLAgent.OUT) file and found below.

Solarwinds

2018-01-29 12:13:40 – ! [125] Subsystem ‘ANALYSISCOMMAND’ could not be loaded (reason: The specified module could not be found)
2018-01-29 12:13:40 – ! [125] Subsystem ‘ANALYSISQUERY’ could not be loaded (reason: The specified module could not be found)
2018-01-29 12:13:40 – ! [125] Subsystem ‘SmartAdmin’ could not be loaded (reason: The specified module could not be found)
2018-01-29 12:13:40 – ! [125] Subsystem ‘SSIS’ could not be loaded (reason: The specified module could not be found)
2018-01-29 12:13:40 – ? [129] SQLSERVERAGENT starting under Windows NT service control
2018-01-29 12:13:41 – ! [355] The mail system failed to initialize; check configuration settings. Error:126 (reason: The specified module could not be found)

I earlier wrote a blog for the same error. SQL SERVER – Error: 14258 – Cannot perform this operation while SQLServerAgent is starting. Try again later

But the messages are not same in SQLAgent.OUT file. If you notice the messages mentioned above, we can see that many subsystems are not able to load. Everywhere we are seeing “Error:126 (reason: The specified module could not be found)”. This error appears when there are missing DLLs which are needed.

WORKAROUND/SOLUTION

While looking at other activities on the server, I suspected something wrong with some common components across all the software running on the machine.

I searched on the internet and found that this could be due to .NET framework issue. So, we went ahead and performed repair of .NET framework. This was the tool which I used Microsoft .NET Framework Repair Tool.

After repairing .NET framework, we were able to run the job. Have you found any other solution to the error mentioned above? Please share via comments so that other blog readers can also benefit.

Reference: Pinal Dave (https://blog.sqlauthority.com)

Solarwinds
, , , ,
Previous Post
SQL SERVER- Unable to Failover AlwaysOn Availability Group to Disaster Recovery Site
Next Post
SQL SERVER – Unable to Start SQL Server Agent. Error – Driver’s SQLAllocHandle on SQL_HANDLE_ENV failed

Related Posts

Leave a Reply

Menu