• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1709
  • Last Modified:

ISA 2004 Problems Under Windows Server 2003 - Please Help!

Okay, here's my situation.  We are running ISA Server 2004 under Windows Server 2003.  A while back, we installed the trial version of ISA 2004, and it worked with absolutely no problems.  We then uninstalled the trial, and ran only a hardware firewall for a couple weeks.  Now, I have installed the full, retail version of ISA 2004 on that same server, and am getting numerous errors.  They are as follows:

1.  The biggest one is that any time I make a change to the firewall policy, and click "Apply," I get the following error: "The configuration changes were saved to storage, but at least one service failed to load these changes.  The event log may include additional information on possible reasons for failure."  When that happens, the only way to apply changes to the firewall policy is to manually restart the Firewall service.

2.  In the "Monitoring" section, when I click on the "Logging" tab and try to click "Start Query," I get the error "The query stopped because an error occurred while it was running."  The same error occurs when I open up the "Sessions" tab and click "Start Monitoring Sessions."

3.  In the Sessions section of the Dashboard, I get a red Circle-X (like when a device is disabled in Device Manager), followed by "????" in the "Number of Sessions" column for Firewall Client and Web Proxy.

4.  In the "Services" tab, I get the same red Circle-X and "????" in the "Service Uptime" column for the Microsoft Firewall.

All of this sounds like some sort of permissions error, like ISA is unable to read/modify information related to the Microsoft Firewall service.  If anyone has any advice on how to fix this, I would be most appreciative.
1 Solution
I would suggest you to re-install W2003 and then re-install ISA Server. Probably you can try to un-install ISA, install Service Pack 1 for Windows 2003 and then install ISA again, but the best case will be installation from the scratch. ISA server is very delicate tool which is causing such problems sometimes ...
CadefassettAuthor Commented:
I just solved my own problem.  All I had to do was change the logon for the "Microsoft Firewall" service from NT AUTHORITY\NetworkService to logon as the Local System Account instead.  Now, all of my problems have disappeared.

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now