Hi there,
I have configured a User Profiles Service Application and successfully started the User Profile Synchronization service, connected to Active Directory and successfully completed an import of AD users.
I have configured several custom User Profile Properties and mapped them to both import and export AD attributes. I can see changes being pulled from AD and pushed to AD (via the export mappings).
So as far as the overall configuration everything appears to work fine. I can view the entries in miisclient.exe and when i click the "idle" link on the User Profiles Service Application home page I can see the list of interactions with AD that correspond to the entries in miisclient.exe. All of these synchs are executed via the User Profiles Service Application from Central Admin.
The issue I am encountering is that when the scheduled synch takes place at 1am (I just left the timer job default settings) I see the following entry in the uls log:
The following services are managed by SharePoint, but their running state does not match what SharePoint expects: FIMSynchronizationService. This can happen if a service crashes or if an administrator starts or stops a service using a non-SharePoint interface. If SharePoint-managed services do not match their expected running state, SharePoint will be unable to correctly distribute work to the service.. Automatic repair is being attempted.
The other properties of the uls message are:
Product: SharePoint Foundation
Category: Health
EventID: 8fs4
Level: Unexpected
(note that for ULS I have configured logging for all categories to be at level Unexpected)
If I open miisclient.exe I see no entries for the time of the uls message. If I click the "Idle" link on the User Profiles Service Application home page I see the following (basically empty) entries:
Stage History Cleanup
.............................
Start Time 8/20/2013 12:00:01 AM
End Time 8/20/2013 12:00:01 AM
-----------------------------------------------------------------
Stage Post-processing
.............................
Start Time 8/20/2013 12:00:01 AM
End Time 8/20/2013 12:00:01 AM
-----------------------------------------------------------------
Stage History Cleanup
.............................
Start Time 8/20/2013 12:01:01 AM
End Time 8/20/2013 12:01:01 AM
-----------------------------------------------------------------
Stage History Cleanup
.............................
Start Time 8/20/2013 12:03:02 AM
End Time 8/20/2013 12:03:02 AM
-----------------------------------------------------------------
So from what I can tell when the timer job attempts to do the synch it gets stopped by "something". Does anyone have any suggestions on what I can do to further diagnose this issue? Is there perhaps some other logging that can be enabled to help?
Cheers,
Colin