WScript.exe - Application Error

[j@ckle]

I have tried posting this in microsoft.public.scripting.wsh group with
no luck. Maybe you guys can help.
-------------------------------------------------------------

I have written a logon script (via vbscript) and some users are
receiving the following error during logon:

-------------------------------------------------------------
Wscript.exe - Application Error
The instruction at "0x7c911639" referenced memory at "0x00f5291d". The
memory could not be "read".

-- Click on OK to terminate the program
-- Click on CANCEL to debug the program

[OK] [CANCEL]
-------------------------------------------------------------

I have provided the logon script for review at
http://www.bv-projects.com/downloads/anar_logon.txt

When a user does receive the error, the script seems to halt right
before connecting the users printers. Although, when the user gets this
error they can typically logout/login and the script will run fine the
second time. But beyond that I am at a loss when troubleshooting this
issue. I just can't seem to fix this annoyance.

As always, any help would be appreciated.

 

[noel]

I'm a biginner in vbs. The statement "On Error Resume Next" means
"continue if error". So, if one error occurs on a line, perhaps the prg
"nfs.exe" witch is launch ( cmd;exe /c nfs.exe ...) is at the origine
of the messagebox.
If you see the log file, you have some help information...
Did you seen event log, appliaction and system?
Can you put audit on "process traking"?
Can you put UserEnvDebugLevel = 0x10002 for create a log of open
session, gpo,etc..? sea
http://support.microsoft.com/default.aspx?scid=kb;EN-US;221833
i can't say more. Sorry.

 

[Michael Harris \(MVP\)]

I have tried posting this in microsoft.public.scripting.wsh group with
no luck. Maybe you guys can help.
-------------------------------------------------------------

I have written a logon script (via vbscript) and some users are
receiving the following error during logon:

-------------------------------------------------------------
Wscript.exe - Application Error
The instruction at "0x7c911639" referenced memory at "0x00f5291d". The
memory could not be "read".

-- Click on OK to terminate the program
-- Click on CANCEL to debug the program

[OK] [CANCEL]

I had a very similar situation a year+ ago following either a w2kpro sp (4?)
or some other wk2 patch (don't remember which). It only triggered on a
script that created a cdo.message instance, and then only during the script
host normal termination process. If I commented out or bypasssed only that
small part of the code, there was no w/cscript.exe application error on
termination.

On a whim, I upgraded to the most recent wsh 5.6 build available for w2k at
the time and it magically resolved the problem. A simple re-install of the
same build may have had the same effect.

In any cas, I never did figure out root cause (not enough hours in the day).
I assume it was something subtle in the host's COM plumbing/cleanup.

Your mileage may vary, or as Scott Adams puts it - BOCTAOE ...