I'm on one of my last steps in migrating from 2010 to 2013.  When I issue the command to  Resume the migration request after the Autosuspend happens, I get a StalledDueToMailBoxLock, and it retries but never completes.  I've removed the request and tried it again, but I get the same thing.  The requests were 24 hours apart.  I have no clients that are connecting to the 2010 server anymore, and all the user mailboxes have been migrated to 2013 successfully.  I haven't found much online about this status, so I'm at a loss.  By the way, this is during my Public Folder migration process.  Sorry for leaving that out.

Thank you.

• Edited by Regular Guy1 Sunday, May 05, 2013 5:04 AM

Hi,

How long did you wait after move moverequest ?

Similar issue for your reference.

http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/345debf0-53ed-460e-a5ac-5ba254c6da20

I waited for 15 minutes or so, and progress was stopped at 95%.  There is next to nothing in my public folder database on Ex2010.

I did find that thread, but it is not the same issue, I'm not having problems with the default database on Ex2013, and I'm not trying to remove it.

I waited 20 minutes for the move request, but it went to stalled almost right away, and stayed there.  There is next to nothing in my Ex2010 public folders, so it shouldn't take long.

Hello, any luck with this?  I am migrating a TON of public folders from 2007 to 2013.  After many starts, stops, redos, I am at this point where it shows that it is "stalledduetomailboxlock".  Any suggestions to complete the public folder migration?  I assume it means the public folder mailbox on the 2013 server, but I haven't done anything aside from the steps in this article (http://technet.microsoft.com/en-us/library/jj150486.aspx) and am now ready to finish.  Any suggestions would be appreciated.

Hi Tom,

No luck on my end yet, as you can see, there's been no response to this thread other than the initial one from Wendy that wasn't really what I'm looking for.  I'm at the point of just creating one from scratch, and moving on because I'm tired of waiting, and I'd really like to get on with decommissioning the old server.

so, the good news is that for me, it eventually worked.  i ended up rebooting the server and re-running the resume command (Resume-PublicFolderMigrationRequest -Identity \PublicFolderMigration) over and over again and finally, it finished.  Our office was closed and i had already run the lock command (Set-OrganizationConfig -PublicFoldersLockedForMigration:$true), but it was still showing that the folder was locked.  regardless, after a day, a few reboots and some patience, it finally completed and we're running in a solely 2013 environment.

Sorry I don't have a silver bullet answer, but a few reboots ended up working for me.

-Tom

• Marked as answer by Regular Guy1 Sunday, June 09, 2013 11:43 PM

Tom,

I really appreciate your follow up.  I haven't been very patient because I have such a small group of users and they don't use Public Folders really.  I will follow your steps, and see if that will do it for me. -Ron

Yes, this did work, I eventually got it to migrate.  Lots of command line fun.  :)

The biggest issue I have found is on step # 4 of document "Migrate Public Folders to Exchange 2013 From Previous Versions" from Microsoft.

ONLY the first mailbox needs the HoldForMigration option. It does say it, but people don't pay attention and create all mailboxes with the switch. This will cause the migration to stop from finishing with the StalledDueToMailBoxLock status.

PD

Running Resume-PublicFolderMigrationRequest -Identity \PublicFolderMigration worked for me after a couple of minutes.

Hi.

I had exact same failure. My failure was that I has run the "Set-OrganizationConfig -PublicFoldersLockedForMigration:$true" script from Exchange 2013 and not the 2007/2010

To get around this problem I had to reboot the Exchange 2007 Information Store service or reboot the server. That reprompted Exchange to look at it again and realize that the mailbox is not locked. Worked like a champ from there.

I think that not many people pay attention to a small detail - after you lock the Public Folders (which has to be done on the legacy server), you need to wait until the lock takes effect.

If you ignore this detail and proceed right away with changing the PreventCompletion property and resuming the Migration Request for a final sync (on the Exchange 2013 server), you get into this situation.

Therefore, first make sure that the lock is applied effectively by trying to open the Public Folders on a client machine. If you are pressed on time, restart the Exchange 2007 server and the PF lock should be applied.

Then, you can change the PreventCompletion to FALSE and resume the Migration Request. If you have reached recently the AutoSuspended status or you've run one more Resume-PublicFolderMigrationRequest before the lock (to minimize downtime), there shouldn't be much data left to be synced and you will reach almost immediately the COMPLETED status.

If you are already in this situation - waiting for too long in StalledDueToMailBoxLock status, shutdown the Exchange 2007 server for a couple of minutes (normally, you will get NetworkFailure state), then start Exchange 2007 and when it is up and running, resume the Migration Request.

• Edited by NetoMeter Screencasts Thursday, January 02, 2014 7:47 PM

 

I've had the similar pf migration issue from 2007 to 2013 and after a bit research found a below link for solution.

I've restarted Information store service on exchange 2013...

http://msexchangeguru.com/2013/04/18/exchange2013-public-folders/

-If multiple source PF databases, wait Replication Interval+1 hour after locking source so they can replicate. Alternatively you can restart the Microsoft Exchange Information Store service to bypass the    waiting time.

I'm so glad I found this post! I ran into the same issue with the "stalledduetomailboxlock" status. I rebooted the Exchange 2007 mailbox server that had the public folder database, executed "Running Resume-PublicFolderMigrationRequest -Identity \PublicFolderMigration" couple of times (probably worked executing the command once but did it twice for good measure), and my migration finished! Thanks again!

Restarting the server shouldn't be necessary.  If it's waiting for a lock, you can either:

1) Wait
2) Dismount and re-mount the source Public Folder database(s)

FYI: You can see that the request is waiting (or not) by running these two lines of code in your 2013 EMS:

$x = Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport
$x.report.entries[-1] | select message

Thanks a lot Mike!

Hi, agreed.

I had the lock on the first database and for me the StalledDuetoMailboxLock lasted  only a few minutes.

Restarting the Exchange 2007 server worked for me. I know this is an old post, but I would like the share this anyway :-)

• Proposed as answer by Doug Kinzinger Wednesday, March 25, 2015 7:11 PM

I ran into the same issue, ran the command on the 2013 and not the 2010, what did you do to resolve, i rebooted 2007 but still have the same locked error.