The following messages result from errors in the Help project file used to build a Help file.
2010 Include statements nested more than 5 deep.
PROBLEM: The #include statement on the specified line exceeds the maximum of five include levels.
RESULT: The compiler aborts the build.
SOLUTION: Simplify the #include statement so that it nests fewer than include levels, and then recompile.
The following messages result from syntax errors in the Help project file.
2030 Comment starting at line linenumber of file filename unclosed at end of file.
PROBLEM: The compiler has unexpectedly come to the end of the Help project file. There may be an open comment in the Help project file or in an include file.
RESULT: The compiler aborts the build.
SOLUTION: Close any open comments within the Help project file, and then recompile.
2050 Invalid #include syntax.
PROBLEM: The #include statement is missing the required filename.
RESULT: The compiler ignores the #include statement.
SOLUTION: Correct the syntax, and then recompile. The correct #include syntax is:
#include <filename>2091 Bracket missing from section heading [sectionname].
PROBLEM: The right bracket (]) is missing from the specified section heading.
RESULT: The compiler ignores the section heading on this line.
SOLUTION: Insert the right section heading bracket, and then recompile.
2111 Section heading missing.
PROBLEM: The section heading on the specified line is not complete, or the first entry in the Help project file is not a section heading.
RESULT: The compiler ignores the section heading on this line and all succeeding lines until it encounters a valid section heading.
SOLUTION: Insert a valid section heading at the appropriate place in the Help project file, and then recompile.
2131 Invalid OPTIONS syntax: ‘option=value’ expected.
PROBLEM: An entry in the [OPTIONS] section is missing the equal sign, or it has some other syntax error.
RESULT: The compiler ignores the invalid option on this line.
SOLUTION: Check the syntax of each option used in the [OPTIONS] section. Fix the incorrect option, and then recompile. For the correct syntax, refer to Chapter 16, “The Help Project File.”
2141 Invalid ALIAS syntax: ‘context=context’ expected.
PROBLEM: An entry in the [ALIAS] section is missing the equal sign, or it has some other syntax error.
RESULT: The compiler ignores the invalid alias string on this line.
SOLUTION: Check the syntax of the entries in the [ALIAS] section. Fix the incorrect entry, and then recompile. For the correct syntax, refer to Chapter 16, “The Help Project File.”
2151 Incomplete line in [sectionname] section.
PROBLEM: An entry in the specified section is incomplete.
RESULT: The compiler ignores the incomplete line.
SOLUTION: Check the section for any incomplete lines and correct them. Then recompile.
2171 Unrecognized text.
PROBLEM: The compiler found some text in the Help project file that it can’t recognize.
RESULT: The compiler ignores the line with the unrecognized text.
SOLUTION: Remove the unsupported text from the Help project file, and then recompile.
2191 Section heading [sectionname] unrecognized.
PROBLEM: The Help project file includes a section heading that the compiler does not recognize or does not support.
RESULT: The compiler ignores the section heading.
SOLUTION: Check all bracketed headings in the Help project file for typographical or other errors. Fix the section heading, and then recompile.
2214 Line in .HPJ file exceeds length limit of 2047 characters.
PROBLEM: There is a line in the Help project file that exceeds the maximum length of 2047 characters.
RESULT: The compiler ignores the line.
SOLUTION: Shorten the line, and then recompile.
The following messages result from general errors in the different sections of the Help project file.
2273 [OPTIONS] should precede [FILES] and [BITMAPS] for all options to take effect.
PROBLEM: The [OPTIONS] section should be the first section in the Help project file so that all the options will be used during compilation. Also, if the ERRORLOG option is used, it should be the first line in the [OPTIONS] section.
RESULT: The Help compiler does not use the ROOT or BMROOT option to locate topic or bitmap files that are listed before the [OPTIONS] section. Also, if the ERRORLOG option is used, the compiler does not write in the log file any errors that were generated before it processed the ERRORLOG option.
SOLUTION: Move the [OPTIONS] section to the beginning of the Help project file, and then recompile.
2291 Section sectionname previously defined.
PROBLEM: The compiler found more than one section with the specified heading in the Help project file.
RESULT: The compiler ignores the duplicate section and continues from the next valid section heading.
SOLUTION: Remove or rename one of the duplicate section headings, and then recompile.
2305 No valid files in [FILES] section.
PROBLEM: The [FILES] section is empty or contains only invalid files.
RESULT: The compiler aborts the build.
SOLUTION: Check the [FILES] section to see if it lists any files. If it does, make sure that the files listed are saved as RTF. After you have a list of valid topic files to include in the build, recompile.
[ALIAS] or [MAP] Section Errors
The following messages result from errors in the [ALIAS] or [MAP] section of the Help project file.
2322 Context string context_name cannot be used as alias string.
PROBLEM: A context string that has been assigned an alias cannot be used later as an alias for another context string. That is, you cannot map a=b and then c=a in the [ALIAS] section.
RESULT: The compiler ignores the attempted reassignment on this line.
SOLUTION: Correct the alias string mapping, and then recompile.
2331 Context number already used in [MAP] section.
PROBLEM: A context number in the [MAP] section of the Help project file was previously mapped to a different context string.
RESULT: The compiler ignores the line with the duplicate context number.
SOLUTION: Check all context numbers to make sure that they are unique. Remove or reassign any duplicate context numbers, and then recompile.
2341 Invalid or missing context string.
PROBLEM: A line in the [MAP] or [ALIAS] section is missing a context string before the equal sign.
RESULT: The compiler ignores the line with the invalid context string.
SOLUTION: Check all context strings to the left of the equal sign. Correct any missing or invalid entries, and then recompile.
2351 Invalid context identification number.
PROBLEM: A context number in the [MAP] or [ALIAS] section is empty or contains invalid characters.
RESULT: The compiler ignores the line with the invalid context number.
SOLUTION: Check the format of all context numbers. Context numbers can be specified as decimal or hexadecimal. Correct any invalid numbers, and then recompile.
2362 Context string context_name already assigned an alias.
PROBLEM: The specified context string has already been assigned an alias in the [ALIAS] section. A context string can have only one alias. That is, you cannot map a=b and then a=c in the [ALIAS] section.
RESULT: The compiler ignores the attempted reassignment on this line.
SOLUTION: Correct the alias string mapping, and then recompile.
2372 Alias string aliasname already assigned.
PROBLEM: You cannot alias an alias. That is, an alias string cannot, in turn, be assigned another alias. You cannot map a=b and then b=c in the [ALIAS] section.
RESULT: The compiler ignores the attempted reassignment on this line.
SOLUTION: Correct the alias string mapping, and then recompile.
The following messages result from errors in the definitions of secondary window types given in the [WINDOWS] section of the Help project file.
2391 Limit of 6 window definitions exceeded.
PROBLEM: The maximum number of window definitions is one main-window definition and five secondary-window definitions.
RESULT: The compiler ignores the additional window definitions.
SOLUTION: Reduce the number of window definitions in the Help project file to five or fewer, and then recompile.
2401 Window maximization state must be 0 or 1.
PROBLEM: The value of the window-state parameter is not zero or 1.
RESULT: The compiler ignores the window definition.
SOLUTION: Correct the entry in the Help project file, and then recompile. The window-state value must be either 0 (normal) or 1 (maximized).
2411 Invalid syntax in window color.
PROBLEM: A window definition in the Help project file has incorrectly defined a window color. A window color definition consists of three decimal numbers, representing the red, green, and blue (RGB) components of the color. The three numbers must be enclosed in parentheses and separated by commas.
RESULT: The compiler ignores the window definition.
SOLUTION: Correct the syntax, and then recompile. The correct syntax for a window color is:
(RRR, GGG, BBB)2421 Invalid window position.
PROBLEM: The window position in a window definition consists of four decimal numbers that define the window’s location on the screen and its width and height. The four numbers must be given in Help’s 1024-by-1024 coordinate system, and they must be enclosed in parentheses and separated by commas.
RESULT: The compiler ignores the window definition.
SOLUTION: Correct the syntax, and then recompile. The correct syntax to indicate the predefined window position is:
(x-coord, y-coord, width, height)2431 Missing quote in window caption.
PROBLEM: The window caption in a window definition must be enclosed in quotation marks.
RESULT: The compiler ignores the window definition.
SOLUTION: Add the missing quotation marks, and then recompile.
2441 Window name windowname is too long.
PROBLEM: The window name exceeds the maximum length of eight characters.
RESULT: The compiler ignores the window definition.
SOLUTION: Shorten the window name to eight or fewer characters, and then recompile.
2451 Window position value out of range 0–1023.
PROBLEM: One or more of the window position coordinates (x-coord, y-coord, width, height) exceed the limit of 1023.
RESULT: The compiler ignores the window definition.
SOLUTION: Correct the numeric values of the window position coordinates so that they fall within the valid range (0–1023), and then recompile.
2461 Window name missing.
PROBLEM: A window definition in the Help project file is missing the window name.
RESULT: The compiler ignores the window definition.
SOLUTION: Specify a name for the window, and then recompile.
2471 Invalid syntax in [WINDOWS] section.
PROBLEM: The entry for a main or a secondary window is incorrect.
RESULT: The compiler ignores the invalid window definition.
SOLUTION: Check the syntax of each window definition, and then recompile. The correct syntax for a window definition is:
window-name="caption", (x-coord, y-coord, width, height), window-state,
(scrolling-RGB), (nonscrolling-RGB), ontop-state2481 Secondary window position required.
PROBLEM: A window definition for a secondary window must specify all four window position parameters—x-coord, y-coord, width, and height—in the Help project file.
RESULT: The compiler ignores the window definition.
SOLUTION: Supply the missing window position parameters, and then recompile.
2491 Duplicate window name windowname.
PROBLEM: The [WINDOWS] section contains window definitions with duplicate window names.
RESULT: The compiler ignores the duplicate window definition.
SOLUTION: Check the uniqueness of each window name, and then recompile.
2501 Window caption windowcaption exceeds limit of 50 characters.
PROBLEM: The caption for the window exceeds the limit of 50 characters.
RESULT: The compiler ignores the window definition.
SOLUTION: Shorten the window caption, and then recompile.
The following error messages are caused by problems in the [OPTIONS] section of the Help project file.
2511 Unrecognized option optionname in [OPTIONS] section.
PROBLEM: The compiler does not recognize or support the specified option.
RESULT: The compiler ignores the unrecognized option.
SOLUTION: Check the [OPTIONS] section for typing errors or invalid options, and then recompile.
2532 Option optionname previously defined.
PROBLEM: The specified option has been defined on a previous line.
RESULT: The compiler uses the first definition and ignores the attempted redefinition.
SOLUTION: Remove one of the duplicate options, and then recompile.
The following error messages are caused by problems with the ROOT or the BMROOT option in the [OPTIONS] section of the Help project file.
2550 Invalid path pathname in optionname option.
PROBLEM: The compiler cannot find the path specified by the ROOT or BMROOT option.
RESULT: The compiler uses the current working directory.
SOLUTION: Correct the path in the ROOT or BMROOT option, and then recompile.
2570 Path in optionname option exceeds number of characters.
PROBLEM: The specified root path exceeds the MS-DOS limit.
RESULT: The compiler ignores the path and uses the current working directory.
SOLUTION: Shorten the path, and then recompile.
The following error messages are caused by problems with the MAPFONTSIZE option in the [OPTIONS] section of the Help project file.
2591 Invalid MAPFONTSIZE option.
PROBLEM: The font range syntax used is invalid. A font range consists of a low and high point size, separated by a hyphen (-).
RESULT: The compiler ignores the option.
SOLUTION: Correct the syntax, and then recompile. The correct syntax is:
MAPFONTSIZE=m[-n]:p2612 Maximum of 5 font ranges exceeded.
PROBLEM: The maximum number of font ranges that can be specified is five.
RESULT: The compiler ignores additional ranges.
SOLUTION: Remove the additional font ranges so that there are five or fewer, and then recompile.
2632 Current font range overlaps previously defined range.
PROBLEM: A font size range overlaps a previously defined mapping.
RESULT: The compiler uses the first range and ignores the second mapping.
SOLUTION: Adjust one or both of the font ranges to remove any overlapping.
The following error messages are caused by problems with the FORCEFONT option in the [OPTIONS] section of the Help project file.
2651 Font name exceeds limit of 20 characters.
PROBLEM: Font names cannot exceed 20 characters.
RESULT: The compiler ignores the option on this line.
SOLUTION: Shorten the font name to 20 or fewer characters, and then recompile.
2672 Unrecognized font name fontname in FORCEFONT option.
PROBLEM: The compiler has encountered a font name that it does not recognize or support.
RESULT: The compiler ignores the font name and uses the default MS Sans Serif font.
SOLUTION: Change the font name to a supported font, and then recompile. For the list of supported fonts, refer to Chapter 16, “The Help Project File.”
The following error messages are caused by problems with the MULTIKEY option in the [OPTIONS] section of the Help project file.
2691 Invalid MULTIKEY option.
PROBLEM: The MULTIKEY option must specify a single capital letter other than the letter K.
RESULT: The compiler ignores the attempted keyword table assignement on this line.
SOLUTION: Correct the syntax, and then recompile. The correct syntax is:
MULTIKEY=char2711 Maximum of 5 keyword tables exceeded.
PROBLEM: The [OPTIONS] section contains more than five MULTIKEY entries, which exceeds the limit of five keyword tables.
RESULT: The compiler ignores the additional keyword tables.
SOLUTION: Reduce the number of keyword tables to five or fewer, and then recompile.
2732 Character already used.
PROBLEM: A character used for indicating the alternate keyword table (MULTIKEY=char) was previously used.
RESULT: The compiler ignores the duplicate keyword table assignment on this line.
SOLUTION: Change the duplicate character to one that has not been used, and then recompile.
2752 Characters ‘K’ and ‘k’ cannot be used.
PROBLEM: These characters are reserved for Help’s standard keyword table.
RESULT: The compiler ignores the attempted keyword table assignment on this line.
SOLUTION: Choose another character for the alternate keyword table, and then recompile.
The following error messages are caused by problems with other options in the [OPTIONS] section of the Help project file.
2771 REPORT option must be ‘ON’ or ‘OFF’.
PROBLEM: The REPORT option specifies an incorrect value.
RESULT: The compiler uses the default value off.
SOLUTION: Correct the entry, and then recompile. The correct syntax is:
REPORT=on/off2811 OLDKEYPHRASE option must be ‘ON’ or ‘OFF’.
PROBLEM: The OLDKEYPHRASE option specifies an incorrect value.
RESULT: The compiler uses the default value on.
SOLUTION: Correct the entry, and then recompile. The correct syntax is:
OLDKEYPHRASE=[off, 0, no, false] or [on, 1, yes, true]2832 COMPRESS option must be ‘OFF’, ‘MEDIUM’, or ‘HIGH’.
PROBLEM: The COMPRESS option specifies an incorrect value.
RESULT: The compiler uses the default value off.
SOLUTION: Correct the entry, and then recompile. The correct syntax is:
COMPRESS=[off, 0, no, false] or [medium] or [on, 1, yes, true, high]2842 OPTCDROM option must be ‘TRUE’ or ‘FALSE’.
PROBLEM: The OPTCDROM option specifies an incorrect value.
RESULT: The compiler uses the default value false.
SOLUTION: Correct the entry, and then recompile. The correct syntax is:
OPTCDROM=[off, 0, no, false] or [on, 1, yes, true]2852 Invalid TITLE option.
PROBLEM: The TITLE option defines a string that is empty or contains more than 32 characters.
RESULT: The compiler truncates the title at 32 characters.
SOLUTION: Add a title if the option is empty or shorten the title if it is too long, and then recompile.
2872 Invalid LANGUAGE option.
PROBLEM: You have specified an ordering that is not supported by the compiler.
RESULT: The compiler uses the default English (U.S.) sorting order.
SOLUTION: Correct the entry, and then recompile. The correct syntax is:
LANGUAGE=scandinavian2893 Warning option must be 1, 2, or 3.
PROBLEM: The warning reporting level can be set only to 1, 2, or 3.
RESULT: The compiler uses full reporting (level 3).
SOLUTION: Correct the entry, and then recompile.
2911 Invalid icon file filename.
PROBLEM: The compiler cannot find the icon file specified in the ICON option, or the file is not a valid icon file.
RESULT: The compiler ignores the file.
SOLUTION: Check to see if the icon file exists and if it is a valid .ICO file. Or if the file is in not in a directory defined by the ROOT or BMROOT option, move the file so that the Help compiler can find it, and then recompile.
2932 Copyright string exceeds limit of 50 characters.
PROBLEM: The maximum length of the copyright string in the About box is 50 characters.
RESULTS: The compiler truncates the copyright string at 50 characters.
SOLUTION: Shorten the copyright notice, and then recompile.
2000 UNKNOWN ERROR, Contact Microsoft Product Support Services
PROBLEM: This error message is the equivalent of an assertion failure.
RESULT: The compiler aborts the build.
SOLUTION: Contact Microsoft Product Support Services.