We have a remote user that was having a pst file migrate through client driven migration. The migration initially failed with an "
Insufficient mailbox quota available" message which in itself was odd since I thought the server was configured to grow the mailbox as needed. Regardless, we upped her quota and had the pst migration resume. We then started seeing the 8567 errors repeatedly on the server and the client stop migrating. I tried the following fix as it describes our problem exactly.
http://seer.entsupport.symantec.com/docs/319148.htm
Howerver, the numbers all seem in sync with one another (the client registry lastcopiedchunk matches the numbers on the server and in the holding and migrator folders).
Any suggestions for this one?
Thanks!