Yes, it is SQL Server 6.5 which is really antique. The scheduled tasks in the SQL Executive (now known as jobs and SQL Server Agent) refused to run. Turning on error logging on the SQL Executive which generates the SQLEXEC.OUT file provided useful information to solve the problem. The following error was logged inside SQLEXEC.OUT.
1/5/2012 10:38:44 AM - + DBLib Message Handler: Login failed- User: deInfoTech\sqlsvr Reason: Not defined as a valid user of a trusted SQL Server connection.
1/5/2012 10:38:44 AM - ! DBLib Error Handler: Login incorrect.
I verified that deInfoTech\sqlsvr is a member of the local Administrators group of the server so it should have admin rights.
Then I tried to logon to SQL Security Manager, I received the following error.
This SQL Server does not support Windows NT SQL Server security stored procedures.
A quick search lead me to INF: How to Troubleshoot SQL Server 6.5 SQL Security Manager Messages. For some reasons, the Full Control rights for the local Administrators group was removed from the HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer key.
I re-granted the rights and restarted the SQLExecutive service. The SQL Executive is back to normal now.
No comments:
Post a Comment