microsoft script debugger and WIN2K

I have a windows 2000 server with IIS running on it, with some asp pages.
It happens so me really often to have the microsoft script debugger window
opened (as if an error has occurred) but no asp page is present in the
window (so no idea where the bug is, even if i as sure there is an error).
For example this behaviour is quite common if during a debug session i close
the debugger.
There is no way, even if i catch the same error page, to have the debugger
opened with the as. file containing the error displayed in the debugger.
And i need to restart the server hoping that the next time the debugger will
open and show the page with the error.
Why is that?
Is it a common problem?
Regards
F.

George
Mon Oct 04 18:54:32 CDT 2004

Sometimes the script debugger cannot access the page where the error =
occurs. This is usually a result of the error not occurring in the ASP =
itself but in a ASP that is included. For example in Visual Interdev =
many ASP pages are included in the ASP that is being used for the =
Application. If the error occurs in one of them accessing the =
Application ASP will throw the error but Script Debugger may not be able =
to access it.

First you should have in IE properties your script debugging set and =
show each error. Then make a simple ASP like this:

<@language=3D"VBScript%>
<%
Dim alpha
alpha =3D 0
Dim alpha
%>

This should throw an error and your script debugger should catch it. =
After it catches it you say OK to allow the debugging session and the =
above ASP should appear in the Window. If this works for you then your =
configuration is fine.

--=20
George Hester
__________________________________
"xkp" <veidt1@hotmail.com> wrote in message =
news:2%f8d.60276$35.2977282@news4.tin.it...
> I have a windows 2000 server with IIS running on it, with some asp =
pages.
> It happens so me really often to have the microsoft script debugger =
window
> opened (as if an error has occurred) but no asp page is present in the
> window (so no idea where the bug is, even if i as sure there is an =
error).
> For example this behaviour is quite common if during a debug session i =
close
> the debugger.
> There is no way, even if i catch the same error page, to have the =
debugger
> opened with the as. file containing the error displayed in the =
debugger.
> And i need to restart the server hoping that the next time the =
debugger will
> open and show the page with the error.
> Why is that?
> Is it a common problem?
> Regards
> F.
>=20
>

xkp
Tue Oct 05 00:21:42 CDT 2004


Thanks for the answer.
Anyway, as i said, the error is catched sometimes.
If i close the debugger, it will become unable to catch it.
sometimes the debbuger opens but with no asp pages displayed.
And in a case like that i have found no way to let it works correctly
(aparte reboot the machine but is quite an hard solution, isnt it?).
Moreover i am interested in errors that happens from server side scripts.
I have found several times debugger opened in my server but with no page
dispalyed, so no idea where is the bug.
regards
filippo

George
Tue Oct 05 12:13:17 CDT 2004

Right that is what I had explained. The error I gave you is a Server =
side error right? It's not client side.
Like I said when the error does not occur in the hosting ASP but in an =
included ASP Script Debugger may "say" there is an error but be unable =
to show it to you. That's just a deficiency in the Script Debugger. If =
what I gave you did bring up in the Script Debugger the ability to debug =
the error in the ASP then you have done all you can do.

I have experienced the same issue. There is a way to have each error =
written to a database that will give the source of where the error =
occurs. It uses the ASP error object.

--=20
George Hester
__________________________________
"xkp" <veidt1@hotmail.com> wrote in message =
news:Gbq8d.62231$35.3166078@news4.tin.it...
>=20
> Thanks for the answer.
> Anyway, as i said, the error is catched sometimes.
> If i close the debugger, it will become unable to catch it.
> sometimes the debbuger opens but with no asp pages displayed.
> And in a case like that i have found no way to let it works correctly
> (aparte reboot the machine but is quite an hard solution, isnt it?).
> Moreover i am interested in errors that happens from server side =
scripts.
> I have found several times debugger opened in my server but with no =
page
> dispalyed, so no idea where is the bug.
> regards
> filippo
>=20
>