IIS 7 and Above
Cannot start IIS after update to Windows 1903
Last post Sep 11, 2019 09:30 AM by Yuk Ding
Sep 08, 2019 12:15 AM|Sbotan|LINK
ISS stopped working after updating to Windows 1903. Possible reason is that Windows Application Process Service is not running. When try to start I get an error msg: Error 15: The system cannot find the drive specified. Tried to copy the file 'applicationHost.config'
in the folder C:\windows\system32\inetsrv\config and saved it as 'applicationHost.config.tmp. This trick worked on Windows 1803, but not this time.
Sep 09, 2019 03:10 AM|Yuk Ding|LINK
It looks like some files get corrupted. It seems to be an 1903 issue more then IIS issue.
1.Please download and run process monitor https://docs.microsoft.com/zh-cn/sysinternals/downloads/procmon.
2.Then try to restart WAS to reproduce the problem.
3. Check whether any file not found error was detected.
4. If step 3 not working, please compare all files logged in process monitor log with a working server. You only have to compare the file size to check whether any file has been corrupted.
5.If you find the corrupted file, please try to copy the file from a working server.
If you need Microsoft help you fix this problem, you could open a support ticket here:
Of course, rebuild OS would be the fastest way to fix this problem.
Sep 11, 2019 01:35 AM|Sbotan|LINK
Thank you for your reply, I really appreciate it. Unfortunately, I cannot completely understand what Procmon shows. There were couple of items where it says "PATH not found", but when I tried to find the same path on a working computer, it just does not
exist there. Other records were weird, such as below:
9:27:38.0614187 PM svchost.exe 1192 QueryDirectory C:\Windows\Registration\R????????????.clb SUCCESS Filter: R????????????.clb, 1: R000000000001.clb.
Not quite understand what it means.
Sep 11, 2019 09:30 AM|Yuk Ding|LINK
I think there must be some file get corrupted after the update.
Have you tried the command sfc /scannow?
You could check what is the last read file before the system start write error event to event viewer and check whether this file has been corrupted. I was hoping to help you check the log but it is very limited for me in forum.
Since this issue is mainly caused by windows update. It is very hard to find the root cause from IIS side.
Do you have backup before the update? I think rollback the backup or rebuild the whole system would be the fastest way to fix this.