You receive error messages when you install Microsoft Operations Manager 2005 a computer that is running Microsoft SQL Server 2000

View products that this article applies to.

SYMPTOMS

When you install Microsoft Operations Manager 2005 a computer that is running Microsoft SQL Server 2000, you receive error messages that resemble the following:

Description: The SQL Server management pack script "SQL Server 2000 Database Health" is unable to successfully connect to the SQL Server instance "MSSQLSERVER". The error message returned is ""
Name: SQL Server 2000 Database Health
Severity: Warning
Resolution State: New
Domain: DomainName
Computer: ComputerName
Time of First Event: 2006-07-12 14:05:00
Time of Last Event: 2006-08-01 02:37:00
Alert latency: 0 sec
Problem State: Active
Repeat Count: 1874 Age:
Source: SQL Server 2000 Database Health:MSSQLSERVER
Alert Id: 5de1229b-a501-4bce-90ce-bac40af14347
Rule (enabled): Microsoft SQL Server\SQL Server 2000\State Monitoring and Service Discovery\SQL Server Database Health

Description: Could not connect using SQLDMO to SQL Instance MSSQLSERVER. However, the instance is currently running.
Name: SQL Server Local Connectivity
Severity: Warning
Resolution State: New
Domain: DomainName
Computer: ComputerName
Time of First Event: 2006-07-12 14:02:00
Time of Last Event: 2006-08-01 02:27:00
Alert latency: 0 sec
Problem State: Active
Repeat Count: 5621
Age:
Source: SQL Server Connectivity MSSQLSERVER Alert Id: 799d83ae-c8f9-4993-93b5-90c788a1f0f5 Rule (enabled): Microsoft SQL Server\SQL Server 2000\State Monitoring and Service Discovery\SQL Server Service Availability

When you try to start the MOM Reporting Console, you may also receive the following error in Microsoft Internet Explorer:

Unable to find script library '/aspnet_client/system_web/1_1_4322/WebUIValidation.js'. Try placing this file manually, or reinstall by running 'aspnet_regiis -c'.

Back to the top

CAUSE

The first two errors that are mentioned in the "Symptoms" section typically occur when the Sqldmo.dll file is not registered.

The third error may occur when the user account that is used for anonymous access does not have the correct permissions. This account must have the permissions that are required to access the MOM 2005 Web Console Web site from the network. This error may also occur when the guest group account does not have the correct permissions to access the computer from the network.

Back to the top

RESOLUTION

To resolve this issue, use one or more of the following methods, depending on the error message that you receive.

Back to the top

Method 1: Register the Sqldmo.dll file

If you receive the first two errors that are mentioned in the "Symptoms" section, follow these steps:

Log on to the computer that is running MOM 2005 and SQL Server 2000 by using an account that has administrative permissions.
Click Start, click Run, type regsvr32.exe sqldmo.dll, and then click OK.
In the Regsvr32 dialog box, click OK.

Back to the top

Method 2: Set the correct anonymous access permissions for the MOM 2005 Web Console Web site

If you use receive the third error that is mentioned in the "Symptoms" section, follow these steps:

Log on to the computer that is running MOM 2005 and SQL Server 2000 by using an account that has administrative permissions.
Click Start, click Run, type Secpol.msc, and then click OK.

Note If the Web server is also a domain controller, you must type Dcpol.msc in the Open box to open the Default Domain Controller Security Settings console.
Under Security Settings, expand Local Policies, and then click User Rights Assignment.
In the right pane, double-click Deny access to this computer from the network.
If the user account that is used for anonymous access is denied access to the Web server from the network, follow these steps:
1. Click the user account that is used for anonymous access.
2. Click Remove, and then click OK.