Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

SQL Agent not able to start on SQL Server 2008 Developer Edition Expand / Collapse
Author
Message
Posted Friday, February 25, 2011 11:28 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, December 10, 2012 3:20 AM
Points: 23, Visits: 133
Dear All,

I have SQL Server 2008 Developer Edition (64-bit) SP1 installed on a Windows Server 2008 R2 machine. For some reason, I can't get the SQL Agent service to start. When I go into the SQL Server Configuration Manager and select the properties of the Agent service and try to change the start mode from 'Disabled' to 'Manual', it comes back with the following error message after a few seconds:

"WMI Provider Error

The remote procedure call failed. [0x800706be]"

Both SQL Server and SQL Agent service are set to log on as the same domain account, which we have on many other SQL servers and the SQL Server service itself is running under this account quite happily.

I've had a look around generally at articles etc... but most of them refer to the Express Edition, which this is not. I've tried temporarily disabling the Windows Firewall, but it seems to make no difference.

Does anyone have any ideas? This is a newly created server and the only SQL installation that has ever been on it is the one referred to above. There's nothing else SQL or otherwise that isn't working fine - just the Agent! Could it be a problem with a setting in the O/S?

Any help would be much appreciated.

Regards,

Chris Stride
Post #1069772
Posted Friday, February 25, 2011 2:35 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: 2 days ago @ 3:27 PM
Points: 77, Visits: 535
Chris Stride (2/25/2011)
Dear All,

I can't get the SQL Agent service to start. When I go into the SQL Server Configuration Manager and select the properties of the Agent service and try to change the start mode from 'Disabled' to 'Manual', it comes back with the following error message after a few seconds:

"WMI Provider Error

The remote procedure call failed. [0x800706be]"



Is the problem that it cannot start or is the problem that the SQL Agent Service is disabled?

Have you tried adding the Service Account to the local Admin group?

see my post here:
http://www.sqlservercentral.com/Forums/Topic1065809-391-1.aspx

If you are receiving errors related to WMI, it could be that either it cannot communicate with WMI or it's corrupted. SQL Agent needs to talk to WMI to log event viewer events.
Post #1069876
Posted Monday, February 28, 2011 4:13 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, December 10, 2012 3:20 AM
Points: 23, Visits: 133
Thanks for your response MiguelSQL. Unfortunately adding the Service Account to the local admin group didn't work. Fails with the same error message.

What I want to achieve is to be able to start the SQL Agent, however I need to be able to set it's Start Mode from 'Disabled' to either 'Manual' or 'Automatic' first. In trying to do that, I get error above.
Post #1070412
Posted Monday, February 28, 2011 4:49 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, December 10, 2012 3:20 AM
Points: 23, Visits: 133
Quick update: Rather bizarrely, I've just discovered, in desperation, that I CAN change the start up mode (and hence start) the SQL Agent via Services in the Control Panel.

Given it wouldn't allow me to do this via the SQL Configuration Manager, which is where I usually do this kind of thing, I had assumed there was no way I would have been able to do this via the Control Panel and didn't try earlier! Although it doesn't solve the issue of the error message, at least I can get on with the agent work!
Post #1070424
Posted Friday, March 25, 2011 4:29 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, March 25, 2011 4:24 AM
Points: 1, Visits: 2
Thanks for posting that Chris. I just had that problem with the SQL 2008 32-bit Developer edition.

It threw the same error when trying to un-disable it through SQL Server Configuration Manager, but once enabled through services.msc, it behaved normally again.
Post #1083873
Posted Tuesday, April 05, 2011 7:22 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, April 30, 2013 2:34 PM
Points: 2, Visits: 128
I am having a similar issue. I have SQL 2008 R2 enterprise edition. SQL Agent will not start. The service account is the same account that I am logging into the server with. It has admin rights on both the OS and SQL instance. When trying to start the agent I gett the following error in the SQL Agent log:

2011-04-05 09:03:42 - ! [298] SQLServer Error: 18456, Login failed for user 'DOMAIN\SERVICE_ACCOUNT'. [SQLSTATE 28000]
2011-04-05 09:03:42 - ! [000] Unable to connect to server 'HOST\INSTANCE'; SQLServerAgent cannot start
2011-04-05 09:03:44 - ! [298] SQLServer Error: 18456, Login failed for user 'DOMAIN\SERVICE_ACCOUNT'. [SQLSTATE 28000]
2011-04-05 09:03:44 - ! [382] Logon to server 'HOST\INSTANCE' failed (DisableAgentXPs)
2011-04-05 09:03:45 - ? [098] SQLServerAgent terminated (normally)

The service account is also the same for the SQL Server Instance which starts with no issues. Additionally, I have another instance of SQL on this box with the same configuration that does not have any issues.
Post #1088597
Posted Tuesday, August 09, 2011 2:23 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 3:59 PM
Points: 46, Visits: 210
Same problem here, but I was able to change the startup type and start the agent from the services console. Thanks.
Post #1157266
Posted Tuesday, November 01, 2011 3:00 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, February 19, 2013 12:44 PM
Points: 4, Visits: 97
I had the same experience on a Windows 2008 R2 box hosting a SQL 2008 R2 64-bit standard install.

By changing the SQLAgent start mode through Windows Services had easily rectified this problem.

Thanks for your advice

Post #1198978
Posted Sunday, February 05, 2012 10:35 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, March 06, 2012 11:46 AM
Points: 3, Visits: 24
faced same issue @ morning, got it resolved through services.msc . But whats the reason behind dis stuff where configuration manager fails to start the services but services.msc does???
Post #1247077
Posted Saturday, April 28, 2012 12:56 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:06 PM
Points: 23, Visits: 173
Thanks Chris, same issue, same resolution. Agent wouldn't start and threw this error whether I tried to change startup type via configuration manager or though management studio(failure not surprising as it was disabled. Through services no problems.
Post #1291982
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse