WMI Configuration Error on SQL 2005 install

▲
0
▼

SQL Server 2005 is giving me the following error during the "System Check" portion of the initial install: "The SQL Server Configuration Checker cannot be executed due to WMI configuration on the machine Error:2147749907 (0x80041013)."

Machine is a Dell D620 running XP SP2.

I found a batch command online that is supposed to fix the problem, but it didn't work.

Any ideas?

sql-server
windows
installation
asked on Stack Overflow Feb 27, 2009 by Shawn Swaner • edited May 2, 2012 by Mr Lister

4 Answers

▲
1
▼

Manju Madhavan on my team finally found the answer:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

The setup asked for long list of files that I had to search around to find. Some were in the i386 folder on the XP SP3 disk, some in %windir%/system32. As the installer would stop and ask for a file I would search around until I found a copy.

Manju found the answer online and documents it on her blog.

answered on Stack Overflow Apr 14, 2009 by Shawn Swaner
▲
0
▼

Are you running Microsoft Operations Manager on your server?

May I suggest disabling any services that utilise the WMI interface, so any performance monitoring software you are using, just whilst you install SQL Server.

Cheers, John

answered on Stack Overflow Feb 27, 2009 by John Sansom
▲
0
▼
  1. Run
  2. type or copy paste rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf
  3. Connect your Windows XP SP3 CD
  4. Find out "i386" folder and click enter and it will copy some file from there and will ask for a .mof file.
  5. Search for the .mof file in where you installed Windows
  6. Copy the location of that file and click OK.

Start installing the SQL Server 2005 and I'm sure you will face no more problems.

answered on Stack Overflow Aug 3, 2012 by Souptik • edited Aug 3, 2012 by Jonas G. Drange
▲
0
▼

I don't know what script did you find, but the one I ran worked like a charm. I'm putting here this answer for the ones that got to this post looking for that error message like I did.

Just execute this .bat file.

Source: Pinal Dave's SQL Authority Blog

answered on Stack Overflow Nov 23, 2012 by daniloquio • edited Nov 23, 2012 by daniloquio

User contributions licensed under CC BY-SA 3.0