RE: ASP 0115 Errors on OWA
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=ENGSA=AL LKB http://support.microsoft.com/support/kb/articles/q244/7/87.asp?LNG=ENGSA=AL LKB http://support.microsoft.com/support/kb/articles/q203/5/73.asp?LNG=ENGSA=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]
RE: ASP 0115 Errors on OWA
I had a similar problem after applying the hot fix for the nimda virus.It replaces asp.dll, which was causing asp pages not load properly. I have had to revert back to an earlier asp.dll. The developers are currently looking into the problem -Original Message- From: John Matteson [mailto:[EMAIL PROTECTED]] Sent: 25 September 2001 16:13 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]
RE: ASP 0115 Errors on OWA
YIKES! You are in for a long strange trip indeed. It took us Alliance support, and an onsite MS engineer to get past these problems. I will dig up a final report, and share it with you! Franklin -Original Message- From: John Matteson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 25, 2001 11:13 AM To: Exchange Discussions (E-mail); Advanced Mail Admins (E-mail) 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 Yahoo! Groups Sponsor -~-- Get your FREE VeriSign guide to security solutions for your web site: encrypting transactions, securing intranets, and more! http://us.click.yahoo.com/XrFcOC/m5_CAA/yigFAA/dpFolB/TM -~- Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ _ 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]
RE: ASP 0115 Errors on OWA
Yuck 0115 errors suck. Most of my random ASP 0115 errors went away with some permission changes. Why permission changes fix RANDOM errors I will never know, but it did help us. The following blurb is from this article: http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q194190 Permission and authentication issues with files and registry keys Errors may occur if the authenticated user does not have sufficient permissions on other files such as custom components, system dynamic- link libraries (DLLs), and even registry keys. ASP scripts are typically executed in the security context of the IUSR_machine_name account. If you believe you are dealing with a permissions problem in the registry, you can use Regedt32.exe to examine permissions on the various registry keys. In particular, you may want to look at ODBC, Jet, ADO, and other keys that might be relevant to the problem. If you have a computer that is working properly, try comparing key permissions between the two computers. The first step is to determine if you really are seeing a permissions problem. A good test is to temporarily add the anonymous logon account (IUSR_machine_name) to the administrators group using User Manager. This gives the IUSR_machine_name account administrative privileges on the computer. If this causes ASP to function properly, you are almost certainly dealing with a permissions issue. NOTE : When you have finished debugging, be sure to remove the IUSR_machine_name account from the Administrators group to minimize the security risk on your server. -Original Message- From: John Matteson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 25, 2001 11: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]
RE: ASP 0115 Errors on OWA
An external web development company .They are still working on the problem. I can send you an earlier ver of file if you want to try that. -Original Message- From: John Matteson [mailto:[EMAIL PROTECTED]] Sent: 25 September 2001 16:13 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]
