WMI Service cannot be started when installing SQL Server Denali CTP3 - by jsmitchell_ct

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
1
Sign in
to vote
ID 682543 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 8/1/2011 8:56:55 AM
Access Restriction Public

Description

After downloading and installing SQL Server Denali CTP3 on a Windows 7 Home Premium 64-bit SP1 machine (Intel Core i5 processor 430M with 4G of memory) runing .net framework 4.0.30319, the only test that fails is WmiServiceStateCheck: "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."

I've run sfc /scannow a couple of times to be sure there are no errors, and have run various scripts that turn the service on and off, repair/restore it, etc. to no avail. I've also tried the installation in safe mode to be sure virus checkers and the like are not interfering. I've also run the setup as an adminstrator to no avail. 

I can't generate any error message with the WMI service so it appears to be working properly. Using WmiMgmt, it show that "authenticated users", "local service", and "network service" all have  "execute methods", "provider write", and "enable account" checked off as allowed. For "administrators", everything except "special permissions" is allowed. Nothing is denied for anyone. I tried giving every group all permissions as a test, but that didn't solve the problem. Further, the "Startup Type" is: Automatic; Local System Account ("Allow service to interact with desktop" is not checked; I tried checking it, but that had no effect). Dependecies: Depends on Remote Procedure Call (RPC); Depended Upon by: Intel Matrix Storage Event Monitor, Internet Connection Sharing (ICS), IP Helper, and Security Center. Nothing out of the ordinary there. 

For comparison, I downloaded SQL Server 2008 R2. Same error. I also tried the 32-bit version. Same error. I reinstalled .net framework 4.0, redownloaded the 64 bit version of Denali. Same error.

From the log:
(05) 2011-08-01 00:28:19 Slp: Initializing rule      : Windows Management Instrumentation (WMI) service
(05) 2011-08-01 00:28:19 Slp: Rule is will be executed  : True
(05) 2011-08-01 00:28:19 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.WmiServiceInfo
(05) 2011-08-01 00:28:19 Slp: The type initializer for 'System.Management.MTAHelper' threw an exception.
(05) 2011-08-01 00:28:19 Slp:    at System.Management.MTAHelper.IsNoContextMTA()
   at System.Management.MTAHelper.CreateInMTA(Type type)
   at System.Management.ManagementPath.CreateWbemPath(String path)
   at System.Management.ManagementPath..ctor(String path)
   at System.Management.ManagementScope..ctor(String path)
   at Microsoft.SqlServer.Configuration.SetupExtension.WmiServiceInfo.Microsoft.SqlServer.Configuration.RulesEngineExtension.IRuleInitialize.Init(String ruleId)
   at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.Execute(Boolean stopOnFailure)
(05) 2011-08-01 00:28:19 Slp: Rule initialization failed - hence the rule result is assigned as Failed
(05) 2011-08-01 00:28:19 Slp: Send result to channel : RulesEngineNotificationChannel

Ideas?

Note: Also see - http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/f317ef2f-7523-4a62-a365-d8244f5858c5
Sign in to post a comment.
Posted by Microsoft on 8/25/2011 at 3:11 PM
Hello,

We are resolving this as external based on the thread.

Regards,
SQL Server
Posted by Andy Cheung [MSFT] on 8/25/2011 at 2:20 PM
Glad to hear the installation went fine.
Posted by jsmitchell_ct on 8/25/2011 at 2:03 PM
Well, finally, the scorched earth approach worked. It took a couple of days straight of installs but everything seems "normal" now. Visual web developer and SQL are now installed. The one gotcha is that Win 7 was installed on this computer and thus all I had was a startup disk, not a full retail copy, which I had to borrow. I now have 30 days to input the authentication code which i have no clue about even though I legally own Win 7. Hopefully when I get around to calling Microsoft to validate my copy they believe me!
Posted by Andy Cheung [MSFT] on 8/23/2011 at 12:33 PM
The dependencywalker results unfortunately do not provide helpful clues to us. The yellow "?" and warnings you saw are not related to this issue. The Windows SDK install errors you encountered may suggest that something else (other than CLR v2.0) is broken. The error messages might provide more information.

Have you considered doing an in-place upgrade to repair the operating system? Here are some info about in-place repair:
http://support.microsoft.com/kb/2255099
http://www.sevenforums.com/tutorials/3413-repair-install.html
Posted by jsmitchell_ct on 8/23/2011 at 11:01 AM
I tried to download the windbg via the common utilities for the win 7 sdk, but got various error messages related to the windows installer not doing its job. Since my son's computer seems to be running fine under Win 7, can I extract the windows installer (v5) from it, and/or even perhaps export registry keys in the event that solves the problem?

This problem has persisted for nearly a month now. Surely someone has an answer?!
Posted by jsmitchell_ct on 8/19/2011 at 7:10 AM
As I've deleted and reinstalled .Net, there's no missing or corrupt file IMO. As this error can be reproduced in Safe Mode, it's not a conflict with another program [For reference, the following are running: Processes - csrss, ctfmon, explorer, taskmgr, winlogon; Services - wudfsvc, winmgmt, RpcSs, RpcEptMapper, ProfSvc, Power, PlugPlay, MsMpSvc, KeyIso, eventlog, DcomLaunch, CryptSvc]. I will add that this computer, though only about a year old, had a failed thermal chip that resulted in sudden shutdowns that might have screwed up a registry entry many months ago.
Posted by jsmitchell_ct on 8/18/2011 at 7:26 PM
For reference, I ran dependencywalker on my son's Win 7 computer where I know the install check passes. He's also missing gpsvc.dll and has the same warning for ieframe.dll. I actually do have various versions of ieshims.dll but I guess not where it's supposed to be?
Posted by jsmitchell_ct on 8/18/2011 at 6:47 PM
GPSVC.DLL has a yellow "?"
IESHIMS.DLL has a yellow "?"
IEFRAME.DLL has a red box
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.
Posted by Andy Cheung [MSFT] on 8/18/2011 at 4:38 PM
The log is helpful (thanks for that), but it doesn't tell us exactly where the issue lies. Let's see if there are any module failing to load. Can you try the following steps and report the result?

1) Download dependency walker tool (click the "Version 2.2 for x86" link) from http://dependencywalker.com
2) Copy the three files in the zip to your local machine. Double click depends.exe to open.
3) In depends UI, click File->Open... in the menu. Browse to the folder "C:\Windows\Microsoft.NET\Framework\v2.0.50727", and select "wminet_utils.dll". Hit Open button.
4) In the middle pane of the UI, you will see a list of modules. Please let us know the name of any module(s) that has a yellow "?", or a red square icon.
Posted by jsmitchell_ct on 8/17/2011 at 5:04 PM
2744,20891.965,CLR Loading log for C:\Users\MyName\Documents\EnumProcesses.exe
2744,20891.965,Log started at 7:56:29 PM on 8/17/2011
2744,20891.981,-----------------------------------
2744,20891.981,LegacyFunctionCall: _CorExeMain
2744,20891.997,FunctionCall: ClrCreateInstance, Clsid: {2EBCD49A-1B47-4A61-B13A-4A03701E594B}, Iid: {E2190695-77B2-492E-8E14-C4B3A7FDD593}
2744,20891.997,MethodCall: ICLRMetaHostPolicy::GetRequestedRuntime. Version: (null), Metahost Policy Flags: 360, Binary: (null), Iid: {BD39D1D2-BA2F-486A-89B0-B4B0CB466891}
2744,20892.043,Installed Runtime: v2.0.50727. VERSION_ARCHITECTURE: 0
2744,20892.059,Installed Runtime: v4.0.30319. VERSION_ARCHITECTURE: 0
2744,20892.059,Input values for ComputeVersionString follow this line
2744,20892.059,-----------------------------------
2744,20892.059,Default Application Name: C:\Users\MyName\Documents\EnumProcesses.exe
2744,20892.075,IsLegacyBind is: 0
2744,20892.075,IsCapped is 0
2744,20892.075,SkuCheckFlags are 0
2744,20892.075,ShouldEmulateExeLaunch is 0
2744,20892.090,LegacyBindRequired is 0
2744,20892.090,-----------------------------------
2744,20892.090,Parsing config file: C:\Users\MyName\Documents\EnumProcesses.exe.config
2744,20892.106,UseLegacyV2RuntimeActivationPolicy is set to 0
2744,20892.106,LegacyFunctionCall: GetFileVersion. Filename: C:\Users\MyName\Documents\EnumProcesses.exe
2744,20892.121,LegacyFunctionCall: GetFileVersion. Filename: C:\Users\MyName\Documents\EnumProcesses.exe
2744,20892.153,C:\Users\MyName\Documents\EnumProcesses.exe was built with version: v2.0.50727
2744,20892.153,Decided on runtime: v2.0.50727
2744,20892.184,MethodCall: ICLRRuntimeInfo::GetProcAddress. Name: _CorExeMain
2744,20892.184,MethodCall: ICLRRuntimeInfo::GetVersionString. Version: v2.0.50727
2744,20892.199,MethodCall: ICLRRuntimeInfo::GetRuntimeDirectory. Version: v2.0.50727
2744,20892.199,The Legacy APIs have been bound to version: v2.0.50727
2744,20892.309,Runtime has been loaded. Version: v2.0.50727
2744,20892.309,LegacyFunctionCall: GetCorVersion.
2744,20892.324,MethodCall: ICLRRuntimeInfo::GetVersionString. Version: v2.0.50727
2744,20892.371,MethodCall: ICLRRuntimeInfo::GetRuntimeDirectory. Version: v2.0.50727
2744,20892.761,LegacyFunctionCall: GetCorVersion.
2744,20892.777,LegacyFunctionCall: GetCorVersion.
2744,20892.777,MethodCall: ICLRRuntimeInfo::GetVersionString. Version: v2.0.50727
2744,20892.777,LegacyFunctionCall: GetCorVersion.
2744,20892.792,LegacyFunctionCall: GetCorVersion.
2744,20892.792,MethodCall: ICLRRuntimeInfo::GetVersionString. Version: v2.0.50727
2744,20892.979,MethodCall: ICLRRuntimeInfo::GetRuntimeDirectory. Version: v2.0.50727
2744,20893.635,LegacyFunctionCall: GetMetaDataInternalInterface
2744,20894.976,LegacyFunctionCall: DllGetClassObject. Clsid: {A8F03BE3-EDB7-4972-821F-AF6F8EA34884}, Iid: {00000001-0000-0000-C000-000000000046}
2744,20894.992,LegacyFunctionCall: LoadLibraryShim. DllName: WMINet_Utils.dll, Version: (null)
2744,20894.992,MethodCall: ICLRRuntimeInfo::GetRuntimeDirectory. Version: v2.0.50727
2744,20895.132,Input values for ComputeVersionString follow this line
2744,20895.148,-----------------------------------
2744,20895.148,IsLegacyBind is: 1
2744,20895.148,IsCapped is 1
2744,20895.148,SkuCheckFlags are 1
2744,20895.148,ShouldEmulateExeLaunch is 0
2744,20895.163,LegacyBindRequired is 0
2744,20895.163,-----------------------------------
2744,20895.163,Parsing config file: C:\Users\MyName\Documents\EnumProcesses.exe.config
2744,20895.163,UseLegacyV2RuntimeActivationPolicy is set to 0
2744,20895.179,LegacyFunctionCall: GetFileVersion. Filename: C:\Users\MyName\Documents\EnumProcesses.exe
2744,20895.179,LegacyFunctionCall: GetFileVersion. Filename: C:\Users\MyName\Documents\EnumProcesses.exe
2744,20895.195,C:\Users\MyName\Documents\EnumProcesses.exe was built with version: v2.0.50727
2744,20895.195,Decided on runtime: v2.0.50727
2744,20895.210,LegacyFunctionCall: LoadLibraryShim. DllName: WMINet_Utils.dll, Version: v2.0.50727
2744,20895.319,LegacyFunctionCall: LoadLibraryShim. DllName: WMINet_Utils.dll, Version: v2.0.50727
2744,20895.397,LegacyFunctionCall: LoadLibraryShim. DllName: culture.dll, Version: (null)
2744,20895.397,MethodCall: ICLRRuntimeInfo::GetRuntimeDirectory. Version: v2.0.50727
2744,20895.663,MethodCall: ICLRRuntimeInfo::GetRuntimeDirectory. Version: v2.0.50727
2744,20918.720,LegacyFunctionCall: DllGetClassObject. Clsid: {0A29FF9E-7F9C-4437-8B11-F424491E3931}, Iid: {00000001-0000-0000-C000-000000000046}
2744,20918.751,LegacyFunctionCall: LoadLibraryShim. DllName: diasymreader.dll, Version: (null)
2744,20918.766,MethodCall: ICLRRuntimeInfo::GetRuntimeDirectory. Version: v2.0.50727
2744,20918.891,LegacyFunctionCall: DllGetClassObject. Clsid: {0A29FF9E-7F9C-4437-8B11-F424491E3931}, Iid: {00000001-0000-0000-C000-000000000046}
Posted by Andy Cheung [MSFT] on 8/17/2011 at 4:38 PM
The wminet_utils.dll you have seems to be correct. Let's see if the shim log can give us more information. Could you follow the steps below and post the log output?

1) Open the registry editor by typing this in the command prompt "C:\>regedit"
2) In the registry editor, go to "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework". On the right pane, right click and create a new string value key. Set the value name to "CLRLoadLogDir" and value data to "[the directory path that contains your EnumProcesses.exe file>"
3) Run EnumProcesses.exe that generates the exception. You will see some log files created in the same folder.
4) Please post the content of the log file "EnumProcesses.exe.CLRLoad00.log"
Posted by jsmitchell_ct on 8/17/2011 at 1:10 AM
Well, I spent an entire day deleting all versions of .net from my PC and re-installing and re-updating everything (which itself was a challenge). Sadly, I got the exact same error. Now what?
Posted by jsmitchell_ct on 8/16/2011 at 6:17 AM
Andy, since I don't know if things were ever "right", I'm hesitant to restore from any point. Since it appears we narrowed the problem down to .net v3.5 (where the exception is thrown), and since I've already tried unchecking the box in Windows 7 to (kind of) reinstall it, what about using the .NET Framework Cleanup Tool to totally get rid of it and then reinstall it? Would I also have to do the same for v4 for this to be effective? Thanks for your continued interest and help on this.
Posted by jsmitchell_ct on 8/16/2011 at 6:13 AM
Results:

c:\Windows\Microsoft.NET>dir /s wminet*

Directory of c:\Windows\Microsoft.NET\Framework\v2.0.50727
11/04/2010 09:58 PM            32,088 WMINet_Utils.dll
             1 File(s)         32,088 bytes

Directory of c:\Windows\Microsoft.NET\Framework\v4.0.30319
03/18/2010 01:16 PM            31,576 WMINet_Utils.dll
             1 File(s)         31,576 bytes

Directory of c:\Windows\Microsoft.NET\Framework64\v2.0.50727
11/04/2010 09:57 PM            42,328 WMINet_Utils.dll
             1 File(s)         42,328 bytes

Directory of c:\Windows\Microsoft.NET\Framework64\v4.0.30319
03/18/2010 02:27 PM            39,256 WMINet_Utils.dll
             1 File(s)         39,256 bytes
Posted by Andy Cheung [MSFT] on 8/15/2011 at 10:00 PM
Thank you for listing the registry key values. The key values look fine to me. Just to double check wminet_utils.dll exists, can you execute the command below in the C:\Windows\Microsoft.NET folder? Does your computer have a restore point before you installed Denali and VS? If so, one option is to restore the system back to a good known state.

C:\Windows\Microsoft.NET>dir /s wminet*

System restore
http://windows.microsoft.com/en-US/windows7/products/features/system-restore
Posted by jsmitchell_ct on 8/15/2011 at 3:59 PM
Andy, do you notice anything out of place in the registry entries below? Thanks.
Posted by jsmitchell_ct on 8/13/2011 at 11:59 PM
1) HKEY_CLASSES_ROOT\CLSID\{A8F03BE3-EDB7-4972-821F-AF6F8EA34884}\InprocServer32\2.0.50727
(Default) REG_SZ (value not set)
ImplementedInThisVersion REG_SZ [blank]

2) HKEY_CLASSES_ROOT\WMINet_Utils.WmiSecurityHelper
(Default) REG_SZ WmiSecurityHelper Class
- CLSID: (Default) REG_SZ {A8F03BE3-EDB7-4972-821F-AF6F8EA34884}
- CurVer: (Default) REG_SZ WMINet_Utils.WmiSecurityHelper.1

3) HKEY_CLASSES_ROOT\WMINet_Utils.WmiSecurityHelper.1
(Default) REG_SZ WmiSecurityHelper Class
- CLSID: (Default) REG_SZ {A8F03BE3-EDB7-4972-821F-AF6F8EA34884}

4) HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{A8F03BE3-EDB7-4972-821F-AF6F8EA34884}
(Default) REG_SZ WmiSecurityHelper Class
InprocServer32:
(Default) REG_SZ C:\windows\syswow64\mscoree.dll
ThreadingModel REG_SZ Both
- 2.0.50727:
(Default) REG_SZ (value not set)
ImplementedInThisVersion REG_SZ [blank]
ProgID: (Default) REG_SZ WMINet_Utils.WmiSecurityHelper.1
Server: REG_SZ WMINet_Utils.dll
VersionIndependentProgID: WMINet_Utils.WmiSecurityHelper

-----

1) HKEY_CLASSES_ROOT\CLSID\{D2EAA715-DAC7-4771-AF5C-931611A1853C}
(Default) REG_SZ WmiSinkDemultiplexor Class
InprocServer32:
(Default) REG_SZ C:\windows\system32\mscoree.dll
ThreadingModel REG_SZ Both
- 2.0.50727:
(Default) REG_SZ (value not set)
ImplementedInThisVersion REG_SZ [blank]
ProgID: (Default) REG_SZ WMINet_Utils.WmiSinkDemultiplexor.1
Server: REG_SZ WMINet_Utils.dll
VersionIndependentProgID: WMINet_Utils.WmiSinkDemultiplexor

2) HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WMINet_Utils.WmiSinkDemultiplexor
(Default) REG_SZ WmiSinkDemultiplexor Class
- CLSID: (Default) REG_SZ {D2EAA715-DAC7-4771-AF5C-931611A1853C}
- CurVer: (Default) REG_SZ WMINet_Utils.WmiSinkDemultiplexor.1

3) HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WMINet_Utils.WmiSinkDemultiplexor.1
(Default) REG_SZ WmiSinkDemultiplexor Class
- CLSID: (Default) REG_SZ {D2EAA715-DAC7-4771-AF5C-931611A1853C}

4) HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D2EAA715-DAC7-4771-AF5C-931611A1853C}
(Default) REG_SZ WmiSinkDemultiplexor Class
InprocServer32:
(Default) REG_SZ C:\windows\syswow64\mscoree.dll
ThreadingModel REG_SZ Both
- 2.0.50727:
(Default) REG_SZ (value not set)
ImplementedInThisVersion REG_SZ [blank]
ProgID: (Default) REG_SZ WMINet_Utils.WmiSinkDemultiplexor.1
Server: REG_SZ WMINet_Utils.dll
VersionIndependentProgID: WMINet_Utils.WmiSinkDemultiplexor

.NET Framework Setup Verification Utility
.NET Framework 2.0 SP2: Succeeded
.NET Framework 3.0 SP2: Succeeded
.NET Framework 3.5 SP1: Succeeded
.NET Framework 4 Client: Succeeded
.NET Framework 4 Full: Succeeded
Posted by Andy Cheung [MSFT] on 8/13/2011 at 12:31 PM
Correction: The DLL name I mentioned below is wminet_utils.dll, not wminetutils.dll.
Posted by Andy Cheung [MSFT] on 8/13/2011 at 12:29 PM
The error message is more helpful. The COMException 0x80131701 (CLR_E_SHIM_RUNTIMEEXPORT) implies the link between CLR v2.0 and wminetutils.dll is somehow broken. Could you tell me what the following registry key and subkey values are on your machine?

1) HKEY_CLASSES_ROOT\CLSID\{A8F03BE3-EDB7-4972-821F-AF6F8EA34884}\InprocServer32\2.0.50727
2) HKEY_CLASSES_ROOT\WMINet_Utils.WmiSecurityHelper
3) HKEY_CLASSES_ROOT\WMINet_Utils.WmiSecurityHelper.1
4) HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{A8F03BE3-EDB7-4972-821F-AF6F8EA34884}

The following is another set of registry values System.Management depends on. Although this key is not related to the exception you are seeing, the key-value structure should be similar to the ones above.

1) HKEY_CLASSES_ROOT\CLSID\{D2EAA715-DAC7-4771-AF5C-931611A1853C}
2) HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WMINet_Utils.WmiSinkDemultiplexor
3) HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WMINet_Utils.WmiSinkDemultiplexor.1
4) HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D2EAA715-DAC7-4771-AF5C-931611A1853C}

I am not sure if there is anything else broken in .NET Framework v2.0 on your machine since you mentioned earlier that Visual Studio install stalled. One way you might be able to find out is to try the Setup Verification tool below:

http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

Hope this helps.


Posted by jsmitchell_ct on 8/13/2011 at 6:18 AM
And, OK, I think we are making progress! Here's the result, consistent with both v3.5 compiles:

Unhandled Exception: System.TypeInitializationException: The type initializer for 'System.Management.ManagementPath' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.Management.MTAHelper' threw an exception. ---> System.Runtime.InteropServices.COMException (0x80131701): Retrieving the COM class factory for component with CLSID {A8F03BE3-EDB7-4972-821F-AF6F8EA34884} failed due to the following error: 80131701.
at System.Management.MTAHelper..cctor()
--- End of inner exception stack trace ---
at System.Management.MTAHelper.CreateInMTA(Type type)
at System.Management.ManagementPath.CreateWbemPath(String path)
at System.Management.ManagementPath..ctor(String path)
at System.Management.ManagementPath..cctor()
--- End of inner exception stack trace ---
at System.Management.ManagementPath..ctor(String path)
at System.Management.ManagementClass..ctor(String path)
at Sample.Main()

Here is my registry entry for CLSID {A8F03BE3-EDB7-4972-821F-AF6F8EA34884}:

InprocServer32
(Default) REG_SZ c:\Windows\system32\mscoree.dll
ThreadingModel REG_SZ Both
ProgID
(Default) REG_SZ WMINet_Utils.WmiSecurityHelper.1
Server
(Default) REG_SZ WMINet_Utils.dll
VersionIndepdendentProgID
(Default) REG_SZ WMINet_Utils.WmiSecurityHelper
Posted by Andy Cheung [MSFT] on 8/12/2011 at 10:28 PM
Thanks for trying out the code sample. Can you try to run the commands below? It will verify if System.Management on CLR 2.0 is working on your machine.

1) Compile ">c:\Windows\Microsoft.NET\Framework\v3.5\csc.exe EnumProcesses.cs" and run the EXE generated.

2) Compile ">c:\Windows\Microsoft.NET\Framework64\v3.5\csc.exe EnumProcesses.cs" and run the EXE generated.
Posted by jsmitchell_ct on 8/12/2011 at 11:18 AM
Any other code samples I can try running?
Posted by jsmitchell_ct on 8/11/2011 at 9:58 PM
Same result!
Posted by Andy Cheung [MSFT] on 8/11/2011 at 7:50 PM
Sorry, the command should be > c:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe EnumProcesses.cs.
Posted by jsmitchell_ct on 8/11/2011 at 7:45 PM
What's in the EnumerateProcesses code sample?
Posted by Andy Cheung [MSFT] on 8/11/2011 at 7:10 PM
Thanks. It appears System.Management 32-bit is working fine on your machine. Could you also try running this command in step 3 > c:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe EnumerateProcesses.cs, and then run the executable generated. Please post the result only if you see an exception.
Posted by jsmitchell_ct on 8/11/2011 at 6:00 PM
Next instance of Win32_Process : System Idle Process
Next instance of Win32_Process : System
Andy, here's the output:
Next instance of Win32_Process : smss.exe
Next instance of Win32_Process : csrss.exe
Next instance of Win32_Process : wininit.exe
Next instance of Win32_Process : csrss.exe
Next instance of Win32_Process : winlogon.exe
Next instance of Win32_Process : services.exe
Next instance of Win32_Process : lsass.exe
Next instance of Win32_Process : lsm.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : MsMpEng.exe
Next instance of Win32_Process : atiesrxx.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : atieclxx.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : spoolsv.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : taskhost.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : dwm.exe
Next instance of Win32_Process : explorer.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : lmgrd.exe
Next instance of Win32_Process : IAAnotif.exe
Next instance of Win32_Process : ePowerTray.exe
Next instance of Win32_Process : avp.exe
Next instance of Win32_Process : conhost.exe
Next instance of Win32_Process : SynTPEnh.exe
Next instance of Win32_Process : lmgrd.exe
Next instance of Win32_Process : msseces.exe
Next instance of Win32_Process : GoogleToolbarNotifier.exe
Next instance of Win32_Process : sidebar.exe
Next instance of Win32_Process : ARCGIS.EXE
Next instance of Win32_Process : WDDMStatus.exe
Next instance of Win32_Process : ePowerSvc.exe
Next instance of Win32_Process : WDSmartWare.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : LMS.exe
Next instance of Win32_Process : SMSvcHost.exe
Next instance of Win32_Process : IScheduleSvc.exe
Next instance of Win32_Process : SeaPort.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : UpdaterService.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : WDDMService.exe
Next instance of Win32_Process : WDSmartWareBackgroundService.exe
Next instance of Win32_Process : WLIDSVC.EXE
Next instance of Win32_Process : IAANTmon.exe
Next instance of Win32_Process : WLIDSVCM.EXE
Next instance of Win32_Process : unsecapp.exe
Next instance of Win32_Process : WmiPrvSE.exe
Next instance of Win32_Process : ePowerEvent.exe
Next instance of Win32_Process : SearchIndexer.exe
Next instance of Win32_Process : NisSrv.exe
Next instance of Win32_Process : svchost.exe
Next instance of Win32_Process : SynTPHelper.exe
Next instance of Win32_Process : LManager.exe
Next instance of Win32_Process : BackupManagerTray.exe
Next instance of Win32_Process : VideoWebCamera.exe
Next instance of Win32_Process : CLMLSvc.exe
Next instance of Win32_Process : PDVD8Serv.exe
Next instance of Win32_Process : acrotray.exe
Next instance of Win32_Process : avp.exe
Next instance of Win32_Process : jusched.exe
Next instance of Win32_Process : MOM.exe
Next instance of Win32_Process : CCC.exe
Next instance of Win32_Process : FNPLicensingService.exe
Next instance of Win32_Process : mscorsvw.exe
Next instance of Win32_Process : UNS.exe
Next instance of Win32_Process : PresentationFontCache.exe
Next instance of Win32_Process : SETUP.EXE
Next instance of Win32_Process : conhost.exe
Next instance of Win32_Process : SCENARIOENGINE.EXE
Next instance of Win32_Process : LANDINGPAGE.EXE
Next instance of Win32_Process : SETUP.EXE
Next instance of Win32_Process : conhost.exe
Next instance of Win32_Process : SCENARIOENGINE.EXE
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : OUTLOOK.EXE
Next instance of Win32_Process : OSPPSVC.EXE
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : rundll32.exe
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : EXCEL.EXE
Next instance of Win32_Process : Procmon.exe
Next instance of Win32_Process : Procmon64.exe
Next instance of Win32_Process : notepad.exe
Next instance of Win32_Process : WINWORD.EXE
Next instance of Win32_Process : splwow64.exe
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : chrome.exe
Next instance of Win32_Process : notepad.exe
Next instance of Win32_Process : cmd.exe
Next instance of Win32_Process : conhost.exe
Next instance of Win32_Process : taskeng.exe
Next instance of Win32_Process : SearchProtocolHost.exe
Next instance of Win32_Process : SearchFilterHost.exe
Next instance of Win32_Process : WmiPrvSE.exe
Next instance of Win32_Process : EnumProcesses.exe
Posted by Andy Cheung [MSFT] on 8/11/2011 at 4:40 PM
Instead of using Visual Studio, could you try the following steps to compile the code:

1) Open a text file and copy the C# code sample (http://msdn.microsoft.com/en-us/library/ysw6xf4d.aspx#Y200) to the file.
2) Save and name the file as EnumProcesses.cs.
3) Execute this command line >c:\Windows\Microsoft.NET\Framework\v4.0.30319\csc EnumProcesses.cs. If your system drive is different, change the path to your system drive. Use the latest version of .NET Framework if you don't have v4.0 installed. If this command line succeeds, you will find a file called EnumProcesses.exe in the same folder as your cs file.
4) Run EnumProcesses.exe. Please report what you see.
Posted by jsmitchell_ct on 8/11/2011 at 3:57 PM
Andy, I'd love to do that but this entire problem began because my Visual Studio install stalled at this point! If you could point me to an already compiled version to download that would be much appreciated.
Posted by Andy Cheung [MSFT] on 8/11/2011 at 1:59 PM
Could you compile and run the C# code sample in the link below and report back the error message you see? The error message might provide more information to narrow down the issue.

http://msdn.microsoft.com/en-us/library/ysw6xf4d.aspx#Y200
Posted by jsmitchell_ct on 8/10/2011 at 9:53 PM
I ran process monitor while executing the Setup Support Rules Checker (aka ScenarioEngine.ext) and saved the log. I tried to correlate what was going on at the exact moment the install log file indicated the exception had been thrown. The problem is all I see are a bunch of "success" notices. There are also a couple of "Fast IO Disallowed" "Name Not Found" and one "File Locked with Only Readers" notices, but that's it. If someone could please tell me what I might be looking for in the log I'll report what it says. If that's a dead end, please let me know that as well. Thanks.
Posted by jsmitchell_ct on 8/10/2011 at 10:01 AM
After extensive checking, every syswow version of the mscoree.dll is in a wow node, ditto for the system32 version only in CLSID. I also just installed the .net framework 4 update and my system is totally up to date. Still the same hair-pulling error. Now what?
Posted by Peter Marcu (MSFT) on 8/9/2011 at 10:23 AM
Luckily there is a fairly simple answer to that. The entries under Wow6432Node should point to c:\windows\syswow64\mscoree.dll while the ones in the native hive should point to C:\Windows\system32\mscoree.dll.

Here are the two equivalent keys for this component to show the difference:

HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{A8F03BE3-EDB7-4972-821F-AF6F8EA34884}\InprocServer32
HKEY_CLASSES_ROOT\CLSID\{A8F03BE3-EDB7-4972-821F-AF6F8EA34884}\InprocServer32

I am curious what could have put you in this state but figuring out if you have any of these mismatches would tell us if we're on the right track here...
Posted by jsmitchell_ct on 8/9/2011 at 6:12 AM
Peter, yes, I tried that to no avail. I also did a search of every occurrence of c:\windows\syswow64\mscoree.dll and found more than a dozen instances. I have no clue when that version is appropriate in the registry and when C:\Windows\system32\mscoree.dll is. But I do think getting this straight is the key to victory.
Posted by Peter Marcu (MSFT) on 8/8/2011 at 10:31 PM
Were you able to look at the COM server registration for that component to see if you had a similar problem as on the forum you found? HKCR\CLSID\{A8F03BE3-EDB7-4972-821F-AF6F8EA34884}\InprocServer32

See if the path there on your 64bit machine is pointing to C:\Windows\system32\mscoree.dll.
Posted by jsmitchell_ct on 8/8/2011 at 10:52 AM
Any luck with the .net team?
Posted by jsmitchell_ct on 8/6/2011 at 10:14 AM
Based on this post, which seems pretty similar, it does appear to be a .net error where native calls work but generate an error via Powershell. Alex, the author, debugs Powershell to find the registry entry affected, which I need further help on how to do.

http://blogs.msdn.com/b/alejacma/archive/2010/10/20/get-wmiobject-the-type-initializer-for-system-management-mtahelper-threw-an-exception.aspx?CommentPosted=true#commentmessage
Posted by jsmitchell_ct on 8/5/2011 at 8:09 PM
Sadly, no, that didn't work. I also tried checking the two sub options for .net 3.5 and that didn't work either (not sure if they should have been checked in the first place). Thanks for at least suggesting something to try.
Posted by Microsoft on 8/5/2011 at 4:52 PM
Thanks for your follow-up. It appears that there is an issue with your CLR 2. If you could, can you try disabling your .net 3.5 from Control Panel > Programs > Programs and Features > Turn Windows features on or off and restart and reenable .net 3.5 to see if it fixes your issue?

If this doesn't help, we might need to route you to .Net folks as it looks like only native calls to WMI complete successfully.

Let us know. Thanks and have a good weekend!

SQL Server
Posted by jsmitchell_ct on 8/5/2011 at 12:52 PM
Get-WmiObject : The type initializer for 'System.Management.MTAHelper' threw an exception
At line:1 char:14
+ get-wmiobject <<<< -Query "SELECT NAME FROM WIN32_SERVICE WHERE NAME = 'winmgmt'"
+ CategoryInfo : NotSpecified: <:> [Get-WmiObject], TypeInitializationException
+ FullyQualifiedErrorid : System.TypeInitializationException,Microsoft.PowerShell.Commands.GetWmiObjectCommand
Posted by Microsoft on 8/5/2011 at 11:12 AM
:)

It appears that your WMI functions as expected. Can you also try this PowerShell script and let us know what you get in result?

get-wmiobject -Query "SELECT NAME FROM WIN32_SERVICE WHERE NAME = 'winmgmt'"

Our apologies for not setting expectations as you are rightfully expecting a follow-up answer in a reasonable amount of time. Our recurring triages that we process issues such as yours currently have a twice a week frequency; Tuesdays and Fridays. Having said that, I'll try to keep an eye out for your response. Thank you for your patience.

Sincerely,
SQL Server
Posted by jsmitchell_ct on 8/5/2011 at 8:34 AM
Note to self: OK, singing apparently isn't working. I can't juggle. I can't dance. Anyone want to see pictures of my summer vacation?
Posted by jsmitchell_ct on 8/5/2011 at 12:33 AM
Perhaps if I started to sing it might attract someone's attention?
Posted by jsmitchell_ct on 8/4/2011 at 7:00 AM
Still looking to proceed but still stuck. Any further ideas here?
Posted by jsmitchell_ct on 8/3/2011 at 7:51 AM
I assume you were expecting an error? That's the odd thing-- every WMI test I run shows the service working properly. As I get the same error for SQL Server 2008 R2, maybe it's just a bug in the Setup Support Rules software?
Posted by jsmitchell_ct on 8/2/2011 at 12:24 PM
Yes, I get back Win32_Service.Name='winmgmt'
Posted by Microsoft on 8/2/2011 at 11:55 AM
Hello,

Thank you for reporting this issue. Please click start and run wbemtest.exe with elevated privileges. Connect to root\cimv2, run query SELECT NAME FROM WIN32_SERVICE WHERE NAME = 'winmgmt'. You should be getting one back in your Query Result window.

Can you please confirm this?

Regards,
SQL Server