When running an Active Server Page (ASP), the following
error occurs:
ASP 0115 A trappable error has occurred
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://support.microsoft.com/kb/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://support.microsoft.com/kb/178354/EN-US/
)
INFO: How Setup Wizard and PDW Uses Dependency Files
185599
(http://support.microsoft.com/kb/185599/EN-US/
)
BUG: OleAut32.dll Is Unregistered Incorrectly
145676
(http://support.microsoft.com/kb/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://support.microsoft.com/kb/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://support.microsoft.com/kb/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://support.microsoft.com/kb/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://support.microsoft.com/kb/193310/EN-US/
)
FIX: ADO 2.0 Generates Error 0115 When Used with IIS 3.0
Back to the top
