Description

Prior to OpenSpan 4.1 SP1, McAfee Host Intrusion Protection Service (HIPS) running on the user desktop could interfere with OpenSpan interrogation of HTML elements in the Internet Explorer browser window.

If running an adapter (either Web or Windows) that starts Internet Explorer, a dialog box with the following message sometimes appeared if HIPS was active:

Translator module OpenSpan.Translators.InternetExplorer.dll failed to load (reason code: 0x00000001). The translator has been added to the list of translators to statically load (see openspan.ini). You must stop and restart interrogation for this change to take effect.

Solution

Users of OpenSpan Studio 4.1 encountering this problem should ensure that Service Pack 1 is installed. Users of OpenSpan 4.5 can find the fix ported to release 4.5 in 4.5 Service Pack 1. (New downloads of OpenSpan 4.5 after mid-October 2010 will automatically include the changes.)

Background

Previously, when HIPS was present and running, OpenSpan Studio sometimes did not get all module load notifications. Notification of MSHTML is critical for operation of the OpenSpan Web adapter.

The 4.1 or 4.5 Service Packs install OpenSpan's next generation hooking and injection layer which tracks all module loads.

The new injection layer becomes active inside the process earlier than the previous injection layer, and uses a different technique which detects module loads that were previously missed, such as MSHTML.dll.

Note

Use of the driver is not supported with the changes. The driver is used when StartMethod "StartAndWait" or "MonitorAll" are specified in the Windows Adapter.

Additional Instructions

If the error message above appears during interrogation, stop and restart interrogation. The message should not appear again.If it appears while running the project, stop and restart the project. Note: Write permission to openspan.ini is required for this to work.

For deployment to runtime-only machines: If the users have write permission to the folder where openspan.ini resides, each user can run the project once to get the openspan.ini update, and no further action is required. If users do not have write permission to the openspan.ini folder, then an updated openspan.ini can be pushed to each runtime-only machine in advance of the project being started.