Help! WScript application error!

Has anybody encountered this before? What does it mean? I see this when my
computer has finished running a logon script. But the script has done
everything and finished properly. And strangely I don't see it every time,
but just occasionally. Is the error msg showing that my logon script has
bugs? If yes, what would they be? Thanks everybody in advance!!!

WScript.exe - Application Error
The execution Single Step
A single step or trace operation has just been completed. (0x80000004)
occurred in the application at location 0x001320aa.

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

McKirahan
Tue Dec 07 04:39:56 CST 2004

"bely" <bely@discussions.microsoft.com> wrote in message
news:52887596-BF0D-4B27-A479-6370EF844159@microsoft.com...
> Has anybody encountered this before? What does it mean? I see this when my
> computer has finished running a logon script. But the script has done
> everything and finished properly. And strangely I don't see it every time,
> but just occasionally. Is the error msg showing that my logon script has
> bugs? If yes, what would they be? Thanks everybody in advance!!!
>
> WScript.exe - Application Error
> The execution Single Step
> A single step or trace operation has just been completed. (0x80000004)
> occurred in the application at location 0x001320aa.
>
> Click on OK to terminate the program
> Click on CANCEL to debug the program

"Click on CANCEL to debug the program" and tell us what you see.

Michael
Tue Dec 07 14:56:57 CST 2004

bely wrote:
> Has anybody encountered this before? What does it mean? I see this
> when my computer has finished running a logon script. But the script
> has done everything and finished properly. And strangely I don't see
> it every time, but just occasionally. Is the error msg showing that
> my logon script has bugs? If yes, what would they be? Thanks
> everybody in advance!!!


What WSH version/build (check the version of wscript/cscript)?

The lastest WSH builds did not add any functionality but did include fixes
for stress bugs which is what you might be seeing during a logon script.

WSH version 5.6.0.8820 is included in xp sp2.

The current WSH 5.6 web download version is 5.6.0.8825.

Download details: Windows Script 5.6 for Windows 2000 and XP
http://www.microsoft.com/downloads/details.aspx?FamilyID=c717d943-7e4b-4622-86eb-95a22b832caa&DisplayLang=en

>
> WScript.exe - Application Error
> The execution Single Step
> A single step or trace operation has just been completed. (0x80000004)
> occurred in the application at location 0x001320aa.
>
> Click on OK to terminate the program
> Click on CANCEL to debug the program

--
Michael Harris
Microsoft MVP Scripting

bely
Fri Dec 10 00:47:08 CST 2004

My version is 5.6.0.6626. I know it is not the newest version. But according
to this, do you think the bug is in my script or in the script host?

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/w2kmsgs/791.asp

I cannot be sure if upgrading the script host helps, bcz as I have said, the
error just occurs occassionally. And I may not be able to upgrade it as my
will (this is not my PC, but is my firm's). Does anybody know what usually
will cause this "application error" so I can modify my script?

Many thx again!

Michael
Fri Dec 10 21:11:58 CST 2004

bely wrote:
> My version is 5.6.0.6626. I know it is not the newest version. But
> according to this, do you think the bug is in my script or in the
> script host?

It is unlikley to be a bug in your script, if, as you say, the script has
actually completed what it was intended to do.

How often is 'occasional'? One out of 10 logons? One out of 100?

Does this problem occur if you re-execute the logon script manually *after*
is has already run during logon? Does it occur with any other scripts?
Does your logon script do anything out of the ordinary?

>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/w2kmsgs/791.asp
>
> I cannot be sure if upgrading the script host helps, bcz as I have
> said, the error just occurs occassionally. And I may not be able to
> upgrade it as my will (this is not my PC, but is my firm's). Does
> anybody know what usually will cause this "application error" so I
> can modify my script?

If the bug is in the 5.6.0.6626 build script host (which I would assume it
is) and has been fixed in a later build (no way to know if it has been),
then your only option is to upgrade to a current build which should (one
would hope) have the most bugs fixed...

Since this is a work PC, you'll have to negotiate with your own tech support
group as to what action to take.

--
Michael Harris
Microsoft MVP Scripting

bely
Tue Dec 14 01:43:01 CST 2004

I found a bug in my script. Due to a design error, it calls Quit() method of
an "InternetExplorer" object twice (the script calls objIE.Quit() then the
_onQuit() function also calls objIE.Quit()). I wonder if the problem is
related to this bug, you know, the bug is there but is often "invisible". I
would be grateful if the answer is positive.


"Michael Harris (MVP)" wrote:

> bely wrote:
> > My version is 5.6.0.6626. I know it is not the newest version. But
> > according to this, do you think the bug is in my script or in the
> > script host?
>
> It is unlikley to be a bug in your script, if, as you say, the script has
> actually completed what it was intended to do.
>
> How often is 'occasional'? One out of 10 logons? One out of 100?
>
> Does this problem occur if you re-execute the logon script manually *after*
> is has already run during logon? Does it occur with any other scripts?
> Does your logon script do anything out of the ordinary?
>
> >
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/w2kmsgs/791.asp
> >
> > I cannot be sure if upgrading the script host helps, bcz as I have
> > said, the error just occurs occassionally. And I may not be able to
> > upgrade it as my will (this is not my PC, but is my firm's). Does
> > anybody know what usually will cause this "application error" so I
> > can modify my script?
>
> If the bug is in the 5.6.0.6626 build script host (which I would assume it
> is) and has been fixed in a later build (no way to know if it has been),
> then your only option is to upgrade to a current build which should (one
> would hope) have the most bugs fixed...
>
> Since this is a work PC, you'll have to negotiate with your own tech support
> group as to what action to take.
>
> --
> Michael Harris
> Microsoft MVP Scripting
>
>
>

bely
Tue Dec 14 03:23:04 CST 2004

Unfortunately the problem persists. I still have to work hard to figure out
the bug.
BTW many thanks to Michael.

And I find that it is nothing related to logon. The error occurs when it is
run manually after logon. And sometimes, I find another version of error, no
matter it is run as logon script or standalone, like this:

WScript.exe - Application Error
The instruction at "0x01301bd" referenced memory at "0x00000000". The memory
could not be "written".

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


But still, the script has completed what it has to do.

bely
Tue Dec 14 03:39:01 CST 2004

I would like to ask, if either version of errors occurs, does it mean the
script immediately quits and the remaining codes would not be run? My script
does write log file, and even error occurs, the log files are completed. Here
are the last few lines:

1 Call f.Write(msg & vbCrLf & "End of log file.")
2 Call f.Close()
3 Set WshShell = Nothing ' wscript.shell object
4 Set WshNetwork = Nothing ' wscript.network object
5 Set objFSO = Nothing ' file system object
6 Set objIE = Nothing ' IE object
7 Set f = Nothing
8 Call WScript.Quit(ret)

If I'm right, at least the error occurs after line 1. But what could go
wrong there? Many thanks again!


"bely" wrote:

> Unfortunately the problem persists. I still have to work hard to figure out
> the bug.
> BTW many thanks to Michael.
>
> And I find that it is nothing related to logon. The error occurs when it is
> run manually after logon. And sometimes, I find another version of error, no
> matter it is run as logon script or standalone, like this:
>
> WScript.exe - Application Error
> The instruction at "0x01301bd" referenced memory at "0x00000000". The memory
> could not be "written".
>
> Click on OK to terminate the program
> Click on CANCEL to debug the program
>
>
> But still, the script has completed what it has to do.

Michael
Tue Dec 14 19:46:04 CST 2004

bely wrote:
> I found a bug in my script. Due to a design error, it calls Quit()
> method of an "InternetExplorer" object twice (the script calls
> objIE.Quit() then the _onQuit() function also calls objIE.Quit()). I
> wonder if the problem is related to this bug, you know, the bug is
> there but is often "invisible". I would be grateful if the answer is
> positive.


Calling objIE.Quit() certainly isn't a good thing ;-). I would never call
it from within an _OnQuit() handler which only fires if Quit() has already
been called or the user manually cloese the IE instance. Calling it that way
sets up a recursive situation where the OnQuit event fires again causing the
event handler to be called again, etc., etc., etc...

So in this case, I *suppose* that the script logic error you found could end
up trashing the WSH host in the process when it tries to cleanup on
shutdown...

--
Michael Harris
Microsoft MVP Scripting

Michael
Tue Dec 14 21:10:00 CST 2004

Ummm... That would be:

Calling objIE.Quit() **more than once** certainly isn't a good thing ;-).
...

--
Michael Harris
Microsoft MVP Scripting