Quantcast
Channel: Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients forum
Viewing all articles
Browse latest Browse all 10580

ECP and OWA Unable to access after CU10 Upgrade

$
0
0

Hi All,

I search for answers on the web but unluckily, the issue still not resolve,

- I have a working environment in our lab, it has an existing Active Directory with Windows 2008 R2 domain/forest functional level,

I successfully deployed the Mailbox/CAS using Exchange 2013 SP1 with out any CU, we need to perform an upgrade to CU10 due to compliance although this is a lab environment, it will use for all users in our organization for some reasons.

So during the CU10 Upgrade, I experience a lot of errors and cannot resolve it, but after starting from the scratch again, remove the Exchange data/components in active directory and create a new vm,I use the Installer of CU10 to deploy exchange 2013 now, and some errors occur during the installation however, I manage to resolve it. 

Now the exchange version is CU10 upgraded, I can access Exchange powershell and toolbox, though I can access the ECP ONLY using "https://localhost/ecp" and can configure settings here, but using "https://hostname.domain.lab/ecp" it redirects to owa authentication(I don'tconfugre http redirection in IIS), same in OWA.

The landing page for authentication can bring up but after logging in it say's:

Message: something went wrong, Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.

URL:https://hostname.domain.lab/owa/auth/errorFE.aspx?httpCode=500

-Verified FAB is working, MS Exchange Services are all running

Note: during Exchange 2013 SP1 no CU installed, all are working well without any errors. after upgrading it to CU10 which AD schema also upgraded, I cannot revert it to "Exchange 2013 SP1 no CU installed" that has fully operational.

Please help someone there, this is a real pain.


Viewing all articles
Browse latest Browse all 10580

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>