What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Problems with wmi

Votes:

0

Hello, My sensors are replacing the following error:

80041013: COM cannot locate a provider referenced in the schema. This error may be caused by any of the following:The provider is using a WMI DLL that does not match the .lib file used when the provider was built.The provider's DLL, or any of the DLLs on which it depends, is corrupt.The provider failed to export DllRegisterServer.An in-process provider was not registered using the regsvr32 command.An out-of-process provider was not registered using the /regserver switch. For example, myprog.exe /regserver.- Note: the OS version of the device could not be determined, WMI might not work reliably.

But,my dll's are ok.

What can I do?

prtg snmp wmi

Created on Jun 20, 2011 2:01:24 PM

Last change on Mar 9, 2018 12:35:41 PM by Luciano Lingnau [Paessler]



3 Replies

Accepted Answer

Votes:

1

Hello,

I'm afraid this is actually something we can't answer as this message comes directly from the target hosts DCOM/WMI. So in fact it's Windows itself reporting this error, and so the question would have to asked to Microsoft.

best regards.

Created on Jun 20, 2011 3:56:49 PM by Torsten Lindner [Paessler Support]



Votes:

0

Hi there, lately i started experiencing the same problem described above. were you able to solve this somehow?

best regards.

Created on Feb 16, 2016 6:16:02 AM



Votes:

0

This is definitely an issue within the DCOM/WMI system on the target machine. If rebooting the target does not help, or only help for a very short time (and the error resurfaces then), we recommend to consider installing a Remote Probe onto the target.
That will mean local WMI monitoring, bypassing the DCOM which often is a lot less problematic. The 2nd alternative would be moving to SNMP (with tools like SNMP Informant) to monitor the target with SNMP instead of WMI.

Created on Feb 17, 2016 8:21:28 AM by Torsten Lindner [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.