-
Title
Error: "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'" -
Description
Capacity Manager collect data jobs fail with error message:
Msg 18456, Level 14, State 1, Line 4 Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.or
Executed as user: <user name> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
-
Cause
User account has insufficient privileges on the target instance to execute the jobs.
OR
User account running the job has insufficient read/write priveleges on the CM Repository DB.
It is possible that the database has been upgraded (e.g. from 2005 to 2008) after the creation of CM jobs.
-
Resolution
1.) If jobs are executed according to a schedule, they are run under the SQL Server Agent account. In that case it is this user account with insufficient privilege.
2.) If the jobs are executed manually, the job is run under the account you are using to connect to SQL Server.
Visit the user permissions according to 1.) or 2.) and ensure it has sufficient privileges as per the Installation Guide for creating/executing Collect Data jobs and read/write on the CM Repository DB. Also check there are no 'deny' access privilege levels on the monitored objects and instance.
3.) if the problem is caused by permissions on the CM Repository DB, then the user account (1. or 2. above) needs read/write permissions.Alternatively, convert the Repository connection to SQL Authentication. The Create/Select Repository Wizard will create a new login called qcm_agentlogin with read/write permissions on the Repository. Make sure this login exists with read/write access, from the monitored server, on the CM Repository DB.
If database has been upgraded, all existing CM jobs will have to be removed and new ones created.
-
Additional Information
To remove old collect data jobs;
- Open Command Line dialog: Start | Run: cmd
- In command line go to the directory where Capacity Manager console is installed
- Then run: CapacityManager.exe /NOENCRYPT
- Capacity Manager console will open
- Run Collect Data Wizard
- Uncheck collecting for the problem instance and go to the end of the wizard -> as a result collect data job and stored procedures will be removed from the problem instance.
- Run Collect Data Wizard again and check collecting for the problem instance -> as a result collect data job and no encrypted stored procedures will be created on the problem instance.