SharePoint 2010 User Profile Sync with FIM fail with need-full-object RRS feed

  • Question

  • I have recently re-created the User Profile Service application on a SharePoint 2010 farm to resolve issues with profile synchronization that occurred.  In the process the existing ProfileDB and SocialDB were retained and FIM's SyncDB dropped to be created a fresh.

    Original problems with profile sync are resolved but now see in Synchronization Service Manager the Management Agent of type "Extensible Connectivity" reports many discovery errors "need-full-object" for users.

    The only event in Windows Event Log for FIMSynchronizationService is a warning

    "...The rules configuration has changed since the last full import or full synchronization.
    User Action
    To ensure the updated rules are applied to all objects, a run with step type of full import and full synchronization should be completed."

    A full synchronization is being run.

    The synchronization runs for 12 hours+ before being shutdown by the farm backup process.  There are around 5000 users in Active Directory and a full sync used to take 5-6 hours.

    What is the best way to resolve this?

    • Edited by Adrian Hilder Tuesday, December 10, 2013 12:25 PM Spelling correction
    Tuesday, December 10, 2013 12:24 PM

All replies

  • Firstly, your question appears to relate to the built-in run-time FIM Sync components deployed as part of SharePoint 2010 - and if this is the case you had best re-post to this forum instead (since this has nuances of its own completely different from the stand-alone FIM product):

    If, however, you are interested in how a FIM person would approach your problem, the need-full-object error occurs when a DELTA import has been processed when a FULL import is required.  My approach would be to run a full import on each of your 2 MAs, followed by a DELTA synchronisation on each - and then if a FULL synchronisation is required the console will alert you to this interactively (if you are running the FIM identity manager console in lieu of using SharePoint wizards) or in the server Event Logs.

    Bob Bradley (FIMBob @ ... now using FIM Event Broker for just-in-time delivery of FIM 2010 policy via the sync engine, and continuous compliance for FIM

    • Proposed as answer by UNIFYBobMVP Thursday, December 26, 2013 1:04 PM
    Thursday, December 26, 2013 1:04 PM