Exchange 2013 Update Issue CU7 to CU13

Updated one of my two dag member servers to CU13.  It didn't finish and when i try to rerun the update i get the following error.  Can someone please tell me how to fix this?



Error:
The following error was generated when "$error.Clear();
          & $RoleBinPath\ServiceControl.ps1 Save
        " was run: "System.Management.Automation.PSSecurityException: AuthorizationManager check failed. ---> System.Runtime.InteropServices.COMException: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (Exception from HRESULT: 0x80070422)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObject.Initialize(Boolean getObject)
   at System.Management.ManagementObject.Get()
   at System.Management.Automation.PsUtils.GetParentProcess(Process current)
   at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId, ExecutionPolicyScope scope)
   at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId)
   at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason)
   at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo commandInfo, CommandOrigin origin, PSHost host, Exception& reason)
   at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host)
   --- End of inner exception stack trace ---
   at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host)
   at System.Management.Automation.CommandDiscovery.ShouldRun(ExecutionContext context, PSHost host, CommandInfo commandInfo, CommandOrigin commandOrigin)
   at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(CommandInfo commandInfo, CommandOrigin commandOrigin, Nullable`1 useLocalScope, SessionStateInternal sessionState)
   at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
   at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
   at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)
   at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".
Sean FabianChief Technology OfficerAsked:
Who is Participating?
 
Mumbai TechConnect With a Mentor Commented:
The same issue and fix has been posted on below article,b basically The fix is to remove the virtual directory and restart the setup:

Remove-WebServicesVirtualDirectory -Identity "MYSERVER\EWS (Exchange Back End)


https://social.technet.microsoft.com/Forums/exchange/en-US/a69afd36-cc5b-445a-8f67-b830771ed976/upgrade-2013-rtm-to-cu1?forum=exchangesvrdeploy
0
 
Mumbai TechConnect With a Mentor Commented:
Please run the following two commands during installation

Get-Service -name winmgmt, remoteregistry, w3svc, iisadmin | set-service -startuptype
automatic

Get-Service -name winmgmt, remoteregistry, w3svc, iisadmin | Start-Service

Ref : the same issue fix available on below post
https://social.technet.microsoft.com/Forums/exchange/en-US/fe02fd5f-8398-4af9-ad82-f240c7f0a178/exchange-2013-cu2-will-not-install-exchange-is-now-in-an-unuseable-state?forum=exchangesvrdeploy
0
 
Sean FabianChief Technology OfficerAuthor Commented:
I did what you said... reran the update and got the following error....

Error:
The following error was generated when "$error.Clear();
          & $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
          & $RoleBinPath\ServiceControl.ps1 Stop $RoleRoles.Replace('Role','').Split(',')
        " was run: "System.Management.Automation.CommandNotFoundException: The term 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\ManageScheduledTask.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
   at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions, CommandOrigin commandOrigin, ExecutionContext context)
   at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
   at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
   at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)
   at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".
0
 
Mumbai TechConnect With a Mentor Commented:
Please refer following article basically you need to uninstall the interim updates which error indicates.

https://social.technet.microsoft.com/Forums/exchange/en-US/519958f9-6538-4d38-b682-1eaca2ab471f/exchange-2013-cu2-installation-problem?forum=exchangesvrdeploy
0
 
Sean FabianChief Technology OfficerAuthor Commented:
Removed the update in windows update and proceeded with the update of cu13 and now am getting this error.....

Error:
The following error was generated when "$error.Clear();
          update-WebServicesVirtualDirectoryVersion -DomainController $RoleDomainController;
          $BEVdirIdentity = $RoleNetBIOSName + "\EWS (Exchange Back End)";
          $be = get-WebServicesVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          {
            $BackEndPort=":444";
            $urlToUse = "https://" + $RoleFqdnOrName + $BackEndPort + "/ews/exchange.asmx";
            new-WebServicesVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -windowsAuthentication:$true -WSSecurityAuthentication:$true -BasicAuthentication:$false -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
          }
          else
          {
            $be | set-WebServicesVirtualDirectory -windowsAuthentication:$be.WindowsAuthentication -WSSecurityAuthentication:$be.WSSecurityAuthentication -BasicAuthentication:$be.BasicAuthentication
          }
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeServicesAppPool" -Version:"v4.0";
        " was run: "System.ArgumentException: The virtual directory 'EWS' already exists under 'EXCH1.THINK.local/Exchange Back End'.
Parameter name: VirtualDirectoryName
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewWebServicesVirtualDirectory.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.