We have an error that has stumped me and is starting to become more and more of a problem. I would rather fix the root cause than treat the symptoms. Persons are imported from HR into FIM. Some persons are succesfully imported and can be seen in both the Portal and Metaverse but FIM apparently does not receive a confirmation and times out after 5 minutes. We perform 2 FIM exports over a single sync so on the 2nd FIM export (or even the next time around) the same person that "timed out" before will be exported to FIM again. You can see 2 of the same persons with the same information in the Portal. The Metaverse shows 2 FIM MA objects connected to the single HR object. I have seen as many as 7 instances of the same individual in the Portal so the issue compounds when not addressed. The simple and quick fix is to create disconnectors on both (or all) FIM MA objects and an explicit disconnector on the HR object so it doesn't happen with the same person again. The part that stumps me is that it seems to recurr with that individual if I allow them to be imported again either by manually projecting them or removing the explicit disconnector and allowing it to import again on the next sync. I don't want these recurring errors to show failed syncs and I also don't want an increasing number of explicit disconnectors on HR records. As far as I can tell there is nothing unique about these employees. The error below shows the initial timeout error. I have no problem increasing the timeout value (assuming it's possible) but I have a strong suspicion that this isn't really an issue of time but of communication. There is an error executing a web service object creation request. Type: System.TimeoutException Message: The request channel timed out while waiting for a reply after 00:04:59.9969997. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. Stack Trace: Server stack trace: at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ContextRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.ResourceManagement.WebServices.WSTransfer.IResourceFactory.Create(Message request) at Microsoft.ResourceManagement.WebServices.ResourceFactoryClient.Create(Message request) at Microsoft.ResourceManagement.WebServices.ResourceFactoryClient.Create(Create createBody) at Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.CreateResource() at MIIS.ManagementAgent.RavenMA.ExportObjectCreation(DataSourceObject dsObject, SchemaManager schemaManager) at MIIS.ManagementAgent.RavenMA.Export(DataSourceObject dsObject) Inner Exception: The HTTP request to 'http://localhost:5725/ResourceManagementService/ResourceFactory' has exceeded the allotted timeout of 00:05:00. The time allotted to this operation may have been a portion of a longer timeout.

Just a sanity check - can you confirm that you've defined a unique relationship (CS to MV) for your IAF sync rule? For there to be duplicates like this it seems like FIM cannot uniquely identify an HR employee connector ...Bob Bradley, www.unifysolutions.net (FIMBob?)

They never fully import so the EmployeeID unique relationship is negated. It imports what I would describe as an empty shell of a person object rather than one with all the attributes. I cleared out the duplicates in the Portal, all the metaverse objects with is_import_error and is_export_error values that weren't 0, and extended the timeout to 15 minutes. At this point I am able to import all of the persons from HR but still can't explain why most persons can be imported in under 10 seconds but these individuals take 10+ minutes.