asked on

SQL Server 2012 SP1 on Windows 2012 cluster core cluster- SQL agent issue

I cannot create/edit/delete sql agent jobs. I am getting the following errors

Msg 14258, Level 16, State 1, Procedure sp_is_sqlagent_starting, Line 9
Cannot perform this operation while SQLServerAgent is starting. Try again later

a. Yes. I restarted the agent many times. failed to different node
b. Yes. Agent XP is enabled
c. Yes. SQL server is not on fibre mode
d. Yes. I tried sp_delete_job sp_create_job

No error messages on event log

Please help

Haresh Nikumbh

have you tried this ?

http://social.msdn.microsoft.com/Forums/en-US/sqltools/thread/4265278f-8d0e-4cf3-87db-ed9b037e6cc3

Matt Bowler

Can you confirm the status of the agent?

EXEC xp_servicecontrol N'querystate',N'SQLServerAGENT'

Can you also review the SQL Agent error logs?

MAK999

ASKER

1. Query State is : Running.
2. http://support.microsoft.com/kb/303287/en-us is not applicable
3. MSDTC is running on the active node and tried moving around.
4. SQLAgent is running under service account. Yes. it is local admin to all the nodes.
5. Nothing odd in sql server agent log. Some errors due to the fact that those features are not installed.

2013-05-15 05:06:55 - ! [125] Subsystem 'ANALYSISQUERY' could not be loaded (reason: A dynamic link library (DLL) initialization routine failed)
2013-05-15 05:06:55 - ! [125] Subsystem 'ANALYSISCOMMAND' could not be loaded (reason: A dynamic link library (DLL) initialization routine failed)
2013-05-15 05:06:55 - ! [125] Subsystem 'SSIS' could not be loaded (reason: A dynamic link library (DLL) initialization routine failed)

MAK999

ASKER

Some more information

declare @i int 
exec xp_sqlagent_is_starting @i output 
print @i

Open in new window

--Returns 1

exec xp_sqlagent_enum_jobs 1,''

Open in new window

--Returns "SQLServerAgent is not currently running."

Actual SQLServer Agent on the cluster is up and running. I can query msdb tables.

ASKER CERTIFIED SOLUTION

MAK999

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Matt Bowler

That's good news. I was about to suggest that something was not right with the installation. The ability to query msdb tables is independent of the agent running, and those errors are not normal.

MAK999

ASKER

resolved.