CIs not getting discovered via Quick Discovery but not via Discovery schedules.

[Gurpreet_Bhami]

Hi,

I am unable to discover the CIs via Discovery schedules. It is giving me an error" Active couldn't classify, No WMI connection", however when I am running the same CI via Quick discovery, it is working fine. 

Please suggest.

[PavanBV]

Are you using the same mid server when trying to run the quick discovery and discovery schedule? Ensure you are using the same MID. 

Also, check the credential record created for that CI and ensure that its applicable for the MID server cluster you are using at the discovery schedule. 

[Gurpreet_Bhami]

Hi Pavan,

Getting the mid server issues. 

Issue source "MIDFilePermEnforcer" encountered at the mid server.  

Short description - An unexpected error occurred: Command: 97bc1e4f-69be-4a58-adf5-760936290954 with id: enforcePerms "D:\ServiceNow MID Server \agent" "snc_mid_Staging MIDServer 2" $true "" timed out after 120 seconds

[Rahul Priyadars]

Make Sure schedule which has given IP for the server , has WMI ports opened from Mid Server to Host.

ServiceNow Discovery uses WMI for discovery, therefore port 135 from the MID Server to the Remote Windows host must be open for initial communication AND high ports 49152 - 65535 must be open for the remainder of the communication. 

If you get "Active, couldn't classify: No WMI connection" error try things mentioned below: This error could be a credential issue or blocked port issue. I would suggest 2 troubleshooting steps to help resolve this error. RDP from the MID server to the Remote Windows host to validate the Windows credential.

https://support.servicenow.com/kb_view.do?sysparm_article=KB0657528

Try this Command from Mid Server to Given Host IP

gwmi win32_operatingsystem -computer 192.168.200.14 -credential 'LOCALDOMAIN\mid'

Regards

RP

[Gurpreet_Bhami]

Hi Rahul,

Getting the mid server issues. 

Issue source "MIDFilePermEnforcer" encountered at the mid server.  

Short description - An unexpected error occurred: Command: 97bc1e4f-69be-4a58-adf5-760936290954 with id: enforcePerms "D:\ServiceNow MID Server \agent" "snc_mid_Staging MIDServer 2" $true "" timed out after 120 seconds