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

KB925644 - https://support.microsoft.com/?id=925644

 

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'.

 

 

Please see the KB article link above for full details. This is an issue PSS have seen numerous times and is typically corrected by registration of the SQLDMO.DLL.