Today I wanted to install my OperationsmanagerDB on my SQL cluster 2005 SP2 actif-passive.
So I started the DBCreatewizard.exe and I got a very strange error mentioning something about
Severity: Error Message: Database creation failed. The database might have been incompletly created or modified. System.InvalidOperationException: An error occurred while trying to create the database on your SQL Server. Check your logs for more information. at Microsoft.EnterpriseManagement.Setup.DBCreateWizard.Program.LaunchDBCreation() at Microsoft.EnterpriseManagement.Setup.DBCreateWizard.SummaryPage.BackgroundThread()
To make a long story short:
We had a lab environment and production environment. Both environments are exact replicas: ip, users, servers, everything is the same. I did the install in the lab environment on my sql cluster and didn’t encounter any problems.
Now in production I had this strange error and asked my dba (that installed the sql cluster in lab and production) to confirm that everything was ok and that everything was the exact replica of the lab….
Now here comes the catch….and also the moment I wanted to kill my DBA….
I analyzed the dbcreatewizard error log that you can find here:
C:Documents and SettingsuserLocal SettingsTemp1
And found the following sentence
10:31: CreateDB: Attempting to create OperationsManager on ELSQL3EWSSCOM threw the following sql exception Cannot use file ‘J:SCOMOPLOGOperationsManager.ldf’ for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.
I checked on my cluster resource and indeed: the Log disk was missing as a dependency!!
So my production environment was not the exact replica as my lab environment. I had to add the Log file disk as a dependency for my sql resource group:
And now I was able to run the dbcreatewizard.exe succesfully!
Hope this helps,