Issue
When attempting to open SQL Server Configuration Manager in order to alter the SQL Server Services configuration on servers with multiple SQL Server instances,
the following error message is returned:
Product
Struxureware Power Monitoring
Power Monitoring Expert
ION Enterprise
ION EEM
Environment
SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014
Cause
SQL Server Configuration Manager is an important tool to make changes to the SQL Server Services configuration, such as changing SQL Service account password,
changes to Network Protocols, enabling SSL, changing SQL Server startup parameters, etc. This component gets installed when any SQL Server components are installed on the server.
SQL Servers with multiple instances of the same or different versions can use same files for configuration manager, thus causing problems or failures when opening the SQL Server Configuration manager. This commonly occurs on servers where there are multiple SQL Server instances of different versions or architectures which have been installed or uninstalled over time.
Resolution
To resolve this problem follow the below steps.
- Run the command by pressing Enter, which should complete without any errors.
- Close and open the SQL Server Confutation Manager by choosing "Run-as-Administrator"
When attempting to open SQL Server Configuration Manager in order to alter the SQL Server Services configuration on servers with multiple SQL Server instances,
the following error message is returned:
Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005
and later servers with SQL Server Configuration Manager. Invalid namespace [0x8004100e]
and later servers with SQL Server Configuration Manager. Invalid namespace [0x8004100e]
Product
Struxureware Power Monitoring
Power Monitoring Expert
ION Enterprise
ION EEM
Environment
SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014
Cause
SQL Server Configuration Manager is an important tool to make changes to the SQL Server Services configuration, such as changing SQL Service account password,
changes to Network Protocols, enabling SSL, changing SQL Server startup parameters, etc. This component gets installed when any SQL Server components are installed on the server.
SQL Servers with multiple instances of the same or different versions can use same files for configuration manager, thus causing problems or failures when opening the SQL Server Configuration manager. This commonly occurs on servers where there are multiple SQL Server instances of different versions or architectures which have been installed or uninstalled over time.
Resolution
To resolve this problem follow the below steps.
- Open a command prompt by choosing "Run-as-Administrator"
- Change the directory to C:\Program Files \Microsoft SQL Server\number\Shared folder
- Type the below command and change the number in the command to respective SQL Server version. See below for the correct number to use for the latest SQL Server version installed.
- Change the directory to C:\Program Files \Microsoft SQL Server\number\Shared folder
- Type the below command and change the number in the command to respective SQL Server version. See below for the correct number to use for the latest SQL Server version installed.
mofcomp "%programfiles(x86)%\Microsoft SQL Server\number\Shared\sqlmgmproviderxpsp2up.mof"
- Run the command by pressing Enter, which should complete without any errors.
- Close and open the SQL Server Confutation Manager by choosing "Run-as-Administrator"
The value of number depends on the version of SQL Server Version
Microsoft SQL Server 2012 110
Microsoft SQL Server 2008 R2 100
Microsoft SQL Server 2008 100
Microsoft SQL Server 2005 90
Released for:Schneider Electric Canada
