Receiving WMI configuration error. SQL Server System Configuration cannot be executed due to that

Receiving WMI configuration error. SQL Server System Configuration cannot be executed due to that

• sophia james

  I just wanted to add to this thread to say that the script also worked for me.

  Thanks so much for that!

  
  

• eman67

  I was also receiving a WMI configuration error when trying to install SQL Server 2005 Standard Edition that was distributed by Microsoft during the Ready To Launch tour.  Running the batch file above fixed my WMI configuration issue.  Thanks!
  

• Yosi Taguri

  Tried it. Worked just as you said. thanks

  

  
  

• Youngy

  I have just run that script and then launched the SQLEXPR_ADV.EXE again, and I still receive this error with the usual WMI configuration message:

  Error:  70346 (0x112ca).

  Windows XP SP2 fully updated from Microsoft Updates.

  
  

• JimGries - MSFT

  This information was perfect.

  I have been looking for the past week, trying to get SQL express to install

  Thanks !!!!!!!!

  
  

• schallm

  I have tried this script several times, with no effect. I have administrator privileges and although I get the same error mentioned by I Mrus, the the LocalSystem account is affected. Beyond having admin authority and having the script (I run it, reboot, install SQL Srver Express; when fails, uninstall with Add/Remove programs) what can be done to correct this. Below is a sample of the Application error from Computer Mangement:

  Event Type: Warning
  Event Source: WinMgmt
  Event Category: None
  Event ID: 63
  Date: 6/7/2006
  Time: 1:03:47 AM
  User: MY_NOTEBOOK\Owner
  Computer: MY_NOTEBOOK
  Description:
  A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
  

  BTW - the link is dead.

  Any ideas

  
  

• steve hallden

  Hi,

  i also have the wmi problem. Then i also wanted to put the script onto the server to fix the wmi. But as soon as i copy the file, it is directly deleted by f-secure, which thinks that the script is a trojan.

  Any suggestions,

  thx in advance.

  
  

• Kevin E

  Many thanks for this wonderful script I must say.

  My internet explorer XP SP2 would not let me go any further than logon and password authentication pages on some web sites. (like www.ewiz.com and others...)

  After trying every possilbe wiht the settings under the tools menu no luck, I was about to reinstall the whole XP...until this script fixed it all...

  Thank you!

  
  

• Coroebus

  I found this batch file and ran it and it fixed my WMI problems on SQL Server 2003. Copy this into notepad as save as fixwmi.cmd and then from a command line run c:\fixwmi.cmd.

  It takes several minutes to complete and at points it appears that it is not running but it is. After it is complete, you see the :END statement start the SQL server installation again and you should be fixed.

  FIXWMI.CMD
  ------------------------
  
  @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
  

  
  
  

• Christian44

  Any idea why the script has not corrected this issue on my laptop

  Dell Lattitude D620

  XP SP2 fully updated

  
  

• mandoman

  Thanks - it worked for me despite Microsoft's on line help checker saying the problem was unknown.
  
  

• Vidhan

  For whatever reason, copying and pasting this script pasted in unicode rather than ascii. This made the cmd parser barf. To convert it from unicode to ascii (on Windows 200 or XP), use the "type" command redirected to a file, e.g,
  
  type original.in.unicode.bat > ascii.copy.bat
  
  Then run the new batch file.
  
  (As it turns out, my problem wasn't with the WMI configuration, but that I'd told my application firewall to deny WMI run permissions.)
  
  
  

• Brian Shepherd

  Rename the file to txt, copy it, rename back to cmd.

  If f-secure still catches that, just disable it and copy the cmd file as is.

  
  
  

• cincyreds

  Thank you for this. God Bless.
  
• Receiving WMI configuration error. SQL Server System Configuration cannot be executed due to that