This document is a reference guide to MarkLogic Server and MarkLogic Application Services error and log messages. Message text is included for all errors. Possible causes and suggested responses are included for many messages.
Each product or product feature has a unique acronym that forms the beginning of its error codes. In this guide, messages are grouped by product/feature acronym, and then by error code within each group. The product/feature acronyms are described in this table:.
Each MarkLogic error message has a unique error code of the form:
featureId-errorId
The featureId identifies the product or product feature related to the message. The errorId uniquely identifies the error within that product or product feature. Use the error code to quickly locate a message within this guide.
If the MarkLogic error code corresponds to an error condition defined by a related W3C standard, the standard's error code is also listed.
The message text in this guide is the text produced by MarkLogic, with symbolic names substituted for the dynamic, context-sensitive portions. The symbolic names are:
variableN - A piece of dynamic information, generated at runtime. For example, the name of a database, the value of a configuration parameter, or a snippet of incorrect code.exception_stack - Related, cascading errors. Errors reported in the exception_stack often report the underlying problem that caused the most recently reported problem.The Cause section for an error lists possible causes whenever possible. The root cause of an error is usually very context dependent, so the actual cause of your error may not be covered.
The Response section for an error suggests possible solutions or things to check. The root cause of an error is usually very context dependent, so the actual best solution to your problem may not be covered.