MID Server time out getting data from SCCM...

DrewW · ‎03-29-2012

I am using the SCCM plugin and trying to import the software data which is about 4,300,000 rows. The import times out before the data is done being compiled. Does anyone have any ideas on how to get the import to wait for the MID server for more than 300 seconds OR a way to break the data up in such a way that I can get it in smaller chunks?

Any help would be appreciated.

Drew

DrewW · ‎06-15-2017

If you take this part of the line returned

agent0.log.0:23493:06/15/17 10:06:16 (917)

You can look at the things that happened before and after list log line to see what the other detail there is.

Are you running the MID Server service as a domain account? If so does that account have access to the SQL box?

Pravin17 · ‎06-15-2017

Hi Drew,

Here are the logs -

4:53 (010) LogStatusMonitor.60 stats threads: 41, memory max: 1828.0mb, allocated: 128.0mb, used: 30.0mb, standard.queued: 0 probes, standard.processing: 1 probes expedited.queued: 0 probes, expedited.processing: 0 probes interactive.queued: 0 probes, interactive.processing: 0 probes

06/15/17 10:05:53 (010) LogStatusMonitor.60 stats threads: 41, memory max: 1828.0mb, allocated: 116.0mb, used: 31.0mb, standard.queued: 0 probes, standard.processing: 1 probes expedited.queued: 0 probes, expedited.processing: 0 probes interactive.queued: 0 probes, interactive.processing: 0 probes

06/15/17 10:06:16 (901) Worker-Standard:JDBCProbeError Worker starting: JDBCProbeError source: Did not get a response from the MID server

06/15/17 10:06:16 (917) Worker-Standard:JDBCProbeError Cancellation called on probe com.service_now.mid.probe.JDBCProbe

06/15/17 10:06:16 (917) Worker-Standard:JDBCProbe SEVERE *** ERROR *** Error when trying to execute: select Inv_AddRemoveProgram.*, vComputer.Name as installed_on from Inv_AddRemoveProgram, vComputer where

Inv_AddRemoveProgram.DisplayName NOT LIKE '%update%' AND Inv_AddRemoveProgram.DisplayName NOT LIKE '%service pack%' AND

Inv_AddRemoveProgram.DisplayName NOT LIKE '%Windows 7%' AND

vComputer.Guid = Inv_AddRemoveProgram._ResourceGuid AND vComputer.IsManaged = 1 ORDER BY _SoftwareComponentGuid

06/15/17 10:06:16 (917) Worker-Standard:JDBCProbe SEVERE *** ERROR *** Socket closed

com.microsoft.sqlserver.jdbc.SQLServerException: Socket closed

at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)

at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1789)

at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:4838)

Also I am not using the domain service account for MID & using the local account for MID server. And i have configured the same user credentials for DB access. This scenario is working for other Altiris DBs we are having in our environment. However, failing for this one only

DrewW · ‎06-15-2017

These makes me curious

06/15/17 10:06:16 (901) Worker-Standard:JDBCProbeError Worker starting: JDBCProbeError source: Did not get a response from the MID server

06/15/17 10:06:16 (917) Worker-Standard:JDBCProbeError Cancellation called on probe com.service_now.mid.probe.JDBCProbe

Why is a cancellation being called and why is the MID Server not getting a response from itself, assuming thats what the one error means....?

Pravin17 · ‎06-15-2017

Right; that too for loading only 20 records. May be the MID server waited for 300 seconds for getting the response from SQL DB & its getting failed & in return it is giving the Response error. Is there a way if i can set or change these 300 seconds to say 2-3 minutes to get response from SQL? So that MID server wait time will increase.

DrewW · ‎06-15-2017

You can, Its in your Import Export properties. Are you sure you are getting data and if so how much? The error you are seeing is indicating that there is an issue with the MID server itself and no amount of waiting is going to get it to work.