ADAM MA Refresh Schema error RRS feed

  • Question

  • We are using FIM 2010

    One MA is connected to ADAM. There is a schema change in ADAM instance (added one new attribute).

    Now i am trying to refresh the schema in ADAM MA. provided credentials are correct. 

    It is also recognizing change in schema, but it is throwing below error at last. I am also able to run Export and Delta Import profiles and it is successful

    Retrieving the new schema ...
    Retrieving the new schema complete
    Comparing new and old schema ...
    The schemas are different
    Retrieving the metaverse data ...
    Retrieving the metaverse data complete
    Validating object type inclusion ...
    Validating object type inclusion completed successfully
    Validating attribute inclusion ...
    Validating attribute inclusion completed successfully
    Validating validating stay disconnector rules ...
    Validating stay disconnector rules completed successfully
    Validating join and project rules ...
    Validating join and project rules completed successfully
    Validating attribute flow rules ...
    Validating attribute flow rules completed successfully
    Validating deprovisioning rules ...
    Validating deprovisioning rules completed successfully
    Validating extension settings ...
    Validating extension settings completed successfully
    The new schema has been validated and is being saved ...
    The attempt to commit the new schema failed

    could you please let me know what may be the reason behind this error. I am not getting any particular reason for this error.

    Tuesday, June 25, 2013 10:14 AM

All replies

  • Have you looked in the Event Log for more clues.

    It is possible that you may have some corruption in your database. Here are some possible solutions:

    1. Normally you can use any admin credentials of the connected system but you might try to use the credentials that are stored in the MA.
    2. Try changing the credentials in the MA and then use the new credentials.
    3. Restart the FIM Sync Service (perhaps there is something wrong in the process memory that would get fixed by cycling the service)
    4. Reboot the Server
    5. Delete the MA and recreate (huge pain)
    6. Contact MSFT Support

    David Lundell, Get your copy of FIM Best Practices Volume 1

    Wednesday, June 26, 2013 4:08 PM
  • Thank you David

    But the error got resolved after some time by itself. No corrective measure was taken from my end.

    Thursday, July 4, 2013 4:01 AM