How to Solve the Error: New-MailboxExportRequest Couldn’t Find The Enterprise Organization Container
Exporting Exchange Mailbox to PST is the daily job of an Exchange user or IT administrator while using Exchange 2016 Server. But sometimes users get an error “new-mailboxexportrequest couldn’t find the enterprise organization container” when users export the Microsoft Exchange mailbox by using the Exchange Admin Center (EAC).
When users use the New-MailboxExportRequest command to export the Exchange Mailbox to Outlook Data File. Then also they get this error: “new-mailboxexportrequest couldn’t find the enterprise organization container”.
How to Resolve the Error: New-MailboxExportRequest Couldn’t Find The Enterprise Organization Container
Users usually got this error when they try to insert the “UNC path to PST”. For this user have to assign the “Mailbox Import Export Role”. After assigning the role then user doesn’t encounter with this error and they can easily export the Exchange Mailbox to Outlook Data File
Steps to Fix this Error Using Exchange PowerShell
Step 1: Open Exchange Management Shell
Step 2: Insert the following command given below:
New-ManagementRoleAssignment -Role “Mailbox Import Export” -User “Name of User”
Step 3: Now run the New-MailboxExportRequest command to export the MS Exchange Mailbox to PST.
Step 4: Finally, the user doesn’t face any error “new-mailboxexportrequest couldn’t find the enterprise organization container” and the Exchange mailbox has been Exported to the PST file.
Note: Same as this one user have to assign the “Mailbox Import Export role” in Exchange Admin Center. After assigning the role, user will not face this error in Exchange Admin Center.
Follow the Steps to Assign the Exchange Management Role in EAC
Step 1: In EAC, go to permission > In the “Admin Roles” > Select Organization Management
Step 2: Double click on Organization Management > In the Role > Select Mailbox Import Export > Click on save button > The role has been assigned
After assigning the role when the user exports the Exchange mailbox to Outlook Data File, they will not face any error couldn’t find the enterprise organization container.
To handle Exchange Server it needs technical knowledge and hand in experience. So, that is any error or corruption occurred they can understand it and easily resolve all the users. Also, users can export only one mailbox to PST at a time.
If a user tries to use Exchange PowerShell to export multiple mailboxes then they have to handle so many errors, because if one of the mailboxes is corrupted that it will create more problems for the user.
If users know how to solve it they can easily resolve the problem but the Naive users don’t know how to fix these kinds of issues. Some time IT admin along with naive users also want the alternative solution to recover highly corrupted EDB files and export multiple Exchange mailboxes to Outlook Data File without any data loss. The solution can save time and effort too.
Best Alternative Solution to Export Exchange Mailbox to PST
User can use the Exchange EDB Converter software provided by SysTools as the professional solution which easily recovers and repair EDB file from corruption and repair public folder database Exchange 2016, 2013, 2010 witn no data loss. This utility export Exchange Mailboxes in batch of any sizes without any loss of data. Then the user does not have to face the error “new-mailboxexportrequest couldn’t find the enterprise organization container”.
It does not require any command to use the software to exports the exchange mailbox. This tool provides the graphical user interface which allows user to load their offline/dismounted EDB file and then they can use the certain option to recover the damaged .edb file and repair Exchange mailbox into a healthy format.
The software also supports Streaming Media File (STM). Users can recover the purged/permanently Exchange database mailboxes by using the Advance Scanning option. This option help users to automatically recover deleted mailbox after retention period.
Apart from the PST file, this professional tool also exports the mailboxes into multiple file formats such as HTML, EML, MSG, MBOX, PDF. So, that user can access their EDB file in different email clients or they can open the Exchange Database emails in a web browser. Also, users can save the database file or mailboxes as a backup for future use.
Key Features Of Automated Solution
- Generate the Outlook Data File in UNICODE PST file
- Maintains original folder structure and data integrity
- Exchange EDB Converter support priv.edb and pub.edb files
- Extract mailbox from EDB file Exchange 2016/2013/2010
- Users can preview the Exchange Mailbox data items: emails, calendars, contacts, journals, tasks, notes
- Provide option to remove encryption from Exchange Mailbox in batch
- The tool is compatible with all versions of Exchange Server, MS Outlook, Windows Operating System
Step Wise Working Of Automated Solution to Export Multiple Exchange Mailbox
Step 1: Download >> Install >> Launch the professional software
Step 2: In the home screen, click on Add File >> Load dismounted/offline EDB File >> Click on Advance scan to recover corrupted and purged mailboxes >> Click on Add
Step 3: Preview Exchange database file, mailboxes or data items >> Click Exported
Note: Export Selected button allows user to export select data items into different file formats.
Step 4: Select all Exchange Mailboxes >> Click on PST >> Click on browse button to set the target file location >> Click Exported
Finally, the user has exported multiple Exchange mailboxes into PST. Now user can check the resultant file from the target file.
Bringing It All Together
The write-up has provided the complete solution to resolve the error “new-mailboxexportrequest couldn’t find the enterprise organization container” from the Exchange Management Shell and Exchange Admin Center. Also, users know the professional solution to export the Exchange mailboxes in bulk to Outlook Data File of any file size. This utility performs the users task in a single shot, without any data loss.