SQL Express 2008 Installation error

Question

I am attempting to install SQL Express 2008 on a laptop running XPProSP2.  The System Configuration Checker fails at the WMI Service rule.  I checked and the WMI service is running.

 

Any help troubleshooting would be greatly appreciated.

 

adaniel3

Answer 1

Could you please provide the whole error. Best think would be to post the setup logs here (look out for the part with return value 3, which indicates the error)

 

Jens K. Suessmeyer

 

Answer 2

This is my first attempt at installing SQL, so I am unfamiliar with the directory structure.  Please let me know where to find the setup logs.

 

Thanks,

adaniel3

Answer 3

%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG

 

Jens K. Suessmeyer

Answer 4

Jens,

 

I tried to copy/paste the log here, but apparently it is too large; and I see no way to attach a file.  What do you suggest?

 

Thanks for you help.

 

adaniel3

Answer 5

Well, either search for the "return value 3" section, or use an external file hoster like R***dshare.

 

Jens K. Suessmeyer

Answer 6

Ok, I am back after having tried everything under the sun to resolve my problem.  I am sorry to appear such an idiot, but I cannot find any files that contain "return value 3".  It appears that every time I exit the SQL installer and go back to it, it creates another folder on my c drive.  Nothing anywhere that I can find points me to the log files containing the info requested.  And I do not know what R***dshare is.

I have tried installing SQL Express 2005 and it has the same problem.  I run the System Configuration Checker.  It tells me the Windows Management Instrumentation (WMI) Service failed.  When I click on the Failed link under status, I get an error window which says:

Rule "Windows Management Instrumentation (WMI) service" failed.

The Windows Management Instrumentation (WMI) service cannot be started.  To continue with the installation you
must troubleshoot and repair your Windows Management Instrumentation (WMI) service.


That's very helpful. Thank you Microsoft.  No link to a troubleshooter.

When I run services.msc,  the Windows Management Instrumentation (WMI) service has a status of Started and a Startup Type of Automatc.

When I click the "View detailed report" link on the SQL Server 2008 Setup/Setup Support Rules window, it takes me to a file

c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081124_142038\SystemConfigurationCheck_Report.htm

which tells me:

Rule Name		Rule Description	Result	Message/Corrective Action
GlobalRules: SQL Server 2008 Setup configuration checks for rules group 'GlobalRules'
	WmiServiceStateCheck	Checks whether the WMI service is started and running on the computer.	Failed	The Windows Management Instrumentation (WMI) service cannot be started. To continue with the installation, you must troubleshoot and repair your Windows Management Instrumentation (WMI) service.

which is no more information than I already had.  Thanks again, Microsoft.

I used the community link at the bottom of that page to get here, and here I am stuck.  If I sound frustrated, I am.

Any help anyone can give me to get me out of this viscious circle would be greatly appreciated.

adaniel3

Answer 7

Maybe my expectations are unreasonable.  Could someone please let me know if anyone is looking at this who has the knowledge to help me, and if so, why I am getting no responses?

Thanks to anyone who can help.

adaniel3

Answer 8

Hello,

While WMI may appear to be running on your server, it is possible that the service is corrupt.  This can be determined easily enough by opening up the "Dependencies" tab for WMI under Services; an error such as "WMI: Initialization Failure " may be thrown.

A solution to this would be to reinstall the WMI service.  This can be done by creating a batch file with the following contents and then executing:

@echo on
cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
for %%i in (*.dll) do RegSvr32 -s %%i
for %%i in (*.exe) do call :FixSrv %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
net start winmgmt
goto End

:FixSrv
if /I (%1) == (wbemcntl.exe) goto SkipSrv
if /I (%1) == (wbemtest.exe) goto SkipSrv
if /I (%1) == (mofcomp.exe) goto SkipSrv
%1 /RegServer

:SkipSrv
goto End

:TryInstall
if not exist wmicore.exe goto End
wmicore /s
net start winmgmt
:End

Answer 9

Hi Kanhar,

Thats a serious claim to be made without any documentation. This script is designed to re-register WMI, what part of this script do you believe will corrupt the Windows folder? If you don't have any evidence you should remove this post.

Thanks,
Mike

---

If this post answers your question, please mark it as an Answer - it will help others searching the forum. This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 10

thanks mike,
this script was very helpful and it did not corrupt any of my windows folder.

Answer 11

Thanks, the script works great.  But I had another problem during the process of running your script, that is my vssapi.dll is missing. I have download that dll before I can carry on the script.

Answer 12

Thanks !!!

Answer 13

Hello, I need help with the exact same problem.

We have a Windows Server Web edition (6.0.6002) and MS SQL 2008 Express R2 won't install:

"Windows Management Instrumentation (WMI) - FAILED" please check the service is running... etc.

The OS and the SQL server are both 32 bit versions.

WMI is running.

Tried restarting the Web Server / Tried re-starting the service.

Tried the script listed here but it wouldn't  make the WMI problem disappear.

Tried MS SQL 2005 Express as well. Throws the same error: WMI error.

Any help guys?

 

The WMI tester throws errors:

.1610 15:43:32 (1) !! ERROR: The following WMI system file(s) is/are missing: ............................................................. 3 ERROR(S)!

.1611 15:43:32 (0) ** - C:\Windows\System32\WBEM\framedyn.dll

.1612 15:43:32 (0) ** - C:\Windows\System32\WBEM\provthrd.dll

.1613 15:43:32 (0) ** - C:\Windows\System32\WBEM\wbemcomn.dll

.1614 15:43:32 (0) ** => Recopy from a working system the missing WMI system files to 'C:\WINDOWS\SYSTEM32\WBEM\'

 

But something doesn't seem to check out since I looked at two of our other Windows Web Server 2008 installations and none of them seem to have these files so it's not like they are really missing.

Does Windows Web Server 2008 not support MS SQL installations?

Answer 14

thanks mike,

this script was very helpful and it solved the same problem occured of WMI while installting SQL server 2008 on my machine.

thanks,

Amit Jain 

Answer 15

Thanks AngryDavie and Kyanzes,

I had executed the batch file and after a restart my computer solved the WMI problem successfully

May be the problem was with Remote Procedure Call (RPC), any idea?

---

SQL Server and T-SQL Tutorials
SQL Server 2011 Features
Our true mentor in life is science

Answer 16

Thank you AngryDavie, it really resolved my problem while installing SQL server Enterprise edition on my windows XP... It really works...

Answer 17

Thank you very much for providing this script. I was having the same issue and it solved my problem.

Answer 18

Hello,

While WMI may appear to be running on your server, it is possible that the service is corrupt.  This can be determined easily enough by opening up the "Dependencies" tab for WMI under Services; an error such as "WMI: Initialization Failure " may be thrown.

A solution to this would be to reinstall the WMI service.  This can be done by creating a batch file with the following contents and then executing:

@echo on
cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
for %%i in (*.dll) do RegSvr32 -s %%i
for %%i in (*.exe) do call :FixSrv %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
net start winmgmt
goto End

:FixSrv
if /I (%1) == (wbemcntl.exe) goto SkipSrv
if /I (%1) == (wbemtest.exe) goto SkipSrv
if /I (%1) == (mofcomp.exe) goto SkipSrv
%1 /RegServer

:SkipSrv
goto End

:TryInstall
if not exist wmicore.exe goto End
wmicore /s
net start winmgmt
:End

I Sign up in this forum ... only to say :: thank you alooooooooooooooooottttttttttttt

Answer 19

Works a treat - thank you very much.

Answer 20

AWESOME. Thanks

Answer 21

Angrydavie, YOU ARE JUST AWESOME!!!!!

Thanks a lot!

Answer 22

Angrydavie Thanks for sharing. It resolved my exact same problem...

Answer 23

Thnx Angrydavie.It solved my problem too.

Answer 24

Hi mike,

 

im having the same problem. what would be the possible solution. i badly need it. thanks mike.

 

Thanks,

Neil

Answer 25

hi angrydavie,

 

how do i start batch file? i don't know hot to start the process.  please let me know.

 

Thanks,

Neil

Answer 26

Thanks a billion!

Answer 27

I Recently encountered the same issue. running the batch script solved the issue. Thank you

-Koti

---

Kotig

Answer 28

The bat file worked for me thanks.

Answer 29

thanks alooottt.....!!!!

 

super likes to ur post.....

 

after running ur batch file its working fine....!!!

People who dosnt know to create a batch file follow this

 

copy and paste above script and save it as .bat

 

thanks again angry davie.........!!!!

Answer 30

thank you Angrydavie very much, it helped a lot

Answer 31

Thank you very much Angrydavie, it helped a lot!

Answer 32

I had the exact same issue and running this script worked for me.

Thanks TMC

Answer 33

worked like a charm

thanks alot

Answer 34

Angrydavie - this worked great!! Thanks!!

Answer 35

I know that this post is long since dead, but thanks so much for this.  This has frustrated me to no end!!!  I did have to attempt the batch file a few times before all of the modules registered.

Thanks again,

Ray

Answer 36

THIS WAS AMAZING! THANK YOU.

Answer 37

AngryDavie is my hero !

Worked like a charm.

Thanks.

Answer 38

I agree -- this batch file, performing steps that logically should have been part of ordinary Windows install, fixes a frequently encountered bug! We've seen it on 5-10 XP, 32-bit machines so far.

Paul T.