November 5, 2009 at 12:34 pm
Hi everyone,
I am doing a clean install of SQL 2008 Enterprise edition on a Windows Server 2008 R2 Enterprise machine. 64-bit. I ran the install for the first time and i was getting errors that I came to find out by searching posts and forums that I needed to apply SP1 before installing SQL Server 2008. So I tried to run the SP1 but it complained about detecting a failed installation. So I uninstalled SQL 2008 and made sure all the files and registry were clean. I installed SP1, which ran okay, then ran the SQL 2008 install again. This time the install went okay but at the very end, I got this error message:
"The MOF Compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as a failure of the WMI server to start"
I had the sysadmin check WMI and she checked permissions, uninstalled/installed it. It is up and running and everything looks okay. I try to rerun the SQL 2008 install and get the same error.
I have been pouring over posts and forums of others that are getting this error too and some solutions pointed to the problem is from installing and uninstalling SQL 2008 multiple times:
"From the setup logs it appears that the machine might have prior failed attempts of installing the same instance multiple times. This in turn, caused the subsequent installs to not create MOF files needed to register the WMI providers."
Has anyone seen this error? Any suggestions on how to fix it?
Thanks! 🙂
Thanks!
Bea Isabelle
November 12, 2009 at 8:32 am
Im guessing the WMI service is running?
Also check that you have IIS installed.
November 12, 2009 at 12:28 pm
Hi,
Thanks for the reply. Yes, both WMI and IIS were checked....stopped/restarted....uninstalled/installed. Still get the same error. :blink:
Isabelle
Thanks!
Bea Isabelle
November 13, 2009 at 3:05 am
Even if you get past this problem, you have a server build that has shown an instability and may have more that you have not yet found. Also you have a server build you (hopefully) will be unable to repeat if you need to rebuild this machine. This may be OK for a personal sandbox situation but is bad news for any server that will take other people's workload.
My advice is to reformat your system disk and start again with a clean Windows install. Now that you know how to get the SQL cluster installed you should avoid this problem next time.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply