Had the .NET Framework 3.0 SP1 update pop up yesterday, so I went ahead and installed it, there was no reboot required, so it seemed OK. However, about an hour later the Firewall service stopped. Looking in the event log there was an error saying something had crashed the w3filter.dll (I did have the 3 event log errors, but I copied them into a forum post yesterday, as I was going to ask this question then, but let the session timeout, and by then I'd cleared the eventlog).
I restarted the Firewall service, which took a few minutes, but it came back up, and web & vpn started working again. However, 5 - 10 minutes later, it stopped again. This time I gave the server a full reboot. When it came back up, it was all working OK, for about an hour, then the firewall service stopped again. This time I uninstalled the .NET Framework 3.0 SP1, and rebooted, since then, it hasn't crashed (touch wood).
Has anyone else had problems with the .NET 3 update? Why would it cause the Firewall service to hang/crash? Should I try the install again, or leave it off - another update appear this morning, only this is .NET 3.0 but no mention of SP1.
Let me ask you a best practice question... should one even install .net framework on the ISA server considering this server will ONLY run windows + the ISA 2006 software like it's suppose to? Why put additional software which needs patching when you don't have to right? I think Server 2003 comes with framework 1.1 installed by default so you can't take that out but why should you install the others?
i have a full featured deployment of an ISA2k6EE-Array here with two nodes which randomly experience exactly the same issues (after running rock-solid and not a single hickup for months under load).
The filters installed are Websense Enterprise 6.3.2 & Trendmicro WebProtect 5.01. But WP has been on there in this version from the beginning and the issues began before upgrading WS to latest 6.3.2. I experience this on both nodes but NONE before installing .NET 3.0 SP1.
There must be some kind of correlation to this ! I will go ahead to my ISA-Array-Lab to see if i can remove the .NET 3.0 SP1 cleanly and see if removing .NET 3.0 resolves the issue - If it does someone should infrom M$ of this issue.
@Tom - Does ISBPA5 (188.8.131.52) need .NET FW 3.0 ? I think only 2.0 is required ....
From: Redmond, WA
To answer several questions: 1. ISABPA only "requires" .NET Framework 1.1 it doesn't use any other version. 2. There are no dependencies betwween any ISA component and any version of the .NET framework. 3. if you have 3rd-party filters installed, you should remove them one-by-one ("disabling" a filter frequently doesn't; it's a filter design bug ) and see if the problem remains