The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.
HTTP 503 for OWA/ECP with the server otherwise reachable usually indicates that the Exchange web application on IIS is failing, not a basic network/DNS issue.
Based on the provided context, there are two Exchange-side issues and resolutions to check first:
- If this started after installing a security update
- Use elevated permissions to reinstall the security update on the server:
- Select Start, type
cmd. - Right‑click Command Prompt → Run as administrator.
- In the elevated window, run the
.mspfile for the Exchange security update (full path) and press Enter. - After the update completes, restart the server.
- Test OWA and ECP again.
- Select Start, type
- If the error persists:
- Open IIS Manager.
- Go to Exchange Back End website → ECP virtual directory.
- Open Application Settings → BinsearchFolder.
- Ensure the paths are the actual Exchange install paths, for example:
-
C:\Program Files\Microsoft\Exchange Server\V15\bin; C:\Program Files\Microsoft\Exchange Server\V15\bin\CmdletExtensionAgents; C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\bin(adjust drive/version if different in the environment).
-
- Open an elevated Exchange Management Shell in
C:\Program Files\Microsoft\Exchange Server\V15\Binand run:-
./UpdateCas.ps1 -
./UpdateConfigFiles.ps1
-
- Open an elevated Command Prompt and run
iisreset. - Restart the server and test OWA/ECP again.
- Use elevated permissions to reinstall the security update on the server:
- If this is Exchange 2013 and you see OWA/ECP failures with server‑side errors
- Install Exchange Server 2013 Cumulative Update 11 or later on the server. This update:
- Fixes a known issue where OWA/ECP requests fail due to a GUID mismatch stored in cookies vs. Active Directory.
- Enables periodic recycling of the OWA/ECP app pools (every 14 days) to prevent recurrence.
- Do not disable this recycle or extend it beyond 28 days, or the issue may return.
- Install Exchange Server 2013 Cumulative Update 11 or later on the server. This update:
If the environment is Exchange 2019 and the 503 appears specifically during client‑side search via EWS (for example, Outlook search returning “We’re having trouble fetching results from server”), this is a known CU13 issue; use Outlook in Online mode or OWA search as a workaround and then follow the server‑side steps in the referenced article.
References: