Third Party Products
General Runtime Issues
The issues listed here are general to all Pikauba Software products. If you don't see the issue you're facing, check the ASPHelp, SQLHelp or DBDocumentor sections. Most issues related to DBDocumentor will be found under the SQLHelp section. If after checking these sections, you still don't find a resolution, please drop us an email, with as many details as possible.
This is a pretty rare error, but one faced by users of older systems. Essentially, it is saying that your system is missing some component that Pikauba Software was unable to supply as part of the installation package. Normally, this is a case of the component being part of a much larger package that Microsoft prefers to not be broken up. Thus far we have only come across three situations where this is the case.
If no error box was displayed indicating the absence of the HTML Help compiler, then there are two known causes.
Internet Explorer is required on any system intended to view the compiled output. Under certain circumstances, it may also be required to compile the output. You need not use Internet Explorer for your default browser, it only needs to be installed.
Pikauba Software uses Microsoft's HTML Help workshop compiler to generate the final output.
It can be obtained from one of two sources. First when you start ASPHelp, DBDocumentor, or SQLHelp the application will perform a test of your system. If the HTML Help workshop is missing, pressing the locate button will either take you to the Pikauba web site where you can download it from Microsoft, or will take you directly to the Microsoft download page.
It can also be obtained for free at: http://msdn.microsoft.com/library/default.asp?URL=/library/tools/htmlhelp/chm/hh1start.htm
If you are running in shareware mode (i.e. not registered), each product has a limitation on the number of files you can process. This number was chosen to give a fair evaluation of the software while still leaving an encouragement for users to register. Registration is simple and cost effective.
The licensing agreement is intended to remind users that they are using an unregistered shareware product. It will be shown once per day until registered. Registration is simple and cost effective.
I'm using Windows 2000 (or higher) and it comes with the HTML Help compiler. Why doesn't your product detect this properly?
While it is true that Windows 2000 and higher has the HTML Help compiler installed, that is only part of the Pikauba requirements. Specifically, the compilation process makes use of the HTML Help workshop to perform the bulk of the compilation. Downloading and installing the HTML Help workshop is a simple process.
Note: During installation of the HTML Help workshop on Windows 2000 and higher systems, you may receive a message indicating that the version of the compiler on your system is newer than that in the workshop. It is safe to accept this warning, as the version on your system will be untouched.
When viewing the output from DBDocumentor, ASPHelp, or SQLHelp I don't see my content. How do I resolve this?
If you are accessing the output from a network share, mapped drive, or substituted drive, then you are probably running into a Microsoft security block. The general manifestation of the problem is a properly formed table of contents, but every entry results in either a "The page can not be displayed" or "Action cancelled" error message in the content pane. This problem is the result of some changes Microsoft made to the protocol used to access individual topics within the CHM. The specific security update is 896358.
The following Microsoft TechNote (http://support.microsoft.com/kb/896054/) describes the scenario in detail, along with several options for working around the problem. The recommended solution is to use the workaround from Example #1, where you have the CHM placed in a known, fixed, network location. The registry changes for whichever workaround you choose will be required to be made on all machines which are expected to access the CHM. This problem is one reason why DBDocumentor 4.00 was enhanced to offer an HTML output option.
Recently, Microsoft made another change in the way it processes CHM content. In this scenario, any CHM content obtained from a non-local machine (i.e. not installed as part of an product, or created locally), will be untrusted. Untrusted in this context means that when you open the CHM, you see a properly formed table of contents, but every entry results in either a "The page can not be displayed" or "Action cancelled" error message in the content pane. The specific security update is 902225.
The following Microsoft TechNote (http://support.microsoft.com/default.aspx?scid=kb;en-us;902225) describes the scenario in detail, along with several options for working around the problem.
© 2001 - 2009 Pikauba Software. All rights reserved.