Since this morning shortly before midnight, all of my WMI sensors fail with the error "Connection could not be established (8002802B: Element not found - Host: gheterm2, User: ghesrvacc, Password: **, Domain: ntlmdomain:soi.dir.solutia.com) (code: PE015)"
I have looked in the knowledgebase and tried to find some reasons why these suddenly fail. I have rebooted Domain controllers, the paessler servers, checked WMI and WBEM, security, accounts and passwords. I found nothing wrong. I also tried the WMITEST utility from Paessler and could not find any problems. For instance, when i test the above sensor with the same credentials and requesting the same info (bandwidth), the system just returns the right data.
What else can I check ?
Lieven Dhaenens.
Article Comments
I have tried that but that doesn't work. The account I am running the probe with now, is domain admin, so that should be sufficient rights. I have done an "upgrade in place" on the server running my local probe, installing the same OS version as it has now, and that seemed to correct the issue. But my local probes are still failing with the same error.
Nov, 2010 - Permalink
Hello Lieven
Did you find a solution why the local probes are failing? i have the same issue!
Thank you very much -Will
Feb, 2011 - Permalink
I don't remember exactly, but as far as I remember, I had to rebuild the WMI repository on the monitoring server. once that was done, all started working again. It was strange, since WMI looked completely normal, but still this fixed it.
Feb, 2011 - Permalink
Hello,
the fact that the WMI Tester succeeds with the WMI Query strongly suggests that the issue lies within account under which the PRTG Probe runs. Most likely you ran the WMI Tester under your "personal" user account which is different then the user account under which the PRTG Probe Service is running (by default the "LOCAL SYSTEM"). You could try changing this (please don't forget to restart the Probe Service after the change).
Best regards.
Nov, 2010 - Permalink