Skip to main content

SQL Server Configuration Manager cannot connect to WMI

Sometime before I faced different kind of issue on one of staging SQL Server. I required to change the TCP port of an instance where multiple instance were running, I just open compmgmt.msc and connected SQLServer Configuration Manager, then I started receiving error : “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 class [0x80041010], SQL Server Cannot Connect to WMI Provider permissions or server is unreachable.


This may caused by an issue with the compiled SQL Configuration Manager GUI’s communication with WMI. If we have multiple instance running on SQL Server on a single windows server or we have un-installed any instances then this kind of issues we may face to connect.


Solution

1. At first start the command prompt

2. Then locate the path of SSCM shared instance based on version, we can get the path where shared tool as below

SQL 2008:  C:\Program Files (x86)\Microsoft SQL Server\90\Shared\
SQL 2008 R2:  C:\Program Files (x86)\Microsoft SQL Server\100\Shared\
SQL 2012:  C:\Program Files (x86)\Microsoft SQL Server\110\Shared\
SQL 2014:  C:\Program Files (x86)\Microsoft SQL Server\120\Shared\

3. Then run the below command from above location.

mofcomp sqlmgmproviderxpsp2up.mof



Now try to connect same again.

Hope you can connect.

Happy reading

Comments

Popular posts from this blog

How to encrypt and decrypt Table data in postgres

For encrypting and decrypting , we must use the bytea data type on the column which we implement. Bcoz bytea will use the pgcrypto method by default. However, you will need to create the pgcrypto extension to enable these functions as they are not pre-defined in PostgreSQL/PPAS. Example CREATE EXTENSION pgcrypto; CREATE TABLE userinfo (username varchar(20), password bytea); >>    Inserting the data in an encrypted format INSERT INTO userinfo VALUES(' suman ',encrypt('111222','password','aes')); select * from userinfo ; >>    Retrieving the data as decrypted format SELECT decrypt(password,decode('password','escape'::text),'aes'::text) FROM userinfo; Thanks for reading Plz dont forget to like Facebook Page.. https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

How to recover msdb database from suspect mode

 It was Monday 9 th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server. “MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. ·          23 May 1995 - First internal release ·          Year 1996 - Version 3 o     Simple CRUD operations o     January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o     production release 1998, from www.mysql.com ·          Year 2002 - Version 4 o     MyISAM o     unions o     Tracking o     B-trees o     s...