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]
ISSUE
SQL Server Configuration Manager error 0x80041010
When you try to open SQL Server Configuration Manager, it fails with 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]
SOLUTION
Recompile the sqlmgmproviderxpsp2up.mof file. Note that this file location varies depending on SQL Server version.
SRSRP.log shows ” The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content.”
ISSUE
SRSRP.log shows: System.Web.Services.Protocols.SoapException: The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content.
SOLUTION
Open Reporting Service Configuration Manager > Connect to SSRS Server Instance.
Click on the Encryption Keys from the left pane.
If you have a backup key with extension “.snk” and Password, Click on the ‘Restore’ button.
If you do not have a backup from the Encryption Keys> Click on Delete button.
Wait for a moment until getting that result.
If you do not have a backup from the symmetric key, you will need to reconfigure the report data source after deleting the encrypted content by doing the following:
Open Report Manager.
Go to Data source.
Click Manage as shown below:
Make sure that the connection string and its credentials have been provided successfully.
Click on Test Connection and make sure that the Connection created successfully
Reopen the related report again, to make sure that the report is loading properly and the The report server cannot decrypt the symmetric key error is gone!
After having configured reporting services, we can create subscriptions in SCCM console to reports from which we want to get updates. This is also a feature from SQL Server Reporting Services, which let us configure the automatic delivery of specified reports by email or to a file share at scheduled intervals. Refer to Operations and maintenance for reporting – Configuration Manager | Microsoft Docs on how to create subscriptions.
We can check the subscription from \Monitoring\Overview\Reporting\Subscriptions in the console. The Status column shows the status of the subscription. It can tell the exact reason in case of errors.
It is quite convenient to verify the subscriptions status from the console. However, I once encounter a weird issue that whenever I clicked on the Subscriptions menu the console crashed. I had no time to debug this crash while it was urgent for me to get a quick result of the subscription result. Where to get the Status of the subscription?
Here is the query you can rely on in such a case –
SELECT
[OwnerID]
,[Report_OID]
,[Locale]
,[InactiveFlags]
,[ExtensionSettings]
,[ModifiedByID]
,[ModifiedDate]
,[Description]
,[LastStatus]
,[EventType]
,[MatchData]
,[LastRunTime]
,[Parameters]
,[DataSettings]
,[DeliveryExtension]
,[Version]
,[ReportZone]
FROM [ReportServer].[dbo].[Subscriptions] ORDER BY LastRunTime DESC;
The LastStatus column shows the exactly the same information as you see in the Status column in Subscriptions in the console. Example (other columns removed from the result) –
LastStatus
Failure writing file \\CONTOSOPS1\temp\ReportsSubs\22.xls : A log on error occurred when attempting to access the file share. The user account or password is not valid.
Failure writing file \\CONTOSOPS1\temp\ReportSubs\test.xls : A log on error occurred when attempting to access the file share. The user account or password is not valid.
This way we do not have to count to SCCM console to get the subscription status of the reports we have subscribed to.
Looking at LocationServices.log, we found the following messages –
05-24-2021 22:59:00.664 LocationServices 5924 (0x1724) 1 proxy MP errors in the last 10 minutes, threshold is 5.
05-24-2021 22:59:49.974 LocationServices 13528 (0x34d8) 2 proxy MP errors in the last 10 minutes, threshold is 5.
05-24-2021 23:00:01.747 LocationServices 9620 (0x2594) 3 proxy MP errors in the last 10 minutes, threshold is 5.
05-24-2021 23:00:31.063 LocationServices 13528 (0x34d8) 4 proxy MP errors in the last 10 minutes, threshold is 5.
05-24-2021 23:00:46.937 LocationServices 15764 (0x3d94) Proxy MP error threshold reached, moving to next MP.
DataTransferService.log –
05-24-2021 23:04:44.994 DataTransferService 15764 (0x3d94) BITS compatible path: http://secondarysite.contoso.com:80/SMS_MP/.sms_pol?%7BF4CA6035-61A2-4146-89C0-50DB591157A0%7D.SHA256:36A294B138C353F4487562349357BE61D23B9C631D8707BC79B712A5D836DC0F
05-24-2021 23:04:44.994 DataTransferService 15764 (0x3d94) BITSHelper: Full source path to be transferred = http://secondarysite.contoso.com:80/SMS_MP/.sms_pol?%7BF4CA6035-61A2-4146-89C0-50DB591157A0%7D.SHA256:36A294B138C353F4487562349357BE61D23B9C631D8707BC79B712A5D836DC0F
05-24-2021 23:04:44.994 DataTransferService 15764 (0x3d94) BITSHelper, remote name = http://secondarysite.contoso.com:80/SMS_MP/.sms_pol?%7BF4CA6035-61A2-4146-89C0-50DB591157A0%7D.SHA256:36A294B138C353F4487562349357BE61D23B9C631D8707BC79B712A5D836DC0F, local name = C:\WINDOWS\CCM\Staging{F4CA6035-61A2-4146-89C0-50DB591157A0}.1.00.tmp
Visiting the highlighted link in the browser on the client computer returns 500 Server Internal Error.
Bits job, retrieved by running “bitsadmin /list /allusers /verbose“, has the following information. Obviously, something goes wrong with the management point on the secondary site. More likely relevant to IIS.
UID: {A5A891C5-4EB7-4EB2-BE44-19BB40F66CCA} DISPLAY: 'CCMDTS Job'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\SYSTEM
PRIORITY: HIGH FILES: 0 / 2 BYTES: 0 / UNKNOWN
CREATION TIME: 5/24/2021 11:04:44 PM MODIFICATION TIME: 5/24/2021 11:17:58 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: REGISTERED NOTIFICATION FLAGS: 11
RETRY DELAY: 60 NO PROGRESS TIMEOUT: 28800 ERROR COUNT: 14
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE: http://secondarysite.contoso.com:80/SMS_MP/.sms_pol?%7BF4CA6035-61A2-4146-89C0-50DB591157A0%7D.SHA256:36A294B138C353F4487562349357BE61D23B9C631D8707BC79B712A5D836DC0F -> C:\WINDOWS\CCM\Staging{F4CA6035-61A2-4146-89C0-50DB591157A0}.1.00.tmp
ERROR CODE: 0x801901f4 - HTTP status 500: An unexpected condition prevented the server from fulfilling the request.
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
We enabled the failed request tracing for IIS on the secondary site, then reproduced the issue by visiting the highlighted URL in red. No surprise, still 500 error. At the same time, failed request tracing logs are generated. Here is what we got –
It points to the getpolicy.dll, which is a file from SCCM itself. Okay, now we know that it is not the IIS that brings the issue but the management point itself.
In MP_Framework.log, we found this information –
MPDB ERROR - CONNECTION PARAMETERS
SQL Server Name : secondarysite.contoso.com\CONFIGMGRSEC
SQL Database Name : CM_SS1
Integrated Auth : True
MPDB ERROR - EXTENDED INFORMATION
MPDB Method : ExecuteSP()
MPDB Method HRESULT : 0x80004005
Error Description : Login failed for user 'lnsvr_admin'.
OLEDB IID : {0C733A63-2A1C-11CE-ADE5-00AA0044773D}
ProgID : Microsoft SQL Server Native Client 11.0
MPDB ERROR - INFORMATION FROM DRIVER
SQL Server Name : SCCMSiteDBSQL02
Native Error no. : 18456
Error State : 1
Class (Severity) : 14
Line number in SP : 1
But what is this ” lnsvr_admin ” user? We tried to find login failure information from the secondary site database CM_SS1 but got nothing (In fact, ” SQL Server Name : SCCMSiteDBSQL02 ” pointed out already the right target sql server but we neglected that information). What is going on? It dawned on us that there could be a linked server object in this secondary site database which is using ” lnsvr_admin ” as the connection account. We were right –
Right click on the linked server object and select Test Connection. It failed.
On the linked server’s events log, we could find similar messages –
The customer told us that that account’s password has been changed by their sql server administrator but they never did any change to the linked server object. All is clear now – the account ” lnsvr_admin ” has the wrong password in the linked server object and thus failed to connect to the linked server.
Solution
After we updated the password for ” lnsvr_admin ” to the correct one, all the errors in MP_Framework.log went away and the ” proxy MP errors …” also disappeared from LocationServices.log and Software Center finally shows applications and updates.
Configuration Manager install failed with “A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online”
Installing Configuration Manager 2002 failed at Database Information with the following error message –
UDL with SQL Server Native Client showed the following message –
The client and server cannot communicate, because they do not posses a common algorithm. Client unable to establish connection Encryption not supported on the client
ConfigMgrSetup.log has such messages –
04-07-2021 11:28:13.230 Configuration Manager Setup 5404 (0x151c) *** [08001][21][Microsoft][SQL Server Native Client 11.0]Encryption not supported on the client. 04-07-2021 11:28:13.230 Configuration Manager Setup 5404 (0x151c) *** [08001][-2146893007][Microsoft][SQL Server Native Client 11.0]SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm.~~ 04-07-2021 11:28:13.230 Configuration Manager Setup 5404 (0x151c) *** [08001][21][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection 04-07-2021 11:28:13.230 Configuration Manager Setup 5404 (0x151c) *** [08001][-2146893007][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
The fact is that SQL Server 2019 is ready on a separate server. Both the SQL server and SCCM server have the same SSL capabilities(IISCRYPTO is a good free tool that gives administrators the ability to enable or disable protocols, ciphers, hashes and key exchange algorithms on Windows Server 2008, 2012, 2016 and 2019). What is the problem then?
It turned out that on SCCM server SQL Server Native Client version, which is 11.0.2100.60, is too low.
Per the official guide, the minimum version is SQL Server 2012 SP4 (11.*.7001.0). The final solution is to upgrade SQL Server Native Client to the supported version. You can download it here –