Unable to open the configuration manager in SQL server 2005

Problem Description in our scenario:


We have a SQL server 2005 (9.00.4035 Enterprise Edition X64) , when we try to open the configuration manager we get the below

error :


SQL Server Configuration Manager


Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager.

The specified module could not be found. [0x8007007e]

Environment :


SQL : sql server 2005 9.00.4035 Ent X64 .
OS   : Win server 2003 Ent X64

Cause of the issue in our scenario:


The following path was missing from the system path of the Environment variables. 

%SystemRoot%\system32 & %SystemRoot%\system32\WBEM

Troubleshooting :

•We confirmed that the WMI was consistent by running a WBEMTEST successfully.

•We then checked the Environmental variables.

In my computer->properties->advanced->Environmental variables saw the below variables ( user and system )

User path      : D:\apps_pub\bsys3020;C:\DOCUME~1\jl19811\LOCALS~1\Temp\jl19811\commands

System Path : %systemroot%\system32;C:\WINNT\system32\wbem;%systemroot%\system32\wbem;C:\apps_srv\sdk15640\DataAccess64\ADONET\dll;C:\apps_srv\sdk15640\DataAccess64\OLEDB\dll;C:\apps_srv\sdk15640\DataAccess\ADONET\dll;C:\apps_srv\sdk15640\DataAccess\OLEDB\dll;C:\apps_srv\sdk15640\DataAccess\ODBC\dll;C:\apps_srv\sdk15640\DataAccess64\ODBC\dll;C:\apps_srv\sdk15640\OCS-15_0\lib3p64;C:\apps_srv\sdk15640\OCS-15_0\lib3p;C:\apps_srv\sdk15640\OCS-15_0\dll;C:\apps_srv\sdk15640\OCS-15_0\bin;D:;;C:\apps_pub\sybase\sdk12521\DataAccess\OLEDB\dll;C:\apps_pub\sybase\sdk12521\DataAccess\ODBC\dll;C:\apps_pub\sybase\sdk12521\OCS-12_5\lib3p;C:\apps_pub\sybase\sdk12521\ADO.NET\dll;C:\apps_pub\sybase\sdk12521\OLEDB;C:\apps_pub\sy base\sdk12521\ODBC;C:\apps_pub\sybase\sdk12521\OCS-12_5\dll;C:\apps_pub\sybase\sdk12521\OCS-12_5\bin;C:\DOCUME~1\sc27431\LOCALS~1\Temp\sc27431\commands;D:\apps_pub\bsys3020;C:\apps_srv\mssql\90\Tools\binn\;C:\apps_srv\mssql (x86)\90\Tools\binn\;C:\apps_srv\mssql\90\DTS\Binn\;C:\apps_srv\mssql (x86)\90\DTS\Binn\;C:\apps_srv\mssql (x86)\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

The highlighted part in BOLD was missing in the system path of the Environment variables.

Workaround in our scenario:


We added %systemroot%\system32;C:\WINNT\system32\wbem;%systemroot%\system32\wbem  to the system path of the Environment variables and rebooted the server and after this we were able to  open the configuration manager.

Note: This post should not be treated as the Microsoft’s Recommendation or Resolution to the problem, it is only a workaround which worked in our environment and so we would like to share it.

Manikandan Veeruchamy
SE, Microsoft Sql Server

Reviewed by

Karthick Krishnamurthy
TL,Microsoft Sql Server

Comments (0)

Skip to main content