Access denied (MicrosoftSQL-DMOODBCSQL status: 42000) Solution

Error 22002: RegCreateKeyEx () Error 5 returned, Access Denied (MicrosoftSQL-DMOODBCSQL status: 42000) SQLServer2000 in order to meet the minimum permission requirements, the start accounts of SQLServer and SQLAgent are usually changed to LocalWindowsUseraccount, later, I went to EnterpriseManagerconfig to set some configurations.

Error 22002: RegCreateKeyEx () Return Error 5, Access Denied (Microsoft SQL-DMO odbc SQL status: 42000) SQL Server 2000 to meet minimum permission requirements, generally, the SQL Server and SQL Agent Startup accounts are changed to the Local Windows User account, and then some configuration settings in Enterprise Manager config are modified.

Error 22002: RegCreateKeyEx () returned error 5, Access Denied (Microsoft SQL-DMO odbc SQL status: 42000)
SQL Server 2000
To meet the minimum permission requirements, both the SQL Server and SQL Agent Startup accounts are usually changed to Local Windows User accounts. This error message is displayed when you go to Enterprise Manager config for some configuration settings, go home and repeat the MCSE Training Kit-SQL Server 2000 System Administrator. It may be a problem with the Server code permission. It is fixed and provided for your reference.

[Status]
After changing the SQL Server startup account to a general local user account or domain user account,
Go to Enterprise Manager to set the SQL Server attribute (configuration) and set the SQL Server or SQL Server
This error message is displayed when [automatic start] is selected for the Agent.

[Cause]
You can use Enterprise Manager to modify the SQL Server startup account. Although the startup account can be automatically granted the necessary permissions, you must modify the logon file to exclude this error message.

[Solution]
1. Start the logon file editor.
2. Back up the logon file before modification
3. Locate the following locations
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ MSSQLServer
If the name is an individual
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ MSSQL $ InstanceName

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ SQLSERVERAGENT
If the name is an individual
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ SQLAgent $ InstanceName

4. Right-click the above Code and select [permission] to add a new set SQL Server startup account. The permission is set to [full control].
After the SQL Server is automatically started in the Enterprise Manager check box, the error message should no longer appear.