This article has been archived. It is offered "as is" and will no longer be updated.
After you install Microsoft Internet Security and Acceleration (ISA) Server 2000 Feature Pack 1 and you turn on the Link Translation filter that is included Feature Pack 1, when you start the Web Proxy service, some link translation rules may not work and the following event ID message may be logged:
Event Type: Error Event Source: Microsoft Web Proxy Event Category: None Event ID: 14146 Description: ISA Server failed to load Web Filter DLL C:\Program Files\Microsoft ISA Server\\LnkTrans.dll. The error code shown in the Data area of the event properties indicates the cause of the failure.
Note The status in the data is 8000ffff. This status translates to the error E_UNEXPECTED (Catastrophic Failure).
The rules and the Link Translation filter may work as expected; however if other Web publishing rules are edited, the event ID 14146 message may be logged.
This problem may occur if the link translation state settings for one or more Web publishing rule are corrupted in either the registry or in the Active Directory directory service. To identify the corrupted data for a stand-alone server, view the storage location in the registry. To identify the corrupted data for enterprise arrays, use Active Directory. In the registry, the corrupted data appears in the following registry key:
The problem occurs because the "msFPCBlobData" entry for that particular GUID key is seen as "empty" by the ISA Server storage management tools (the entry contains 00 00 00 00). However, the entry must have the following data:
This data is a combination of unicode strings that spells out "Enabled" and "NoCache" and their associated values. Because an empty set is not valid, the link translation load failure occurs. Because an "empty" state can also be correctly interpreted as "no setting," Linktrans.dll now treats this condition as "disabled."
A supported hotfix is 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 software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) 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 -------------------------------------------------------------- 25-May-2003 13:19 3.0.1200.271 34,064 Lnktrans.dll
To work around this behavior, obtain the Linktrans fix from the following ISAtools Web site:
Run the tool on the affected ISA Server computer (stand-alone) or on any ISA Server computer in the affected array (enterprise). The tool locates all link translation-related VendorParametersSets values in all Web publishing rules, and then adds the missing entries to those VendorParameterSets values without modifying any other data. This script is only intended to fix the .dll load failure problem, it does not resolve the storage corruption problem.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.