Reporting InitialSync Job Timeout RRS feed

  • Question

  • After installing FIM Reporting, my initialsync job ran for about 24 hours before failing due to "Timeout expired".  I have since increased the memory on both the SC Management and SC Datawarehouse servers and kicked off the InitialSync job again.  Each time it now runs for about 1.5hrs before failing with an error stating "The relationship source specified in the discovery data item is not valid." followed by some XML data.  Theres an Error (ID 68) in the App Log on the FIM Service Server that the "FIM Reporting ETL Job failed while making a call to the System Center Service Manager Management Server SDK service" can suggests this may be a network issue, internal issue, or to install the FIM Reporting scripts on the DW.  I have reinstalled these as well.

    Any suggestions on where to go from here?



    • Edited by RYounk007 Monday, October 1, 2012 3:26 PM
    Monday, September 24, 2012 8:13 PM

All replies

  • As I have been continually increasing the disk/memory/cpu on the SC Management Server, I am still running into "The requested operation timed out" error on the Initial Reporting job in the Portal.  It is not clear to me what time-out is being hit here or how to increase this.  I suspect it may be due to that fact that I have over 300,000 requests that need to be loaded into System Center.  Any suggestions on how to identify and/or increase the timeouts in SCSM would be approciated.



    • Edited by RYounk007 Monday, October 1, 2012 3:49 PM
    Monday, October 1, 2012 3:30 PM
  • Apparently the relationship error is transient in Service Manager and shouldn't keep the process from completing.  Also, while it is possible to increase the timeout on both the Service Manager Server and Data Warehouse server using the registry key below, this has not solved the timeout issue that I am seeing.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse]

    "Command Timeout Seconds "=dword:00000384 – Updates the DW processing timeout from 5 minutes to 15 minutes.

    Referenced here:

    Wednesday, October 31, 2012 7:57 PM