Peter J. Boettcher — Wed, 31 Jul 2002 12:35:53 +0000

Before you kill yourself or **GASP** ditch all your asp pages can you try running the site on another server? Try to mirror what your host is running as close as possible (OS, IIS, ADO versions, etc) and see if you get the same error. If not then it is something your host has done, probably in regards to permissions.

Are you using a custom COM object or any ADO?

Sparklebug — Wed, 31 Jul 2002 01:48:49 +0000

It's still happening ASP 0115 is driving me to despair!

I'm am a complete ASP newbie so have sent the FAQ link given by Peter to our web hosts and the ASP coder who has been working on our site. The hosts claim it's our code, the coder isn't sure exactly where the problem lies.

I've checked that every form and input on the site is named and have re-uploaded any pages where changes were made - turned out there were quite a number of them (none from our current coder, however). Also, whole directories of ASP where a number of errors were found have been removed for fixing.

Yet still it persists, some days worse than others (today none of our ASP seems to be working at all - yesterday it was barely a problem).

So what to do? Does it normally take this long to sort out? Shall I kill myself now rather than continuing to do battle with it? Should I ditch all of our ASP pages?

Any clues would be much appreciated.

Yours in desperation
Bug x

Peter J. Boettcher — Fri, 28 Jun 2002 12:29:45 +0000

The dreaded ASP 0115 error! That basically means that IIS doesn't know what happened but something isn't right. Most of the time it has to do with an external COM object or ADO or sessions.

Check out this link for more info: http://www.aspfaq.com/show.asp?id=2171

One thing they don't mention is to name all your forms. It sounds wierd but there is a bug in the form collection when you don't name all your forms, I think this has been fixed for IIS5 though.