Re: ISA 2k4 firewall service failure on reboot
- From: "Jim Harrison \(ISA SE\)" <jmharr@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 13 Sep 2007 15:17:47 -0700
Make sure you're not trying to keep more than 7 days' worth of logs.
MSDE can only service 8 simultaneous connections and if you have more than 7
active databases, MSDE will churn through connect / disconnect / reconnect
in order to serve those additional requests.
This can cause MSDE startup to take longer than fwsrv can wait.
--
Jim Harrison (ISA SE)
This posting implies no warranty and confers no rights.
http://catb.org/~esr/faqs/smart-questions.html
"Chris" <Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E4BB3F70-7545-42BC-A2E0-5E48628DE866@xxxxxxxxxxxxxxxx
Hi,
Whenever I restart our ISA Server 2004 SP3 (win2k3 sp1) the firewall service
will not start automatically.
The error logs have only the following errors:
a) Event ID 14001
Firewall Service failed to initialize. Previous event log entries might help
determine the proper action.
b) Event ID 21192
The Microsoft Firewall was unable to connect to MSDE database. The MSDE
Error description is: Could not find database ID 110. Database may not be
activated yet or may be in transition., Multiple-step OLE DB operation
generated errors. Check each OLE DB status value, if available. No work was
done., Property value is invalid. Make sure the value is typed correctly..
After logging in the firewall service can be started successfully through
the management console without having to do anything else.
This server is usually remotely managed and having to log on physically
after a reboot to start the firewall service is not an option I have all the
time.
regards,
Chris
.
- Prev by Date: Re: DHCP Server on combined DC/ISA Server
- Next by Date: Blocking Ares
- Previous by thread: Re: DHCP Server on combined DC/ISA Server
- Next by thread: Re: ISA 2k4 firewall service failure on reboot
- Index(es):
Relevant Pages
|
Loading