Hi, Why am I getting this error message? "Microsoft.Metadirectory.services.ProvisioningBySyncRuleException; An object with DN "7" already exists in management agent "FILE MA". Surely FIM should have some basic logic inside that says 'hey, this object already exists I am not going to try replicate it again' ? thanks

Do you use decleartive (portal-based, codeless) or classical provisioning? For declarative provisioning you propably created a Synchronzation Rule, enabled "Create Ressource in external system" and specified an outbound attribute flow for the DN. If the configuration / logic you've implemented doesn't guaratee a uniquness of the DN, the SE provisioning.dll will throw the error. /Matthias

There is no build in feature in declarative provisioning to just ignore this error. You should fix your source data to get rid of the error. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Do you use decleartive (portal-based, codeless) or classical provisioning? For declarative provisioning you propably created a Synchronzation Rule, enabled "Create Ressource in external system" and specified an outbound attribute flow for the DN. If the configuration / logic you've implemented doesn't guaratee a uniquness of the DN, the SE provisioning.dll will throw the error. /Matthias yes, but I do not understand why that logic is incorrect? I want to create a resource in an external system...isnt that what this product is meant to do? So since FIM does not quarantee the uniqueness of the DN, I will simply ignore this error and move on then.

Do you use decleartive (portal-based, codeless) or classical provisioning? For declarative provisioning you propably created a Synchronzation Rule, enabled "Create Ressource in external system" and specified an outbound attribute flow for the DN. If the configuration / logic you've implemented doesn't guaratee a uniquness of the DN, the SE provisioning.dll will throw the error. /Matthias yes, but I do not understand why that logic is incorrect? I want to create a resource in an external system...isnt that what this product is meant to do? So since FIM does not quarantee the uniqueness of the DN, I will simply ignore this error and move on then.

There is no build in feature in declarative provisioning to just ignore this error. You should fix your source data to get rid of the error. Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation Fix the source data? Its 2 users records with 3 attributes (EmployeeID, Firstname, LastName)...I do not understand what is there to fix?

There is no build in feature in declarative provisioning to just ignore this error. You should fix your source data to get rid of the error. Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation Fix the source data? Its 2 users records with 3 attributes (EmployeeID, Firstname, LastName)...I do not understand what is there to fix?

Couldn't you join them first? The object in the Portal and the File MA?http://setspn.blogspot.com

I could certainly try that, will let you know...I am rebuilding the lab again to see if I missed something the previous 5 times.

troubleshooting FIM is almost impossible...I have rebuilt everything from scratch (again)...and now I have even more errors then before...all in the FIM forums :-)

I have rebuilt the lab - its easier and quicker then troubleshooting FIM. Thanks for all your help.