Getting 503 server error

Question

I have published the cloud web application and upgraded build in windows Azure platform, browse .cspkg and .cscfg files and upgrade the old build with this new publish build.

publish build deployed successfully and showing ready to use.

But when i click on DNS link i got 503 server error.

 

can anybody help me on this issue.

 

Thanks in advance.

Answer 1

Hi Sayyed123,

Please check HTTP Error 503 - Service unavailable for a general explanation of this error. Mostly the cause is that the page has thrown an unhandled exception.

Have you enabled Azure Diagnostics and checked if there are any unexpected exceptions? Please make sure the Azure Storage connection strings are pointing to the real stroage account.

Thanks.

---

Wenchao Zeng
Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework

Answer 2

Sayyed123,

 

Whenever I experience a 503 error on an Azure site I find it helpful to test directly on the server.  You may have to edit the server’s host file so you get the properly DNS resolution to your site but that should give you a more accurate explanation of the issue.

 

- Bryan Soltis

Answer 3

Hi Sayyd,

 

Usually this error appears when there is an issue starting Application Pool. Either it's not started or during initializing the web application causes some issue so it's in dead.

1. Check if there is no service issues from Windows Azure for the zone you have selected: http://www.microsoft.com/windowsazure/support/status/servicedashboard.aspx
2. Check this blog have some solutions if you are facing similar issues: http://www.leggetter.co.uk/2009/08/28/windows-azure-503-service-unavailable.html
3. If you have enabled RDP to your Instance, Check Event Logs, it should have some information
4. During intialization of the web role, check the code if it's failing to init (that might be your database connection or Storage services or anything else)
5. Enable diagnostics and gather IIS logs to see the error details.

Let me know your findings or if you need further help.

 

---

Mahesh Devjibhai Dhola [Please mark best and acceptable replie(s) as the ANSWER(S)]