Anyone else having issues with ASP.Net on Server 2K3 after the latest MS security update?
-
I woke up this morning to a freshly rebooted server thanks to an MS update, and all of the sudden xcopy deploying updates to any asp.net application (website or web service) results in *every* asp.net web application reporting a compile error. I tried editing the web.config (i.e. insert or delete some whitespace) in order to get asp.net to recompile/recache, but that only works 1/10 times. Deleting the entire asp.net cache doesn't even work. The only workaround I've found so far is a complete server reboot, which is, well, crap. Anyone else experiencing this, or is it just our server that's gone all whacky today?
-
I woke up this morning to a freshly rebooted server thanks to an MS update, and all of the sudden xcopy deploying updates to any asp.net application (website or web service) results in *every* asp.net web application reporting a compile error. I tried editing the web.config (i.e. insert or delete some whitespace) in order to get asp.net to recompile/recache, but that only works 1/10 times. Deleting the entire asp.net cache doesn't even work. The only workaround I've found so far is a complete server reboot, which is, well, crap. Anyone else experiencing this, or is it just our server that's gone all whacky today?
Haven't had the problems. But a faster way than a server restart is to stop the application pool for erroneous app and delete the dotnet cache for the app and start the application pool again. Personally I'm finding also this to be to much fuzz, so if someone else is having a better method I'm all ears
-
Haven't had the problems. But a faster way than a server restart is to stop the application pool for erroneous app and delete the dotnet cache for the app and start the application pool again. Personally I'm finding also this to be to much fuzz, so if someone else is having a better method I'm all ears
Well, it's not just us.. I got a skype call from an old sysad friend of mine who's got the exact same problem happening on 3 different continents since the last Server 2K3R2 update. In his case, installing and re-installing the .net runtimes fixed the issues he had, but this unfortunately doesn't work for us. He is running asp.net code on netfx v1.1, v2.0, v3.0 and v3.5, whereas *all* of our code is compiled against netfx v3.5 (i.e. 2.0 + extensions), so not the same config. However, we are now able to restore working service without rebooting by using NET STOP IISADMIN /Y followed by NET START W3SVC to force IIS to start over. I feel like I've just been time-warped 10 years into the past to the days of classic ASP and COM, *ugh* This still means the every website, web service and the ftp service have to be killed any time we want to make even the most *minor* change to any of our hosted apps (which is crap), but at least we're not going down for 2-3 minutes, and DNS and mail can continue to function throughout it all. Not a resolution, but at least a sloightly better work-around for us.