none
Fim Reporting - Initial Sync failure RRS feed

  • Question

  • Hi,

    I've got an issue with FIM Reporting in FIM 2010 R2. After SCSM intallation (SCSM in with FIM on the same server (another instances of SQL), Warehouse+SQL for Warehouse in another), when Management Packs were all "Deployed" and FIMPostInstallScriptsForDataWarehouse.ps1 script has been run, I've run Start-FIMReportingInitialSync.ps1 script as noted here http://www.wapshere.com/missmiis/installing-reporting-for-fim-r2.

    I've checked at the FIM Portal and the result of this run is: Error.

    Reporting Job Details: 

    ObjectTypeName: FIMDW.FIMAttributeType, AttributeName: FIMAttributeTypeDataType, RequestIdentifier: 00000000-0000-0000-0000-000000000000, ObjectID: 703c5735-0d86-44a5-82c3-75550498e600, Value: Reference, DataType: String, MultiValue: False, Added: True, SubscriptionDetails: <DataWarehouseClassProperty ClassTypeIdentity="FIMDW.FIMAttributeType" PropertyIdentity="FIMAttributeTypeDataType" ManagementPackIdentity="Microsoft.Forefront.IdentityManager.Datawarehouse.Base"/>, EventTime: 09/21/2012 14:19:41

    Event Viewer: (there are three errors connected to the issue)

    Error 9/21/2012 4:19:41 PM 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

    Microsoft.ResourceManagement.Service: System.InvalidOperationException: ObjectTypeName: FIMDW.FIMAttributeType, AttributeName: FIMAttributeTypeDataType, RequestIdentifier: 00000000-0000-0000-0000-000000000000, ObjectID: 703c5735-0d86-44a5-82c3-75550498e600, Value: Reference, DataType: String, MultiValue: False, Added: True, SubscriptionDetails: <DataWarehouseClassProperty ClassTypeIdentity="FIMDW.FIMAttributeType" PropertyIdentity="FIMAttributeTypeDataType" ManagementPackIdentity="Microsoft.Forefront.IdentityManager.Datawarehouse.Base"/>, EventTime: 09/21/2012 14:19:41 ---> 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()

    How to troubleshoot what is misconfigured? Or how to resolve it?


    Keep trying


    Friday, September 21, 2012 2:30 PM

Answers

  • Tried a few things, but with no idea how to troubleshoot it I've reinstalled:

    - SCSM (both Manager and Warehouse)

    - SQL Instances for SCSM databases (just to make sure to have "clean" deployment)

    - FIM Reporting

    Now, after waiting for MPSyncJob I've got it running.

    I have no idea how to resolve the issue.


    Keep trying

    Tuesday, September 25, 2012 12:35 PM