Microsoft KB Archive/303019

= Web Proxy and Firewall Services Do Not Start =

Article ID: 303019

Article Last Modified on 1/15/2006

-

APPLIES TO


 * Microsoft Internet Security and Acceleration Server 2000 Standard Edition

-



This article was previously published under Q303019



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
The Proxy service and Firewall service do not start, and the following event ID messages are logged in the Application Event log:

Event Type: Error

Event Source: Microsoft Web Proxy

Event Category: None

Event ID: 11000

Date: 6/28/2001

Time: 12:33:57 PM

User: N/A

Computer: UMITT2K

Description:

Microsoft Web Proxy failed to start.

The failure occurred during Reading protocol rules because the configuration property of the key

SOFTWARE\Microsoft\Fpc\Arrays\{37EABF10-3326-4280-B1AF-DB6DF68A49D0}\ArrayPolicy\Proxy-Protocol-Rules\{FF3DA41B-A332-4B67-8B26-D0ADD2453D8B}\ScheduleUsed could not be accessed. Use the source location 2.546.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.

Data:

0000: 02 00 00 00

-and-

Event Type: Error

Event Source: Microsoft Web Proxy

Event Category: None

Event ID: 14127

Date: 6/28/2001

Time: 12:33:57 PM

User: N/A

Computer: UMITT2K

Description:

The Web Proxy service could not initialize (error code). The internal error code in the Data area of the event properties indicates the cause of the failure.

Data:

0000: 02 00 07 80 ...?

-and-

Event Type: Error

Event Source: Microsoft Firewall

Event Category: None

Event ID: 11000

Date: 6/28/2001

Time: 12:46:13 PM

User: N/A

Computer: UMITT2K

Description:

Microsoft Firewall failed to start. The failure occurred during Reading protocol rules because the configuration property of the key SOFTWARE\Microsoft\Fpc\Arrays\{37EABF10-3326-4280-B1AF-DB6DF68A49D0}\ArrayPolicy\Proxy-Protocol-Rules\{FF3DA41B-A332-4B67-8B26-D0ADD2453D8B}\ScheduleUsed could not be accessed. Use the source location 2.546.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.

Data:

0000: 02 00 00 00

The following event ID messages are logged in the System Event log:

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7024

Date: 6/28/2001

Time: 12:48:23 PM

User: N/A

Computer: UMITT2K

Description:

The Microsoft Web Proxy service terminated with service-specific error 147942402.

-and-

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7024

Date: 6/28/2001

Time: 12:48:44 PM

User: N/A

Computer: UMITT2K

Description:

The Microsoft Firewall service terminated with service-specific error 213007.



CAUSE
This behavior may occur because the Site and Content rules and Protocol rules are set to use schedules in Policy rules. The Proxy and Firewall services check the msFPCAppliesAlways values in each Policy-Access-Rules and Proxy-Protocol-Rules entry under Array GUID and Array Policy, for example:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fpc\Arrays\{37EABF10-3326-4280-B1AF-DB6DF68A49D0}\ArrayPolicy\Proxy-Access-Rules\{10DC9E4A-CA38-40FC-98CC-083AE023515D}

If the msFPCAppliesAlways value is set to any value other than &quot;FF FF FF FF&quot;, there must be a ScheduleUsed registry key under each GUID of the Policy-Access-Rules and Proxy-Protocol-Rules entries. If the key does not exist, you cannot start Proxy or Firewall Services.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To determine the rule that is causing the problem, check the GUID of the rule in the event log, and then locate this GUID in the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fpc\Arrays\{37EABF10-3326-4280-B1AF-DB6DF68A49D0}\ArrayPolicy

The rule name is listed in the msFPCName registry value.

To resolve this issue, use either of the following methods:

Method One

 * 1) Start the Internet Security and Acceleration (ISA) Server Management snap-in.
 * 2) Right-click either Site and Content Rules or Protocol Rules, and then click Properties.
 * 3) Click the Schedule Tab, change the Schedule box to any new value, and then click Apply.
 * 4) Select the value again, and change the value back to the original value, and then click Apply.

When you use this method, the ScheduleUsed registry key is created in the registry for the rule that you selected. After you complete this procedure, start the services. If services do not start, use the same procedure, but choose another rule.

Method Two

 * 1) Change all msFPCAppliesAlways registry values to &quot;FF FF FF FF&quot; for each Proxy-Access-Rules and Proxy-Protocol-Rules entry that is represented with a GUID under Policy-Access-Rules and Proxy-Protocol-Rules.
 * 2) Reconfigure the Schedule policy by using the ISA Server Management snap-in.



STATUS
This behavior is by design.

Additional query words: Firewall Webproxy w3proxy

Keywords: kbenv kbprb KB303019

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.