Grab our RSS feeds Follow us on Twitter Join our Facebook Group Connect with us on LinkedIn
myITforum.com, Powered by You.
you are not logged in

Articles

Newslinks

Links

Downloads

Site Services

Community Forums

Discussion Lists

Article Search

Newsletter

Web Blogs

FAQs

Live Support

myITforum TV

Take a Poll

Monthly Drawing

myITforum Network

User Group Directory

Our Partners

About Us

Register

Login

BRONZE PARTNER:

BRONZE PARTNER:



Industry News:




  Home : Articles : SMS 2.x print | email | | Forums |   print | email | | Blogs |   print | email | | Wiki |   print | email | | FAQs |   print | email | Article Search  
Failed to open MOM Administrative Console after SP1


Bookmark and Share

By: Nissim Ben-Maor
Posted On: 1/30/2003

Many people come across the following errors when they try using the MOM admin Console on a remote machine after they upgrade to SP1:

First Error: (See figure 1)

Failed to connect to the database on 'X'. Class not registered.
Clicking on Details:
0x80040154: Class not registered.

Second Error: (See figure 2)

Failed to retrieve the DAS server name.
Clicking on Details:
Class not registered
Result code: 80040154

Figure 1 - Failed to connect to the database Error







Figure 2 - Failed to retrieve the Das server name Error







It is also possible that you will get a Snap-in failed to initialize error and the MMC MOM Admin Console will close.

Figure 3 - Snap-in failed to initialize Error







Some times after clicking the OK button - will eventually open the MOM Admin Console but you will cross more other errors pop-up messages.


Reason:

This will happen when using a MOM Version 1.0 Admin Console to connect to a MOM SP1 database.
Database changes forced the removal of the DAS Locator COM object in order to support Database installation on Cluster.
It is this object that allowed the MOM Version 1.0 Admin Console to connect successfully to the database.


Solution:

Upgrade the MOM Admin Console on the remote computer to MOM Admin Console Service Pack 1 Version.


How will I identify MOM installation Version?

There are many methods in order to find which MOM installation version you are using.
In my next article I will post most of them, in the mean time here is one method you can use in order to check your MOM installation Version.

Using Regedit.exe

Note: Is it strongly recommended to backup your registry before using Regedit.exe

The different between MOM with SP1 is a new DWORD key in the registry named "Service Pack" with Value = 1.

In MOM Version 1.0 you will not find this key.

The following section will instruct you how to use Registry Editor in order to determent what is you MOM version:

  1. Open the Registry Editor by running the command line:

    Regedit.exe

  2. On the right pan navigate to the following key:

    HKLM\Software\Mission Critical Software\OnePoint\Configurations\Default\McsApplications\Operation Manager\Install

  3. MOM version 1.0 installation: (See figure 4)

    - On the right pane you cannot find a DWORD key named "Service Pack".
    - Look at String key named "VersionNumber" verify the Value is lower then "4.00.1300.0"

    Figure 4 - MOM version 1.0 installation (Without the Service Pack DWORD key)





  4. MOM SP1 version installation: (See Figure 5)

    - On the right pane look for DWORD key named "Service Pack"
    - The String key named "VersionNumber" is equal or greater then "4.00.1300.00"
    Close Registry Editor

    Figure 5 - MOM Version SP1 (With the Service Pack DWORD key)








I hope this article has been informed to you.

Any suggestions or questions are more then welcome and you can post them in the myITforum Article Discussions Forum or drop me an email.
The MOM forum is also a good place to find assistance with MOM issues.

Nissim Ben-Maor

  myITforum.com ©2010 | Legal | Privacy