CIM - Classify Probe Timed Out

[juancarvajal]

Hello, I'm having troubles to make the discover of an ESX Server.

The problem it's with the "CIM - Classify" Probe, the error is "Session has timed out".

I tried to add the socket_timeout and connection_timeout parameters but the result it's the same.

And it can't continue with the identification phase it never creates the CI. I tried to add a SNMP Classification and it did create the CI, but with this it doesn't populate all the values and relationships that should have.

[KristyS]

Were you able to find a solution to this issue?  I have the same error attempting to scan a storage device. 

[juancarvajal]

There was a problem with the server using 2 IP Addresses, we didn't keep working with this so I don't know what happened.

Did you try using SNMP with the storage device?

[Santosh Kumar8]

this look very old thread, however just wanted to check if anyone got this resolved. I am getting same error.

<results error="Session has timed out" probe_time="140037" result_code="900000"><result/>

[Sivaramakrishn3]

Not sure if this is helpful for this particular issue(ESX discovery). But, for anyone who is after a solution for the CIM session timeout error, start with checking your CIM credentials. My CIM credential was disabled(active=false) when I got this error. The error disappeared when I made the CIM credential active. 

I was able to find the issue when I was troubleshooting with cim_query ServiceNow tool. More on the tool in KB0782305 (Storage Discovery Quick Start Guide). You can access the tool using the url,
 https://<INSTANCE_NAME>/cim_query2.do