Microsoft KB Archive/194190

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

Article ID: 194190

Article Last Modified on 5/15/2006

-

APPLIES TO


 * Microsoft Active Server Pages 2.0
 * Microsoft Internet Information Server 4.0

-



This article was previously published under Q194190



We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.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



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_ 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_) to the administrators group using User Manager. This gives the IUSR_ 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_ 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 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 INFO: How Setup Wizard and PDW Uses Dependency Files

185599 BUG: OleAut32.dll Is Unregistered Incorrectly

145676 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 PRB: Random ASP 0115 Errors when Submitting Form

</li> 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 FIX: ASP 115 Error Occur With The Session Object

</li> Use of components that are not thread-safe in a multi-threaded environment

150777 INFO: Descriptions and Workings of OLE Threading Models

</li> 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 FIX: ADO 2.0 Generates Error 0115 When Used with IIS 3.0

</li></ul>

Keywords: kberrmsg kbprb KB194190

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.