Return to Product Support > Learning Center > FAQ

Detecting and debugging errors

Contensive has several error reporting schemes to help detect, locate and debug errors. This is a brief description of error handling processes.

ErrorTrapping

As Microsoft recommends, all asp code should be run from procedures, not at the 'page level'. In the sample code below, we have a recommendation of error trapping and reporting in asp and aspx procedures for Contensive sites.

The Contensive public "ccLib.ErrorTrapping" returns the state of the ErrorTrapping site property. If True, asp errors should be set to On Error Resume Next, and error should be be logged to Contensive with ReportError2().

If a site Developer turns on Verbose Reporting, the state of ErrorTrapping is changed to false, and script errors are allowed to display.

HTML Comment errors

With ErrorTrapping true, all errors on a page are displayed as HTML comments on the page. Tocheck for errors at any point, view source for a brief description of any error.

Error Pop-ups

If you are logged in as a developer, errors produce a pop-up windows with more the extended details about the error.

TrapLog

All errors are logged in the Database in the ccTrapLog table. Under Administration, there is a Trap log report that lets you access this data easily. It can also be found under Trap Logs on the Developer Menu.

TrapLog files

The extended error information is available in the Content files path on the server as well.

Trap Email

If the site properties for SMTP Server and TrapEmail site properties are set, trap errors are sent to the TrapEmail address.

Site Monitoring

The external status method returns the number of errors found during initialization, or "Contensive OK". To call the method, use the following

http://mysite/index.asp?method=status

This page was last reviewed Saturday, April 04, 2009