April SQLExpress CTP Installation fails with error 29535 (WMI not configured properly)

April SQLExpress CTP Installation fails with error 29535 (WMI not configured properly) by TomL

Closed

as Fixed

Type:	Bug
ID:	124587
Opened:	4/24/2005 7:31:45 PM
Access Restriction:	Public
Duplicates:	127237

Workaround(s)

view

User(s) can reproduce this bug

When installing April SQL Server Express CTP, installation fails with error 29535, indicating
something is wrong with WMI:
--------------------------------------------------------------------------------
Machine         : PTOML
Product         : Microsoft SQL Server 2005 Express Edition CTP
Product Version : 9.00.1116
Install         : Failed
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0019_PTOML_SQL.log
Last Action     : InstallFinalize
Error String    : Setup configuration check cannot be executed due to WMI configuration on the computer C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. For details, see the Sqlrunxx.log file or call Microsoft Product Support.
Error Number    : 29535
--------------------------------------------------------------------------------

Installation report shows no problem with WMI:
--------------------------------------------------------------------------------
System Configuration Check

- WMI Service Requirement (Success)
    * WMI Service Requirement
    * Check Passed
.................(continues)
---------------------------------------------------------------------------------

Previous Beta of VSC# and SQLExpress had been installed, but had been removed as per directions before this install was attempted. Uninstall and reinstall, either as part of the VSC# 2005 Beta 2 or SQLEXPR.exe stand-alone gets same error.

Details (expand)

English

SQL Server 2005 Community Technology Preview April 2005 - Express Edition

Setup

Windows XP SP2 Professional

English

+++++ I had to remove old text to allow room for this new text ++++++++++
-->4/28 11:15 I reproduced the problem and ran the mofcomp commmand as you suggested. The output of the mofcomp command shows an 'access denied' error for lines 73-79 in the .mof file; I have no idea what the 'access denied' error means or what's causing it. All the screen captures, log files, etc are in the 'InstanceToShowRunningMof.zip' file attached to this bug report.

4/28 19:37 PM PST -----------------------------
I've had hell with my Direcway satellite connection trying to upload the .zip file with everything in it. I've now broken it apart and have successfully sent up all the small parts. Unfortunately, I cannot get the .zip file of SQL Setup's .cab file uploaded, along with all the other log files. However, if you can tell me which specific file(s) you need, I can try to send them individually.
I apoligize for my ISP; I've spent several hours with them on the phone yesterday and today trying to get these uploads to go. Thanks, Tom.

+++++ I had to remove old text to allow room for this new text ++++++++++
-->4/28 11:15 I reproduced the problem and ran the mofcomp commmand as you suggested. The output of the mofcomp command shows an 'access denied' error for lines 73-79 in the .mof file; I have no idea what the 'access denied' error means or what's causing it. All the screen captures, log files, etc are in the 'InstanceToShowRunningMof.zip' file attached to this bug report.
---->4/29 10:19A PST:
The uploaded file "command window screen capture when mofcomp run while SQL installation 'halted' with error.jpg" is in the .zip file of the same name and shows the output of running the mofcomp command while the installation of SQL was 'halted' on the error; in other words, when the SQL installation stopped with the error message, I ran mofcomp and captured the screen output from the mofcomp command, and then clicked "OK" on the SQL installation error message and let it rollback the failed installation. I found out that if I let the failed installation complete, the 'backout' of the installation seems to clear out everything in SQL's LOG directory.

0 attachments

Posted by Microsoft on 5/2/2005 at 11:28 AM

NULL

Posted by TomL on 5/1/2005 at 4:54 PM

===> 5/1
By using the information you provided about the key "HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\", I was able to change the permission to full permission on that key and all subkeys for owner 'SYSTEM' and the installation successfully ran to completion. I also tried changing to full permission for 'Administrator' but the installation would not successfully complete with that setting.

Thanks for your help. I now know how to circumvent this problem should I have it again.

Posted by Microsoft on 4/29/2005 at 11:34 AM

I found the root cause for the problem. When setup compiles that mof file it creates registry keys and it failed with access denied. There is HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SQL Server\\Services\\ key with some sub-keys and setup canon write to these keys. To workaround your problem you can either delete Services hive or grant full access to Administrator and Local system to that hive and rerun setup. It should fix your problem for now.

We are taking actions to fix it in future:
1. The error message is misleading and it will be updated
2. Setup logging will be improved so we can figure a failure without asking for additional files.
3. Setup will remove Services hive during uninstall.

Posted by Microsoft on 4/28/2005 at 6:33 AM

This issue difficult to repro. Would it be possible to run setup once more and when it fails open a console window and launch this command:
Mofcomp “C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof”

The mof file is the files that failed it is in the message. Once this is done can you attach output from mofcomp to the bug.

Posted by Microsoft on 4/28/2005 at 6:18 AM

Posted by Microsoft on 4/25/2005 at 9:04 AM

The OS's affected are: Win 2003, Win2003 SP1(x86, IA64, x64), and XP PRO SP1 and higher

Check and see if you have the following manifest files %windir%\system32 mmc.exe.manifest,w3wp.exe.manifest, inetinfo.exe.manifest, dllhost.exe.manifest and %windir%\system32\wbem\wmiprvse.exe.manifest
Renaming these will fix the problem. Some Yukon install failures leave these manifest files behind.
This error can also be seen if WMI is indeed corrupt on your machine. Try these cmd line statements:

Mofcomp.exe %windir%\system32\wbem\cimwin32.mof
Regsvr32 wbemupgd.dll
regsvr32 wbemsvc.dll
wmiprvse /regserver

Posted by TomL on 5/1/2005 at 4:59 PM

The problem, as identified by Microsoft personnel, is that registry key 'HKLM\SOFTWARE\Microsoft\Microsoft SQL Server' is not being set correctly during installation of the SQL Express April 2005 CTP server, regardless of whether it is installed as part of the Visual C#2005 Express installation, or via stand-alone installation using SQLEXPR.exe.

This circumvention allows the installation to complete; however, it is not known whether making the circumvention might cause other problems during installation or during runtime.

Using regedit, set the permission for "HKLM\\SOFTWARE\\Microsoft\\Microsoft SQL Server" and all subkeys to have full read/write permission for user 'SYSTEM'. The installation should then complete successfully.