Exchange 2013 CU15 update fails on step 15 of 17.

Running Exchange 2013 Ent SP1 on server 2012R2 Datacenter.  When I try and do the Exchange2013-x64-cu15 update it fails on step 15. with the error below.  The only odd part about or install is ECP and OWA are a different website and IP in IIS.

The following error was generated when "$error.Clear();
          $FEOWAVdirIdentity = $RoleNetBIOSName + "\OWA (Default Web Site)";
          $FEOWAVdir = get-OwaVirtualDirectory -Identity $FEOWAVdirIdentity -DomainController $RoleDomainController;

          if ($FEOWAVdir -ne $null)
            Set-OwaVirtualDirectory -Identity $FEOWAVdir.Identity -ExternalUrl $FEOWAVdir.ExternalUrl -InternalUrl $FEOWAVdir.InternalUrl -ExternalAuthenticationMethods $FEOWAVdir.ExternalAuthenticationMethods -BasicAuthentication ([Convert]::ToBoolean($FEOWAVdir.BasicAuthentication)) -WindowsAuthentication ([Convert]::ToBoolean($FEOWAVdir.WindowsAuthentication)) -DigestAuthentication ([Convert]::ToBoolean($FEOWAVdir.DigestAuthentication)) -FormsAuthentication ([Convert]::ToBoolean($FEOWAVdir.FormsAuthentication)) -LiveIdAuthentication ([Convert]::ToBoolean($FEOWAVdir.LiveIdAuthentication)) -OAuthAuthentication ([Convert]::ToBoolean($FEOWAVdir.OAuthAuthentication)) -AdfsAuthentication ([Convert]::ToBoolean($FEOWAVdir.AdfsAuthentication));
        " was run: "Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'SDL02-VM72\OWA (Default Web Site)' couldn't be found on ''.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.GetObjectWithIdentityTaskBase`2.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Cordell EmbryAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Tom CieslikIT EngineerCommented:
The operation couldn't be performed because object 'SDL02-VM72\OWA (Default Web Site)' couldn't be found on ''.

It looks like you have some issue with your DNS settings for OWA.
You can create new forward lookup zone in your DNS with your External Exchange Name for example and create A record pointing to your internal Exchange IP address.

Refresh DNS and try again.
Cordell EmbryAuthor Commented:
My other exchange server that has the default websites with no changes installed the update with no issues......
Tom CieslikIT EngineerCommented:
All servers is resolving DNS and IIS settings separately.
If you sure there is no problem in DNS check your IIS setting on affected server and compare it with IIS on server that's working OK

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Tom CieslikIT EngineerCommented:
Best solution provided. No more other questions from author
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.