Change HTTP/1.1 503 Service Unavailable error on Front-end

Posted on 2008-02-08
Medium Priority
Last Modified: 2010-04-21
My Front-End Exchange server never really goes down (it doesn't do anything that would make it), however, occasionally my back-end will go down (patches, hardware issues etc).  Although it doesn't happen often, it is inevitable that when it happens, I get the barrage of "did you know that email is down" calls.  Primarily, my concern is that when people go to OWA & login, they get re-directed to the HTTP/1.1 503 Service Unavailable error page, which means that FE cannot communicate with the BE.  I would like to replace the 503 error page with a custom generated HTM page that has a hyperlink to my IT Systems Status webpage.  That way everyone will have the ability to click on the link & see if email is down, if it isn't reported, to report it.

I looked on my FE box & found that the custom errors section doesn't have 503 listed...is that on the back-end Exchange that it is coming from?  Or how can I change this?

Hopefully this makes sense.  I am on Exchange/Windows 2003.

Question by:rustyrpage
  • 2
LVL 25

Accepted Solution

kieran_b earned 2000 total points
ID: 20856405
Last time I tried to do this (for exactly the same reasons you are) I came to the conclusion that it is not changeable.


Point 3.


Author Closing Comment

ID: 31429240
That link didn't work...?

That's annoying then huh?  I guess Microsoft wants us to get as many calls as possible as administrators =)
LVL 25

Expert Comment

ID: 20868645
The link is working for me; the key point is this;

3. In the Error messages for HTTP errors list, click the HTTP error that you want to change, and then click Edit.

  Note     The following errors are not customizable: 400, 403.9, 411, 414, 500, 500.11, 500.14, 500.15, 501, 503, and 505.

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes Top 9 Exchange troubleshooting utilities that every Exchange Administrator should know. Most of the utilities are available free of cost. List of tools that I am going to explain in this article are:   Microsoft Remote Con…
Here is a method which can be used to help resolve a "Content Index Failed" error on a Microsoft Exchange Server.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

601 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question