Just posted by Peter Geelen – thought this worthy of a reblog for the #FIM2010 and #MIM2016 community.
This article has been posted on TNWiki at: FIM2010 Troubleshooting: MIISActivate – FIM Sync service terminated with service-specific error %%-2146234334.
Situation
Failing over a FIM Sync Server to the standby FIM sync server using MIISActivate.
After using successfully MIISActivate, the FIMSync Service fails to start and logs an error in the eventviewer.
Symptoms
You’ll see 2 error messages in the event viewer, erro 7024 and error 6324.
Error 7024
Reference
This error is pretty similar or exactly like the error described in the following Wiki article:
FIM2010 Troubleshooting: FIM Sync service terminated with service-specific error %%-2146234334.
Screen
Error message Text
Log Name: System Source: Service Control Manager Date: 3/02/2016 15:08:59 Event ID: 7024 Task Category: None Level: Error Keywords: Classic User: N/A Computer: servername.domain.customer Description: The Forefront Identity Manager Synchronization Service service terminated with service-specific error %%-2146234334. Event Xml: <Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”> <System> <Provider Name=”Service Control Manager” Guid=”{555908d1-a6d7-4695-8e1e-26931d2012f4}” EventSourceName=”Service Control Manager”… |
View original post 735 more words
IdM for Real 