Forum Discussion

Roelknippen's avatar
Roelknippen
Copper Contributor
Mar 02, 2023

Error during installation CU23 on single exchange 2016 server

Hi,

 

I'am doing an upgrade of tot CU23 on a exchange 2016 server and during the update I am getting the following error:

 

Error:
The following error was generated when "$error.Clear();
."$RoleInstallPath\Scripts\ConfigureCafeResponseHeaders.ps1";
CreateCustomHeadersNodeForBackend 'autodiscover'
CreateCustomHeadersNodeForBackend 'ecp'
CreateCustomHeadersNodeForBackend 'ews'
CreateCustomHeadersNodeForBackend 'oab'
CreateCustomHeadersNodeForBackend 'owa'
CreateCustomHeadersNodeForBackend 'powershell'
CreateCustomHeadersNodeForBackend 'pushnotifications'
CreateCustomHeadersNodeForBackend 'rpcproxy'
CreateCustomHeadersNodeForBackend 'sync'
CreateCustomHeadersNodeForBackend 'mapi\emsmdb'
CreateCustomHeadersNodeForBackend 'mapi\nspi'
" was run: "System.Management.Automation.MethodInvocationException: Exception calling "Load" with "1" argument(s): "'“' is an unexpected token. The expected token is '"' or '''. Line 209, position 16." ---> System.Xml.XmlException: '“' is an unexpected token. The expected token is '"' or '''. Line 209, position 16.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseAttributes()
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.Load(String filename)
at Load(Object , Object[] )
at System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke(Object target, Object[] arguments, MethodInformation methodInformation, Object[] originalArguments)
--- End of inner exception stack trace ---
at System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke(Object target, Object[] arguments, MethodInformation methodInformation, Object[] originalArguments)
at System.Management.Automation.DotNetAdapter.MethodInvokeDotNet(String methodName, Object target, MethodInformation[] methodInformation, PSMethodInvocationConstraints invocationConstraints, Object[] arguments)
at System.Management.Automation.DotNetAdapter.MethodInvoke(PSMethod method, PSMethodInvocationConstraints invocationConstraints, Object[] arguments)
at System.Management.Automation.Adapter.BaseMethodInvoke(PSMethod method, PSMethodInvocationConstraints invocationConstraints, Object[] arguments)
at System.Management.Automation.Interpreter.DynamicInstruction`3.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".

Error:
The following error was generated when "$error.Clear();
."$RoleInstallPath\Scripts\ConfigureCafeResponseHeaders.ps1";
CreateCustomHeadersNodeForBackend 'autodiscover'
CreateCustomHeadersNodeForBackend 'ecp'
CreateCustomHeadersNodeForBackend 'ews'
CreateCustomHeadersNodeForBackend 'oab'
CreateCustomHeadersNodeForBackend 'owa'
CreateCustomHeadersNodeForBackend 'powershell'
CreateCustomHeadersNodeForBackend 'pushnotifications'
CreateCustomHeadersNodeForBackend 'rpcproxy'
CreateCustomHeadersNodeForBackend 'sync'
CreateCustomHeadersNodeForBackend 'mapi\emsmdb'
CreateCustomHeadersNodeForBackend 'mapi\nspi'
" was run: "System.Management.Automation.RuntimeException: You cannot call a method on a null-valued expression.
at CallSite.Target(Closure , CallSite , Object , Object )
at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
at System.Management.Automation.Interpreter.DynamicInstruction`3.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".

Error:
The following error was generated when "$error.Clear();
."$RoleInstallPath\Scripts\ConfigureCafeResponseHeaders.ps1";
CreateCustomHeadersNodeForBackend 'autodiscover'
CreateCustomHeadersNodeForBackend 'ecp'
CreateCustomHeadersNodeForBackend 'ews'
CreateCustomHeadersNodeForBackend 'oab'
CreateCustomHeadersNodeForBackend 'owa'
CreateCustomHeadersNodeForBackend 'powershell'
CreateCustomHeadersNodeForBackend 'pushnotifications'
CreateCustomHeadersNodeForBackend 'rpcproxy'
CreateCustomHeadersNodeForBackend 'sync'
CreateCustomHeadersNodeForBackend 'mapi\emsmdb'
CreateCustomHeadersNodeForBackend 'mapi\nspi'
" was run: "System.Management.Automation.RuntimeException: You cannot call a method on a null-valued expression.
at CallSite.Target(Closure , CallSite , Object , Object )
at System.Management.Automation.Interpreter.DynamicInstruction`3.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".

Error:
The following error was generated when "$error.Clear();
."$RoleInstallPath\Scripts\ConfigureCafeResponseHeaders.ps1";
CreateCustomHeadersNodeForBackend 'autodiscover'
CreateCustomHeadersNodeForBackend 'ecp'
CreateCustomHeadersNodeForBackend 'ews'
CreateCustomHeadersNodeForBackend 'oab'
CreateCustomHeadersNodeForBackend 'owa'
CreateCustomHeadersNodeForBackend 'powershell'
CreateCustomHeadersNodeForBackend 'pushnotifications'
CreateCustomHeadersNodeForBackend 'rpcproxy'
CreateCustomHeadersNodeForBackend 'sync'
CreateCustomHeadersNodeForBackend 'mapi\emsmdb'
CreateCustomHeadersNodeForBackend 'mapi\nspi'
" was run: "System.Management.Automation.MethodInvocationException: Exception calling "Save" with "1" argument(s): "Invalid XML document. The document does not have a root element." ---> System.Xml.XmlException: Invalid XML document. The document does not have a root element.
at System.Xml.XmlDocument.Save(String filename)
at Save(Object , Object[] )
at System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke(Object target, Object[] arguments, MethodInformation methodInformation, Object[] originalArguments)
--- End of inner exception stack trace ---
at System.Management.Automation.DotNetAdapter.AuxiliaryMethodInvoke(Object target, Object[] arguments, MethodInformation methodInformation, Object[] originalArguments)
at System.Management.Automation.DotNetAdapter.MethodInvokeDotNet(String methodName, Object target, MethodInformation[] methodInformation, PSMethodInvocationConstraints invocationConstraints, Object[] arguments)
at System.Management.Automation.DotNetAdapter.MethodInvoke(PSMethod method, PSMethodInvocationConstraints invocationConstraints, Object[] arguments)
at System.Management.Automation.Adapter.BaseMethodInvoke(PSMethod method, PSMethodInvocationConstraints invocationConstraints, Object[] arguments)
at System.Management.Automation.Interpreter.DynamicInstruction`3.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".

 

I did do al de prerequirements and all whe passed succesfully. 

 

How can I resolve this issue. 

 

Hope you can help 


Roel Knippen

 

 

1 Reply

  • LunaScott's avatar
    LunaScott
    Iron Contributor

    You can try the following steps hopefully they will help you 
    1. Do these basic checks first 
    Restart the server 
     Turn off your antivirus software 
     Run the installation with administrator privileges (right-click on the installer → “Run as administrator”) 
    2. Install the necessary components 
     Make sure you have installed: 
    .NET Framework 4.8 
    Visual C++ Redistributable 
    Run the following commands to install Windows features: 
    powershell 
    Install-WindowsFeature RSAT-ADDS, NET-Framework-45-Features, Web-Mgmt-Console 
    3. Update the AD schema manually (if errors are reported) 
    powershell 
    . \Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms 
    4. Formal installation CU23 
    cmd 
    . \Setup.exe /Mode:Upgrade /IAcceptExchangeServerLicenseTerms 
    5. Quick Check of Common Errors 
    Error 0x80070643 → Uninstall the old version of Visual C++ and reinstall the latest version.
    PendingReboot → Restart the server and try again.
    Permission problem → Install with Enterprise Admins group account. 
    6. After installation verify 
    powershell 
    Get-ExchangeServer | Select Name, AdminDisplayVersion 
    should show Version 15.1 (Build 2507.6).
    If it still fails → Collect logs from C:\ExchangeSetupLogs and contact Microsoft Support.