I've managed to export users to FIM without any problems but I get an error on every group I try to export from the Metaverse to FIM. I followed the instructions as detailed here: http://social.technet.microsoft.com/Forums/en/ilm2/thread/e6a09fa9-e8bc-4fd1-bc19-b07c21375ee3 apart from using cn to export to AccountName when configuring the attribute flows) but get the following error when trying to export using the FIMMA: Fault Reason: The request message contains errors that prevent processing the request. Fault Details: <RepresentationFailures xmlns="http://schemas.microsoft.com/2006/11/ResourceManagement" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><AttributeRepresentationFailure><AttributeType>MembershipLocked</AttributeType><AttributeValue></AttributeValue><FailureMessage>An attribute is required to complete the operation.</FailureMessage><AttributeFailureCode>RequiredValueIsMissing</AttributeFailureCode></AttributeRepresentationFailure></RepresentationFailures> I have set MembershipLocked as "false" (without quotations) as a constant in my sync rule. Have I missed something? Please let me know if any further info is needed.

Have you check the paragraph about Configuring the Fabrikam FIMMA in the instruction and verify that you correctly select the attribute membershipLocked to export to FIMMA ?

Yep, there's definitely an Export attribute flow set up for MembershipLocked.

Just had a closer look at the error I'm getting and when you click on 'Validate Object Against Schema', I get the following errors: Required attribute 'Domain' is missing. Required attribute 'MembershipAddWorkflow' is missing. Required attribute 'Scope' is missing. Required attribute 'Type' is missing. Required attribute 'MembershipLocked' is missing. I assume they are missing from the metaverse which would indicate that my synchronization rule is at fault. I configured the rule in FIM as specified in the article above. I used the domain attribute I created when setting up the users synchronization rule.

I'm intrested in this aswel since i have exactly the same error and attributes missing

I've resolved this and unfortunately it was my fault! I tried to synchronize into FIM before finishing all the required config, I then made the changes and didn't run the full initialization phase again - I was just trying to export from the MV. Do you have sync rules and attribute flow set up for all these attributes as well?

Its working now for new groups that I make, but distrubution groups that I tried to provision like this in an earlier attempt are still giving me the error. Not sure what the problem was. I deleted them now but they seem stuck in my MV, but i'll figure that out

I have had the same issue. I have them in MV with all the correct attributes. Now have the same export errors because they are stuck. What is the solution to delete them out? I want to run a clean export but can't since these are still in there. Any suggestions?

I delete the connector space and it will do a clean export.

Problem seems to be solved but worth noting that some of the group attributes (like MembershipAddWorkflow) are CASE SENSITIVE. So "None" meets constraints but "none" doesn't.

I'm hoping by replying to this old thread that I can bump it up and get some help. I have almost the same issue going on as the original poster but wtih a different attribute. The error I get once validated against the schema is: Required attribute 'Connector' is missing. When viewing the export in progress tab it is only adding ResourceParent and SynchronizationRuleID. I can run a preview and generate a full sync and it appears fine and has the connector attribute with a value. Any suggestions? let me know what other info i can provide.

One reason for this type of errors is "precedence". If you try to export a value to a MA with higher precedence in MV Import flow it will not export. If you do a preview you will see the Import take place into MV but also chekc the outbound flows in the preview to verify that the exports are not blcoked by precedence.