jplatovsky
asked on
Exchange 2013 Cumulative Update 8 Error
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-Exsetd ataAtom -AtomName SharedMachineSettings -DomainController $RoleDomainController
" was run: "Microsoft.Exchange.Manage ment.Deplo yment.Exse tdataExcep tion: An error occurred with error code '3238218282' and message 'Failed to contact Windows domain controller.'.
at Microsoft.Exchange.Managem ent.Deploy ment.Manag eExsetdata Atom.Handl eExsetdata ReturnCode (UInt32 scErr)
at Microsoft.Exchange.Managem ent.Deploy ment.Manag eExsetdata Atom.Build ToBuildUpg radeAtom(A tomID atomID)
at Microsoft.Exchange.Managem ent.Deploy ment.Build ToBuildUpg radeExsetd ataAtom.In ternalProc essRecord( )
at Microsoft.Exchange.Configu ration.Tas ks.Task.<P rocessReco rd>b__b()
at Microsoft.Exchange.Configu ration.Tas ks.Task.In vokeRetrya bleFunc(St ring funcName, Action func, Boolean terminatePipelineIfFailed) ".
Any ideas?
Error:
The following error was generated when "$error.Clear();
buildToBuildUpgrade-Exsetd
" was run: "Microsoft.Exchange.Manage
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Configu
at Microsoft.Exchange.Configu
ASKER
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.
I am using administrator and have full rights. It is. Nothing has changed.
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.
So there are a few things to check but the error is somewhat obvious. I would start with what I have suggested.
Will.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Microsoft fixed the problem
Make sure that the Exchange Server is pointing to the correct domain controller.
Will.