I got these at one time too, and saved this article
MS wrote awhile back:
The Dreaded "ASP 0115" Error
error 'ASP 0115'
Unexpected error
/<Web Name>/<ASP file name>.asp
A trappable error occurred in an external object. The script
cannot continue running.
If you get this error message, you have a leg up on this process. When the
error is displayed on the returned ASP page, you now know two things:
what page it was that caused the problem to occur
that an exception occurred in an external object
If knowing the page that is causing the problem is enough for you to figure
out the problem, then you don't need to go any further. However, if this is
not the case for you, take a look at the second bit of information that this
error gives us. This error tells you that an exception occurred in an
external object.
Well, that is great information, right? All you need to do is to remove all
calls to external objects on the page and see if it fails. This is usually
not possible since removing all Server.CreateObject statements in an ASP
page would leave your page with only the intrinsic objects, such as
Application, Session, Request, and Response. ASP's power comes from being
able to create an instance of any Active Server Component or COM object. If
you remove all calls to external objects, this leaves you with a pretty
boring page. ASP considers any object that it creates with a
Server.CreateObject statement to be an external object.
============================================================================
Following articles may help:
http://support.microsoft.com/support/kb/articles/q173/7/41.asp?LNG=ENG&SA=AL
LKB
http://support.microsoft.com/support/kb/articles/q244/7/87.asp?LNG=ENG&SA=AL
LKB
http://support.microsoft.com/support/kb/articles/q203/5/73.asp?LNG=ENG&SA=AL
LKB
John Allhiser MCSE CCNA
Network Engineer
Business Men's Assurance
-----Original Message-----
From: John Matteson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 25, 2001 10:13 AM
To: Exchange Discussions
Subject: ASP 0115 Errors on OWA
Good morning to you all:
After closing all watertight doors and hatches and weathering the
latest virus storms, we started having problems with our OWA server. The
problem crops up intermittently with OWA users both from the Internet, from
our VPN and inside the corporate network.
The server is NT 4.0 with the Option Pack IIS 4 installed. All
Service Packs, necessary hotfixes and patches for Nimda and CodeRed were
installed (not confirmed if the rollup security patch was installed).
However, my problem is this, users are getting ASP 0115 errors when
attempting to reach the OWA server. This happens sometimes, before getting
the certificate popup, and sometimes after typing in their userid at the
basic login page. Usually hitting REFRESH will be enough to let the user in,
but sometimes they will have to wait a while, then try again.
I've searched Tech net, but most of the KB's point to coding errors.
All of this is stock coding directly from Microsoft, no locally developed
code at all.
Any suggestions as to where I should start looking to fix this, or
do I need to nuke the server and start again?
John Matteson; Exchange Manager
Geac Corporate Infrastructure Systems and Standards
(404) 239 - 2981
Reduce your stress; Resign as the General Manager of the Universe
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
