Jim Jones
asked on
Exchange OWA issues following migration
We are having an issue with Exchange following a SBS > 2016 rollout. With the OWA virtual directory ECP is working fine, mobiles are working fine but if you run /owa you are prompted to login but as soon as you click login you get a 500 error and the URL has redirected you to https://server-exch01.xxx.local:444/owa/auth/logon.aspx?url=https://server-exch01.xxx.local:444/owa/&reason=0 (this is internally and externally). Both addresses are actually set to https://remote.xxx.com
We have tried rebuilding virtual directories, updating addresses, applying updates, etc with no luck. Can someone point us in the right direction?
We have tried rebuilding virtual directories, updating addresses, applying updates, etc with no luck. Can someone point us in the right direction?
ASKER
Hi Valentina,
Thanks - exactly the same issue using localhost as the hostname.
Jim
Thanks - exactly the same issue using localhost as the hostname.
Jim
Hi Jim,
it is working in SBS?
You have the same behaviour with user in Exchange 2016 and SBS?
Regards
Valentina
it is working in SBS?
You have the same behaviour with user in Exchange 2016 and SBS?
Regards
Valentina
ASKER
Hi Valentina,
The SBS has had Exchange removed as it is now fully on the new box. The redirected URL is the new server name.
Thanks,
Jim
The SBS has had Exchange removed as it is now fully on the new box. The redirected URL is the new server name.
Thanks,
Jim
Hi Jim,
Please check that all the exchange services are running:
Test-ServiceHealth
Make sure that the Microsoft Exchange Forms Based Authentication service is started.
Regards
Valentina
Please check that all the exchange services are running:
Test-ServiceHealth
Make sure that the Microsoft Exchange Forms Based Authentication service is started.
Regards
Valentina
ASKER
Hi Valentina,
Test-ServiceHealth shows everything as fine.
Any other ideas?
Thanks,
Jim
Test-ServiceHealth shows everything as fine.
Any other ideas?
Thanks,
Jim
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Valentina,
Server has been rebooted on a number of occasions.
Version 15.1 (Build 1261.35) currently installed and running
Thanks,
Jim
Server has been rebooted on a number of occasions.
Version 15.1 (Build 1261.35) currently installed and running
Thanks,
Jim
HI Jim,
Please check the following command:
Get-OwaVirtualDirectory | FL Identity,*url*,*auth*
You need to be sure that basic authentication is true and forms authentications too.
Regards
Valentina
Please check the following command:
Get-OwaVirtualDirectory | FL Identity,*url*,*auth*
You need to be sure that basic authentication is true and forms authentications too.
Regards
Valentina
ASKER
Hi Valentina,
OWA Url addresses are correct, Basic and Forms authentication on
Thanks,
Jim
OWA Url addresses are correct, Basic and Forms authentication on
Thanks,
Jim
ASKER
Hi Valentina,
We applied the latest CU last night and that appears to have fixed it. In the notes there was a mention of OWA issues and this must have been one of them.
Thanks for the help.
Jim
We applied the latest CU last night and that appears to have fixed it. In the notes there was a mention of OWA issues and this must have been one of them.
Thanks for the help.
Jim
Do you have the same issue if you try the following url:
https://localhost/owa
Check that you do not have redirection in OWA.
Regards
Valentina