I have 2 Exchange 2013 CU5 servers running on Windows Server 2012.  Domain Controllers are also Windows server 2012.

When applying the CU7 update to the first one to be updated, I get the following errors in the ExchangeSetup.log file.  I cannot uninstall nor can I continue the installation.  The error does not indicate WHICH registry key is missing.  I presume the missing key is on the GC since the ConfigureNetworkProtocolParameters.ps1 script updates a GC (according to the notes in the ps1 file).

Has anyone else had this problem?  Ideas on how to resolve?

Thanks!

[01/30/2015 19:47:58.0620] [1] Exception : Microsoft.Exchange.Management.Deployment.ScriptExecutionException: The following error was generated when "$error.Clear(); 
          . "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1"; 
          Enable-RpcOverTcpPortScaling; 
          Enable-ExtendedTcpPortRange
        " was run: "System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The registry key at the specified path does not exist.
   at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)". ---> System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The registry key at the specified path does not exist.
   at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.InternalExecuteScript(String script, Boolean handleError, Int32 subSteps, LocalizedString statusDescription)
   at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.ExecuteScript(String script, Boolean handleError, Int32 subSteps, LocalizedString statusDescription)
   at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.GenerateAndExecuteTaskScript(InstallationCircumstances installationCircumstance)
[01/30/2015 19:47:58.0635] [1] [ERROR] The following error was generated when "$error.Clear(); 
          . "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1"; 
          Enable-RpcOverTcpPortScaling; 
          Enable-ExtendedTcpPortRange
        " was run: "System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The registry key at the specified path does not exist.
   at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)".
[01/30/2015 19:47:58.0635] [1] [ERROR] The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The registry key at the specified path does not exist.
[01/30/2015 19:47:58.0635] [1] [WARNING] An unexpected error has occurred and a Watson dump is being generated: The following error was generated when "$error.Clear(); 
          . "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1"; 
          Enable-RpcOverTcpPortScaling; 
          Enable-ExtendedTcpPortRange
        " was run: "System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The registry key at the specified path does not exist.
   at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)".

Hi

Did you prepare AD and Schema before hand? is your account part of all the correct groups?

AD is prepared and Schema is updated via the setup program successfully before it ever gets to this phase.

My account is in Domain Admin, Enterprise Admin, Organization Management and Schema Admins groups so I should have the right credentials.

Hi,

I looked into ConfigureNetworkProtocolParameters.ps1 file, the registry key related to this error is HKLM:\\SOFTWARE\Policies\Microsoft\Windows NT\Rpc and a value EnableTcpPortScaling.

If this registry key is missing, please try to create it. Go to HKLM:\\SOFTWARE\Policies\Microsoft\Windows NT\Rpc  -> Click Edit -> New -> DWORD -> enter EnableTcpPortScaling -> double click it and change the value data to 1.

Then try to apply CU7 update to check this issue.

Note: Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

https://support.microsoft.com/kB/256986?wa=wsignin1.0

Best Regards.

• Edited by Lynn-Li 5 hours 0 minutes ago

Hi,

I looked into ConfigureNetworkProtocolParameters.ps1 file, the registry key related to this error is HKLM:\\SOFTWARE\Policies\Microsoft\Windows NT\Rpc and a value EnableTcpPortScaling.

If this registry key is missing, please try to create it. Go to HKLM:\\SOFTWARE\Policies\Microsoft\Windows NT\Rpc  -> Click Edit -> New -> DWORD -> enter EnableTcpPortScaling -> double click it and change the value data to 1.

Then try to apply CU7 update to check this issue.

Note: Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

https://support.microsoft.com/kB/256986?wa=wsignin1.0

Best Regards.

• Edited by Lynn-Li Monday, February 02, 2015 6:50 AM

I tried manually adding that registry key - didn't help.

Turns out Endpoint Protection Manager was blocking something.  Once I disabled it, the update installed.

• Marked as answer by David A Smith 11 hours 40 minutes ago