The reason, I like SQL Server as a product is that there are multiple solutions to one problem and one can use the method they find most convenient. Almost three years ago, I wrote a blog post about how to solve the error: Configuration Manager – Cannot Connect to WMI Provider. You Do Not Have Permission or The Server is Unreachable. The other day, I faced the same error again and this time I solved it with a different method. Let us learn how I did that.  When I was working with my client Comprehensive Database Performance Health Check, I suddenly received the following 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 and later servers with SQL Server Configuration Manager. SOLUTION/WORKAROUND – WMI ProviderHere is what we did to fix the problem. The first opened a command prompt in the location machine and ran the following command according to the SQL Server version which was installed on the machine. SQL Server 2005 mofcomp “%programfiles(x86)%\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof” SQL Server 2008 / R2 mofcomp “%programfiles(x86)%\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof” SQL Server 2012 mofcomp “%programfiles(x86)%\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof” SQL Server 2014 mofcomp “%programfiles(x86)%\Microsoft SQL Server\120\Shared\sqlmgmproviderxpsp2up.mof” SQL Server 2016 mofcomp “%programfiles(x86)%\Microsoft SQL Server\130\Shared\sqlmgmproviderxpsp2up.mof” SQL Server 2017 mofcomp “%programfiles(x86)%\Microsoft SQL Server\140\Shared\sqlmgmproviderxpsp2up.mof” SQL Server 2019 mofcomp “%programfiles(x86)%\Microsoft SQL Server\150\Shared\sqlmgmproviderxpsp2up.mof” When you run the above statement, it will give you success output. However, if due to any reason, you do not get Success, you will have to follow the suggestion provided in my earlier blog post over here. I hope you will be able to solve your problem easily and quickly and get started with SQL Server Configuration Manager. If you are familiar with any such other tip or trick, do let me know and I will be happy to post about them on this blog post with due credit to you. Thank you for your response detail of error log is as follow, i will also be attaching a pdf file of the ss error i got 2022-11-22 19:42:33.45 Server Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 Copyright (C) 2019 Microsoft Corporation Express Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 22621: ) (Hypervisor) 2022-11-22 19:42:33.46 Server UTC adjustment: -5:00 2022-11-22 19:42:33.46 Server (c) Microsoft Corporation. 2022-11-22 19:42:33.46 Server All rights reserved. 2022-11-22 19:42:33.46 Server Server process ID is 16216. 2022-11-22 19:42:33.46 Server System Manufacturer: 'HP', System Model: 'HP ENVY x360 2-in-1 Laptop 15-ey0xxx'. 2022-11-22 19:42:33.46 Server Authentication mode is WINDOWS-ONLY. 2022-11-22 19:42:33.46 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Log\ERRORLOG'. 2022-11-22 19:42:33.46 Server The service account is 'NT AUTHORITY\LOCAL SERVICE'. This is an informational message; no user action is required. 2022-11-22 19:42:33.46 Server Registry startup parameters: -d C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\DATA\master.mdf -e C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Log\ERRORLOG -l C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\DATA\mastlog.ldf 2022-11-22 19:42:33.46 Server Command Line Startup Parameters: -s "SQLEXPRESS" -m "SqlSetup"-q "SQL_Latin1_General_CP1_CI_AS" -T 4022 -T 4010 -T 3659 -T 3610 -T 8015 -d "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Template Data\master.mdf" -l "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf" 2022-11-22 19:42:33.47 Server SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 2022-11-22 19:42:33.47 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2022-11-22 19:42:33.47 Server Detected 15679 MB of RAM. This is an informational message; no user action is required. 2022-11-22 19:42:33.47 Server Using conventional memory in the memory manager. 2022-11-22 19:42:33.47 Server Page exclusion bitmap is enabled. 2022-11-22 19:42:33.55 Server Buffer Pool: Allocating 2097152 bytes for 1795553 hashPages. 2022-11-22 19:42:33.56 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033) 2022-11-22 19:42:33.57 Server Buffer pool extension is already disabled. No action is necessary. 2022-11-22 19:42:33.59 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled. 2022-11-22 19:42:33.61 Server Query Store settings initialized with enabled = 1, 2022-11-22 19:42:33.61 Server The maximum number of dedicated administrator connections for this instance is '1' 2022-11-22 19:42:33.61 Server This instance of SQL Server last reported using a process ID of 12720 at 2022-11-22 7:42:29 PM (local) 2022-11-23 12:42:29 AM (UTC). This is an informational message only; no user action is required. 2022-11-22 19:42:33.62 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 2022-11-22 19:42:33.62 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 2022-11-22 19:42:33.62 Server Lock partitioning is enabled. This is an informational message only. No user action is required. 2022-11-22 19:42:33.63 Server In-Memory OLTP initialized on standard machine. 2022-11-22 19:42:33.63 Server [INFO] Created Extended Events session 'hkenginexesession' 2022-11-22 19:42:33.63 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required. 2022-11-22 19:42:33.64 Server Total Log Writer threads: 2. This is an informational message; no user action is required. 2022-11-22 19:42:33.64 Server Database Mirroring Transport is disabled in the endpoint configuration. 2022-11-22 19:42:33.64 Server clwb is selected for pmem flush operation. 2022-11-22 19:42:33.64 spid9s Warning ****************** 2022-11-22 19:42:33.64 Server Software Usage Metrics is disabled. 2022-11-22 19:42:33.64 spid9s SQL Server started in single-user mode. This an informational message only. No user action is required. 2022-11-22 19:42:33.64 spid9s Starting up database 'master'. 2022-11-22 19:42:33.66 spid9s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Template Data\master.mdf. 2022-11-22 19:42:33.75 Server CLR version v4.0.30319 loaded. 2022-11-22 19:42:33.86 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319. additional log info from bootstrap Overall summary: Final result: Failed: see details below Exit code (Decimal): -2061893606 Start time: 2022-11-22 19:36:21 End time: 2022-11-22 19:43:00 Requested action: Install Setup completed with required actions for features. Troubleshooting information for those features: Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Next step for BC: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Next step for Conn: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Machine Properties: Machine name: NELSON Machine processor count: 16 OS version: Microsoft Windows 11 Home (10.0.22621) OS service pack: OS region: United States OS language: English (United States) OS architecture: x64 Process architecture: 64 Bit OS clustered: No Product features discovered: Product Instance Instance ID Feature Language Edition Version Clustered Configured Package properties: Description: Microsoft SQL Server 2019 ProductName: SQL Server 2019 Type: RTM Version: 15 SPLevel: 0 Installation location: C:\SQL2019\ExpressAdv_ENU\x64\setup\ Installation edition: Express Product Update Status: None discovered. User Input Settings: ACTION: Install ADDCURRENTUSERASSQLADMIN: true AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE AGTSVCPASSWORD: ***** AGTSVCSTARTUPTYPE: Disabled ASBACKUPDIR: Backup ASCOLLATION: Latin1_General_CI_AS ASCONFIGDIR: Config ASDATADIR: Data ASLOGDIR: Log ASPROVIDERMSOLAP: 1 ASSERVERMODE: TABULAR ASSVCACCOUNT: <empty> ASSVCPASSWORD: <empty> ASSVCSTARTUPTYPE: Automatic ASSYSADMINACCOUNTS: <empty> ASTELSVCACCT: <empty> ASTELSVCPASSWORD: <empty> ASTELSVCSTARTUPTYPE: 0 ASTEMPDIR: Temp BROWSERSVCSTARTUPTYPE: Disabled CLTCTLRNAME: <empty> CLTRESULTDIR: <empty> CLTSTARTUPTYPE: 0 CLTSVCACCOUNT: <empty> CLTSVCPASSWORD: <empty> CLTWORKINGDIR: <empty> COMMFABRICENCRYPTION: 0 COMMFABRICNETWORKLEVEL: 0 COMMFABRICPORT: 0 CONFIGURATIONFILE: CTLRSTARTUPTYPE: 0 CTLRSVCACCOUNT: <empty> CTLRSVCPASSWORD: <empty> CTLRUSERS: <empty> ENABLERANU: true ENU: true EXTSVCACCOUNT: <empty> EXTSVCPASSWORD: <empty> FEATURES: SQLENGINE, REPLICATION, CONN, BC, SDK, LOCALDB FILESTREAMLEVEL: 0 FILESTREAMSHARENAME: <empty> FTSVCACCOUNT: <empty> FTSVCPASSWORD: <empty> HELP: false IACCEPTPYTHONLICENSETERMS: false IACCEPTROPENLICENSETERMS: false IACCEPTSQLSERVERLICENSETERMS: true IACKNOWLEDGEENTCALLIMITS: false INDICATEPROGRESS: false INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\ INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\ INSTALLSQLDATADIR: <empty> INSTANCEDIR: C:\Program Files\Microsoft SQL Server\ INSTANCEID: SQLEXPRESS INSTANCENAME: SQLEXPRESS ISMASTERSVCACCOUNT: NT AUTHORITY\Network Service ISMASTERSVCPASSWORD: <empty> ISMASTERSVCPORT: 8391 ISMASTERSVCSSLCERTCN: <empty> ISMASTERSVCSTARTUPTYPE: Automatic ISMASTERSVCTHUMBPRINT: <empty> ISSVCACCOUNT: NT AUTHORITY\Network Service ISSVCPASSWORD: <empty> ISSVCSTARTUPTYPE: Automatic ISTELSVCACCT: <empty> ISTELSVCPASSWORD: <empty> ISTELSVCSTARTUPTYPE: 0 ISWORKERSVCACCOUNT: NT AUTHORITY\Network Service ISWORKERSVCCERT: <empty> ISWORKERSVCMASTER: <empty> ISWORKERSVCPASSWORD: <empty> ISWORKERSVCSTARTUPTYPE: Automatic MATRIXCMBRICKCOMMPORT: 0 MATRIXCMSERVERNAME: <empty> MATRIXNAME: <empty> MRCACHEDIRECTORY: NPENABLED: 0 PBDMSSVCACCOUNT: <empty> PBDMSSVCPASSWORD: <empty> PBDMSSVCSTARTUPTYPE: 0 PBENGSVCACCOUNT: <empty> PBENGSVCPASSWORD: <empty> PBENGSVCSTARTUPTYPE: 0 PBPORTRANGE: <empty> PBSCALEOUT: false PID: ***** QUIET: false QUIETSIMPLE: false ROLE: AllFeatures_WithDefaults RSINSTALLMODE: DefaultNativeMode RSSVCACCOUNT: <empty> RSSVCPASSWORD: <empty> RSSVCSTARTUPTYPE: Automatic SAPWD: <empty> SECURITYMODE: <empty> SQLBACKUPDIR: <empty> SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS SQLJAVADIR: <empty> SQLMAXDOP: 0 SQLMAXMEMORY: 2147483647 SQLMINMEMORY: 0 SQLSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE SQLSVCINSTANTFILEINIT: true SQLSVCPASSWORD: ***** SQLSVCSTARTUPTYPE: Automatic SQLSYSADMINACCOUNTS: NELSON\Nwach SQLTELSVCACCT: NT Service\SQLTELEMETRY$SQLEXPRESS SQLTELSVCPASSWORD: <empty> SQLTELSVCSTARTUPTYPE: Automatic SQLTEMPDBDIR: <empty> SQLTEMPDBFILECOUNT: 1 SQLTEMPDBFILEGROWTH: 64 SQLTEMPDBFILESIZE: 8 SQLTEMPDBLOGDIR: <empty> SQLTEMPDBLOGFILEGROWTH: 64 SQLTEMPDBLOGFILESIZE: 8 SQLUSERDBDIR: <empty> SQLUSERDBLOGDIR: <empty> SUPPRESSPAIDEDITIONNOTICE: false SUPPRESSPRIVACYSTATEMENTNOTICE: false TCPENABLED: 0 UIMODE: AutoAdvance UpdateEnabled: true UpdateSource: MU USEMICROSOFTUPDATE: false USESQLRECOMMENDEDMEMORYLIMITS: false X86: false Configuration file: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20221122_193621\ConfigurationFile.ini Detailed results: Feature: Database Engine Services Status: Failed Reason for failure: An error occurred during the setup process of the feature. Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Component name: SQL Server Database Engine Services Instance Features Component error code: 0x851A001A Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes. Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=15.0.2000.5&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026 Feature: SQL Server Replication Status: Failed Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Component name: SQL Server Database Engine Services Instance Features Component error code: 0x851A001A Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes. Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=15.0.2000.5&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026 Feature: SQL Browser Status: Passed Feature: SQL Writer Status: Passed Feature: LocalDB Status: Passed Feature: Client Tools Backwards Compatibility Status: Failed Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Component name: SQL Server Common Files Component error code: 0x84BB0001 Error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start. Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=15.0.2000.5&EvtType=0xA60E3551%400xD3BEBD98%401211%401&EvtType=0xA60E3551%400xD3BEBD98%401211%401 Feature: Client Tools SDK Status: Passed Feature: Client Tools Connectivity Status: Failed Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail. Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Component name: SQL Server Common Files Component error code: 0x84BB0001 Error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start. Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=15.0.2000.5&EvtType=0xA60E3551%400xD3BEBD98%401211%401&EvtType=0xA60E3551%400xD3BEBD98%401211%401 Rules with failures or warnings: Rules report file: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20221122_193621\SystemConfigurationCheck_Report.htm |
