Is there any way to tell why a program is dying?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

jmDesktop - 27 May 2008 16:28 GMT

Not sure where to post this, but I have a vbscript that is dying and I
do not know why. It runs for a while then disappears (dies.) I know
that vbscript has no decent error handling, but that I can do if
err.number >0 ...., It isn't a problem with the script, however, and I
believe it is dying because of something outside of it - in the OS or
some other conflict.

Is there any way to build a .NET program that monitors and logs why
the program dies and not just that it died? I'm not sure how to
proceed.

Thanks for any help.

Reply to this Message

Alvin Bruney [ASP.NET MVP] - 28 May 2008 03:22 GMT

have a look at your machine logs (eventvwr) look for anything suspicious.
script is typically difficult to debug. If you can modify the script you may
want to place output information every couple of lines so that you can
follow the output in a log file to narrow down where in the script it is
dying.

Signature

Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book, 2nd Edition
Exclusively on www.lulu.com/owc $19.99
-------------------------------------------------------

> Not sure where to post this, but I have a vbscript that is dying and I
> do not know why. It runs for a while then disappears (dies.) I know
[quoted text clipped - 8 lines]
>
> Thanks for any help.

Reply to this Message

Is there any way to tell why a program is dying?

Free Magazines