D
dlanders1
Greetings,
I hope this is an appropriate place to pose this question (moderate away if needed)...
I am seeing an issue with IIS resets in Win2012 R2 after the July 2018 patches were installed in dev/test. If I issue an IIS reset either via inetmgr or command line, the w3wp.exe process is killed in Task Manager but the WWW publishing service stays in a stopping state. I haven't seen anyone mention this anywhere so I wanted to check with the community to see if I am the only one and if there are any thoughts on what the cause might be.
We found that rolling back the patches seems to fix the issue but not every server seems affected. Our Infra team found that recalling KB4338824 was enough to fix the issue on some servers but not all. I did also see that some folks reported issues installing KB4340558 but we did not have any problems with that. It's worth adding that one of our vendors informed us they had clients with similar issues but it doesn't appear app-specific as other systems experienced issues as well.
Here's what went in:
Other than the reset, we're not seeing any other odd behavior. Please let me know if anyone else is seeing this, or if there are ideas of what the cause may be. Of course if there is more info I can provide that would be helpful please let me know that as well and I'll do my best to accommodate. Thanks in advance!
Continue reading...
I hope this is an appropriate place to pose this question (moderate away if needed)...
I am seeing an issue with IIS resets in Win2012 R2 after the July 2018 patches were installed in dev/test. If I issue an IIS reset either via inetmgr or command line, the w3wp.exe process is killed in Task Manager but the WWW publishing service stays in a stopping state. I haven't seen anyone mention this anywhere so I wanted to check with the community to see if I am the only one and if there are any thoughts on what the cause might be.
We found that rolling back the patches seems to fix the issue but not every server seems affected. Our Infra team found that recalling KB4338824 was enough to fix the issue on some servers but not all. I did also see that some folks reported issues installing KB4340558 but we did not have any problems with that. It's worth adding that one of our vendors informed us they had clients with similar issues but it doesn't appear app-specific as other systems experienced issues as well.
Here's what went in:
Other than the reset, we're not seeing any other odd behavior. Please let me know if anyone else is seeing this, or if there are ideas of what the cause may be. Of course if there is more info I can provide that would be helpful please let me know that as well and I'll do my best to accommodate. Thanks in advance!
Continue reading...