Terminated the probe because the max timeout was reached: 610 seconds

[brukasmj]

The warning as printed in the subject line is popping up in the Logfile section and related to Powershell / Wmi runner

Is this something related to shortage of resources on the mid server or is it just a setting which needs to be customized ?

thanks

John

[Henrik Jutterst]

Hi Bharat!

So, here's the feedback I told you I was going to add to the issue.

It actually seems that WMI permissions was the case. What I did was, after looking into the logs on the MID-server, was to verify that WMI permissions was fully granted for the users running MID server service. And after that re-ran the Discovery and viola! The issue was not showing up any more.

But there is more behind this issue I think, because I have been working a lot with stored credentials in ServiceNow and I also think that might have been an issue to related problems. I'm pretty sure the username and password was correct in my case, but there's also important to have the correct domain before username (example: domain\username) and I think that also was one of the issue behind what I was experiencing not to work.

So, John. Do validate credentials and WMI permissions. That's my best tip. Also, make sure you are a domain user with local admin on all target machines and have permissions to run remote PowerShell scripts on all the target machines.

Regards

/Henrik

[Henrik Jutterst]

John, take a look at the comment I just did. It solved my issue and it might solve yours too.

Good luck!

/Henrik

[Henrik Jutterst]

John, please take a look at this link. I think this is the real issue behind this warning message.

WMI classification probe timeout

In short, we set the threads back to 25 and even though it took a lot longer time the prob time out message was solved.

Good luck.