August 20, 2013 at 11:31 am
I failed over our Cluster (SQL 2008 R2) and the SQL Agent did not start (AgentXPsDisabled)... I ran this script which brings SQL Agent online, but ALL the jobs "Next Run" is set to "Not scheduled"
EXEC sp_configure 'allow updates', 0
RECONFIGURE
go
-- then:
sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure 'Agent XPs', 1;
GO
RECONFIGURE
GO
EXEC sp_configure 'allow updates', 0
RECONFIGURE
I tried restarting SQL Agent from the SQL Server Config Manager but to no avail. Thoughts?
August 20, 2013 at 1:16 pm
Look at the SQL Server Agent error log (separate from SQL Server error log); there will (should) be more info there on why Agent could not start.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
August 20, 2013 at 11:56 pm
You mention the instance is installed on a cluster. In a cluster you need to start the Agent Service by starting the SQL Agent Cluster Resource in Cluster Administration.
October 15, 2013 at 5:59 am
Also -- Check the SQL Server ERROR LOG to verify your DB's are NOT "IN RECOVERY" state -- specifically the distribution DB, as this will delay the job scheduler NEXT RUN seeds. (fyi, if you view the SQL Agent ERROR LOG, it may say "waiting for databases to recover")
Our distribution db was IN RECOVERY for 2 hours after a failover to NODE 2 in a cluster. Once the recovery completed, the job scheduler dynamically populated the NEXT RUN values for all jobs.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply