SQL Doc
Latest version: 2.1
Knowledge Base
Assertion failure outputting in CHM format
Category: Troubleshooting & error messages
Date: 03 Dec 2008
Product: SQL Doc
Versions: 1.x, 2.0
When creating database documentation in Compiled HTML Help (CHM) format, the following error may occur:
Assertion failure: (pszTmp == m_pCompiler->m_pHtmlMem->psz).
There appears to be a limitation on the index size acceptable by Microsoft HTML Help Studio, which SQL Doc uses to create the CHM file. Once the index grows past 3300 entries, HTML Help Studio crashes with this error. Since this software has been supplied by Microsoft, it is impossible for us to resolve the issue.
One possible workaround is to include fewer databases or fewer database objects in the database documentation desired from SQL Doc.
The other possibility is to manually trim the index. SQL Doc should leave all of the CHM source files in the same folder that you have chosen as the output location, in a subfolder whose name contains "_src_".
Open the SQLDoc.hhk file and trim it by removing all text between <LI><OBJECT> and </OBJECT> for each node that you want to exclude from the index.
After you have trimmed the index, you may attempt to compile the project manually using Microsoft HTML Workshop.
Document ID: KB200804000244 Keywords: SQL,Doc,assertion,failure
Was this article helpful?
SQL Doc
- Logging and log files
- Database description runs off page (Version 1.x)
- Changing the project save location (Version 1.x)
- Assertion failure outputting in CHM format
- No database objects are visible for databases using compatibility level 70
- Can't see database objects
- SQL Doc fails with 'Object reference not set to an instance of an object'
- Retaining CHM documentation source files
- Unhandled exception: input string was not in a correct format
- Minimum database permissions required for the user running SQL Doc
- SQL Doc database object description persistence
- Installing HTML Help Workshop fails silently
- Unable to cast object of type 'bn' to type 'bh'
- Logging and log files
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SQL Doc
- Activating your products
- Activating your products
- Getting help offline
- SQL Doc release notes - version 2.xx
all SQL products
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs

Using SQL Doc