FIX: Traffic is not forwarded or you receive an error message about ADVAPI32.dll when you use a Windows XP client to start an application from a Forefront Unified Access Gateway 2010 Service Pack 3 portal


Symptoms


When you use a Windows XP client to start an application that uses the Socket Forwarder component from a Microsoft Forefront Unified Access Gateway 2010 Service Pack 3 (SP3) portal, you may notice that traffic is not forwarded as expected. Or, you receive the following error message:

Entry Point Not Found
The procedure entry point EventActivityIdControl could not be located in the dynamic link library ADVAPI32.dll.

Cause


The EventActivityIdControl API is unintentionally called in the SP3 client components. This API is available only in Windows Vista and later versions.

Resolution


This problem is fixed in the update that is described in Description of Rollup 1 for Forefront Unified Access Gateway 2010 Service Pack 3 .

Status


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

More Information


Windows XP clients that use the Forefront Unified Access Gateway client components may not function correctly after Service Pack 3 is installed. Clients are automatically requested to update the Forefront Unified Access Gateway client components when they access the portal for the first time after a service pack is installed. The installation of the client components may succeed without any warnings. However, functionality such as the Socket Forwarder component may not function correctly after the update is installed.

References


For more information about software update terminology, please see Description of the standard terminology that is used to describe Microsoft software updates .