troubleshooting Question

Exchange 2013 Cu install fails at client server role install

Avatar of Paul Vanatsky
Paul VanatskyFlag for United States of America asked on
Microsoft OfficeExchangeOutlookMicrosoft 365Installation
5 Comments1 Solution130 ViewsLast Modified:
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.
   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
   at Microsoft.Exchange.Management.SystemConfigurationTasks.WebAppVirtualDirect
ory source, IConfigDataProvider dataProvider)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOwaVirtualDirect
   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.
Saif Shaikh
Server engineer

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 5 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros