Share via

Error 25156. Failed to create MOM database error when installing SCOM 2007. Error Code: -2147217900.

  • Article

You may experience this error when installing the SCOM database to a SQL 2005 cluster.

**Run the installation on the SQL node that hosts the Virtual Node**  

 

clip_image001

 

This error is caused when SQL 2005 is missing disk dependencies within the SQL 2005 Group. 

 

The Fix:

1.  Within the cluster administrator take the SQL group offline.

 

**If the disks are missing you MUST take the SQL group offline in order for any "new" disks to be recognized. You will not be prompted to take it offline either.... :(

 

2.  Properties of SQL server - Dependencies tab -> make sure that all disks are listed.

 

You should have a SQL Network name dependency, and the Physical disk should be listed here as well.

 

3.  If the disks are not there - add them - bring the cluster back on-line

4.  Re-run the SCOM installation

 

*** For additional Information Please refer to:

https://technet.microsoft.com/en-us/library/bb381402.aspx

 

>edwalt

Comments

  • Anonymous
    October 25, 2007
    I have that problem on a stand alone machine..

  • Anonymous
    December 13, 2007
    http://moreaboutmen.com/genre/rock-alternative/g307/  ,http://moreaboutmen.com/genre/rock-alternative/g307/

  • Anonymous
    January 17, 2008
    I do have this on a standalone machine as well...

  • Anonymous
    January 17, 2008
    i have to admit, I had a "-" in the DB name, that led to this error.

  • Anonymous
    February 29, 2008
    aSR8f6 r u crazzy? I told u! I can't read!

  • Anonymous
    March 01, 2008
    iCrR5C r u crazzy? I told u! I can't read!

  • Anonymous
    March 06, 2008
    9OZPTR r u crazzy? I told u! I can't read, man!

  • Anonymous
    March 06, 2008
    jDKvFy r u crazzy? I told u! I can't read!

  • Anonymous
    March 07, 2008
    1nRu6t r u crazzy? I told u! I can't read!

  • Anonymous
    March 07, 2008
    ibtDPO r u crazzy? I told u! I can't read!

  • Anonymous
    March 07, 2008
    G36VRJ r u crazzy? I told u! I can't read!

  • Anonymous
    March 08, 2008
    sl5hSH r u crazzy? I told u! I can't read!

  • Anonymous
    March 08, 2008
    OP48I4 r u crazzy? I told u! I can't read!

  • Anonymous
    March 08, 2008
    im37Ae r u crazzy? I told u! I can't read!

  • Anonymous
    April 15, 2009
    I found that since I was doing an dvanced setup and placing these in folders that were not already created it failed. Once I pre-created the folders for data and logs it installed perfectly. this is on Windows 2003 R2 x64 Ent SP2 single server with SQL 2005 x64 SP2

  • Anonymous
    May 12, 2009
    My fix was same as the previous post.  I didn't have a standalone server, but wasn't installing the datawarehouse in a cluster server.  All I needed to do was manually create the path and the install was fine.  

  • Anonymous
    October 20, 2009
    I found this is a problem when using the advanced options in the installer. You must first create the log and data sub-directories when running the advanced install with SCOM / Reporting. Windows Server 2008 x64 / Sql 2005 x64 - Standalone System Center

  • Anonymous
    January 27, 2010
    I had the same problem, using the advanced option. Creating the folders prior to the installation solved it. Thanks Guru!!!