I need to provision records to an Oracle table that has a primary key that has a setup to auto-increment . i used the GUID/DN Trick in the outbound sync rule but i still have an error appears in the FIM Synchronization server (missing-anchor-component) as a management agent error , and when i look to the details i can see this error ([Add] Bad anchor) in the connected data source error. the real problem is that when i open the table in the database i can see the row provisioned successfully, in the next FIFS run profile it disconnects the old Connector (that made an error) and joins the added-row as a new connector to the corresponding metaverse object and works fine !!! i used the GUID/DN Trick in a sql table before and it worked well (based on this ref. http://social.technet.microsoft.com/Forums/en-US/identitylifecyclemanager/thread/e3c01b18-ce40-44d2-ad60-85e49ba7731e/). So i want to know where this error comes from !!! and i wanna solve this problem please. Thanks,Ali Merdan Software Development Engineer - BlueCloud Corp.

Have you configured it as described here? Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

YESS but unfortunately it didn't work :SAli Merdan Software Development Engineer - BlueCloud Corp.