MS Help Viewer 1.0 applications (HelpLibManager.exe & HelpLibAgent.exe) log all status, warning and error messages to the Windows Application Event Log. This page displays the last 3 days of log events. To see more than 3 days click the "Windows Event Log" link. This will display the full Windows Event Log window. Help Viewer 1.0 logs the following kinds of events: HelpLibManager, HelpLibAgent, Help CacheLib, Help Index, Help Protocol, Help Zip. These are all generated by Help Viewer assemblies.
HLM Example: When you install a help file, HLM typically displays a message such as "The 'p' start tag on line 698 position 9 does not match the end tag body". This gives you enough information to fix the problem. The message is saying it found a <p> tag but found a </body> tag instead of a </p> tag. The <p> tag is not closed. Unfortunately HV 1.0 does not report the name of the source file in error. Use mshcMigrate migrate log to find out which HTML topic file is in error (in the log file, errors are marked with 2x asterisks **).
Finding and Fixing Merge ErrorsHelpLibManager.exe version 1.0 reports errors via the Windows Error Log but does not report the topic file name where the error occurred.
Applications such as mshcMigrate.exe should locate all syntax problems for you.
If not then you could try this binary debug approach:
- Gut your .mshc help package (zip file) of everything except the HTML topic files.
- Delete half the topic files and try to merge.
- Keep deleting and merging until you find the merge error.
Help Viewer 1.0 needs well formed XML (XHTML) so once you find the file in error, open it in something like "MS Expression Web 3.0" which has great XHTML validation. You could also try "HTML Tidy" which is very good at actually fixing XHML syntax problems. If possible you should also validate for correct XML syntax since the Microsoft routines use XML document reader classes to read & parse the help topics.
|
|
