Code Project

Link Unit

Thursday, September 05, 2013

SQL Server Configuration Manager – Cannot connect to WMI provider – Invalid class [0x80041010]





SQL Server Configuration Manager – Cannot connect to WMI provider – Invalid class [0x80041010]

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]






Occasionally, during setup, some .mof (Managed Object Format) files don't get installed or registered correctly.  There is a program called mofcomp that is responsible for registering and storing the data associated with .mof files.  If the .mof file information becomes damaged or compromised, or never installed correctly, the problem will result in an error message like above:



Solution:

Mofcomp "%programfiles(x86)%\Microsoft\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
 





SQL SERVER – FIX : ERROR : (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: )




 SQL SERVER – FIX : ERROR : (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: )

Checklist in case of above error

#1. SQL Server service must be running.
Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> SQL Server Services, and check if SQL Server service status is “Running”.

#2. TCP/IP enabled.
When two or more SQL Servers are connected across network they do all communication using TCP/IP. The default port of SQL Server installation is 1433. This port can be changed through SQL Server Configuration Manager. TCP/IP should be enabled for SQL Server to be connected.

#3. Add Port  in Windows Firewall on SQL Server instance.
Go to Control Panel >> Windows Firewall >> Change Settings >> Exceptions  >> Add Port

#4 Enable Remote Connection
In order to connect to machine other than local we need to enable remote connection on instance.

#5 Enable SQL Server Browser service