This is a list of error messages that are visible in Message view on certain conditions.
Code |
Text |
Help Topics |
100 |
INCLUDE file "%s" not found |
Make sure that the include file path in Project Manager is set correctly. |
101 |
Error including file "%s": %s |
For more information about including files, see Including Text from External Files. |
102 |
INCLUDE file "%s" recursively includes itself |
It is not allowed to use an include tag in an included file. For details, see Including Text from External Files. |
106 |
TITLE tag must have an argument |
The argument in the title tag is missing. For details, see Title Tag. |
107 |
TITLEIMG tag argument |
The argument in the titleimg tag is missing. For details, see Property Tags. |
108 |
Multiple TITLE tags | |
109 |
Multiple TITLEIMG tags |
There may only exist one titleimg per topic. For more information about property tags, see Property Tags. |
110 |
TOPICORDER tag must have an integer argument |
The argument in the topicorder tag is missing. For details, see Property Tags. |
111 |
TOPICORDER argument is not an integer value |
The argument of the topicorder tag has to be a number. For details, see Property Tags. |
112 |
Multiple TOPICORDER tags |
There may only exist one topicorder tag per topic. For details, see Property Tags. |
113 |
ALIAS must have an argument |
Make sure there is a topic ID contained in the alias tag. For more information about combining topics, see Multiple Use of Comments. |
114 |
Multiple ALIAS tags |
There may only exist one alias tag per topic. For more information about combining topics, see Multiple Use of Comments. |
115 |
ALIASOF must have at least one argument |
Make sure there is a topic ID enclosed by the aliasof tags. For more information about combining topics, see Multiple Use of Comments. |
116 |
GROUP tag must have at least one name argument |
Make sure there is a topic ID enclosed by the group tags. For more information about groups, see Topic Hierarchy. |
117 |
AUTOLINK must have ON or OFF argument | |
118 |
IMPLEMENTATION must have ON or OFF argument |
Make sure there is ether on or off enclosed by the implementation tags. For details, see Property Tags. |
119 |
Nesting PRE tags within PRE or CODE elements is not allowed |
Make sure that no pre tags are enclosed by pre or code tags. For details, see Character and Paragraph Formatting. |
120 |
/PRE does not have a PRE tag |
For details, see Character and Paragraph Formatting. |
121 |
Nesting CODE tags within PRE or CODE elements is not allowed |
Make sure that no code tags are enclosed by pre or code tags. For details, see Character and Paragraph Formatting. |
122 |
/CODE does not have a CODE tag |
For details, see Character and Paragraph Formatting. |
123 |
Unterminated CODE or PRE tag | |
124 |
COMBINE must have an argument |
Make sure there is a topic ID enclosed by the combine tags. For more information about combining topics, see Multiple Use of Comments. |
125 |
Multiple COMBINE tags |
There may only exist one combine tag per topic. For more information about combining topics, see Multiple Use of Comments. |
126 |
COMBINEWITH must have at least an argument |
Make sure there is at least one topic ID enclosed by the combinewith tags. For more information about combining topics, see Multiple Use of Comments. |
127 |
Javadoc tag @%s ignored |
Not all Javadoc tags are supported by Doc-O-Matic. A list of unsupported Javadoc tags appears on page Javadoc and in the topic Handling Javadoc Tags. |
128 |
Don't know how to handle Javadoc tag @%s |
Indicates a Javadoc tag that is supported by Doc-O-Matic but that has not been given a specific meaning. On the page Edit Sections Javadoc tags can be added as section starter strings. |
129 |
The tag "%s" is not supported in a table |
For example, table tags are not supported in a table. |
130 |
Created 1 automatic link |
For details, see Automatic Linking. |
131 |
Created %d automatic links |
For details, see Automatic Linking. |
132 |
Could not resolve variable "%s" |
Make sure the variable is defined on the AutoDoc > Variables page. For details, see Using Variables. |
133 |
The version information "%s" in VERSIONSPECIFIC is invalid |
The argument of the versionspecific tag has to be a number. For details, see Property Tags. |
134 |
The topic version is not accurate, the version information "%s" does not match the project's version. |
This message informs you that the topic is not exported because its version number does not match the project's version number. For more information about the version-checking feature, see Outdated Topics. |
136 |
Unknown TABLE argument "%s" |
The argument of the table tag can only be noborders. Other arguments are not supported. For details, see Tables. |
137 |
Unknown IMAGE argument "%s" |
The argument of the image tag can either be a filename without path or a filename without path and extension. For details, see Images. |
138 |
HASTOCENTRY must have ON or OFF argument |
Make sure there is ether on or off enclosed by the hastocentry tags. For details, see Property Tags. |
140 |
XML tags are not support in the project |
XML support is not turned on in your project. The support can be turned on on the XMLDoc Support page. For more information about XMLDoc support, see Using XML. |
141 |
Unknown XML tag "%s", ignored |
Make sure that the XML tags you use are known to Doc-O-Matic. You have to insert unknown tags as section starters on the page Sections. |
142 |
The %s tag is superseded by the current setting |
If you use the Contents Designer to rearrange your topics the group, contentsentry and the topicorder directives in your comments are ignored after saving the project. For details, see Topic Hierarchy. |
143 |
STOPFORMAT is ignored |
stopformat tags are ignored. |
144 |
COPY must have an argument |
Make sure there is at least one topic ID enclosed by the copy tags. For more information about combining topics, see Multiple Use of Comments. |
145 |
Multiple COPY tags |
There may only exist one copy tag per topic. For more information about combining topics, see Multiple Use of Comments. |
146 |
COPYTO must have at least one argument |
Make sure there is at least one topic ID enclosed by the copy tags. For more information about combining topics, see Multiple Use of Comments. |
147 |
HASTOCENTRY is ignored |
hastocentry tags are no longer valid. They are ignored. For details, see Property Tags. |
148 |
Malformed EXTERNAL tag |
The external tag is not correctly inserted. For details, see Property Tags. |
149 |
Unknown topic property "%s" |
This value of the property tag is not known to Doc-O-Matic. For details, see XMLDoc Tags. |
150 |
Unknown documentation source "%s" |
This type in the docsource tag is not known to Doc-O-Matic. For details, see XMLDoc Tags. |
151 |
The label "%s" is not defined in this configuration |
Make sure that this label is defined for this configuration on the Text Labels settings page. |
Code |
Text |
Help Topics |
200 |
%s for example "can not create file" or "can not open file" |
This happens if a file used in the project is in use by another program or the directory or the file does not exist. Can not open file appears, if the output format you are exporting is already opened. Close the output format before exporting the documentation again. |
400 |
Fatal Error: Cannot connect to output generator "%s". |
This indicates an installation problem. Reinstall the program or contact support. |
401 |
In topic "%s": %s: Topic with ID "%s" does not exist in this project. |
This message indicates a broken link. The Topic ID of the topic you linked to does not exist in the project. |
402 |
In topic "%s": %s: Topic with ID "%s" exists in this project but it is not exported. |
This message indicates a broken link. The topic to which you linked is not exported. |
403 |
In topic "%s": Link does not have a target. |
For more information about links, see Links. |
404 |
The symbol "%s" does not have a description |
Informs you about an undocumented symbol. |
405 |
One or more parameters of function "%s" do not have a description |
Informs you about an undocumented parameter. |
406 |
The return value of function "%s" does not have a description |
Informs you about an undocumented return value. |
407 |
In topic "%s": The topic has both a COMBINE and an ALIAS target, using the COMBINE target. |
If you add an alias and a combine directive to a topic the combine directive is executed. |
408 |
Export aborted. |
This indicates an installation or another problem. Reinstall the program or contact support. |
409 |
Export aborted by user. |
Informs you about having aborted the export. |
410 |
Fatal Error while generating output: %s |
This is a program problem. Please contact support. |
411 |
One or more parameters of function "%s" do not have a name |
Missing name of a parameter. |
412 |
Error writing link database: %s |
For details, see Link Databases. |
413 |
Error executing custom build command "%s" |
An error occurred while executing the custom build command. |
414 |
Custom build command "%s" returned exit code "%d", build process stopped |
The custom build command has returned an exit code >0 which indicates an error condition. |
Code |
Text |
Meaning/Help Topics |
500 |
Internal Error //: Topic "%s": Don't know how to handle element "%d". |
This is a program problem. Please contact support |
501 |
Topic "%s": Could not find image file for image "%s". |
Make sure the image is located in the image directory to which the image path is set to. For details, see Resolving Images. |
502 |
Error creating file: "%s" |
Make sure the output directory is set correctly. For details, see Saving Output Formats. |
503 |
Error opening file: "%s" |
Make sure the output directory is set correctly. For details, see Saving Output Formats. |
504 |
Fatal Error: "%s" |
This indicates an installation or an another problem. Reinstall the program or contact contact support. |
505 |
Help compiler "%s" does not exist. |
The Help compiler is ether not installed or cannot be found on the inserted path. For details, see Help Compiler. |
506 |
Using color "%s" in raw RGB format. |
Informs you that you have used a RGB value in this color tag. For details, see Colors. |
507 |
Could not convert "%s" into a valid RGB value. |
Make sure the RGB value you used in this color tag is valid. For details, see Colors. |
508 |
Cannot use unmapped color "%s". | |
509 |
Topic "%s": Could not load image file "%s". Error:"%s " |
Make sure you use an image file extension that can be used by the respective output format. For details, see Resolving Images |
530 |
Target ID "%s" does not exist in this project. |
Informs about an invalid link. For details, see Links and Editing Link. |
531 |
Target in EXTLINK missing. |
Make sure there is a topic ID enclosed by the extlink tags. For more information about external links, see Property Tags. and Resolving External Links. |
532 |
The link to topic "%s" could not be resolved because there is no matching target available in the link database. |
Make sure the topic ID you are using as target is available in the link database. For more information about link databases, see Link Databases. |
533 |
No matching EXTLINK tag found for /EXTLINK. |
The extlink tag is missing. For more information about external links, see Links. |
534 |
No image file argument in IMAGE tag. |
Missing file name in the image tag. For more information about inserting images, see Images. |
Code |
Text |
Meaning/Help Topics |
553 |
Error Executing help compiler "%s" |
Make sure the Help compilers are installed correctly and the correct path is set on page HTML Help. |
554 |
Help project file "%s" does not exists.'; |
Make sure the path for the customized Help project file is set correctly. |
555 |
Error: Unterminated PRE or CODE block'; |
Make sure the pre and code tags are terminated. For details, see Character and Paragraph Formatting. |
556 |
Could not delete file "%s". |
Make sure the HTML files are in the folder that is set on HTML page Files and Folders. |
558 |
Could not copy image source file "%s" to output file "%s". |
This error occurs if Doc-O-Matic tries to copy an image file to the output directory and the copy operation fails. Usually this happens, if the file in the output directory exists and is read-only. Make sure no image files in the output directory are read-only. |
559 |
Could not convert image source file "%s" to output file "%s". |
This error occurs when Doc-O-Matic attempts to convert an *.bmp into a *.png graphic file. Make sure no image files in the output directory are read-only. |
560 |
HHC5010: Error: Cannot open "%s". Compilation stopped |
Make sure that the HTML Help is closed before building it again. |
561 |
Frames are not supported in HTML Help, frames will not be used. |
Frames are only supported in WebHelp and Help 2. Frames are not used in HTML Help 1.x. |
562 |
One or more image files missing for dynamic TOC, using static TOC |
The dynamic TOC feature in HTML output works only if the image files used for + - and leaf are available. If these images are missing, the feature will not be used and a static TOC will be generated. |
563 |
One or more output image files are missing (%s). |
This error occurs when Doc-O-Matic could not find one or more image files used as buttons or indicators. |
564 |
Codepage "%s" error. |
The codepage, used to create UTF-8 content either is invalid or not installed on this system. For details, see the Help Project Options settings page. |
565 |
Could not find content placeholder in template file "%s". |
The HTML template does not contain a content placeholder for Doc-O-Matic created output. |
Windows Help
Code |
Text |
Meaning/Help Topic |
580 |
The following font(s) are not available on your system, the filter will use the default system font. |
Generating the Windows Help these fonts have to be available on your system otherwise the default system fonts are used. |
581 |
Font missing: "%s" |
Lists the fonts that are missing on your system. |
582 |
The following font(s) do not support the character set your system is using. Using these fonts may result in unreadable text in the generated documentation:'; |
Select another font that supports your character set. For details, see Creating Outputs in other Languages and Characters. |
583 |
Font character set mismatch: "%s"'; |
Lists the fonts that do not support your character set. |