We help IT Professionals succeed at work.

Exchange 2013 Cumulative Update 8 Error

jplatovsky
jplatovsky asked
on
I updated Exchange with CU 8 and got an error (see below) but now exchange is not working.  Not receiving or sending.  Outlook cannot connect, etc....

Any ideas?

Error:
The following error was generated when "$error.Clear();
      buildToBuildUpgrade-ExsetdataAtom -AtomName SharedMachineSettings -DomainController $RoleDomainController

" was run: "Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '3238218282' and message 'Failed to contact Windows domain controller.'.
   at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.HandleExsetdataReturnCode(UInt32 scErr)
   at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.BuildToBuildUpgradeAtom(AtomID atomID)
   at Microsoft.Exchange.Management.Deployment.BuildToBuildUpgradeExsetdataAtom.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Comment
Watch Question

Will SzymkowskiSenior Solution Architect
Most Valuable Expert 2015
Top Expert 2015

Commented:
When you did the update to CU8 did it actually complete successfully? CU8 also requires a schema update. Did your account or whatever account was used have schema admins access? In the error message it is specifically stating it cannot connect to a domain controller.

Make sure that the Exchange Server is pointing to the correct domain controller.

Will.

Author

Commented:
CU8 did not complete.  The error that i posted was during the installation and did not complete.
I am using administrator and have full rights.  It is.  Nothing has changed.
Will SzymkowskiSenior Solution Architect
Most Valuable Expert 2015
Top Expert 2015

Commented:
Does the Administrator account have schema admins access as well? Also the main error in the post is pointing to communicating with a Domain Controller. Does this server have DNS properly configured and also does this Exchange server have a DC in the same site?

So there are a few things to check but the error is somewhat obvious. I would start with what I have suggested.

Will.
Thanks for you help but this was not the answer for this case.  Actually, Microsoft Tech Support got involved an update corrupted the some of the files.

Author

Commented:
Microsoft fixed the problem