Event ID 5, event ID 14079, and event ID 14176 are logged in the Application log on your Internet Security and Acceleration Server computer

The Microsoft Web Proxy service on a computer that is running Microsoft Internet Security and Acceleration (ISA) Server may occasionally stop responding or quit unexpectedly. When this behavior occurs, users cannot connect to the Internet through your ISA Server computer.

Additionally, events that resemble the following events are logged in the Application log:

Event ID: 14079
Type: Error
Source: Microsoft ISA Server Control
Description:
Due to an unexpected error, the service w3proxy stopped responding to all requests. This occurred 1 time(s) in the past 2:59 hours. Try to stop the service or kill the corresponding process if it does not respond, and start it again. Check the Event Viewer for related error messages.

Event ID: 14176
Type: Error
Source: Microsoft Web Proxy
Description:
Disk cache Drive:\urlcache\Dir1.cdat failed to initialize. Some errors were encountered when ISA Server restored specific data cache files. ISA Server will now attempt to recover these files. These errors may have occurred because there was not enough time to complete all necessary shutdown operations, when ISA Server was previously shut down. To avoid this in the future, you can increase the value of the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WaitToKillServiceTimeout registry key. Identify the reason for cache failure by examining previous recorded events, or the error code. The error code in the Data area of the event properties indicates the cause of the failure (internal code: 503.6333.3.0.1200.166).

Event ID: 5
Type: Error
Source: Microsoft Web Proxy
Description:
The Microsoft Web Proxy failed to log information to file FileName.log in path Drive:\ISALOGS. The data is the error code. For more information about this event, see ISA Server Help.

This behavior may occur if the ISA Server Web Proxy log file is corrupted. Web Proxy log file corruption can be caused by one or more of the following:

• Virus scanning software
  
  Note Antivirus software can corrupt the log files or the cache files if it locks the file for scanning while ISA Server tries to access the file.
• Backup software
• Third-party ISA Web filtering software
• Server monitoring software
• Hard disk or disk controller hardware errors

Warning This workaround may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

Note An antivirus program is designed to help protect your computer from viruses. You must not download or open files from sources that you do not trust, visit Web sites that you do not trust, or open e-mail attachments when your antivirus program is disabled.

For more information about computer viruses, click the following article number to view the article in the Microsoft Knowledge Base: To resolve this issue, do one or more of the following:

• Remove or disable any third-party ISA Server Web filtering software. Contact the third-party vendor for help and to determine whether an upgrade is available.
• If you are running antivirus or backup software, make sure that you exclude the ISALogs folder. By default, the ISALogs folder is located in the folder where you installed ISA Server. Typically, this location is Drive:\Program Files\Microsoft ISA Server.
• Try to move the log folder to a different physical hard disk or to a different logical hard disk drive.

After you try one or more of these procedures, make sure that the Microsoft Web Proxy service is running. To do this, following these steps:

1. Click Start, point to Programs, point to Administrative Tools, and then click Services.
2. Locate the Microsoft Web Proxy service.
3. Make sure that the service indicates a status of Started.
4. If the service is not running, right-click Microsoft Web Proxy, and then click Start.

If the Microsoft Web Proxy service does not start, rename the corrupted log file, and then start the service.