Third Party Products
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.
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.
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.
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:
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:
The most common reasons for a commented item to not appear in the output include:
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.
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.
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.
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.
© 2001 - 2009 Pikauba Software. All rights reserved.