One of the steps is to import the FIM Synchronization configuration when performing a FIM Configuration Migration. During my last migration I received the following error message nearly at the end of the process:

In words:

An error was encountered while trying to update the metaverse configurations The synchronization rule’s boolean constant flow must only use ‘true’ or ‘false’. Import attribute flow rules update FAILED.

So I opened up the Synchronization Service management console and started to look for an SR with a boolean in it’s flow.

Found!:

It seems we have “membershipLocked” being set to false for an ISR. This information (the attribute flow updates) are stored in the MV.XML file which are located in the directory you exported to/ are importing from.

When you search for that attribute you will see that the export replaced the “false” by “0”. Simply change it back to “false” and rerun the import.

I’m currently setting up a lab with FIM 2010 R2 (BETA) and I was struggling to get my FIM MA created…

I encountered some issues with time sync before, so I started looking for issues with my connection to the  SQL Server/Database. Eventually I noticed a new Event Log on the FIM Server: Forefront Identity Manager Management Agent!

It was already populated with quit some errors:

In words:

System: System.UriFormatException: Invalid URI: The format of the URI could not be determined.
   at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
   at MIIS.ManagementAgent.RavenMA.InitializeConnection(XmlNode connectionInformationNode, XmlNode encryptedAttributeNode, Boolean runInitialization)
   at MIIS.ManagementAgent.RavenMA.UIInitialize(String pszInitString, Int32& pfValid, String& ppszResult)

When I saw this it immediately came clear that I didn’t used the http://***:5725 notation. Now when you install an all in one box, during the FIM Service and Portal installation wizard you are asked like 10 times for your FIM Service base address. During this wizard you just have to specify the URL. However in the FIM MA configuration you have to include the http and the port… Getting rusty ; )

Summary: FIM 2010 R2 seems to come with a new dedicated event log for FIM MA event log entries. This will be great help for troubleshooting FIM MA related issues for sure!