Formativ Applets and McAfee VirusScan

[Anonymous]

We have a few clients who are reporting an error that appears to be occur when a Formativ applet is loaded in GroupWise on machines running McAfee VirusScan 8.0. The error is reported in Formativ Dialog, as follows:

Window Caption: Sorry, the applet could not be executed
Access Violation at address 1803215C in module ‘scriptproxy.dll’
Read of address 00000000

Do you know if the Formativ product is compatible with McAfee VirusScan 8.0, or have any suggestions as to a workaround for this error?

Thank You

John H
IntelliReach Corporation

Topic

[Support 2]

Hi John,

Yes, this is a known issue which was introduced with 8.0i. Another post offers the solution (link to post). I have also quoted the post below.

Let us know if their fix does not solve the problem.

Kind Regards,

Advansys Support

quote:

---

I got the same problem (access violation with scriptproxy.dll) with McAfee 8.0i. It is a new “feature” from McAfee that javascript and vbscripts are scanned, e.g. they redirect the scripts to their own engine.
You can disable this by modifying the registry with the following info from NAI.

Q: I’m getting errors when executing
JavaScript/VBScript. How does ScriptScan work?

A: There are two registry entries, one for
JSCRIPT.DLL and one for VBSCRIPT.DLL that are
redirecting calls to the VirusScan Enterprise
ScriptScan DLL called SCRIPTPROXY.DLL.
ScriptScan is an optional component; you can
remove it from your computer to see if errors
subside. The registry keys to check are;

HKCRCLSID{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}InprocServer32

– Default value should be:
c:windows foldersystem32jscript.dll
(The path is operating system specific.)

– VSE sets:
c:program filesnetwork associatesvirusscanscriptproxy.dll

HKCRCLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}InprocServer32

– Default value should be:
c:windows foldersystem32vbscript.dll
(The path is operating system specific.)

– VSE sets:
c:program filesnetwork associatesvirusscanscriptproxy.dll

---

[Author]

Replies