PRB: ASP 0115 a Trappable Error Has Occurred

• Active Server Pages

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 machine that is working properly, try comparing key permissions between the two machines.
  
  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 machine. 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, please see the following article in the Microsoft Knowledge Base:
  

  Q185874 TITLE : 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, please see the following article(s) in the Microsoft Knowledge Base:
  

  Q178354 : INFO: Dependency Files and How Setup Wizard/PDW Use Them
  
  Q185599 : BUG: OleAut32.dll Is Unregistered Incorrectly
  
  Q145676 : Registry Overwritten with Same ProgID/Different Bitness Server




• Unhandled errors returned from components



• Form elements are not named For additional information, please see the following article in the Microsoft Knowledge Base:
  

  Q173741 : 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 DLL
  
  For additional information, please see the following article in the Microsoft Knowledge Base:
  

  Q177036 : FIX: ASP 115 Error Occur With The Session Object




• Use of components that are not thread-safe in a multi-threaded environment
  
  For additional information, please see the following articles in the Microsoft Knowledge Base:
  

  Q191979 : PRB: VB Component Not Marked Apartment Produces ASP 0115 Error
  
  Q172925 : INFO: Security Issues with Objects in ASP and ISAPI Extensions
  
  Q150777 : INFO: Descriptions and Workings of OLE Threading Models




• Using Microsoft Data Access Components (MDAC) 2.0 on IIS 3.0.
  
  For additional information, please see the following article in the Microsoft Knowledge Base:
  

  Q193310 : FIX: ADO 2.0 Generates Error 0115 When Used with IIS 3.0

Additional query words:

Keywords          : kberrmsg kbASP kbGrpASP 
Version           : winnt:
Platform          : winnt 
Issue type        : kbprb 

Last Reviewed: May 25, 1999