none
GalSync/FIM sync service hangs on specific object RRS feed

  • Question

  • I have galsync set up with MIM 2016. Full import works as expected.  Full sync works as expected on all but one MA.  On one MA, the service appears to hang when attempting to provision a specific object.  Of course, I can't get it to log any specifics about the object, only the MV objectID which is never actually created. The FIMSynchronizationService process goes to full CPU utilization on the core it's running on and ignores stop commands. I can kill the process, restart the service, and everything begins to work as expected, until I try to run a full sync on the affected MA again. This is a new FIM/MIM/Galsync installation and has never completed a full sync with this MA.

    This is an excerpt from the galsync.log file (some names changed):

    10:02:57 AM, 1/5/2018: Entering provisioning for MV group ba44b5dc-a9f1-e711-810f-005056ae35b3
    10:02:57 AM, 1/5/2018: Adding CN=working group 1,OU=unit,DC=domain1,DC=com
    10:02:57 AM, 1/5/2018: Adding CN=working group 1,OU=unit,DC=domain2,DC=com
    10:02:57 AM, 1/5/2018: Adding CN=working group 1,OU=unit,DC=domain3,DC=com
    10:02:57 AM, 1/5/2018: Adding CN=working group 1,OU=unit,DC=domain4,DC=com
    10:02:57 AM, 1/5/2018: Entering provisioning for MV group bf44b5dc-a9f1-e711-810f-005056ae35b3
    10:02:57 AM, 1/5/2018: Adding CN=working group 2,OU=unit,DC=domain1,DC=com
    10:02:57 AM, 1/5/2018: Adding CN=working group 2,OU=unit,DC=domain2,DC=com
    10:02:57 AM, 1/5/2018: Adding CN=working group 2,OU=unit,DC=domain3,DC=com
    10:02:57 AM, 1/5/2018: Adding CN=working group 2,OU=unit,DC=domain4,DC=com
    10:02:58 AM, 1/5/2018: Entering provisioning for MV group 5a0941e4-31f2-e711-810f-005056ae35b3

    And that's it, the process hangs and nothing else is added to the log. The GUIDs for the working groups stay the same across attempts to sync.  The GUID for the last group changes every time.  That GUID does not exist in the mms_metaverse table on the database (the others do, of course).

    Can anyone provide any pointers?  Is there some way to get it to give me information about the object it's hanging on so I can try removing/excluding it or something? 

    Thanks,

    Friday, January 5, 2018 5:53 PM

All replies

  • You can use SQL Profiler to find out which object it hangs on. Your Sync DB could be corrupted.

    You could then disconnect that one group, by moving it to an out of scope OU, let it delete from the other side. Then move it back and let it recreate again.

    If that doesn't fix it, you might need MSFT support to run StoreCheck to fix any corruption.


    David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

    Friday, February 23, 2018 5:48 PM