Share via


Troubleshooting: The Exchange server for the database object wasn’t found in Active Directory Domain Services

Issue

We have been working with my customer to upgrade from Exchange Server 2010 to Exchange Server 2016. During the design discussions, the customer told us they tried to upgrade Exchange on their own but ran into some issues. After finalizing the design, we started to work on Exchange Server 2016 implementation. During the installation of Exchange Server 2016, we ran into a problem on step 10 related to “Exchange server for the database object wasn’t found in Active Directory Domain Services. The object may be corrupted

http://msexperttalk.com/wp-content/uploads/2016/11/1.png

Error:

The following error was generated when “$error.Clear();

Get-MailboxDatabase -Server $RoleFqdnOrName | Mount-Database -ErrorAction SilentlyContinue

” was run: “System.InvalidOperationException: The Exchange server for the database object “DB02″ wasn’t found in Active Directory Domain Services. The object may be corrupted.

at Microsoft.Exchange.Management.SystemConfigurationTasks.GetDatabaseTask`1.WriteResult[T](IEnumerable`1 dataObjects)

at Microsoft.Exchange.Management.SystemConfigurationTasks.GetDatabaseTask`1.InternalProcessRecord()

at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)”.

The Exchange server for the database object “DB02” wasn’t found in Active Directory Domain Services. The object may be corrupted.

at Microsoft.Exchange.Management.SystemConfigurationTasks.GetDatabaseTask`1.WriteResult[T](IEnumerable`1 dataObjects)

How to fix it?

When started to troubleshoot the issue, verified that we do not have a database on Exchange Server 2010 that has a name of “DB02“. As per error, it's definitely trying to connect to database DB02 which doesn’t exist. Decided to look at ADSIEdit to verify if we have any dormant objects from previous upgrades that is causing this issue. Looking at the ADSIEdit, we can see that we do have a DB02 object but that database does not exist. Manually removed the DB02 from ADSIEdit and performed AD replication to replicate the changes. After removing the DB02 from ADSIEdit, was able to install Exchange Server 2016 without any issues.

http://msexperttalk.com/wp-content/uploads/2016/11/2.jpg