SCCM Integration failing to pull in computers with error "Did not get a response from the MID server"

[Brandon Warren]

Our SCCM Integration was pulling in computers until about a month ago. We just noticed it's failing and don't know what might've changed to break it. When we execute the scheduled import it runs for the full 300 seconds and then returns the error "Did not get a response from the MID server". Other threads suggested looking at the logs on the mid server so those are pasted below. Any help would be greatly appreciated! 

Thanks in advance!

01/08/19 17:17:19 (002) Worker-Standard:JDBCProbeError Slow execution (265ms) of script: probe:JDBCProbeErrorHandler
01/08/19 17:17:19 (002) Worker-Standard:JDBCProbeError WARNING *** WARNING *** No probe registered to cancel for a given agent correlator 9f89688fdbb6a3c014f45716f496191d
01/08/19 17:17:19 (002) Worker-Standard:JDBCProbeError Enqueuing: C:\ServiceNow\MIDServer1\agent\work\monitors\ECCSender\output_2\ecc_queue.07ba2803dbf6a3c014f45716f49619f2.xml
01/08/19 17:17:19 (002) Worker-Standard:JDBCProbeError Worker completed: JDBCProbeError source: Did not get a response from the MID server time: 0:00:00.281
01/08/19 17:17:19 (034) Worker-Standard:JDBCProbe Enqueuing: C:\ServiceNow\MIDServer1\agent\work\monitors\ECCSender\output_s\ecc_queue.1682f8a99ba0000001.xml
01/08/19 17:17:19 (049) Worker-Standard:JDBCProbe Enqueuing: C:\ServiceNow\MIDServer1\agent\work\monitors\ECCSender\output_s\ecc_queue.1682f8a99ba0000002.xml
01/08/19 17:17:19 (049) Worker-Standard:JDBCProbe Worker completed: JDBCProbe source: 27a0bc575b223200dade2e65f0f91a83 time: 0:00:00.297
01/08/19 17:17:19 (409) ECCSender.1 Sending ecc_queue.07ba2803dbf6a3c014f45716f49619f2.xml
01/08/19 17:17:19 (627) ECCSender.1 Sending ecc_queue.1682f8a99ba0000001.xml
01/08/19 17:17:19 (862) ECCSender.1 Sending ecc_queue.1682f8a99ba0000002.xml
01/08/19 17:17:24 (616) Worker-Standard:JDBCProbe Worker starting: JDBCProbe source: 673170975b223200dade2e65f0f91a69
01/08/19 17:17:24 (850) Worker-Standard:JDBCProbe Waiting for connection semaphore
01/08/19 17:17:24 (850) Worker-Standard:JDBCProbe Obtained connection semaphore
01/08/19 17:17:24 (850) Worker-Standard:JDBCProbe SELECT * FROM

[Jeets]

Hello 

Initially check if the datasource has no network issues and midserver too.

If its fine, you can add system property - glide.jdbcprobeloader.retry to set the number of times JDBC probe attempts to connect to JDBC data source.

You can also check : glide.jdbcprobeloader.retry_millis Sets the number of milliseconds a JDBC probe waits between retry 

Try setting it to 10 minutes for 3 retries and see. 

[Brandon Warren]

Jeets,

Thanks for the quick reply. Our SCCM integration is pulling in software just fine so I don't think it's an issue with the data source (correct me if you think otherwise). 

As far as adding the system properties, I've added the two that were recommended and received the same error.

Any other suggestions are greatly appreciated.

Thanks again!

-Brandon

[Brandon Warren · Accepted solution]

I was able to figure this out, the "Did not get a response from the MID server" message was being caused by the fact that we were running it with load balanced MID servers. Once we removed the load balancers, we stopped receiving the error.