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**
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:
http://technet.microsoft.com/en-us/library/bb381402.aspx
>edwalt
I have that problem on a stand alone machine..
http://moreaboutmen.com/genre/rock-alternative/g307/
,http://moreaboutmen.com/genre/rock-alternative/g307/
I do have this on a standalone machine as well...
i have to admit, I had a "-" in the DB name, that led to this error.
aSR8f6 r u crazzy? I told u! I can't read!
iCrR5C r u crazzy? I told u! I can't read!
9OZPTR r u crazzy? I told u! I can't read, man!
jDKvFy r u crazzy? I told u! I can't read!
1nRu6t r u crazzy? I told u! I can't read!
ibtDPO r u crazzy? I told u! I can't read!
G36VRJ r u crazzy? I told u! I can't read!
sl5hSH r u crazzy? I told u! I can't read!
OP48I4 r u crazzy? I told u! I can't read!
im37Ae r u crazzy? I told u! I can't read!
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