We help IT Professionals succeed at work.

Exchange 2013 Cu install fails at client server role install

Single Exchange server  2013 preparing to move us to Office 365 via hybrid .  The other night I attempted install of CU22 and it failed at Client Access Server Role. I should have posted here sooner been trying to work through this and have fixed most of the errors it reported except the ones below.
Last time I checked - yesterday , all services were operational server component states were active [I put it in maintenance mode when doing the upgrade]   Mail is coming in but can't access via owa or outlook.
Below is Error Log from last upgrade attempt , it references the owa calendar pool app, I recreated the owa virtual directories but no joy. I appreciate any help you can offer

.  Mailbox role: Client Access service                       FAILED
     The following error was generated when "$error.Clear();
          Update-OwaVirtualDirectory -DomainController $RoleDomainController;
          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
-AppPoolName:"MSExchangeOWAAppPool" -Version:"v4.0";
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
-AppPoolName:"MSExchangeOWACalendarAppPool" -Version:"v4.0";
        " was run: "Microsoft.Exchange.Data.InvalidObjectOperationException: Pro
perty DefaultDomain can't be set on this object because it requires the object t
o have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.
5.6500.0).
   at Microsoft.Exchange.Data.PropertyBag.set_Item(PropertyDefinition key, Objec
t value)
   at Microsoft.Exchange.Data.Directory.ADPropertyBag.set_Item(PropertyDefinitio
n key, Object value)
   at Microsoft.Exchange.Data.ConfigurableObject.set_Item(PropertyDefinition pro
pertyDefinition, Object value)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.WebAppVirtualDirect
oryHelper.UpdateFromMetabase(ExchangeWebAppVirtualDirectory webAppVirtualDirecto
ry)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.WebAppVirtualDirect
oryHelper.FindWebAppVirtualDirectoryInSameWebSite[T](ExchangeWebAppVirtualDirect
ory source, IConfigDataProvider dataProvider)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOwaVirtualDirect
ory.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fun
cName, Action func, Boolean terminatePipelineIfFailed)".


The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
Comment
Watch Question

Jason CrawfordTransport Ninja
CERTIFIED EXPERT

Commented:
Do you have any Exchange 2007 servers either in your environment or in AD?
Paul VanatskyIT systems Manager

Author

Commented:
I don't but thanks for replying. I actually ended up calling microsoft.. the call is going on 4 hours now .
Server engineer
CERTIFIED EXPERT
Commented:
As per the error: The object's current version is 0.0 (6.5.6500.0).

It looks like you have a lower version of exchange installed in your environment probably exchange 2003.

Remove the server uninstall or remove server container from adsiedit
Paul VanatskyIT systems Manager

Author

Commented:
Thanks ! had two exchange 2010 old servers in AD, the tech removed them.  He is still working on version numbering issue.
Paul VanatskyIT systems Manager

Author

Commented:
Thank you for the replies and 2003 remnants in AD turned out to be the issue.
Not sure why after running AD prep and schema prep moving from  2003-20010 and then to 20013.
This is the first time this issue has raised it's head. 5 hours later and it's fixed .