Microsoft Knowledge Base Email Alertz

(885734) - Describes a problem that may occur when you try to install MOM 2005 on a computer that has been upgraded to Windows Server 2003. You may receive the Database setup fails with Error Code -2147221164 (Class not registered) error.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 885734 - Last Review: October 25, 2006 - Revision: 1.1

"Failed to create MOM database" error when you try to install MOM 2005 on a computer that has been upgraded to Windows Server 2003

SYMPTOMS

When you try to install Microsoft Operations Manager (MOM) 2005 on a computer whose operating system has been upgraded from Microsoft Windows 2000 to Microsoft Windows Server 2003, you may receive the following error during the MOM 2005 Setup program:
Failed to create MOM Database. Error Code -2147221164 (Class not registered)

CAUSE

This problem typically occurs after you upgrade a Windows 2000-based computer to Windows Server 2003. When you upgrade to Windows Server 2003, the version of the Oledb32.dll file that is located in both the WINNT\System32\Dllcache folder and the Program Files\Common Files\System\Ole DB\Oledb32.dll folder on the Windows 2000-based computer is not upgraded to the version of the Oledb32.dll file that is included in Microsoft Data Access Components (MDAC) 2.8.

WORKAROUND

To work around this problem, first determine which version of the Oledb32.dll file currently resides in both the WINNT\system32\dllcache folder and the Program Files\Common Files\System\Ole DB folder. If the Oledb32.dll file has not been upgraded correctly, overwrite the file with a version that is copied from a computer that has MDAC 2.8 installed. To do this, follow these steps:
  1. Right-click Start, and then click Explore.
  2. In Windows Explorer, locate the Oledb32.dll file in the following folders:
    • DriveLetter\WINNT\System32\Dllcache
    • DriveLetter\Program Files\Common Files\System\Ole DB
  3. Right-click one of the Oledb32.dll files, and then click Properties.
  4. In the Oledb32.dll Properties dialog box, click the Version tab, and then note the version number that is next to File version.
  5. Repeat steps 3 though 4 for the other Oledb32.dll file.
  6. If the file version number for the Oledb32.dll files is 2.71.9042.0 or earlier, overwrite the Oledb32.dll files with the Oledb32.dll file that is included in MDAC 2.8. The Oledb32.dll file that is included in MDAC 2.8 is version 2.80.1022.0. To do this, copy the Oledb32.dll file from a computer that has MDAC 2.8 installed and overwrite the older files. Make sure that you verify that the Oledb32.dll file is the correct version. To do this, repeat steps 1 through 6.

REFERENCES

To download MDAC 2.8, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=en)

APPLIES TO
  • Microsoft Operations Manager (MOM) 2005
Keywords: 
kbtshoot kbprb KB885734
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Terry Fedirko - terry.fedirko NOSPAM-AT-NOSPAM reuters.com Reported as Irrelevant  
Written: 2/9/2006 9:44 AM
This procedure works but did not solve my problem. I follow this procedure to a tee but still get the same error. My System is Window Server 2003 with the latest SP and Security patches also MS SQL 2000 is installed with the Reporting Services that has the lastest Service Pack installed. Also MDAC 2.8 has been installed and OleDB32.Dll version is set to 2.82.1830.0. A response to this comment would be greatly appreciated.