Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Web Proxy logging truncates URLs after 254 characters in ISA Server 2000


View products that this article applies to.

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/) Description of the Microsoft Windows registry

↑ Back to the top


Symptoms

You have configured logging for the Web Proxy service in Microsoft Internet Security and Acceleration (ISA) Server 2000. However, in the log files that ISA Server 2000 generates, Web Proxy logging truncates URLs after 254 characters. You expect an ISA Server 2000 log file to contain the whole URL that was requested during the Web Proxy transaction.

↑ Back to the top


Cause

This problem occurs because the URI Web Proxy log field has an incorrect length. The URI Web Proxy log field should have a length of 2048 characters. However, because of a problem in ISA Server 2000, this field is incorrectly reduced to 254 characters.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

You must have ISA Server 2000 Service Pack 2 installed to apply this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
313139 How to obtain the latest Internet Security and Acceleration Server 2000 service pack

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart the ISA Server Web Proxy service (W3Proxy.exe) after you install this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name
   --------------------------------------------------------------  
   30-May-2005  23:20  3.0.1200.417      222,712  Msfpc.dll        
   30-May-2005  23:20  3.0.1200.417      402,424  W3proxy.exe      

Hotfix installation information

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

After you apply this hotfix, you must create the following registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3Proxy\Parameters

Value name: MaxUriLogLength
Value type: REG_DWORD
Value data: decimal value
In this registry entry, replace decimal value with a decimal value from 254 through 4095. (254 is the default value.) For example, to increase URI logging to the maximum value, type 4095 (decimal) in the Value data box of this registry entry.

Note If you perform logging to a Microsoft SQL Server database, you must extend the URI field in that database to the same size as the value that you specified in the MaxUriLogLength registry entry. If you do not extend this database field, logging is not successful because the larger URI value exceeds the size of the URI field in the database.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: KB898787, kbhotfixserver, kbpubtypekc, kbqfe, kbfix, kbbug, kbfirewall

↑ Back to the top

Article Info
Article ID : 898787
Revision : 6
Created on : 6/14/2007
Published on : 6/14/2007
Exists online : False
Views : 304