[Company Logo Image] 

Home Up Contents Coffee Break Credits Glossary Links Search

 
Warning Event ID 208

 

 

Home
Analysis Services
Azure
CLR Integration
High Availability
Open Source
Security
SQL Server 2008
SQL Server 2012
SQL Server 2014
SQL Server 2016
Tips
Troubleshooting
Tuning

Warning Event ID 208.


Applies to: Microsoft SQL Server 2005 Developer Edition

 

Error Message.

Event Type:          Warning
Event Source:        SQLSERVERAGENT
Event Category:     Job Engine
Event ID:              208
Date:                   1/25/2008
Time:                   12:35:01 AM
User:                    N/A
Computer:             ClusterSQL
Description:
SQL Server Scheduled Job <job name> (0x141D83565CD2EA46BAFF2679B78A882F) - Status: Failed - Invoked on: 2008-01-25 00:35:00 - Message: The job failed. Unable to determine if the owner <user name> of job <job name> has server access (reason: SQL Server blocked access to procedure 'dbo.sp_sqlagent_has_server_access' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online. [SQLSTATE 42000] (Error 15281)).
 



Problem Description.

We ran into this warning message on a 2-node cluster, when we changed the service account used by the SQL Server Agent service for a new one without restarting the service, in consequence two jobs that run every minute started to fail.

This warning is also logged for other reasons, please refer to error MSSQLSERVER Event ID 3041.


Solution.

Restarting the SQL Server Agent service and then running the jobs solved the problem.  Considering that both service accounts, the old one and the new one, had the same rights, permissions and privileges.

 


 

 

.Send mail to webmaster@sqlcoffee.com with questions or comments about this web site.