Online Manuals



Installation Issues


Runtime Issues



Third Party Products

Microsoft Security Updates

ASPHelp Runtime Issues

The issues listed here are specific to ASPHelp.  If you do not see the issue you're facing addressed, it may be addressed in the general section, or it may be new to us.  If after checking the general section, you still don't find a resolution, please drop us an email, with as many details as possible.

Table of Contents

  1. I get "Runtime Error 53. File Not Found." after I press Finish.
  2. Not all includes are hyperlinked, why?
  3. Some of the HTML elements in my project are missing in the output.
  4. Some of the ASP elements in my project are missing in the output.
  5. I commented the tag, but it's not in the output.
  6. How do I include custom session objects?
  7. My Functions and Subroutines are not processed?
  8. I get output text indicating that my form was not closed, why?
  9. ASPHelp produces a large number of output files. Is there a way to automatically clean them up?

I get "Runtime Error 53. File Not Found" after I press Finish.

This error indicates one or more configuration files are missing.  If you receive this error, first try reinstalling the ASPHelp, and if that fails, send a file listing for the installation path where ASPHelp is installed to support.  By default, this location is Program Files/ASPHelp.  We will determine which file is missing, and send you an update.  

Beginning with version 1.2 of ASPHelp, this error should never occur.  Rather, if a file is missing a dialog box will indicate which file is missing.

Back to Top

Not all include files are hyperlinked, why?

When viewing the source of an ASP page, you have the option of viewing include files as hyperlinks (i.e. being able to click on them to view the underlying code).  There are a few reasons why these items might not be hyperlinked.

  1. Recurse includes might be off.  In this case, ASPHelp is not aware of the include files presence.
  2. Include includes might be off.  In this case, ASPHelp is aware of the presence of includes, but has not included them at user request.
  3. The include might not be on the local disk.  Since ASPHelp does not work with IIS directly, virtual includes are not always available to it for parsing.  As a result, they won't be included.
  4. The file might be missing.   
Back to Top

Some of the HTML elements in my project are missing in the output.

The HTML parser contained within ASPHelp is currently fairly sensitive to unvalidated HTML.  Examples of poor HTML that may cause ASPHelp to misread HTML elements include: 

  • Failure to close anchor tags
  • Failure to close form blocks
  • Failure to name input elements
  • Failure to reliably use quotes around attributes of HTML tags (e.g. <a href="home.asp name="home">
  • Missing form tags around form elements
Back to Top

Some of the ASP elements in my project are missing in the output.

We have seen this in two distinct situations.

First, if you are using nested With blocks, and each nesting level includes a separate ASP object, misreads can occur.

Secondly, if you set a stock ASP object to a new variable, ASPHelp will not parse information surrounding that new variable.  e.g the following will generate a misread for the variable Item:

Set objRequest = Request

strItem = objRequest.QueryString("Item")

Back to Top

I commented the tag, but it's not in the output.

The most common reasons for a commented item to not appear in the output include:

  1. The tag item physically doesn't exist and you are not using the override tag.  Common examples include typographical errors, and the base tag being missing.  To resolve this, search the ASP for the item you are attempting to document to verify it's presence.
  2. Unless the override is specified, ASPHelp will only document those items it finds.  If a parsing error were to occur, it is possible for the ASP element to exist, but for ASPHelp to believe it missing.
  3. Verify the format of the tag.  Most tags now require a separator between the item name and the comment.  This separator is the ^^ symbol.
Back to Top

How do I include custom session objects?

Custom session objects are defined in the session options tab of step 2.  To define your custom session object, you need to enter the name of the object as used in your page (i.e. if it is named objSession, use objSession), and enter the method name used to access generic variable names.

Note that the object name must be used consistently on all pages otherwise some pages may lack documentation of session object usage.

Back to Top

Why are my functions and subroutines not processed?

Versions of ASPHelp between version 1.1 and 1.5 did not process the contents of any server side functions or subroutines.  Version 1.0 was able to process them, but erroneously included the contents of a function or subroutine, even if it was not used, and only once, even if it were present several times.  This posed a problem when working with script libraries, and method inclusion was dropped temporarily.

Version 1.5 of ASPHelp now includes the contents of server side methods if they are referenced in the server side script of the page, but only if the option check in step 2 is selected.  The default value of this is unchecked for compatibility reasons. 

Back to Top

Why do I get a message in my output text indicating that a form was not closed?

Generally this is caused by unvalidated HTML.  If ASPHelp sees a begin FORM tag in the output HTML stream, it expects that a close FORM tag will also be present.  If it is unable to locate a matching close FORM tag, it will display this condition.  ASPHelp looks for close FORM tags forward from the current open tag until the end of the file, or until a new open FORM tag is located.

If you experience this situation, it will be advisable to run an HTML validator on the page output from your server for the control path in question as there is a strong possibility that you do not have valid HTML on that control path.

Back to Top

ASPHelp produces a large number of output files.  Is there a way to have ASPHelp automatically clean them up?

Prior to version 1.5 of ASPHelp there was no method to automatically clean the temporary output files from the system.  With version 1.5 you can now instruct ASPHelp to remove any temporary files it generates.

Back to Top


© 2001 - 2009 Pikauba Software. All rights reserved.