Video Screencast Help

Intermittent failure by VBScript returns -1073741819 on W2K8 R2

Created: 22 Nov 2011 • Updated: 29 Nov 2011 | 1 comment
This issue has been solved. See solution.

All , I have a small VBscript that returns the count of drives that does not have 'NTFS' formatting.

I am encountering an issue on Windows 2008 R2 platform and is intermittant.Sometimes VBscript works sometimes it doesnt.When it does not run properly, VBScript returns -1073741819.

In the script ,A variable is initialized to zero and then for each local filesystem thats not 'NTFS' we increment it and at the end return the value of that variable using WScript.Quit variable.

From another forum I learnt :"The error number -1073741819 in hex is 0xC0000005 which indicates an access violation in windows. An access violation means your process has tried to access memory that does not belong to it."

Comments 1 CommentJump to latest comment

rakesh.padikar's picture

[NOT TESTED]

From this thread : https://www-304.ibm.com/support/docview.wss?uid=swg21514870

May be we could try the workaround(s) on one of the Windows 2008 R2 if possible.

Cause:
The negative return code -1073741819 is actually the translation of 0xC0000005.
This code mean ACCESS_VIOLATION and it is returned directly from the cscript manager. Usually this kind of problem is caused by an AntiVirus software running on the machine.

Diagnosing the problem:
If you are using McAfee,the problem is most likely caused by the SCRIPTSN.dll, which is installed with McAfee Version 8.8 (this dll is responsible for the script virus scan) even if the ScriptScan component is disabled.

This McAfee technote explains the cause of the problem:
https://kc.mcafee.com/corporate/index?page=content&id=KB71660&actp=search&viewlocale=en_US&searchid=1313422826655

The problem occurs on Windows 2008 R2 and McAfee 8.8.
Basically, the SCRIPTSN.dll is hooked into the scripting engine (cscript) even if ScriptScan is disabled.
Watchdog on Windows platform strongly leverages on cscript engine, so it may be impacted by this configuration.

Resolving the problem:
The McAfee technote above describes two possible work arounds:

Workaround 1 :-  Enable ScriptScan in the VirusScan Console:

Click Start, Programs, McAfee, VirusScan Console.
Right-click On-Access Scanner and select Properties.
Under General Settings, click the ScriptScan tab.
Select Enable ScriptScan.
Click Apply and OK.

Workaround 2 :-  Un-register SCRIPTSN.dll:

-Select Start, Run, type cmd, and press ENTER.
Type the appropriate command and press ENTER:

32 bit computers:
cd c:\Program Files\Common Files\McAfee\SystemCore

64 bit computers:
cd c:\Program Files (x86)\Common Files\McAfee\SystemCore
cd c:\Program Files\Common Files\McAfee\SystemCore

-To completely disable the SCRIPTSN.dll, type the following command and press ENTER:
regsvr32.exe /u SCRIPTSN.dll

Solution:
This issue is resolved in McAfee VirusScan Enterprise 8.8 Patch 1

SOLUTION