We are setting up a development FIM environment, the beginning of our upgrade from ILM to FIM. We have loaded 250k identities from a data store that is basically all of our unique keys, and have exported the population to the FIM MA. The FIM MA export is only exporting MVObjectID. For all but 5 users, the export succeeded. The last five users all fail with the following error. Any ideas? --- There is an error executing a web service object creation request. Type: Microsoft.ResourceManagement.WebServices.Client.UnwillingToPerformException Message: Fault Reason: The endpoint could not dispatch the request. Fault Details: <DispatchRequestFailures 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"><DispatchRequestAdministratorDetails><FailureMessage>A resource with the specified Identifier already exists.</FailureMessage><DispatchRequestFailureSource>ResourceIdentifierAlreadyExists</DispatchRequestFailureSource></DispatchRequestAdministratorDetails></DispatchRequestFailures> Stack Trace: at Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.CreateResource(Guid identifier, String synchronizationSequenceIdentifier) at MIIS.ManagementAgent.RavenMA.ExportObjectCreation(DataSourceObject dsObject, SchemaManager schemaManager, Boolean specifyObjectId) at MIIS.ManagementAgent.RavenMA.Export(DataSourceObject dsObject) Inner Exception: The endpoint could not dispatch the request.

I had the same error when loading large number of objects, I extended the timeouts of FIM different components I'm not 100% sure but I think the SQL is saturated with the large number of requests and cannot process any other requests It's never too late in life ... to start living

Amer, Thank you for the response. We received a total of 73 export errors during our 250k export run. We deployed the hotfix to throttle up the FIM MA throughput to get a decent load time, but even with the hotfix it took two days. I re-ran the export of the 73 pending, and 68 completed successfully. So those only seemed to error out due to FIM performance constraints. I've attempted to re-export the final five numerous times, and they don't export. So something seems amiss about these five. Thanks, Greg

Amer, Thank you for the response. We received a total of 73 export errors during our 250k export run. We deployed the hotfix to throttle up the FIM MA throughput to get a decent load time, but even with the hotfix it took two days. I re-ran the export of the 73 pending, and 68 completed successfully. So those only seemed to error out due to FIM performance constraints. I've attempted to re-export the final five numerous times, and they don't export. So something seems amiss about these five. Thanks, Greg Generally either AccountName or ObjectSID is not unique and that's what causes this error.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

My gut tells me Brian has your answer, and that what I'm about to suggest won't help in this instance, but just in case... When having problems exporting to the FIM portal, always go to the portal and search for failed requests around the time you were trying to export. There may be more information there about the problem. Are there any events in the application log of the FIM Service server related to these errors? I would expect the logs on the FIM Sync server to have basically the same details you see in the Sync Manager. (This is assuming they're different boxes, of course.) Chris

Generally either AccountName or ObjectSID is not unique and that's what causes this error. My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com I had this error in the past, and re-running the export again solved the problem, I think it's related more to the build version, but if you are stuck with some specific users then you need investigate for other issues on these users It's never too late in life ... to start living