How to Fix “Object Couldn’t be Found on the Primary Domain” Error? Complete Solution

Summary: In this write-up, we will discussed and provide solution on how to fix the error “Object couldn’t be found on the primary domain”.

When Microsoft Exchange Administrator and users export Exchange database mailboxes to the Outlook PST file from Exchange Server via PowerShell New-MailboxExportRequest command, then they encounter this error which is given below:

New-MailboxExportRequest -Mailbox “testing01” -FilePath “\\exch\admin\desktop\new.pst”

Error “Object Couldn’t be Found on the Primary Domain” Occurs After Executing the Command

The PowerShell cmdlet given above seems fine but still, users encounter this error:

Note: Use will face the same error when they export the Exchange mailbox to Outlook data file via Exchange Admin Center

How to Fix the Error: Object Couldn’t be Found on the Primary Domain?

Users can use the solution provided below and resolve the error:

First, ensure all the prerequisites are met which is required to export mailbox to Outlook PST file.

1. Make sure that the Exchange Mailbox Import Export role are assigned properly
2. Verify the folder where the EDB mailboxes is to be exported is network-shared
3. Check that the Exchange Trusted Subsystem security group with full control is provided in the target file

Verify the mailboxes that users are trying to export isn’t disabled or deleted. To check this, go to AD (Active Directory) user & computer on the domain controller. Then check the FQDN of domain controller is easily accessible from the server that users are exporting.

Also make sure that if you are exporting the EDB mailboxes, then the root domain controller is reachable from the Microsoft Exchange Server & users being in a child domain controller.

Users have to consider that if the Exchange database mailbox users are on the child domain controller & EDB emails are in root domain controller, then the MS Exchange Server may face some problem to identify the location of user. Users may also face some issue when they use the PowerShell command to export the mailboxes because both the domain controllers are in same forest.

Then, add the domain controller parameter which specifies to the command that were to look for the Exchange user mailbox.

New-MailboxExportRequest –Mailbox ‘testing01’ –FilePath “\\exch\admin\desktop\new.pst” –DomainController “inset_the_name_of_mailbox_domain”

This PowerShell cmdlet export the Exchange database mailboxes from root domain where Microsoft Exchange Server exists.

Note: It needs in-depth knowledge and hands-on experience to use the Exchange Management Shell. Otherwise, you will find the method complex and time-consuming. If you are new to MS Exchange Environment, instead of using the manual solution users can use the advanced software provided by SysTool which provides simplified as well as the hassle-free solution to export mailboxes in bulk.

Use Best Alternative Solution

SysTools EDB to PST Converter software is used by various IT Experts, Exchange, and naive users for bulk export mailbox to PST Exchange 2010, 2013, 2016 from offline/dismounted Exchange database file in a simplified manner. This utility support various mailboxes such as: user, archive, shared, legacy, disconnected and user can easily export all these mailboxes to the Outlook data file in batch without any command.

The software provides an interactive graphical user interface which makes the user works a lot easier and saves user time too. It offers dual scan mode option which easily repair EDB file and resolves database corruption Exchange 2010, 2013, 2016 without any data loss. To remove minimal corruption, users can select the Quick scan and for highly corrupted and damaged EDB file select the advance scan mode.

After conversion of Exchange database mailboxes, the utility automatically created an export report in CSV file format which contains the success and fail count exported mailbox data.

Key Features Of Automated Wizard

1. Support public and private Exchange database file
2. Preview Microsoft EDB mailbox data items before conversion
3. Preserve actual folder structure and keep metadata intact
4. Export selective mailbox items by using date & categories filter option
5. Remove email encryption (SMIME/OpenPGP) from Exchange mailboxes in bulk
6. Extract mailbox to MBOX, EML, PST, HTML, MSG, PDF file formats
7. Suitable with all Windows OS, Outlook and Exchange Server versions

Bringing It All Together

This write-up provides detailed solution to fix the error “Object couldn’t be found on the primary domain” by using the solution provided here but sometimes users may find it difficult to resolve the issue because they might be new to the Exchange environment or technicality. In that case, users can use the advanced software mentioned in the above section which easily export multiple mailboxes to the Outlook PST file in batch in a hassle freeway.