Hi,

 I have a frustrating issue on EXCH 2013 SP1 CU7. Outlook clients work fine but logging onto OWA or ECP does not. When trying to logon to OWA we get infinite "still working on it" , ECP just blinks and we get logon screeen again. We cannot logon - independently on browser used. Problem is that there are NO errors in application nor in system log. We had also checked the IIS logs, and again, no errors(mostly OK 200 messages from clients connecting from outlook)

 Got this problem before CU7, hoping the update will resolve it but its the same. Tried to recreate OWA nad ECP virtual directories multiple times but no change. Everything is in default dirs.

Exchange connectivity test, autodiscover is OK.

Also have to point out that Frontend and Backend are using valid certificates(cert with public name for front end and selfsigned for backend)

Auth for Backend (OWA and ECP) are anon and integrated(when i disable anaon, nothing changes), for Frontend - Basic for OWA and ECP is enabled - i.e. its in default state

It worked till about 3 weeks ago...

 Can you help, please? Should I reinstall Exchange or its some bug? T

Hi fandango71,

Thank you for your question.

Did the issue occur all users?

Did you use different browser to check if the issue persist?

Is there former version Exchange server existed in organization?

We could enable Windows Authentication on OWA and restart IIS to check if the issue persist.

We suggest you post snapshot when you logon OWA for our troubleshooting.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Hi,

 it occur to all users.

 When going from server itself i got what its in screenshot, when going from outside or inside client the screen just blanks and present logon screen again, no matter what browser I am using.

 No former Exchange.

 Windows auth on Font End(its already enabled on Back End)?

Please note that all clients Outlook(they are using Exchange connection, not IMAP or POP), mobile,... have no issues at all. They are connecting from inside and also from outside.

Tried to add/change auth on Front End but no channge.

Pete

 

Hi fan,

Run the following command on Exchange 2013 to check if there are any components is inactive:

Get-ServerComponentState "servername"

Then we could run the following command to active it:

Set-ServerComponentState  "<servername>" -Component <ComponentName> -Requester Functional -State Active

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Hi, 

 thanks for answer. There were 2 components inactive:

ForwardSyncDaemon

ProvisioningRps

I activated them but nothing changed.

During the time I had also reinstalled whole Exchange(also with IIS and process activation, manually deleted any residual files, pruned AD and registry) successfully from latest medium (CU8), Exchange is running with no apparent errors but the problem still persists...

Pete

Hi fandango,

We could disable A/V software on Exchange and logon OWA on Exchange server directly to check if the issue persist.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim