Windows 10 update breaks IIS
-
Has anyone else experienced this? My IIS 10 server has been functioning fine for several months. Today I get [HttpException (0x80004005): Could not load type '%Windir%\System32\inetsrv\compdyn.dll'.] on every single page that uses ASP.Net. My only guess is that an automatic Win 10 update has changed something but what? Bah!!! I may not last forever but the mess I leave behind certainly will.
-
Has anyone else experienced this? My IIS 10 server has been functioning fine for several months. Today I get [HttpException (0x80004005): Could not load type '%Windir%\System32\inetsrv\compdyn.dll'.] on every single page that uses ASP.Net. My only guess is that an automatic Win 10 update has changed something but what? Bah!!! I may not last forever but the mess I leave behind certainly will.
-
Has anyone else experienced this? My IIS 10 server has been functioning fine for several months. Today I get [HttpException (0x80004005): Could not load type '%Windir%\System32\inetsrv\compdyn.dll'.] on every single page that uses ASP.Net. My only guess is that an automatic Win 10 update has changed something but what? Bah!!! I may not last forever but the mess I leave behind certainly will.
I've not seen that one, but I don't use dynamic compression locally. Turning off dynamic compression should get you back up and working for now. You might need to uninstall/reinstall the feature to get it working again.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I've not seen that one, but I don't use dynamic compression locally. Turning off dynamic compression should get you back up and working for now. You might need to uninstall/reinstall the feature to get it working again.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Thanks. I'll give that a try. Still don't know why this just stopped working. We are philosophical about power outages here. A.C. come, A.C. Go. I may not last forever but the mess I leave behind certainly will.
-
I've not seen that one, but I don't use dynamic compression locally. Turning off dynamic compression should get you back up and working for now. You might need to uninstall/reinstall the feature to get it working again.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Richard Deeming wrote:
You might need to uninstall/reinstall the feature windows 10 to get it working again.
New keyboard? That was a Hell of a typo.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Richard Deeming wrote:
You might need to uninstall/reinstall the feature windows 10 to get it working again.
New keyboard? That was a Hell of a typo.
I wanna be a eunuchs developer! Pass me a bread knife!
Oh so tempting... Manged to recover by rolling back to an earlier restore point. Still no idea what caused it though. We are philosophical about power outages here. A.C. come, A.C. go.
-
I've not seen that one, but I don't use dynamic compression locally. Turning off dynamic compression should get you back up and working for now. You might need to uninstall/reinstall the feature to get it working again.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
An update for anyone who is interested. I managed to replicate this issue by turning on dynamic compression. It worked fine until the machine was rebooted and then the same symptoms were presented. Turning dynamic compression off didn't help and uninstalling it didn't do any good. Once again I had to restore to an earlier point. Now I have no idea if dynamic compression was somehow turned on to cause this. I never use it and as far as I was aware it had not been installed. Looking at the config history only showed static compression enabled and dynamic compression disabled. Similarly no clues in the event viewer logs. No IIS logging was enabled. My bad. I suspect this may have been a permissions issue. The offending dll having been locked for some reason. Meanwhile, it aint broke and I'm not going to fix it until it is. Thanks for your help with this. I may not last forever but the mess I leave behind certainly will.
