Yesterday, our branch office ISA server (HP Proliant) crashed when installing SP3. After that, it was necessary to use the "repair" option in ISA setup to get it up and running again (without SP3).
The errors in the app. log are: Event ID: 14056 The application filter (DNS Filter, CLSID={49FE2B2F-3BB4-495C-87C8-3890C3C35756}) performed an illegal operation inside the Firewall service process at method FilterInit. The Firewall service terminated. To resolve this error, remove recently installed application filters and restart the service. If this does not resolve the problem, contact the component vendor.
You might want to hold off on installing SP3 until they work the bugs out of the installer. Most people are getting it to install just fine, but if yours isn't installing, wait a couple of days for the fix.
Thanks for the tip. Seems worth to try. The only thing it bothers me is that ISA management console was not open. ISA SP3 update happend at 4am in the morning with auto Windows update. No one was logged on at the console and none RDP connections were open.
I will try it anyway and let you know how it went. (I will have to drive again all the way to the remote office... Oh well.)
My SP3 problem is different than everybody elses. I installed over a remote desktop session because this ISA server is in the Bahamas. (I'm in Houston) Upon reboot, I can no longer make a remote desktop connection. However, the server is up and running fine. (it appears) I had someone locally log onto the console and verify that RDP was enabled for management. It appeared that nothing was changed in the configuration by the SP3 install.
Got any clues? Maybe I'll have to go to paradise to figure it out? :)
realize my help there in Nassau is simply someone I asked to log onto the console and has no idea what he is looking at.
But yes, I painfully walked him through creating a real time monitor and had him watch for me and call out any records using port 3389. He did see them and they were not being denied. They were simply listed as "initiated connection" and then immediately followed by "closed connection"
And on my client side I got the same error you get when a Terminal Server is not available.
If I have him log in again, should I have him just install SP2 over it? Or any better suggestion? Cheers
Is the ISA Firewall configured to accept remote access VPN client connections? In that way, you might be able to figure it out for yourself. You might need to have your assistant create a rule that allows VPN clients access to the local host network, though.
Well, I had the fellow in Nassau log in locally and reapply SP2 for me. Immediately I could RDP back in. (big sigh of relief). I then logged out and had HIM reaaply SP3 from the console. When he stated it was finished, I was able to RDP in as well!
So I guess my advice is don't install SP3 over an RDP session. The RDP session is interupted during the SP install anyway. So it isn't a gracefull way of going about it in the first place.
Thanks for your assistance. I'm a happy ISA boy again. Even if I don't get to take a Lear down to Paradise for emergency repairs! :)
Intially, I had exactly the same errors as Henoh in the event log following the installation of SP 3 - it was a manual installation from the server console, and no one had an RDP session to the server, so the management console wasn't open.
Anyway, the fix from ISA Server Product Team Blog worked, but following the succesfull installation of SP 3, I now have the same problem as Snakebit - I'm unable to establish an RDP session.
I haven't tried to apply SP 2 and then SP 3 again - after all the server now works, and since my server is not in the Bahamas, it's not a major issue.
But certainly MS should work on the installation routine of SP 3.
Well, I had the fellow in Nassau log in locally and reapply SP2 for me. Immediately I could RDP back in. (big sigh of relief). I then logged out and had HIM reaaply SP3 from the console. When he stated it was finished, I was able to RDP in as well!
So I guess my advice is don't install SP3 over an RDP session. The RDP session is interupted during the SP install anyway. So it isn't a gracefull way of going about it in the first place.
Thanks for your assistance. I'm a happy ISA boy again. Even if I don't get to take a Lear down to Paradise for emergency repairs! :)
Hi Snake,
Good to hear you got everything working and that you didn't have to travel to paradise to fix it :)
Intially, I had exactly the same errors as Henoh in the event log following the installation of SP 3 - it was a manual installation from the server console, and no one had an RDP session to the server, so the management console wasn't open.
Anyway, the fix from ISA Server Product Team Blog worked, but following the succesfull installation of SP 3, I now have the same problem as Snakebit - I'm unable to establish an RDP session.
I haven't tried to apply SP 2 and then SP 3 again - after all the server now works, and since my server is not in the Bahamas, it's not a major issue.
But certainly MS should work on the installation routine of SP 3.
Good to hea r you got it working! The RDP is still a bit of a mystery to me, since once I actually got SP3 installed and working, RDP wasn't a problem.
I am also having a problem installing SP3 on an ISA 2004 EE server. I did download the proper Service pack, I triple checked that . Everytime I install the sp it will fail and then the Firewall service fails to start. Only way to get it working again is reinstall SP2. I tried all the suggestions offered by Jim Harrison and still the same problem. I do not have any Management Console open, I make it a point to reboot the server before any kind of updating.
Here is an excerpt from my log file of the install. If anyone would like the entire log file, I can email it upon request. Hopefully one of the many experts here can help get this service pack installed.
MSI (c) (28:9C) [18:54:08:473]: Product: Microsoft ISA Server 2004 - Update 'Microsoft ISA Server 2004 Service Pack 3' could not be installed. Error code 1603. Additional information is available in the log file c:\sp3.log.