MIM 2016 Troubleshooting: Unable to run the Management Agent (Error: 0x8023063d)
Applies to
Reported issue for MIM 2016
Situation
When you try to run a second synchronization run profile in parallel, when another synchronization run profile is running already you get an error message pop up on the screen and in the event viewer.
Error
Error message on screen
Event viewer
Log Name: Application
Source: FIMSynchronizationService
Date: dd/mm/yyyy hh:mm:ss
Event ID: 6309
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: server.domain.test
Description:
The server encountered an unexpected error while performing an operation for a management agent.
"BAIL: MMS(3120): ..\ma.cpp(3419): 0x8023063d (The operation cannot be performed because other synchronization run profile is already running. FIM Synchronization Service doesn't supports concurrent execution of synchronization run profiles.)
Forefront Identity Manager 4.4.1459.0"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="FIMSynchronizationService" />
<EventID Qualifiers="49152">6309</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="yyyy-mm-ddThh:mm:ss.000000000Z" />
<EventRecordID>42684</EventRecordID>
<Channel>Application</Channel>
<Computer>server.domain.test</Computer>
<Security />
</System>
<EventData>
<Data>BAIL: MMS(3120): ..\ma.cpp(3419): 0x8023063d (The operation cannot be performed because other synchronization run profile is already running. FIM Synchronization Service doesn't supports concurrent execution of synchronization run profiles.)
Forefront Identity Manager 4.4.1459.0</Data>
</EventData>
</Event>
Solution
Although the message is logged as an error in the eventviewer, which looks like a bug, this is behaviour as designed.
Currently, there is no solution for this error as MIM 2016 does not allow to run sync run profiles in parallel.
The error seems pretty drastic, by displaying a BAIL error, but it's a warning and blocker for running sync in parallel.
So, it's not a bug, as the failure of the MA is a BAIL event when MIM detects another MA is running. Because customers\implementers regularly ignore the "non BAIL" warnings, they have ignored this best practice and support has had many cases for this issue.
 Caution |
|---|
Check this Support-Info: (Sync): Run Profile Optimization blog post on the Identity and Access Management Support Team Blog. "running more than a single synchronization run profile execution at a time is not supported. The supported method is to execute run profiles asynchronously, allowing each run profile to complete before executing another." |
In short: do not run synchronization run profiles in parallel and even running import/export in parallel has some risks.
Note
As mentioned by Darren Robinson, you can still run the import and/or export run profiles in parallel.
Background
Running sync run profiles in parallel is a major cause for FIM/MIM Synchronisation database corruption. Therefore the latest updates for the MIM solution block the parallel execution.
As explained in: https://support.microsoft.com/en-us/help/3134725/hotfix-rollup-package-build-4.3.2195.0-is-available-for-microsoft-identity-manager-2016
Issue 4
Running more than one run profile with a synchronization task at the same time may cause data corruption.
Note A message box is displayed with a 0x8023063D error code.
References
Hotfixes
- https://support.microsoft.com/en-us/help/3134725/hotfix-rollup-package-build-4.3.2195.0-is-available-for-microsoft-identity-manager-2016
- Latest MIM builds: http://aka.ms/idmbuildversions
MS IAM Support Blog
- https://blogs.technet.microsoft.com/iamsupport/2015/08/27/info-run-profile-optimization/
- https://blogs.technet.microsoft.com/iamsupport/2017/03/28/support-info-microsoft-identity-manager-2016-sp1-hotfix-4-4-1459-0-released/
External blog