If you’re exporting a large size mailbox to PST in Exchange Server 2010, probably you may get 0x80040115 Mapi_e_network_error during exporting a mailbox data to PST file. Of-course, exporting user’s mailbox data in a PST file is a very regular task in Exchange environment but if you’re exporting large sizes (5 GB+) mailboxes using New-MailboxExportRequest shell command; mailbox exporting process may be hang and then fail without completing the process.
So today I’m going through few simple ways to resolve 0x80040115 Mapi_e_network_Error, and discussing the causes with their solution whenever you receive this error during export a large Exchange 2010(SP1) mailbox to PST file. But before start the procedure, let’s talk about this error first…
The error code 0x80040115 translates to Mapi_e_network_error, usually specifies problem with connection to any of the stores involved in the mailbox exporting process.
Causes of 0x80040115 Mapi_e_network_error
Case 1: The 0x80040115 Mapi_e_network_error message code may be occurred by corrupt windows system files as damaged system files entries might be the actual threat of your computer. There can be many events such as improper shutdown, incomplete installation or uninstallation, improper deletion of hardware or programs, or also a spyware/virus/adware attack on your computer which may have resulted in the system files errors.
Case 2: Another case, it was suspicion that connection to the PST was the issue as PST file was accessed across the network. PST was shared on Windows 7 workstation where EMS (Exchange Management Shell) was being used to run the Power Shell scripts. So the main question arises here, why do we need PST to be on same system where export process is also running? The simple answer, we don't need to go over the network during the export process.
Troubleshooting MAPI_E_NETWORK_ERROR (0x80040115)
Fix for Case 1:
· Log on your computer as Administrator account and open System Restore option.
· Just restore your computer to an earlier time restore point.
· Once it’s done, restart your computer.
However, it has been detected the mailbox exporting problem might be fixed very rarely by applying this technique. But you can perform this process as initially troubleshooting step.
Fix for Case 2:
· Create a folder/share on CAS server 1 and provide the Exchange Trusted Subsystem Read/Write access to the share as described here.
· In command, you need to specify new share as our file path and also specify CAS 1 MRSServer setting in your New-MailboxExportRequest command (i.e. New-MailboxExportRequest -Mailbox user1 -FilePath “\\CAS1\PSTFileShare\userA.pst” -MRSServer CAS1.domain.com).
By executing above solution, transfer rate will increase much higher than last time when you exported mailbox on Exchange 2010. So if you’re planning to export big size user mailbox data to PST file using this method, it will complete the larger size mailbox export process within few hours without any failure.
That’s it. However, solution 2 is bit tough to implement until you haven’t good knowledge of Exchange Power Shell scripting. So only execute that method if you can control the process till the last of the completion. Otherwise, there is a widely used Exchange mailbox export tool 'Stellar EDB to PST Converter' which you can download here to export any size of Exchange EDB file or mailbox to Outlook PST file to any desire location on your computer.
Hope, it works…