Hi All I am doing CSV to AD sync in FIM RC1. when i am running Full Synchronization on FIM MA it is giving following error. " Microsoft.MetadirectoryServices.ProvisioningBySyncRuleException: The DN must be set before calling CSEntry.CommitNewConnector" error. I have set "dn" as initial flow in AD Outbound sync rule,but the error is still coming. i am able to flow objects from CSV->FIM Portal->AD but i dont want the error to come.

How are you constructing you DN, by string constants or with workflow etc. what I wonder is if you're sure the DN you are flowing isn't empty and are you sure you don't have an additional non initial flow of DN?Henrik Nilsson Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

I have noticed the same error but the issue was with the 'Initial Flow' setting. Once the checkbox was selected, it worked fine. Also, I have configured the additional non initial flow of DN for rename of DNs. Without this additional flow, rename of DN wont happen.

You're correct! ...So make sure the DN is really an initial flow and that it's not empty.Henrik Nilsson Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

thanks to u both the problem is solved there were some users created in FIM portal that had not DN set

Just at side note. I was getting the same error message and yet I had the DN configured with an initial flow checked. What it turned out to be was I had DisplayName as an outbound atttribute but the value was null and I did not have "allow null value" set. As soon as I set the DisplayName it all worked.

Yes, even worse, if you have your DN dependent upon DisplayName (CN=DisplayName + OU...) and it's NULL then provisioning won't fail, it just won't happen at all. I don't believe this threw any errors at all.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com

I am now having this problem. I have provisioned Groups from FIM to AD prior to this, yet now I'm seeing this error for the latest "test" group creation. I have the dn being created in the outbound sync rule for the groups and it is set as initial flow only. I also have displayname being flowed to displayname. I created a group prior to this in FIM and it flowed correctly with all attributes flowing, after undoing the flow scope option in the portal. This second "test" is getting this error and I can't see why among the three or four responses out there for this. Any help would be appreciated.

I am now having this problem. I have provisioned Groups from FIM to AD prior to this, yet now I'm seeing this error for the latest "test" group creation. I have the dn being created in the outbound sync rule for the groups and it is set as initial flow only. I also have displayname being flowed to displayname. I created a group prior to this in FIM and it flowed correctly with all attributes flowing, after undoing the flow scope option in the portal. This second "test" is getting this error and I can't see why among the three or four responses out there for this. Any help would be appreciated. Hi gdtilhman, You need to be careful when you create your "DN" because when you have an outbound synchronization rule, you need to take the Conector Space values instead of the metaverse values. eg. Metaverse Attribute VS Conector Space Attribute givenName and fistName sn and lastName So you can look for into your FIM MA Conector Space in order to know wich attribute want to export Regards.