Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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 (https://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.
Checklist Item | Description |
---|---|
SQL Server Instance Check |
|
SQL Server |
|
Determine which Management Agent is returning the Stopped-Server |
|
Determine which Run Profile is returning the stopped-server |
|
Refresh Credentials |
|
Review the Run History (Operations Tab) |
|
Application Event Log |
|
Storechk.Exe |
|
FIM Service Management Agent |
|
NOTES:
|
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 |
Source: FIMSynchronizationServiceEvent ID: 6301Description:The server encountered an unexpectederror 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:
Open Internet Explorer and navigate to the FIM Portal
Click Search Requests on the menu on the left
To search requests for today, simply click the magnifying glass
I. If you need to review prior days, you may have to execute an advanced search
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.
Property Name | Default Value | Description |
asynchronous | True | This property controlswhether FIM MA uses the older synchronous channel or the new asynchronouschannel when communicating with FIM Service. |
Aggregate | True | This property controls whether FIM MA cansend data to FIM Service in batches. |
aggregationThreshold | 1000 | This property controls the number ofattributes per aggregated batch. |
delayUpdateAcknowledgements | False | This property controlswhether the FIM Management Agent sends acknowledgements to FIMSynchronization Service immediately upon Request completion, or withholdsthem until the end for Update operations. Setting this to true may reduce theoverall time to export data, but the FIM Synchronization Service UIstatistics are not updated as frequently. |
exportRequestsInProcessMaximum | 50 | This property controls themaximum number of export requests thatcan be in process. |
To resolve this scenario it is recommended to go through the following steps:
Default:: Asynchronous Processing isenabled with a 1000 record threshold | <resourceSynchronizationClient/> |
Disable Asynchronous Processing | <resourceSynchronizationClientasynchronous=“false” aggregate=“false”/> |
Asynchronous Processing on with athreshold of 300 objects | <resourceSynchronizationClientasynchronous=“true” aggregate=“true” aggregationThreshold=“300” /> |
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in