Wednesday, April 06, 2005 12:34 PM szurgot

Windows 2003 Service Pack 1 Gripe (also applies to .NET installs)

I installed Service Pack 1 on my test computer, then installed it live a day later. Everything worked fine, except I have one gripe. (This also applies to .NET upgrades) On two of the machines, I had the ASP.NET State Server running. On both of those machines, it was off after the upgrade, and set to manual, so I had to go in and reset it. I'm all for having things off by default, but if a service is on, it should stay on. The same thing happens with the .NET upgrades (1.1 and 2.0) They should also detect the state of ASP.NET state, and maintain it.

Otherwise, no problems! <grin>

Comments

# Is Windows getting too secure ?

Wednesday, April 06, 2005 4:07 PM by TrackBack

Is Windows getting too secure ?

# re: Windows 2003 Service Pack 1 Gripe (also applies to .NET installs)

Wednesday, April 06, 2005 8:59 PM by David Taylor

Yes....That happened for me as well.

I first installed on 3 less important machines (that did not use the State Service). Then finally did a remote RDP install to a production machine (which always scares me).

So when the box came back online the only two problems were:
a) State Server was off.
b) A problem with Windows Services for Unix caused one of it's processes to crash (note we were not even using Windows Services for Unix...so this was not an issue).

I read that b) can be solved just by uninstalling and reinstalling the latest version. And a) was easy to manually start, but frustrating.

BTW I did panic when it first happened because I was hitting the web app remotely, where the actual error did not return show (web.config errors not showing remotely)...so I thought "UH OH"....

Anyway...The whole upgrade was done remotely from start to end in under 30 minutes, including the reboot...so overall very high marks to MS for the upgrade.