
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. Some on the other hand just make no sense because there seems to be no problem with the mentioned resources. Some Stalled Move Request errors are straight forward and highlight an existing problem. This happens when the threshold for certain resources has been reached. Exchange 2016 ( we have CU8 in place ) utilizes throttling on move requests as well.



If you are reading this you have certainly noticed a Stalled Move Request at times.
