My Dirsync stopped working. I found this link which explains how Microsoft Tech Support handles the situation, and also what "may" be causing the problem.
As of 11/09/2013, I am still looking for a root cause.
Anyway, the Dirsync to Office 365 stopped working, and I discover that the Service will not restart.
In the event log, I see the following error:
"FIMSynchronizationService Event ID 6208. The Server Encryption Key could not be accessed"
See the following link:
http://community.office365.com/en-us/forums/613/t/24384.aspx
One submission says:
"With the assistance of Office 365 support, I have resolved the issue. The procedure:
- uninstall Microsoft Online Services Directory Sync Tool
- uninstall SQL Server Express
- delete FIMSynchronization database files
- Install dirsync.exe (Microsoft Online Directory Synchronization Service)
- Add enterprise admin domain account to local group MIIS_Admins
- Add permissions for the enterprise admin account for registry key HKLM\SOFTWARE\Microsoft\Forefront Identity Manager\2010\Synchronization Service
- Add permissions for the enterprise admin account for registry key HKLM\Software\Microsoft\MSOLCoexistence\
- Run directory synchronization configuation wizard"
"I had dirsync working fine and then on days when windows updates ran the dirsync would stop. I would then have to uninstall all of dirsync and all of the sql stuff and then re-install it. If this were a one time thing it wouldn't have been a big deal but it happened a few times and I've deduced that the problem must be with windows updates as dirsync stops working immediately after the server is restarted from the updates."
No comments:
Post a Comment