SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:

Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          {
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          }
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The virtual directory 'ecp' already exists under 'server/name'.
Parameter name: VirtualDirectoryName".

Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          {
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          }
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".

Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          {
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          }
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".

!! And now transport service won't start and mail is unavailable !!

Any help would be appreciated.

I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

January 27th, 2015 1:28pm

Also FYI

The SP1 install fails at about 90% through the "Mailbox role: Client Access service

Free Windows Admin Tool Kit Click here and download it now
January 27th, 2015 1:38pm


I tried what was mentioned here:

https://social.technet.microsoft.com/Forums/en-US/66eb22ee-c686-45f8-a49f-3e13cfcb9548/exchange-2013-sp1-update-install-error-client-access-role-front-end-transport-service-failed?forum=exchangesvrdeploy

It got me past the errors posted above. I also had to manually create the front end ecp in default web site as posted in the above link. I did this on the fly after Client acces service STEP of install completed while it then moved on to the next and had it built quickly enough that the install was not interrupted on me as it was for poster in the link.

January 27th, 2015 3:05pm

Hi,

Thanks for your response.

From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.

Hope this can be helpful to you.

Best regards,

Free Windows Admin Tool Kit Click here and download it now
January 30th, 2015 10:10am

Yes I did that from both default and back end. It solved my exchange application backup issue AND actually increased detail on some of my event log entries to assist me in finding all kinds of remaining dirty entries for our old exchange server in AD I was able to remove with ADSI. Things are running much more smoothly now and exchange application backups with Windows Server Backup are still working again every evening now.
February 2nd, 2015 7:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics