When I attempt to update the code on a IIS webserver by replacing the old code with my new code, I receive 503 Service Unavailable replys when attempting to access any of the replaced pages on the server. What is the cause of this failure and what steps can I take to correct such errors? Thanks.
A:
Could be lots of things. Did you try iisreset after updating the pages?
Eugene Katz
2008-10-07 12:57:14
A:
I agree with Eugene. It could be lots of things. If you publish locally, can your local IIS run the pages?
wcm
2008-10-07 13:00:06
A:
Sorry, I'm aware that I am supposed to amend my post to answer the questions that are asked, but I cannot seem to figure out how to do so.
I did have the server reset. The deployment procedure was to publish to a separate directory on the server, delete the old code except web.config and then copy in the new code (except web.config).
I can access files on the server that are in non-virtual folders. Also, global.aspx runs when the server is restarted.
Re: amending the post. The edit link should show up when you mouse over the question. Beware that too much editing will put your question in Community mode. You can also use comments, like I'm doing here.
Eugene Katz
2008-10-07 13:12:25
I do not get an edit link (only offensive and comment links), maybe because I'm not using OpenID authentication? I also can't use comments because I don't have the required 50 reputation points. Sorry.
2008-10-07 13:16:10
have you checked the windows event logs? Also, what version of IIS?
Eugene Katz
2008-10-07 13:19:47
check IIS logs as well. Usually in %windir%\System32\LogFiles
Eugene Katz
2008-10-07 13:22:09
I don't have access to the server itself. I only have write access to the wwwroot directory. The deployment server is using IIS/6.0. My development machine has IIS/5.1.
2008-10-07 13:28:05
+1
A:
I would do a few things:
Check the windows event logs for any web related errors.
Check the IIS logs to see if there is anything odd with the requests.
Double check the permissions of all the new files, make sure they match the files that do work.
Perform an IISReset after you deployed.
Make sure your virtual directory, or sub folders are set up correctly in IIS and didn't change in the deployment.
AaronS
2008-10-07 13:26:51
A:
Re this answer, I seem to remember having a problem like this, and it turned out that it was because I was updating the files via ftp, and the there was some conflict between the rights of the FTP user and the IIS user.
Benjol
2008-10-07 13:35:27
A:
You probably need to get together with whomever has access to the server to look at the errors. Short of that, can you try putting the old code back to see if it still works? If not, it's likely a configuration error.
Also, editing the web.config will get the application restarted. It's a useful trick when you can't access IIS.
Eugene Katz
2008-10-07 13:36:05
A:
If the associated ApplicationPool is disabled you also get the 'Service Unavailable' exception. (can be seen in the logs)
bob
2009-09-14 07:08:52