Error in Classic ASP site brings the entire site down

[Fregas]

There is an old site that i'm having to maintain in classic asp. For
some reason, the original developers didn't belive in validation, so
there are many places where if the user puts in invalid data,
asp/vbscript throws a big sql server error. In development, on my
windows XP box, I can see this error (basically the field is not large
enough in sql server for the text they are trying to enter.) However,
when this error occurs on the production windows 2000 server box that
the hosting company is using, it brings the entire asp website down.
Static pages and ASP.NET pages still work fine, but all the classic asp
pages hang and hang and are entirely unresponsive.

Is there some setting or issue with windows 2000 where these types of
errors would crash the whole website? its like a transaction is
deadlocked or something but this hanging behavior doesn't happen on
windows xp on my local box. I check the sql server database shows all
the connections for that site's sql login to be sleeping.

I know i can simply enlarge the field and/or put in data validation.
But i want to make sure that if there are any other similar errors in
the future, they don't bring the site down. Any ideas?

[Jon Paal]

I doubt if it is ASP locking.

Sounds like the database is locking up and any pages which attempt to be used that also require the database are unable to work.

Try an ASP page that doesn't use the database to confirm which is locking up, ASP or the database. If this non-database page also
fails, check to see if there is a global.asa file has a problem which is subsequently affecting all other pages.


"Fregas" <fr****@gmail.comwrote in message news:11**********************@n51g2000cwc.googlegr oups.com...

There is an old site that i'm having to maintain in classic asp. For
some reason, the original developers didn't belive in validation, so
there are many places where if the user puts in invalid data,
asp/vbscript throws a big sql server error. In development, on my
windows XP box, I can see this error (basically the field is not large
enough in sql server for the text they are trying to enter.) However,
when this error occurs on the production windows 2000 server box that
the hosting company is using, it brings the entire asp website down.
Static pages and ASP.NET pages still work fine, but all the classic asp
pages hang and hang and are entirely unresponsive.

Is there some setting or issue with windows 2000 where these types of
errors would crash the whole website? its like a transaction is
deadlocked or something but this hanging behavior doesn't happen on
windows xp on my local box. I check the sql server database shows all
the connections for that site's sql login to be sleeping.

I know i can simply enlarge the field and/or put in data validation.
But i want to make sure that if there are any other similar errors in
the future, they don't bring the site down. Any ideas?

[Fregas]

Well, the plot thickens.

Apparently, if ANY error gets thrown on the whole site, even something
as simple as a VBScript syntax error, the entire ASP site goes down.
For a test, i made a page that just had one line of code: <%= now() %>.
If I change that to some gibberish, like <%= asdfasdf() %>, the whole
site goes down. So it is definitely NOT database related at all.
Thanks for your guidance as it helped me narrow down the problem
further.

I also looked in the Global.asa, and all that does is set on
application variable and one session variable, both of which are
strings.

Does ANYONE have any clues? Does microsoft monitor this newsgroup?

Thanks,
Craig

Jon Paal wrote:

I doubt if it is ASP locking.

Sounds like the database is locking up and any pages which attempt to be used that also require the database are unable to work.

Try an ASP page that doesn't use the database to confirm which is locking up, ASP or the database. If this non-database page also
fails, check to see if there is a global.asa file has a problem which is subsequently affecting all other pages.

[Bob Barrows [MVP]]

Fregas wrote:

Well, the plot thickens.

Apparently, if ANY error gets thrown on the whole site, even something
as simple as a VBScript syntax error, the entire ASP site goes down.
For a test, i made a page that just had one line of code: <%= now()
%>. If I change that to some gibberish, like <%= asdfasdf() %>, the
whole site goes down. So it is definitely NOT database related at
all. Thanks for your guidance as it helped me narrow down the problem
further.

I also looked in the Global.asa, and all that does is set on
application variable and one session variable, both of which are
strings.

Does ANYONE have any clues?

Sorry, but I don't. Try the .inetserver.iis group.

Does microsoft monitor this newsgroup?

Sort of. They look for messages from MSDN subscribers. If you are a
subscriber go to the website and look for the managed newsgroups. You
should see some instructions there. If you are not a subscriber, then
don't count on getting a MS response.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Anthony Jones]

"Fregas" <fr****@gmail.comwrote in message
news:11**********************@q40g2000cwq.googlegr oups.com...

Well, the plot thickens.

Apparently, if ANY error gets thrown on the whole site, even something
as simple as a VBScript syntax error, the entire ASP site goes down.
For a test, i made a page that just had one line of code: <%= now() %>.
If I change that to some gibberish, like <%= asdfasdf() %>, the whole
site goes down. So it is definitely NOT database related at all.
Thanks for your guidance as it helped me narrow down the problem
further.

I also looked in the Global.asa, and all that does is set on
application variable and one session variable, both of which are
strings.

Does ANYONE have any clues? Does microsoft monitor this newsgroup?

You don't have debugging enabled in the application configuration for the
site do you?

>
Thanks,
Craig

Jon Paal wrote:

I doubt if it is ASP locking.

Sounds like the database is locking up and any pages which attempt to be

used that also require the database are unable to work.

Try an ASP page that doesn't use the database to confirm which is

locking up, ASP or the database. If this non-database page also

fails, check to see if there is a global.asa file has a problem which

is subsequently affecting all other pages.