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:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fpc\Arrays\{CurrentArrayGUID}\Publishing\Proxy-WebPub-Rules\{WebPubRuleGUID}\VendorParametersSets\{VendorParametersSetGUID}\
In Active Directory, the
corrupted data appears in
the following location:
CN={VendorParametersSetGUID},CN=VendorParametersSets,CN={WebPubRuleGUID},CN=Proxy-WebPub-Rules,CN=Publishing,CN={CurrentArrayGUID},CN=Arrays,CN=Fpc,CN=System,DefaultNamingContext
When
you view
the
VendorParameterSetGUID
key in
the registry (or
if you view the Active
Directory
location), when
you view the particular
GUID key ,
you see the following entry:
"msFPCName"="{c202d356-5e93-4813-b737-b6f3e02c246c}"
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:
"msFPCBlobData"=hex:02,00,00,00,10,00,00,00,45,00,6e,00,61,00,62,00,6c,00,65,\
00,64,00,00,00,0b,00,00,00,10,00,00,00,4e,00,6f,00,43,00,61,00,63,00,68,00,\
65,00,00,00,0b,00,00,00
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."