Last post Mar 10, 2021 09:08 AM by Sean Fang
Mar 09, 2021 07:43 AM|CopBlaster|LINK
I just exported a server package from my old IIS server and imported it to new one using Web Deploy 3.6, but all websites on the new one always say 503 Service Unavailable. I made sure that the IIS user on the new server has full control of the inetpub/wwwroot
directory but there is no change. This happens with every app pool including the default one.
I noticed a thread on another website by someone saying that their new server did not have all the same modules installed as the old one. Is it true that the importing the package does not import modules?
Mar 09, 2021 09:02 AM|CopBlaster|LINK
I checked Web Platform installer and found out that the URL Rewrite module and others were not included when I imported the package. I tried installing URL Rewrite but the problem is still there. Why doesn't the export actually export everything?
Mar 10, 2021 09:08 AM|Sean Fang|LINK
The 503 response from the IIS machine, Service Unavailable, is the result of repeated application crashes. Since the w3wp.exe worker process, created by IIS to execute a web application, is crashing frequently, the respective IIS application pool
is turned off. So you can check if the status of your application pool is started.
If the application pool is started, then you need to troubleshoot. 503 should be coming from http.sys you need to check in HTTP err logs for the exact reason. you can find HTTP err log files here, C:\Windows\System32\LogFiles\HTTPERR Search for the site
you are trying to browse in the logs and the last but one field will give you reason.
And you can also find the evidence of repeated w3wp.exe crashes and Rapid-Fail Protection
in Windows Events, in the System log with Source=WAS.