MID Server time out getting data from SCCM...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-29-2012 10:20 AM
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
- Labels:
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-29-2012 12:37 PM
It looks like doubling the Java memory has resolved the crash problem and it also looks like the results are starting to come back.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2017 07:43 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2017 07:47 AM
What does the MID server log show?
If its a windows box with powershell installed you can run this to get the lines that have errors in the last hour.
$path = "<PATHTOAGENTLOG>\agent0.log.0"
$h = ("0" + (Get-Date).AddHours(-1).Hour)
$pattern = "" + (Get-Date -Format MM\\/dd\\/yy) + " " + $h.Substring($h.Length - 2, 2) + "(.)*\* error \*"
Select-String -path $path -pattern $pattern -AllMatches
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2017 08:09 AM
Thank you Drew. Here is the output that i got -
agent0.log.0:23493: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
agent0.log.0:23497:06/15/17 10:06:16 (917) Worker-Standard:JDBCProbe SEVERE *** ERROR *** Socket closed
agent0.log.0:23523:06/15/17 10:06:16 (917) Worker-Standard:JDBCProbe SEVERE *** ERROR ***
com.microsoft.sqlserver.jdbc.SQLServerException: Socket closed
agent0.log.0:23574:06/15/17 10:13:51 (308) Worker-Standard:JDBCProbe SEVERE *** ERROR *** Error when trying to
execute: select distinct vcomp.*, vhwcompsys.Manufacturer, vhwcompsys.Model, vacct1.[Chassis Type] from
vHWComputerSystem vhwcompsys join vComputer vcomp on vcomp.Guid = vhwcompsys._ResourceGuid left join vAC_ChassisType
vacct1 on vcomp.Guid = vacct1.Guid where vcomp.IsManaged = 1
agent0.log.0:23576:06/15/17 10:13:51 (308) Worker-Standard:JDBCProbe SEVERE *** ERROR *** The query has timed out.
agent0.log.0:23601:06/15/17 10:13:51 (308) Worker-Standard:JDBCProbe SEVERE *** ERROR ***
com.microsoft.sqlserver.jdbc.SQLServerException: The query has timed out.
agent0.log.0:23710:06/15/17 10:41:05 (421) Worker-Standard:JDBCProbe SEVERE *** ERROR *** Error when trying to
execute: select distinct vcomp.*, vhwcompsys.Manufacturer, vhwcompsys.Model, vacct1.[Chassis Type] from
vHWComputerSystem vhwcompsys join vComputer vcomp on vcomp.Guid = vhwcompsys._ResourceGuid left join vAC_ChassisType
vacct1 on vcomp.Guid = vacct1.Guid where vcomp.IsManaged = 1
agent0.log.0:23712:06/15/17 10:41:05 (421) Worker-Standard:JDBCProbe SEVERE *** ERROR *** The query has timed out.
agent0.log.0:23737:06/15/17 10:41:05 (421) Worker-Standard:JDBCProbe SEVERE *** ERROR ***
com.microsoft.sqlserver.jdbc.SQLServerException: The query has timed out.
agent0.log.0:23792:06/15/17 10:47:36 (032) Worker-Standard:JDBCProbe SEVERE *** ERROR *** Error when trying to
execute: select Inv_AddRemoveProgram.*, vComputer.Name as installed_on from Inv_AddRemoveProgram, vComputer where
agent0.log.0:23796:06/15/17 10:47:36 (032) Worker-Standard:JDBCProbe SEVERE *** ERROR *** Socket closed
agent0.log.0:23822:06/15/17 10:47:36 (032) Worker-Standard:JDBCProbe SEVERE *** ERROR ***
com.microsoft.sqlserver.jdbc.SQLServerException: Socket closed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2017 08:11 AM
I am able to execute these queries successfully from MID server sql server management studio; but they are getting timed out from SNOW data sources while executing.