IIS 7 and Above
503 when publishing my asp.net mvc application
Last post Oct 16, 2018 01:18 AM by Terry Peng
Oct 09, 2018 06:22 AM|b.dev|LINK
When I publish my ASP.NET MVC application from visual studio to IIS, using Web Deploy, during the deployment, my app throws 503 service unavailable and it keeps throwing the error after one minute the publish finishes.
I have checked the windows event logs and there were not any error at all.
Oct 10, 2018 09:58 AM|Terry Peng|LINK
According to my experience, I could easily to reproduce the issue while the site's application pool is stopped. So I would suggest you check if your application pool stopped now. You could try to change/create another application pool for your site.
Besides, as far as I know, 503 error are usually reported in the http.sys error logs. The log file is "%Systemroot%\System32\LogFiles\HTTPERR\httperr1.log". You could check the s-reason field for more information. For instance, if I manually closed the application
pool, the s-reason is "Disabled". What's your s-reason?
Oct 10, 2018 01:08 PM|b.dev|LINK
I just checked the http.sys logs and found these reasons, are the most common reasons of failure :
Oct 11, 2018 05:24 AM|Terry Peng|LINK
All http.sys error will be record in the log file. As far as I know, these s-reason are not for 503 error.
Please backup the log files, clear your original log data. Then try to connect your application and check the new generated log data while you got error.
These newly generated log data are for your 503 error message. You could also get the 503 state code in the log record.
2018-10-10 01:19:56 ::1%0 50056 ::1%0 804 HTTP/1.1 GET / 503 20 Disabled DefaultAppPool
Please share us the s-reason for these log data.
Besides, have you checked if changing application pool could work for you?
Oct 13, 2018 12:03 PM|b.dev|LINK
I opened a httperr5 log file and found that there is no column related to http status. All the fields that my log file has, are as below:
#Fields: date time c-ip c-port s-ip s-port cs-version cs-method cs-uri sc-status s-siteid s-reason s-queuename
Oct 16, 2018 01:18 AM|Terry Peng|LINK
sc-status is indeed the http status, you could try to connect the site and check the newly generated log data.
Besides, have you checked the statue of your application pool while the error happen?