Your Exchange Server Blog

Stalled Move Request Exchange 2016

If you are reading this you have certainly noticed a Stalled Move Request at times. Exchange 2016 ( we have CU8 in place ) utilizes throttling on move requests as well. This happens when the threshold for certain resources has been reached.

Some Stalled Move Request errors are straight forward and highlight an existing problem. Some on the other hand just make no sense because there seems to be no problem with the mentioned resources.

In our case we have triggered just one move request at a time and the I/O operations on the disk where the target mailbox database resides were minimal. But we still got a StalledDueToTarget_DiskLatency status and a Stalled Move Request.

While move requests with a status like Stalledduetohigherpriorityjobs continued after a while , others went in status StalledDueToTarget_DiskLatency or Relinquishedwlmstall and stalled for hours just to resume and stall again and kill the move request.