This blog post serves to inform IT professionals and users alike of a common issue with Exchange Server and Domain Controllers. In this blog post, we will discuss the potential causes of the issue and potential solutions.
A common issue that IT professionals and users face is the inability to perform an operation in Exchange Server due to an “object new exchange server could not be found on domain controller” error message. This issue can be frustrating and can cause a disruption in service. No matter the size of the organization or the environment, this issue can affect any user trying to perform an operation in Exchange Server.
The “object new exchange server could not be found on domain controller” error message can be caused by a number of different issues, ranging from minor misconfigurations to a more complex problem. As a result, troubleshooting the issue can be quite a challenge. In this blog post, we will discuss the potential causes of the issue and possible solutions.
The operation cannot be performed because the message has been changed – Fix
Following the execution of the command, the below error will be prompted.
The inability to locate object test1 on the domain prevented the operation from being completed. lan. + FullyQualifiedErrorId: 44ACBC3C, Microsoft, CategoryInfo: NotSpecified: (0:Int32) [New-MailboxExportRequest], ManagementObjectNotFoundException Exchange. Management. RecipientTasks. NewMailboxExpo rtRequest .
However, before doing so, we must ensure that the prerequisites for exporting from Exchange Server to PST are met. Make sure the most recent service pack and all necessary patches are installed if you have Exchange Server 2010 or 2013.
Second, you might verify that the command is being executed by a member of the Exchange administrators group and that the destination location has Exchange Trust Subsystem enabled with full control over the share and folder.
According to the error message above, the username was not located in the domain controller. Make sure the user is not disabled or deleted first. The Active Directory Users and Computers on your domain controller can be used to verify this. Ensure that the server you are exporting from can access the FQDN of your domain controller.
If you are exporting from a root domain controller and the users are under a child domain controller, that is another thing to verify. For example, you have domain. lan, and you have divided your Active Directory based on the region, such as emea domain. lan or us. domain. lan. In this situation, you would need to ensure that the Exchange Server can connect to your root domain controller.
Another thing to keep in mind is that Exchange will have some issues determining the location of the user if your users are on the child domain controller and the email is on the root domain controller. The New-MailboxExporRequest cmdlet may encounter some problems when looking up the user to export, despite the fact that both domain controllers are in the same forest.
Despite being created and located in the same forest, the user is not listed in the primary Active Directory, and in this case, is not in the domain. lan but in the us. domain. lan. By default, if the Exchange Server is installed under domain. lan, the export script will not find the user.
In this situation, you must ensure that the domain controller is present in your server’s export script so that you can specify where the script should look for the user.
After the user entered the mailbox username and the network shared path for the PST file folder, everything is now looking good with the command. However, the user has run into the following error: The operation failed because object “xxx” was not located on “domain name.” + FullyQualifiedErrorId: 44ACBC3C, Microsoft, CategoryInfo: NotSpecified: (0:Int32) [New-MailboxExportRequest], ManagementObjectNotFoundException Exchange. Management. RecipientTasks. NewMailboxExportRequest.
Backup requirements – The export option enables you to pick and choose which mailboxes you want to export while leaving the others alone.
Exchange Recovery supports mailbox export to the Outlook PST file format in addition to fixing corrupt offline EDB files. After previewing the mailbox contents, it converts EDB mailboxes to PST files and permits moving only desired data (with smart filters). Users can transfer mailboxes from any Exchange Server version’s offline EDB file (including versions prior to Exchange 2010) to PST and other locations like live Exchange, Microsoft 365, and Outlook profiles.
Even if the Exchange administrator used the Exchange Admin Center interface to perform the Exchange mailbox export, the error may still occur.
Each administrator must regularly perform the necessary task of exporting Exchange mailboxes to PST. Mailboxes become slower and less responsive as their size increases. Also, there are multiple requirements for an Exchange mailbox backup-.
Error “Object Couldn’t be Found on the Primary Domain” Occurs After Executing the Command
Although the PowerShell cmdlet mentioned above appears to work fine, users still experience the following error:
