Microsoft Knowledge Base Email Alertz

(194190) - When running an Active Server Page (ASP), the following error occurs: ASP 0115 A trappable error has occurred

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 194190 - Last Review: July 3, 2008 - Revision: 6.1

PRB: Error "ASP 0115 a Trappable Error Has Occurred"

This article was previously published under Q194190
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 7.0 running on Microsoft Windows Server 2008. IIS 7.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
http://www.microsoft.com/technet/security/prodtech/IIS.mspx (http://www.microsoft.com/technet/security/prodtech/IIS.mspx)
For more information about IIS 7.0, visit the following Microsoft Web site:
http://www.iis.net/default.aspx?tabid=1 (http://www.iis.net/default.aspx?tabid=1)

SYMPTOMS

When running an Active Server Page (ASP), the following error occurs:
ASP 0115 A trappable error has occurred

CAUSE

An unhandled exception has occurred, and ASP does not have any more information about the error.

Listed below are some of the common causes for ASP returning the 0115 error, followed by some recommended troubleshooting techniques:
  • 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. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
    185874  (http://kbalertz.com/Feedback.aspx?kbNumber=185874/EN-US/ ) How to Troubleshoot Permissions in IIS 4.0
  • Incorrectly registered DLLs or incompatible DLL version issues

    If you are developing applications with Visual Basic for your Web server, you might create a dependency file and compare the file versions to the files installed on your server. For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
    178354  (http://kbalertz.com/Feedback.aspx?kbNumber=178354/EN-US/ ) INFO: How Setup Wizard and PDW Uses Dependency Files
    185599  (http://kbalertz.com/Feedback.aspx?kbNumber=185599/EN-US/ ) BUG: OleAut32.dll Is Unregistered Incorrectly
    145676  (http://kbalertz.com/Feedback.aspx?kbNumber=145676/EN-US/ ) Registry Overwritten with Same ProgID/Different Bitness Server
  • Unhandled errors returned from components
  • Form elements are not namedFor additional information, click the article number below to view the article in the Microsoft Knowledge Base:
    173741  (http://kbalertz.com/Feedback.aspx?kbNumber=173741/EN-US/ ) PRB: Random ASP 0115 Errors when Submitting Form
  • For IIS version 3.0, use of the ASP Session Object prior to version 1.24.09 of the ASP DLLFor additional information, click the article number below to view the article in the Microsoft Knowledge Base:
    177036  (http://kbalertz.com/Feedback.aspx?kbNumber=177036/EN-US/ ) FIX: ASP 115 Error Occur With The Session Object
  • Use of components that are not thread-safe in a multi-threaded environment
    150777  (http://kbalertz.com/Feedback.aspx?kbNumber=150777/EN-US/ ) INFO: Descriptions and Workings of OLE Threading Models
  • Using Microsoft Data Access Components (MDAC) 2.0 on IIS 3.0.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
    193310  (http://kbalertz.com/Feedback.aspx?kbNumber=193310/EN-US/ ) FIX: ADO 2.0 Generates Error 0115 When Used with IIS 3.0

APPLIES TO
  • Microsoft Active Server Pages 2.0
  • Microsoft Internet Information Server 4.0
Keywords: 
kberrmsg kbprb KB194190
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate