Re: Error 213007 on PowerEdge 2550
- From: "Nick Chadwick" <nick@xxxxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Tue, 4 Sep 2001 14:52:16 +0100
Joseph,
Have you recently deleted any protocol definitions? ISA Server warns you when
you do this, that if the deleted definition is used in any "Allowed Protocol"
policies, the Firewall service will fail to start.
Nick Chadwick
Development & Technical Support Manager
Comsoft Limited, UK
Tel: +44-(0)20-8240-4452 Fax: +44-(0)20-8240-4449 Mobile: +44-(0)7740-362408
Email: nick@xxxxxxxxxxxxxx < mailto:nick@xxxxxxxxxxxxxx>
Web: http://www.comsoft.ltd.uk/
-----Original Message-----
From: Jim Harrison [mailto:jim@xxxxxxxxxxxx]
Sent: 04 September 2001 14:49
To: [ISAserver.org Discussion List]
Subject: [isalist] Re: Error 213007 on PowerEdge 2550
http://www.ISAserver.org
What other event log entries are you getting?
Is the server using ACPI IRQ sharing?
Jim Harrison
MCP(2K), A+, Network+, PCG
----- Original Message -----
From: Joseph King
To: [ISAserver.org Discussion List]
Sent: Monday, September 03, 2001 9:35 PM
Subject: [isalist] Error 213007 on PowerEdge 2550
http://www.ISAserver.org
We have ISA Standard Edition running on a Dell PowerEdge 2550.
The specs are: 1 GHz PIII, 512 MB of RAM, and 18 GB of disk space.
The Windows 2000 Server has SP2 installed, is a member of an NT domain, and is
supporting 400 users.
We have already gotten used to the fact that despite 2 rebuilds, we have to
reboot at least once per day because the internal NIC stops responding (no
matter which NIC is internal).
However, after today's reboot, the firewall service failed to start.
The system log gives me an event ID 7024 with the following description: "The
Microsoft Firewall service terminated with service-specific error 213007." The
corresponding application log error was: "Microsoft Firewall failed to start.
The failure occurred during Reading protocols because the configuration
property msFPCName of the key
SOFTWARE\Microsoft\Fpc\Arrays\{03700E96-6874-41BF-8E6D-876A399BAF18}\PolicyElements\Protocols\{158DB1ED-0D67-4753-AEC6-4188CE7644FC}
could not be accessed. Use the source location 2.1927.3.0.1200.50 to report
the failure. The error code in the Data area of the event properties indicates
the cause of the failure. For more information about this event, see ISA Server
Help. The error description is: The system cannot find the file specified."
There is only 1 Q article referring to that error, and that is Q284701 at
http://support.microsoft.com/support/kb/articles/Q284/7/01.ASP. It does not
seem to apply to our scenario, because this server never ran a beta or release
candidate version of ISA.
Uninstalling and re-installing ISA did not resolve the problem
Has anyone seen anything similar? Despite 30 days of testing, we've had nothing
but problems since we put this server into production, and I am open to any and
all suggestions.
In Your Service,
Joseph King, MCSE
http://www.joking.net/
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jim@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
nick@xxxxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
**********************************************************************
Disclaimer: This e-mail contains proprietary information some or all
of which may be legally privileged. It is for the intended recipient
only. If an addressing or transmission error has misdirected this
e-mail, please notify the author by replying to this e-mail and then
permanently delete the message from your computer. If you are not the
intended recipient you must not use, disclose, distribute, copy, print
or rely on the e-mail.
The opinion expressed in this Email is that of the author and not
necessarily that of Comsoft Limited.
While attachments are virus checked, Comsoft Limited do not accept any
liability in respect of a virus which is not detected.
**********************************************************************
Other related posts:
