44 HELP-00001 to HELP-40001

HELP-00001: Error when creating HelpXmlPullParser due to XmlPullParserException for location: {0}

Cause: An XmlPullParserException was thrown while running _processDocument in the HelpXmlPullParser contructor.

Action: Verify that the location of the JavaHelp-format file exists.

Level: 1

Type: WARNING

Impact: Logging

HELP-00002: Error when creating HelpXmlPullParser due to IOException for location: {0}

Cause: An IOException was thrown when running Process Document in the HelpXmlPullParser contructor.

Action: Verify that the location of the JavaHelp-format file exists

Level: 1

Type: WARNING

Impact: Logging

HELP-00003: Error when executing search in SearchModel.

Cause: SearchModel threw a SearchException when starting the search.

Action: Log a bug against the application.

Level: 1

Type: WARNING

Impact: Logging

HELP-00004: View passed to SearchModel does not contain data in QueryHandler format.

Cause: The view object passed to SearchModel did not contain data in the expected QueryHandler format.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-00005: Unexpected exception occurring in Help Share.

Cause: An unexpected exception occurred in the code.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-00006: Error when parsing document using XML parser

Cause: An XMLParseException was thrown when processing the XML document.

Action: Log a bug against the application.

Level: 1

Type: WARNING

Impact: Logging

HELP-10001: Unexpected exception occurring in OHW Share.

Cause: An unexpected exception occurred in the code.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10002: Adding book {0} to library fails because of LibraryException.

Cause: A LibraryException was thrown.

Action: Log a bug against the application.

Level: 1

Type: WARNING

Impact: Logging

HELP-10003: encountering severe exception when parsing locale from file

Cause: A ConfigParseException was thrown when creating PerLocaleInfo from file.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10004: class name attribute is required on [localeFromProvider]

Cause: The class attribute was missing for the localeFromProvider tag.

Action: Add the class name attribute.

Level: 1

Type: ERROR

Impact: Logging

HELP-10005: error in loading per locale provider {0}

Cause: An unexpected exception was caught when loading the per locale provider.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10006: unrecognized tag {0} in {1} section

Cause: There was an unrecognized tag in the configuration section.

Action: Check the configuration file for unrecognized tags in the configuration section.

Level: 1

Type: ERROR

Impact: Logging

HELP-10007: no [locale] section in [locales]

Cause: The required [locale] section was missing in [locales].

Action: Check the help configuration file to ensure that [locales] has at least one child [locale].

Level: 1

Type: ERROR

Impact: Logging

HELP-10008: error in loading custom protocol class: {0}

Cause: An unexpected exception was caught when loading the Custom Protocol class.

Action: Verify that the Custom Protocol class is valid.

Level: 1

Type: ERROR

Impact: Logging

HELP-10009: error in loading branding provider: {0}

Cause: An unexpected exception was caught when loading the Branding Provider class.

Action: Verify that the Branding Provider class is valid.

Level: 1

Type: ERROR

Impact: Logging

HELP-10010: configuration file is empty

Cause: The Help configuration file was empty.

Action: Verify that the Help configuration file exists and contains content.

Level: 1

Type: ERROR

Impact: Logging

HELP-10011: {0} attribute is required on [helpConfiguration]

Cause: The version attribute was not available on the [helpConfiguration] section.

Action: Add the version attribute to the [helpConfiguration] section of the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10012: Version {0} is not a recognized version. Accepted versions are: {1}

Cause: The version provided was not recognized as an accepted version.

Action: Verify that an accepted version is used in the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10013: duplicate {0} section in the Help configuration file

Cause: There was a duplicate section in the Help configuration file.

Action: Check the Help configuration file for duplicate sections and remove them.

Level: 1

Type: ERROR

Impact: Logging

HELP-10014: tag {0} is not recognized

Cause: Unrecognized tags were found in the Help configuration file.

Action: Remove all unrecognized tags from the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10015: no {0} section found

Cause: A required section was not found in the Help configuration file.

Action: Add the required section to the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10016: Expecting: {0}. Finding: {1}.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-10017: The {0} attribute is missing in [customProtocol].

Cause: The attribute was missing in the Custom Protocol definition.

Action: Add the required attribute to the Custom Protocol definition.

Level: 1

Type: ERROR

Impact: Logging

HELP-10018: The attribute {0} is missing in [alias].

Cause: The required attribute was missing from the navigator alias definition.

Action: Add the required attribute to the navigator alias definition.

Level: 1

Type: ERROR

Impact: Logging

HELP-10019: Text or image source attribute is required in [branding].

Cause: The text or image attribute was missing from the [branding] section of the Help configuration file.

Action: Ensure that the text or image attribute is non-empty and points to a valid location.

Level: 1

Type: ERROR

Impact: Logging

HELP-10020: The {0} attribute on the [branding] tag cannot be empty.

Cause: The required attribute was missing from the [branding] section.

Action: Add the required attribute to the [branding] section.

Level: 1

Type: ERROR

Impact: Logging

HELP-10021: Text key or image source key attribute is required in [brandingFromResource].

Cause: The text key or image source attribute was missing from [brandingFromResource].

Action: Ensure that the text or image attribute is non-empty and points to a valid location.

Level: 1

Type: ERROR

Impact: Logging

HELP-10022: The {0} attribute is required on [brandingFromResource].

Cause: The required attribute was missing from the [brandingFromResource] section.

Action: Add the required attribute to the [brandingFromResource] section.

Level: 1

Type: ERROR

Impact: Logging

HELP-10023: The {0} attribute is required on [brandingFromProvider]

Cause: The required attribute was missing from the [brandingFromProvider] section.

Action: Add the required attribute to the [brandingFromProvider] section.

Level: 1

Type: ERROR

Impact: Logging

HELP-10024: error finding configuration file at: {0}

Cause: The configuration file was not found at the specified location.

Action: Verify that the location of the configuration file is valid.

Level: 1

Type: ERROR

Impact: Logging

HELP-10025: The view {0} with base path {1} passed to the SearchDispatcher does not contain a valid QueryHandler.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-10026: trying to access site with invalid path: {0}

Cause: There was an attempt to access a file through an invalid path.

Action: Verify that the file path is correct.

Level: 1

Type: ERROR

Impact: Logging

HELP-10027: missing or empty {0} attribute in [localeFromFile]

Cause: A required attribute was missing or empty in the [localeFromFile] section.

Action: Add the required attribute to the Help configuartion file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10028: Location of locale file is not valid.

Cause: The location of the locale file was not valid.

Action: Supply a valid location for the locale file in the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10029: Locale file is empty.

Cause: The locale file has no content.

Action: Supply a valid locale file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10030: The locale file cannot be found.

Cause: The locale file was not available at the location specified in the Help configuration file.

Action: Verify that the locale file exists at the location specified in the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10031: The {0} locale is not allowed without a corresponding country section.

Cause: The locale was used without an accompanying country section.

Action: Add a country section for this locale.

Level: 1

Type: ERROR

Impact: Logging

HELP-10032: unrecognized book: {0}

Cause: An unrecognized book tag was found in the Help configuration file.

Action: Check the Help configuartion file for helpSet or helpBook tags and remove or correct the unrecognized book tag.

Level: 1

Type: ERROR

Impact: Logging

HELP-10033: no books in [books] section

Cause: There was no book child in the books parent tag in the Help configuration file.

Action: Add a book child element to the books parent tag.

Level: 1

Type: ERROR

Impact: Logging

HELP-10034: Attribute {0} is missing in helpSet.

Cause: The required attribute was missing from the helpSet tag.

Action: Add the required attribute to the helpSet tag.

Level: 1

Type: ERROR

Impact: Logging

HELP-10035: duplicate helpSet or helpBook {0} : {1}

Cause: A duplicate helpSet or helpBook attribute was encountered.

Action: Remove the duplicate entry from the helpset configuartion file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10036: Location of {0} is not valid.

Cause: The location of the file was not valid.

Action: Ensure that the location of the file is valid.

Level: 1

Type: ERROR

Impact: Logging

HELP-10037: Attribute {0} is missing in helpBook.

Cause: The required attribute was missing from the helpBook tag.

Action: Add the required attribute to the helpBook tag in the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10038: Attribute {0} is missing in contentLocation tag.

Cause: The required attribute was missing from the contentLocation tag.

Action: Add the required attribute to the contentLocation tag in the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10039: Content location is not valid.

Cause: The content location path was invalid.

Action: Ensure that the Help configuration file contains a valid content location base URI.

Level: 1

Type: ERROR

Impact: Logging

HELP-10040: duplicate {0} attribute {1} for content location

Cause: There was a duplicate attribute for the content location.

Action: Remove the duplicate entry from the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10041: Content location is missing or malformed.

Cause: The content location was missing or malformed

Action: Verify that the content location path exists, and that it is a valid path.

Level: 1

Type: ERROR

Impact: Logging

HELP-10042: no known locales

Cause: There was no known locale information available.

Action: Verify that the Help configuration file contains a known locale.

Level: 1

Type: ERROR

Impact: Logging

HELP-10043: CustomProtocolName and converter must not be null.

Cause: The custom protocol name and the converter were not valid.

Action: Verify that the custom protocol name and the converter are not null in the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-10044: PerLocaleConfiguration cannot be used in unloaded state.

Cause: The PerLocaleConfiguration was not loaded into memory before an attempt was made to use it.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10045: error creating book information for id: {0}

Cause: There was an error while creating the book information.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10046: passed null per locale configuration

Cause: A null PerLocaleConfiguartion object was passed.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10047: calling init method for a second time in navigator manager

Cause: The init method was called a second time in AbstractNavigatorManager.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10048: FastMessageFormat supports only numeric arguments.

Cause: The FastMessageFormat method was passed non-numeric arguments.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10049: end of pattern symbol not found

Cause: The end of pattern symbol was not found.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10050: FastMessageFormat: empty argument - {}.

Cause: An empty argument was passed to FastMessageFormat.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10051: The operation {0} is not supported.

Cause: The execution of this method was not supported.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-10052: Search for {0} yielding {1} number of results.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

HELP-10053: Search for {0} yields no results.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Logging

HELP-10054: invalid topic id link: {0} reported from {1}

Cause: An invalid topic id was found.

Action: Review the help topic map file and the topic content file and correct the invalid topic id.

Level: 1

Type: WARNING

Impact: Logging

HELP-10055: trying to access invalid topic id {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-10056: Topic {0} does not have a target that can be followed.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-10057: discovery of a null topic in the Help files

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-10058: (Debug Mode: {0} Missing Helpsets)

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-20001: cannot find global configuration with URL: {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-20002: cannot find required servlet context parameter: {0}

Cause: The required servlet context parameter was not found.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-20003: critical error in OHW configuration

Cause: There was a critical error in the Help configuration file.

Action: Verify the correctness of the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-20004: unrecognized view type {0} is ignored

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-20005: cannot instantiate navigator of type: {0}

Cause: The navigator could not be instantiated.

Action: Verify the correctness of this navigator type in the Help configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-20006: cannot update auto sync component

Cause: There was a failure when updating the auto sync UI component.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-20007: no topic id or topic file for linkHelp=false

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-20008: failure when creating tree model in Rich TOC Navigator

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-20009: failure when trying to index tree model for TOC navigator

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-20010: cannot find required ohwConfigFileURL

Cause: OHW Help Provider requires an OHW configuration file, but this file was not found.

Action: Ensure that the path points to a valid OHW configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-20011: unable to create global configuration

Cause: The global configuration object could not be created.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-20012: unexpected exception when trying to get embedded content for Rich Help Provider

Cause: An unexpected exception was caught when trying to get the embedded content for Rich Help Provider.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-20013: The file protocol suggests that the OHW Config file is not located on local file system.

Cause: OHW Config file is not located on local file system.

Action: Please make sure that the OHW Config file is located on local file system.

Level: 1

Type: WARNING

Impact: Logging

HELP-30001: cannot find required servlet init parameter {0}

Cause: The required init parameter for the Help servlet was not found.

Action: Check the Help servlet definition in the web.xml file of the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-30002: critical error in OHW configuration: {0}

Cause: There was a critical error in the OHW configuration file that caused a MalformedURLException.

Action: Correct the OHW configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-30003: Critical error in OHW configuration. Config URL: {0}

Cause: There was a critical error in the OHW configuration file.

Action: Correct the OHW configuration file.

Level: 1

Type: ERROR

Impact: Logging

HELP-30004: failing to load UIX file

Cause: There was a failure when loading the UIX file.

Action: Ensure that the UIX file is valid.

Level: 1

Type: ERROR

Impact: Logging

HELP-30005: failure to parse {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-30006: cannot find UIX path {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-30007: OHW is encountering an unexpected error.

Cause: There was an unexpected error in OHW-UIX.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-30008: cannot instantiate navigator of type {0}

Cause: The specified navigator could not be instantiated.

Action: Log a bug against the application.

Level: 1

Type: ERROR

Impact: Logging

HELP-30009: cannot load class alias of type {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging

HELP-40001: error when loading icon: {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Logging