{"id":105026,"date":"2022-07-21T04:15:26","date_gmt":"2022-07-21T04:15:26","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=105026"},"modified":"2025-10-07T09:30:27","modified_gmt":"2025-10-07T09:30:27","slug":"fix-object-username-could-not-be-found-on-domain-corp","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/fix-object-username-could-not-be-found-on-domain-corp\/","title":{"rendered":"How to Fix Error – The Operation couldn\u2019t be Performed because Object \u2018Username\u2019 couldn\u2019t be Found on Domain.corp?"},"content":{"rendered":"

In Exchange Server, you may need to export a mailbox to PST file for various reasons, such as routine maintenance, for archiving, when an employee leaves the organization, or before performing a mailbox clean-up. Sometimes, when you try to export mailboxes to PST file<\/a> using the Exchange Admin Center (EAC) or using the New-MailboxExportRequest cmdlet without the -DomainController parameter, you get an error message – The Operation couldn’t be Performed because Object ‘Username’ couldn’t be Found on Domain.corp<\/em>.<\/p>

\n
\"Error<\/figure>\n<\/div>

You may also get the above error when trying to uninstall an Exchange Server.<\/p>

In this blog, we will discuss how to resolve the Operation couldn’t be Performed because Object ‘Username’ couldn’t be Found on Domain.corp<\/em> error.<\/p>

Why does the Object couldn’t be found on the Domain.corp Error Occur?<\/strong><\/h2>

When an operation is initiated from one domain (e.g., the parent) that attempts to access a user object residing in another domain (e.g., a child domain) and the operation doesn’t correctly reference the domain where the user object exists, the system may fail to locate the object, resulting in this error.<\/p>

Resolving the Operation couldn’t be Performed because<\/em> Object couldn’t be found on the Domain.corp Error<\/strong><\/h2>

You can follow the below methods to resolve the error, depending on the scenario.<\/p>

1. Run New-MailboxExportRequest with DomainController Parameter<\/strong><\/h3>

If you’re getting this error when exporting the mailbox to PST, you can use the New-MailboxExportRequest<\/a><\/strong> PowerShell cmdlet with the DomainController <\/strong>parameter to avoid this error (see the below example).<\/p>

New-MailboxExportRequest -Mailbox \"User\" -FilePath \\\\server\\PSTExport\\export.pst -DomainController <DomainController><\/strong><\/code><\/pre>
\n
\"DomainController<\/figure>\n<\/div>
In the above command,<\/p>
    \n
  1. Adding the -DomainController<\/strong> switch enables you to explicitly provide the name of domain controller of the active directory where the user resides.<\/li>\n\n\n\n
  2. The export process will access the specified domain controller to get the user information and export the mailbox.<\/li>\n<\/ol>
    However, to export the mailboxes to PST, your user account must have the Mailbox Import Export role assigned to it. Additionally, the user account also have the read\/write permissions for the folder where the converted PST is to be stored.<\/p>
    After running theNew-MailboxExportRequest cmdlet, you can use the Get-MailboxExportRequest<\/a> cmdlet to view the status of export request.<\/p>
    2. Use an EDB to PST Converter Software<\/strong><\/h3>
    As an alternative, you can use Stellar Converter for EDB –a specialized EDB to PST converter software<\/a> to export Exchange mailboxes to PST. This software can directly export the mailboxes from the EDB file (hosted or offline) to PST files without the need of a running Exchange Server. It doesn’t require any additional permissions. The software can process up to 8 mailboxes simultaneously for faster conversion. It converts the mailboxes and other EDB file items, including public folders to PST files while keeping their original format intact. The software can also export the mailboxes and other EDB file items to a live Exchange Server or Microsoft 365.<\/p>
    3. Install the Exchange Server Security Updates<\/strong><\/h3>
    If you are getting this error while uninstalling the Exchange Server 2019 or 2016 with January 2023 updates, you need to install the June 2023 security updates to fix the issue. You can refer to the links given below for detailed process:<\/p>