Hi Guys,

I got this error message keeps popping up in the event viewer like every minute.. i have no clue what is this error message is for. can anyone give me some idea or point me to the right direction

Exchange 2013 running 2 node DAG. the error message is found on the passive node.

"The Microsoft Exchange Migration Workflow service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service."

Thanks

Are you running any mailbox migrations?  If so can you stop them and see if the error goes away?

Hi,

Please confirm if there is any mailbox migration in your Exchange server. If that is the case, please complete the migration, then check whether the issue persists.

Additionally, here is a similar thread for your reference:

https://social.technet.microsoft.com/Forums/en-US/eefd3732-d9f5-4832-b8e9-b5a99d37fc30/microsoft-exchange-migration-workflow-service-terminated-unexpectedly?forum=exchangesvrdeploy

Regards,

Hi,

Any updates?

Regards,

This is also happening to my site. We have the same setup as a1rw1n - two-node Exchange 2013 DAG. The "Migration Workflow" service on the passive node keeps crashing and restarting itself in a loop.

This only started happening after upgrading both nodes to CU6. The active node has no such problems, and the Migration Workflow service runs fine.

Also, when running "Get-ServerComponentState" on the affected server, the following components show as "Inactive":

• RwsProxy
• EcpProxy

Restarting both servers does not make any difference.

Can you please advise a solution? There are no migrations currently in progress, and there weren't any at the time of the CU6 upgrade.

• Edited by Jack Bryan Friday, November 21, 2014 1:27 AM

This is also happening to my site. We have the same setup as a1rw1n - two-node Exchange 2013 DAG. The "Migration Workflow" service on the passive node keeps crashing and restarting itself in a loop.

This only started happening after upgrading both nodes to CU6. The active node has no such problems, and the Migration Workflow service runs fine.

Also, when running "Get-ServerComponentState" on the affected server, the following components show as "Inactive":

• RwsProxy
• EcpProxy

Restarting both servers does not make any difference.

Can you please advise a solution? There are no migrations currently in progress, and there weren't any at the time of the CU6 upgrade.

• Edited by Jack Bryan Friday, November 21, 2014 1:27 AM

This is also happening to my site. We have the same setup as a1rw1n - two-node Exchange 2013 DAG. The "Migration Workflow" service on the passive node keeps crashing and restarting itself in a loop.

This only started happening after upgrading both nodes to CU6. The active node has no such problems, and the Migration Workflow service runs fine.

Also, when running "Get-ServerComponentState" on the affected server, the following components show as "Inactive":

• RwsProxy
• EcpProxy

Restarting both servers does not make any difference.

Can you please advise a solution? There are no migrations currently in progress, and there weren't any at the time of the CU6 upgrade.

• Edited by Jack Bryan Friday, November 21, 2014 1:27 AM

Honestly, I haven't seen this happen at any place that I have done migrations at.  The only thing I can recommend is that you contact MSFT support with a crash dump of the migration service and see if they can give you an answer based on that.

• Marked as answer by Winnie LiangMicrosoft contingent staff, Moderator Monday, December 01, 2014 1:50 AM

Honestly, I haven't seen this happen at any place that I have done migrations at.  The only thing I can recommend is that you contact MSFT support with a crash dump of the migration service and see if they can give you an answer based on that.

• Marked as answer by Winnie LiangMicrosoft contingent staff, Moderator Monday, December 01, 2014 1:50 AM

Honestly, I haven't seen this happen at any place that I have done migrations at.  The only thing I can recommend is that you contact MSFT support with a crash dump of the migration service and see if they can give you an answer based on that.

• Marked as answer by Winnie LiangMicrosoft contingent staff, Moderator Monday, December 01, 2014 1:50 AM

Winnie,

If you do not actually answer the question, but simply refer to other options please do not mark a question as 'answered'.  I've seen other microsoft employees do similar things and it is annoying and devaluates the forums.

I have observed exactly the same issue on a freshly installed Exchange 2013 (CU6) DAG (4 nodes, 2 sites) with -no- user mailboxes yet, and no migrations. Your 'answer' has helped exactly zero.

On topic: I wonder if this is still the case: (CU3)

"The Microsoft Exchange Migration Workflow service is just a placeholder for a service will be implemented in the future. Therefore, the behavior that's described in the "Symptoms" section is the expected behavior.

Note Leave the service startup type set to Manual or change it to Disabled to prevent the system from trying to automatically start the service."

https://support.microsoft.com/kb/2901754

Paul, I have the same problem as listed in the thread (in my case a fresh 2 node DAG and 2 sites, upgrading from 2010) and ultimately set the service to Manual (It is set to automatic in the latest in CU6).  This does not seems to effect the environment in any way that I have noticed. It would be nice if Microsoft would give us a little more information on what exactly this service is supposed to do.

Bump, I've also got this issue on CU6, it was never an issue on SP1/CU4. I am also curious if what Paul asked about in regards CU3 is still true or not, that this service is a place holder only.

I also would like to wholeheartedly second what Paul says about the marked answer on this discussion. What has been marked as the answer here does not answer the question at all.

Seems CU7 removed this service all together. All good

Winnie,

If you do not actually answer the question, but simply refer to other options please do not mark a question as 'answered'.  I've seen other microsoft employees do similar things and it is annoying and devaluates the forums.

So very true. I wish they would stop doing this. Before these paid moderators were in the forums, answers were actually usefull most of the time. Now you are given a very general answer or you are directed to the first link a search on Google (or probably Bing) gives. On top of that they mark their own non-answer as an answer. Very frustrating...