Thursday, August 19, 2010

Tips for troubleshooting SQL Agent Error: 15281

Tips for troubleshooting SQL Agent Error: 15281
Chris Skorlinski
Microsoft SQL Server Escalation Services
We encountered an interesting problem the other day I thought I would post on ReplTalk.  Customer call when they noticed the SQL Server Agent resources in their SQL 2008 clustered installation would not start.  The following error appeared in the Windows Application and System Event log.
Windows Application Event Log
SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect
to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
[sqagtres] StartResourceService: Failed to start SQLAgent$SQL2K5 service.  CurrentState: 1
[sqagtres] OnlineThread: ResUtilsStartResourceService failed (status 435)
[sqagtres] OnlineThread: Error 435 bringing resource online.
Windows System Event Log
The Cluster service failed to bring clustered service or application 'SQL Server (SQL2K5 )' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Cluster resource 'SQL Server Agent (SQL2K5 )' in clustered service or application 'SQL Server (SQL2K5 )' failed.
We also looked in the MSSQL\LOG folder for SQL Server to see what error messages SQL Server Agent was reporting.  Here is where we noticed Error: 15281.
Read more: REPLTalk covers Using and Tuning SQL Replication