Discovery of Windows servers is not going beyond identification phase

[Rakesh16i]

Hi,

We have two MID servers, with same version and same reach-ability to the IP ranges with configured to use same credentials. However discovery of Windows servers is not successful with one MID server (getting completed with status "classified"), but when discovery happens thru other MID, it could able to successfully create the CI.

I can see the following error message

'MultiProbe script error for probe `Windows - Network`: ReferenceError: "related_data" is not defined.'

Please suggest what needs to be done to resolve this issue.

Regards,

Rakesh

[Daniel Draes]

Check if your MID Server has the correct version installed. Most likely it is missing an upgrade.

[Rakesh16i]

All the MID servers are having same version...

[natem]

This is the correct answer. I found that our MID Servers failed to auto-upgrade when we upgraded to Geneva. There may be a bug that is preventing the auto-upgrade from working... but I was able to fix this issue by upgrading the MID Server (actually had to install a new one and uninstall the old...)

[Daniel Draes]

You can contact HI support to get deeper help.

For me it worked to make sure the MID server was upgrade to the correct build. It seems the response from the WMI Probe looks different based on the MID build. You could compare them by looking the the ECC Queue entries of direction 'input' and probe 'WMIProbe'.