none
MIM 2016 SP1 Reporting Initial Sync Failing RRS feed

  • Question

  • Hello Everyone,

    I am experiencing an issue with the MIM Reporting failing on the Initial Sync. Both times I have experienced the issue has been with the MIM 2016 SP1 install media. SCSM Service manager is on a separate server with SQL and SCSM DW is on a separate server with SQL. I first complete the SCSM 2012 Service Manager and Data Warehouse installation, register the Data Warehouse and confirm the initial MPSync job finishes with all Management Packs imported/associated. Then I run the MIM 2016 SP1 Reporting installation and confirm the MIM Management Packs are all imported/associated and showing up in Reports in the SCSM console. Then I run the FIMPostInstallScriptsForDataWarehouse.ps1 script which completes successfully. When I run the Start-FIMReportingInitialSync.ps1 script and check the Reporting Job in the MIM Portal, it fails immediately and produces the below errors.

    Firewall is off between the servers as well. Has anyone seen this issue before and have a solution?

    Reporting Job Details: 

    ObjectTypeName: Person,

    AttributeName: ObjectType,

    RequestIdentifier: 00000000-0000-0000-0000-000000000000,

    ObjectID: 7fb2b853-24f0-4498-9534-4e10589723c4,

    Value: Person,

    DataType: String,

    MultiValue: False,

    Added: True,

    SubscriptionDetails: <DataWarehouseClassProperty ClassTypeIdentity="FIMDW.FIMPerson" PropertyIdentity="FIMObjectType" ManagementPackIdentity="Microsoft.Forefront.IdentityManager.Datawarehouse.Base" ManagementPackVersion=”1.0.0.1”/>,

    EventTime: 12/05/2016 19:38:27

    Event Viewer: (Three errors connected to the issue)

    Error
    12/5/2016 11:38:17 AM
    Microsoft.ResourceManagement.ServiceHealthSource
    68 None

    "The FIM Reporting ETL job failed while making a call to the System Center Service Manager Management Server SDK service.  This could be caused by a network or service interruption which is preventing communication between the FIM Service and the System Center Service Manager SDK Service, or by an internal error within System Center.

    To fix this issue, ensure that there are no firewalls or network connectivity issues which may be preventing communication between these two services. Also ensure that the System Center Management and System Center Data Access services are running on the System Center Service Manager Management Server.

    If you encounter this error after running your first ETL job, ensure that you have installed the FIM Reporting support scripts on your Data Warehouse machine.  You can find these scripts in the Service and Portal folder of your FIM media.

    For more information about this error, view the most recent reporting job in the FIM Portal and look for any exceptions which may have occurred.
    "

    Error
    9/21/2012 4:19:41 PM
    Microsoft.ResourceManagement 3
    None

    Reporting Job Manager: Reporting job halted due to error.

    Error
    9/21/2012 4:19:41 PM
    Microsoft.ResourceManagement 3
    None

    ObjectTypeName: Person, AttributeName: ObjectType, RequestIdentifier: 00000000-0000-0000-0000-000000000000, ObjectID: 7fb2b853-24f0-4498-9534-4e10589723c4, Value: Person, DataType: String,

    MultiValue: False, Added: True, SubscriptionDetails: <DataWarehouseClassProperty ClassTypeIdentity="FIMDW.FIMPerson" PropertyIdentity="FIMObjectType" ManagementPackIdentity="Microsoft.Forefront.IdentityManager.Datawarehouse.Base" ManagementPackVersion=”1.0.0.1”/>, EventTime: 12/05/2016 19:38:27 ---> System.InvalidOperationException: Cannot find management pack with identity Microsoft.Forefront.IdentityManager.Datawarehouse.Base
       at Microsoft.ResourceManagement.Reporting.DataProvider.DataWarehouseManagementPackManager.GetManagementPack(String managementPackKey)
       at Microsoft.ResourceManagement.Reporting.DataProvider.DataWarehouseObjectGenerator.CreateEnterpriseManagementObject(Guid objectIdentifier, String classType, String managementPackIdentity)
       at Microsoft.ResourceManagement.Reporting.DataProvider.DataWarehouseObjectGenerator.CreateEnterpriseManagementObject(DataWarehouseClassMapping mapping)
       at Microsoft.ResourceManagement.Reporting.DataProvider.DataWarehouseCollection.ProcessEntry(ExportLogEntry entry)
       --- End of inner exception stack trace ---
       at Microsoft.ResourceManagement.Reporting.DataProvider.DataWarehouseCollection.ProcessEntry(ExportLogEntry entry)
       at Microsoft.ResourceManagement.Reporting.DataProvider.DataWarehouseProvider.ProcessBatch(List`1 batch)
       at Microsoft.ResourceManagement.Reporting.ReportingManager.ExecuteBatchOfExtractTransformLoad(IDataManager dataManager)
       at Microsoft.ResourceManagement.Reporting.ReportingManager.ExportData(IDataManager dataManager)
       at Microsoft.ResourceManagement.Reporting.ReportingManager.RefreshSchema()
       at Microsoft.ResourceManagement.Reporting.JobManager.Run()

    Monday, December 5, 2016 9:03 PM

Answers

  • Jordan

    I would recommend you opening a case right now to track this we have reproduced this on new OOB installs and the product group is working on a resolution. A case will help track the resolution. The main issue it appears the reporting bindings are missing or not installed as part of the installer

    • Marked as answer by Jordan Stelzl Wednesday, December 7, 2016 5:41 AM
    Tuesday, December 6, 2016 12:47 PM
    Moderator

All replies

  • Did you verify the things the event viewer message asked about?  

    To fix this issue, ensure that there are no firewalls or network connectivity issues which may be preventing communication between these two services. Also ensure that the System Center Management and System Center Data Access services are running on the System Center Service Manager Management Server.

    If you encounter this error after running your first ETL job, ensure that you have installed the FIM Reporting support scripts on your Data Warehouse machine.  You can find these scripts in the Service and Portal folder of your FIM media.

    (Also, when you installed reporting did you specify the SCSM Service Manager (not Data Warehouse) server as the reporting server?)


    Tuesday, December 6, 2016 11:44 AM
  • Jordan

    I would recommend you opening a case right now to track this we have reproduced this on new OOB installs and the product group is working on a resolution. A case will help track the resolution. The main issue it appears the reporting bindings are missing or not installed as part of the installer

    • Marked as answer by Jordan Stelzl Wednesday, December 7, 2016 5:41 AM
    Tuesday, December 6, 2016 12:47 PM
    Moderator
  • Thanks for the reply SamiVV.

    I have confirmed everything that is being presented in the error messages and ensured that MIM Reporting is pointing to the Service Manager management server.


    Tuesday, December 6, 2016 4:19 PM
  • Thanks for the information David and confirming that you have this issue as well. I will go down the path of opening a case with Microsoft.
    Tuesday, December 6, 2016 4:20 PM
  • Hi,

    We are facing the same issue.  Can you please let us know how it was resolved.  We have the exact error on running InitialSynch job with MIM 2016.  It would be a great help if you can post the solution here.

    Thanks


    • Edited by Deepa L Thursday, December 29, 2016 8:49 PM
    Thursday, December 29, 2016 8:48 PM
  • Did this get resolved?  Can you please post the steps taken to resolve it.  Appreciate it.  Thanks


    Deepa


    Thursday, December 29, 2016 9:02 PM
  • We are working on a fix for this issue !! Will reply once we have published a resolution we have several cases logged fro this issue
    Tuesday, January 3, 2017 2:48 PM
    Moderator
  • Hi David,

    We are also getting same error. Is it resolved or still open?

    please let us me know.

    Regards,

    Gnana

    Wednesday, January 18, 2017 1:51 PM
  • We have exactly the same issue on our new MIM 2016 SP1 environment in which we used the old databases from the FIM 2010 R2 environment that did not have FIM Reporting installed. Once installed on the new environment we got error "Reporting job halted due to error" every time after Reporting Job was created in MIM.

    On the other hand this error does not appear on our test environment in which we did in place upgrade from FIM 2010R2 to MIM2016SP1.

    Hopefully MS will provide fix soon!

    Tuesday, January 31, 2017 8:23 AM
  • The issue happens only with blank database.  So for instance if you have data in database and run the job it would run fine.  However with blank/new database it errors out.  So in place upgrade would work fine.

    Microsoft is still working on the solution to fix it in SP1. Meanwhile we tried a work around for new/blank database.  We installed MIM 2016 without SP1. We then configured reporting and ran the Reporting jobs.  All jobs run fine without any errors.  Then upgrade to SP1.


    Deepa

    • Proposed as answer by Deepa Lakhani Thursday, February 9, 2017 3:53 PM
    Thursday, February 9, 2017 3:53 PM
  • For Customers facing this issue we do have a resolution , We plan to ship a public fix. If critical please open a support case to receive private until public releases . Per recommendation once public hotfix is announced please upgrade to this version


    Kind regards, David David Steadman - MIM Engineering Lead

    Friday, March 3, 2017 12:35 PM
    Moderator
  • Hi folks,

    is the public fix available?

    Br Frank

    Friday, May 12, 2017 10:08 AM
  • We are also facing this issue with old installations and also OOB installations.

    Can you please hurry with this issue and also report what is going on!

    Friday, May 12, 2017 10:52 AM
  • Does anyone know what the fix is?
    Tuesday, July 17, 2018 5:25 PM
  • Hi Jordan,

    Have you fixed that issue?

    Currently, i am also facing the same issue while running initial sync as a part of complete configuration of MIM Reporting.

    Please help me if you have resolved the same.

    Thanks in advance.

    Friday, November 16, 2018 5:30 AM
  • Hi All,

    Can anyone help me on this issue?

    Thanks in advance.

    Monday, November 19, 2018 7:01 AM
  • Hello,

    has this issue been fixed in any of the hotfix? I moved my old MIM databases to new server, installed fresh version of MIM 4.6.34.0 (upgrading old databases), installed fresh SCSM for reporting and getting same error ....


    Borys Majewski, Identity Management Solutions Architect (Blog: IDArchitect.NET)

    Saturday, November 21, 2020 11:19 PM
  • OK. I found the reason (and workaround). 
    SCSM 2019 and SQL 2019 has some issue with TLS 1.2 so I had to switch on previous TLS version (I did it some time ago so I forgot about it already). 
    I did the same right now on MIM server (which by default has TLS 1.2 only as it is new server) and it now started to communicate with SCSM.

    Borys Majewski, Identity Management Solutions Architect (Blog: IDArchitect.NET)


    Sunday, November 22, 2020 12:06 AM