Saturday, December 14, 2013

Attempting to move a mailbox from Exchange 2003 server throws the error: “Mailbox database ‘2d14e873-68fc-4475-acf6-1eb3f3909753’ is offline.”


You attempt to move a mailbox from Exchange 2003 server with the New Local Move Request but receive the following error:

image image

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:05


Mailbox database '2d14e873-68fc-4475-acf6-1eb3f3909753' is offline.

MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010)
Diagnostic context:
    Lid: 11672   dwParam: 0x6D9      Msg: EEInfo: NumberOfParameters: 4
    Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
    Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[1]: Unicode string:
    Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[2]: Long val: -545057711
    Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[3]: Long val: 382312662
    Lid: 45169   StoreEc: 0x824    
    Lid: 44273 
    Lid: 59431   EMSMDB.EcDoConnectEx called [length=110]
    Lid: 34855   EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
    Lid: 56945 
    Lid: 59431   EMSMDB.EcDoConnectEx called [length=110]
    Lid: 34855   EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=15]
    Lid: 59505   StoreEc: 0x3F2    
    Lid: 52465   StoreEc: 0x3F2    
    Lid: 60065 
    Lid: 33777   StoreEc: 0x3F2    
    Lid: 59805 
    Lid: 52209   StoreEc: 0x3F2    
    Lid: 56583 
    Lid: 52487   StoreEc: 0x3F2    
    Lid: 19778 
    Lid: 27970   StoreEc: 0x3F2    
    Lid: 17730 
    Lid: 25922   StoreEc: 0x3F2    
Click here for help...

Exchange Management Shell command attempted:
' Students/S4 Students/KAKnights-Fubler' | New-MoveRequest -TargetDatabase 'BBS Alumni Database'

Elapsed Time: 00:00:00


While there are various reasons why this error would be thrown, one of them is that the Exchange 2003 server’s mailbox store does not have proper permissions.  Check the permissions on the store’s properties to ensure that the Allow inheritable permissions from the parent to propagate to this object and all child objects. Include these with entries explicitly defined here. is selected:





Andrew Hawk said...

While moving Exchange database there are many other similar errors that arise in between. A simple & recommended way to move Exchange database is to get help from a software that converts Exchange database into PST file format. Then using Powershell import these PST files into any Exchange server.

Get Helpful Product for Moving Exchange Database. (

jhon drake said...
This comment has been removed by the author.
Kaye R. Jenkins said...

Exchange issues without facing any interference. It is the relevant and result-oriented solution to get back crucial Exchange database.

Get More info:-

Robert Keys said...

EDB to PST converter software smoothly convert EDB to PST file and save complete data in Outlook. EDB exporter tool efficiently recover corrupt EDB file and export EDB emails with all meta-data in new PST file location within few minutes. It access EDB file and Extract EDB to PST from all Exchange versions :-

Gilbert Young said...

Use EDB to PST Converter Software that keep the environment of MS Exchange functioning well and running. With this software, you can repair damaged or corrupt EDB server files and extract both multiple and single EDB mailboxes and export the same into Outlook PST, EML, HTML, RTF and MSG formats or Office 365 or Text file. Read more:-

johnbarker said...

Best software to recover EDB file and convert EDB file to PST file with whole EDB folders.


Make My Digital Signature said...

Thank you for describing in detail. It is a valuable information. We are the supreme provider of Digital signature certificate