mtxit
asked on
ISA Server & Web Proxy errors
Hi, I'm gettin the following errors when trying to start ISA Service "The Microsoft ISA Server Control service terminated with service-specific error 278540 (0x4400C)" Event ID 7024. Source - Service control manager
I also can't start the Web Proxy service. Error 1068 The dependency or service group failed to start.
Event - The Microsoft Web Proxy service depends on the Microsoft ISA Server Control service which failed to start because of the following error:
The service has returned a service-specific error code. Event id - 7001.
any suggestions most welcome.
I also can't start the Web Proxy service. Error 1068 The dependency or service group failed to start.
Event - The Microsoft Web Proxy service depends on the Microsoft ISA Server Control service which failed to start because of the following error:
The service has returned a service-specific error code. Event id - 7001.
any suggestions most welcome.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have this same problem happening on a very new installation of SBS 2003 Premium R2 that's been upgraded to SQL 2005. Taking this advice:
"Also remember the most important thing for ISA is the ability to write to a log file. If for ANY reason ISA cannot write to the log files then it will stop the firewall services.Check your logging settings, from the Monitoring console. Select the logging tab, expand the view on the right-hand side then select the Tasks tab.Check the settings in Configure Firewall Logging, and Configure Web Proxy Logging."
looked at those settings, and they were both set to use the MSDE for logging. since I've upgraded to SQL 2005 and don't have MSDE installed anymore, I think this is why it's not working right. it does exactly what he said, stopping the firewall services. so I changed them both to use a W3C file, and when I restarted the services, this time they all started with no problems. i'm going to try a restart and see if I get another string of errors in the event log because of this.