Active, couldn't classify: No WMI connection

[anandtk]

Getting this popular error in discovery.

Usually the issues would be around any of the following, not this time.

Already verified the following.

MID server and target (Windows7) are reachable.

Target TCP 135 , 139, 445, DCOM Ports: â—¦High port range 49152 - 65535
â—¦Low port range 1025 - 5000 All are kept open.

Account has :

Local admin right,

Domain wide account,

with password as never expire,

access to execute 'WMI queries' on the target servers.

I have personally used the discovery account to login to the server and ran a simple command on the command prompt and it works well.

Wondering what could be the next step.

WBEM test???

Please share your ideas.

[bernyalvarado]

Hi Anand,

Which services do you restarted? Do you also checked the credentials of your ServiceNow WMI collector service and restarted it?

Thanks,

Berny

[anandtk]

Berny,

You know what ! the discovery is running successfully now.

Did the following thing:

pointed the MID server credentials to the right account > restarted the MID server services > discovery still failing > found SNOW was using the incorrect credentials first and then not moving to the right credential > Was able to find the right credential because of credential test > disabled the incorrect credential > re-discovered the Windows > discovery success >

Now enabled the incorrect credential> credential affinity worked> Discovery is now cool

Bernyl, by the way what WMI collector service are you referring to please? I haven't come across that so far.

Where can I read more onthat?

[bernyalvarado]

That's great! I'm so glad you got it working!!

On regards the WMI collector service... it's one of those many things for which i believe there's no documentation. You just learn it by experience . I'm not sure if you know but Discovery is capable of running its process using the account which is associated MID Server services. This is important specially when customers do not want to enter a high privileged account into the ServiceNow credential store. For such cases, make sure you have that account setup to execute that WMI service as well.  

In anyway, just as many things in life... now you know one more thing you may want to restart if you ever start having mystery / unexplainable issues that may related to the WMI queries.

Have a wonderful rest of your day! Blessings!

Berny  

[kaustubhjjw]

Hey Bernie,

I'm facing a similar issue of a different kind.

Windows classification probe is throwing an error about WMI connections failing. The input queue of the WMI: Classify looks like this:-

gwmi : Could not get objects from namespace root\default. Access deniedAt <<PATH>>/mid.jakarta-05-03-2017__patch5-10-18-2017_10-25-2017_1637.windows.x86-64 (3)\agent\scripts\PowerShell\WMIFetch.psm1:363 char:20+ ...           $reg = gwmi -list -computer $computer -credential $cred -namespa ...+                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo                   : ObjectNotFound: (:) [Get-WmiObject], ManagementException+ FullyQualifiedErrorId : INVALID_NAMESPACE_IDENTIFIER,Microsoft.PowerShell.Commands.GetWmiObjectCommandYou cannot call a method on a null-valued expression.

However, single probe Tests for the Identity probe on the same IPs are successful.

Credential tests are also successful.

Eventually Discovery does not proceed beyond the Classify stage.

Thoughts?

[Ravish Shetty]

hi Berny, do you mean going to the mid server services on the server and changing the log on to use the log on credentials?