0x80230405 (The operation failed because the object cannot be found
The stopped-server status is a common status that is seen in the FIM Synchronization Service Engine when executing an import and/or export run on a given management agent. The following information has been compiled to provide guidance on how to begin troubleshooting a stopped-server status and possibily resolve a stopped-server status.
The stopped-server status is a WMI Return Code (http://msdn.microsoft.com/en-us/library/windows/desktop/ms699322(v=vs.100).aspx) from the RunStatus Property.
Additionally, this blog will cover at-least one specific scenario that had a stopped-server status.
FIM 2010 R2 – Receiving a stopped-server when running an export on the FIM Service Management Agent. The export will sit there for a few minutes and then return a stopped-server status and stop the export. Actions Taken
Application Event Log
Event ID: 6301
The server encountered an unexpected error in the synchronization engine:
"BAIL: MMS(6588): d:\bt\9394412\private\source\miis\server\sqlstore\csobj.cpp(15136): 0x80230405 (The operation failed because the object cannot be found)
BAIL: MMS(6588): d:\bt\9394412\private\source\miis\server\sqlstore\csobj.cpp(14776): 0x80230405 (The operation failed because the object cannot be found)
2. Request History: Based on the fact that we are running an Export on the FIM Service Management Agent, and that we are seeing a message indicating that the object cannot be found the next stop is the Request History. You can review Request History via the following steps:
d. If you see a request for msidmCompositeType then the issue could very well be asynchronous processing.
In FIM 2010 R2 Asynchronous Processing was enabled by default.
NOTE: Asynchronous Processing is where we process a batch of records at one time.
3. Review Asynchronous Processing Configuration: Since we have an idea that the problem is asynchronous processing, let’s review the current asynchronous processing configuration.
This property controls whether FIM MA uses the older synchronous channel or the new asynchronous channel when communicating with FIM Service.
This property controls whether FIM MA can send data to FIM Service in batches.
This property controls the number of attributes per aggregated batch.
This property controls whether the FIM Management Agent sends acknowledgements to FIM Synchronization Service immediately upon Request completion, or withholds them until the end for Update operations. Setting this to true may reduce the overall time to export data, but the FIM Synchronization Service UI statistics are not updated as frequently.
This property controls the maximum number of export requests that can be in process.
To resolve this scenario it is recommended to go through the following steps:
Default:: Asynchronous Processing is enabled with a 1000 record threshold
Disable Asynchronous Processing
<resourceSynchronizationClient asynchronous=“false” aggregate=“false”/>
Asynchronous Processing on with a threshold of 300 objects
<resourceSynchronizationClient asynchronous=“true” aggregate=“true” aggregationThreshold=“300” />