Re: Error 213007 on PowerEdge 2550
- From: Joseph King <joseph.king@xxxxxxxxxx>
- To: "'[ISAserver.org Discussion List]'" <isalist@xxxxxxxxxxxxx>
- Date: Tue, 4 Sep 2001 14:02:29 -0700
Nick,
We haven't deleted any protocol definitions, but on a hunch, I removed all
of the allowed protocols, and then re-added them. Now the service starts.
Thanks!
So, I'm just back to trying to understand why the internal NIC stops
responding once per day...
- J
-----Original Message-----
From: Nick Chadwick [mailto:nick@xxxxxxxxxxxxxx]
Sent: Tuesday, September 04, 2001 6:52 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] Re: Error 213007 on PowerEdge 2550
http://www.ISAserver.org
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: Joseph King
To: [ISAserver.org Discussion List]
Sent: Monday, September 03, 2001 9:35 PM
Subject: [isalist] Error 213007 on PowerEdge 2550
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}\PolicyE
lements\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/
Other related posts:
