Message Text
Transaction variable1 aborted: exception_stack
Cause
A distributed transaction was aborted because at least one participant failed to successfully commit the transaction. The logged message includes the underlying cause in the exception_stack.
Response
Refer to the secondary error messages to determine the root cause of the failure.
W3C XQuery Standard Equivalent: err:XPST0080
Message Text
Invalid cast to abstract type variable1
Cause
Your code attempted to cast a value to xs:Notation or xs:anyAtomicType.
Response
Correct your code.
Message Text
Invalid $cts:action variable1; should be "continue", "break", or "skip"
Cause
An invalid action was specified for $cts:action to a Search Built-in, such as cts:highlight or cts:walk. The only valid values for $cts:action are "continue", "break", and "skip".
Response
Correct your code and retry.
Message Text
Invalid action variable1; should be "continue", "break", or "skip"
Cause
An invalid action was returned from the callback to a Search Built-in, such as cts.highlight or cts.walk. The only valid return values from the callback function are "continue", "break", and "skip".
Response
Correct your code and retry.
Message Text
There can be only one root node.
Message Text
There can be only one root node.
Message Text
There can be only one root node.
Message Text
A document node must be the first node.
Message Text
There can be only one root node.
Message Text
There can be only one root node.
Message Text
There can be only one root node.
Message Text
There can be only one root node.
Message Text
There can be only one root node.
Message Text
This node builder is finished.
Message Text
All forests in the database are retired
Message Text
Application level authentication required
Cause
The operation attempted requires application level authentication. Application-level authentication bypasses all authentication and automatically logs all users in as a specified default user.
Response
Use the Admin Interface to specify a default user and set its permissions. Any users accessing the server automatically inherit the security attributes (roles, privileges, default permissions) of the default user. Application-level authentication is available on HTTP and WebDAV servers.
For more information, see the Understanding and Using Security Guide.
Message Text
variable1 : variable2 is invalid : variable3
Cause
The declaration of the App server is invalid.
Response
Verify that the app server declaration is valid and that it follows the endpoint declaration JSON schema
Message Text
variable1 is invalid
Cause
XDMP-ARG is usually thrown by API functions receiving invalid parameter values. For example, passing xdmp:hex_to_integer an input string that doesn't represent a valid hexadecimal number; or, passing a sequence as an external variable parameter to xdmp:eval or xdmp:invoke.
Response
Correct your code.
Message Text
arg9 is invalid: variable1
Cause
XDMP-ARG-FORESTMAP is usually thrown by API functions receiving invalid parameter values. For example, 1. Keys of the map is not a subset of $forest-ids. Error: XDMP-FORESTMAPNOTSUBSET 2. There are duplicate in values of the map (after supplement of self-mapping). Error: XDMP-FORESTMAPDUPVALUE 3. doesn't appear alone in the first element of the value of a map entry. Error: XDMP-FORESTMAPINVALIDCLEAR
Response
Correct your code.
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
variable1 is not of type variable2
Cause
XDMP-ARGTYPE indicates a mismatch between the actual type (variable1) and expected type (variable2) of a function call argument. For example, passing an empty sequence when a node is expected. The message usually includes context information about the expression where the error occurred.
XDMP-ARGTYPE may also occur as the side-effect of another syntax or semantic error.
Response
Correct your code.
Message Text
Invalid array element
Cause
Invalid array element.
Response
Check element and try again.
Message Text
A cycle was detected in the array entry
Cause
An array cannot be member of itself, either directly or indirectly.
Response
Do not add the array as a member of itself.
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Invalid coercion: variable1 as variable2
Cause
XDMP-AS indicates a mismatch between the actual type (variable1) and expected type (variable2) of an expression. For example, using an empty sequence when a node is expected. The message usually includes context information about the expression where the error occurred.
XDMP-AS may also occur as the side-effect of another syntax or semantic error.
Response
Correct your code.
W3C XQuery Standard Equivalent: err:FOTY0013
Message Text
Functions cannot be atomized
Cause
An attempt was made to atomize a function. This might be via a call to the built-in fn:data function, or implicitly.
Message Text
Attribute with name variable1 already exists
Cause
An update operation such as xdmp:node-insert-child attempted to insert an attribute node for an attribute that already exists.
Message Text
Cannot use variable1 as an attribute name
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Cannot use variable1 as an attribute name
Message Text
No prefix has been defined for attribute namespace URI variable1
W3C XQuery Standard Equivalent: err:XQTY0024
W3C XSLT Standard Equivalent: err:XTDE0410
Message Text
Attribute node cannot follow non-attribute node in element content
Cause
Attribute constructors must appear before any elements or character data in an element constructor.
Response
Correct your code by moving the attribute constructor before any elements or character data in the parent element constructor.
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Invalid attribute value character variable1
Cause
The less-than character (<) may not be used as the literal value of an attribute. Less-than always indicates the beginning of a markup tag.
Response
Correct your code. For example, use a computed attribute constructor.
Message Text
A namespace-qualified attribute name cannot be "xmlns".
Message Text
Authorization mismatch: variable1 specified, server wants variable2
Cause
The client application used an authentication scheme that did not match what MarkLogic Server expected. For example, the client used basic when the server expected digest.
This error sometimes occurs when the browser caches credentials across a change to the server's authentication scheme.
Response
Change the application server's authentication scheme in the Admin Interface, if appropriate. Or, pass the desired authentication scheme as an explicit option:
<options xmlns="xdmp:http">
<authentication method="digest">
<username>myname</username>
<password>mypassword</password>
</authentication>
</options> For more information, see the Understanding and Using Security Guide.
Message Text
$m with identifier variable1
Message Text
AWS KMS error: variable1 variable2: variable3
Cause
An error occurred on the Amazon Web Services Key Management Service.
Message Text
AWS KMS socket error: variable1 variable2 exception_stack
Cause
An error occurred communicating with the Amazon Web Services Key Management Service.
Message Text
Cannot determine AWS service and region from domain 'variable1'
Cause
The domain name used to access an AWS service does not look like an AWS domain name, of the form service.amazonaws.com or service.region.amazonaws.com.
Response
When accessing AWS services use domain names of the form service.amazonaws.com or service.region.amazonaws.com. Examples: s3.amazonaws.com, s3.us-west-1.amazonaws.com, kms.us-east-2.amazonaws.com.
Message Text
Cannot backup to Data directory/subdirectories: variable1
Cause
The configured backup directory is the same as, or is a sub-directory of, MarkLogic's data directory.
Your backup directory may not be inside the MarkLogic Server installation or data area. For example, on Unix, you should not save your backups under /var/opt/MarkLogic or /opt/MarkLogic.
Response
Configure your backups to use a directory that is not inside the MarkLogic Server installation or data directories.
Message Text
Backup data directory is corrupt: variable1
Cause
The backup data directory is corrupted. The error may be caused by file system errors, such has disk failures. Backups cannot proceed until the problem is corrected.
Response
Review the surrounding MarkLogic Server and system error log messages to identify the underlying cause. If you have a current maintenance contract with MarkLogic, you can contact MarkLogic Technical Support for assistance.
Message Text
Backup data directory currently has a backup job in progress: variable1
Cause
A restore was attempted while another process was already running a backup. Or, another process has the backup directory locked.
Response
If there is another backup running, wait for it to complete or kill it.
Message Text
Backup data directory does not exist: variable1 on host variable2
Cause
The configured backup directory does not exist or cannot be found.
Response
Check the existence and permissions of the backup directory. Check your backup configuration for errors in the backup directory name.
Message Text
Not enough disk space for backup: variable1
Cause
The disk containing the backup directory has run out of disk space.
Response
Make more space on your backup disk, or move your backups to a disk with sufficient space.
Message Text
Cannot backup to installation directory/subdirectories: variable1
Cause
Your backup directory is inside the MarkLogic Server installation or data directory tree. For example, on Unix, the backup directory is configured as a sub-directory of /opt/MarkLogic or /var/opt/MarkLogic.
Response
Configure your backups to use a directory that is not inside the MarkLogic Server installation or data directories.
Message Text
Cannot backup to a forest's public data directory/subdirectories: variable1
Cause
The configured backup directory is within a forest's data directory. Your backup directory should not be inside the MarkLogic Server installation or data directory tree. For example, on Unix, the backup directory should not be configured as a sub-directory of /opt/MarkLogic or /var/opt/MarkLogic.
Response
Move your backups to a location outside of any installation or public forest data directories.
Message Text
Error in backup: variable1
Message Text
Restore from incremental backup failed. Documents missing from the catalog.
Message Text
Backup pathname conflicts with data directory: variable1
Cause
The configured backup directory is the same as, or is a sub-directory of, MarkLogic's data directory.
Your backup directory may not be inside the MarkLogic Server installation or data area. For example, on Unix, you should not save your backups under /var/opt/MarkLogic or /opt/MarkLogic.
Response
Configure your backups to use a directory that is not inside the MarkLogic Server installation or data directories.
Message Text
Backup pathname is not a directory: variable1
Cause
You attempted to restore a forest from a pathname that does not refer to a directory.
Response
Confirm the existence of the source directory. Check for broken symbolic links. Correct any typographical errors in the pathname.
Message Text
No forests specified for backup or restore.
Cause
You attempted to start a database backup or restore without including any forests. A backup or restore must include at least one forest.
Response
Change your backup configuration to include at least one forest.
Message Text
Forest variable1 already has backup in variable2
Message Text
Cannot backup in-memory stand: variable1 (variable2 <= variable3 < variable4)
Message Text
Backup pathname conflicts with install directory: variable1
Cause
The configured backup directory is the same as, or is a sub-directory of, MarkLogic's installation directory.
Your backup directory may not be inside the MarkLogic Server installation or data area. For example, on Unix, you should not save your backups under /var/opt/MarkLogic or /opt/MarkLogic.
Response
Configure your backups to use a directory that is not inside the MarkLogic Server installation or data directories.
Message Text
No backup found in backup pathname: variable1
Message Text
Backup passphrase cannot be longer than 1000 characters
Message Text
Backup passphrase cannot be shorter than 16 characters
Message Text
Backup timestamp too old for forest: variable1
Message Text
Bad variable1
Cause
Many different kinds of error can log this message. Refer to the error text for details. Often, XDMP-BAD indicates an unexpected internal error condition.
Response
Refer to the full text of the error for additional information. For more assistance, contact MarkLogic Technical Support if you have a current maintenance contract.
W3C XQuery Standard Equivalent: err:XQST0045
Message Text
Functions annotations may not use a reserved namespace
Cause
A function annotation uses a reserved namespace.
Response
Choose a different namespace.
Message Text
The plugin is compiled for another version of the MarkLogic plugin API. expected: variable1, found: variable2, host: variable3
Cause
The plugin is compiled for another version of the MarkLogic plugin API.
Response
Recompile the plugin, or otherwise obtain a compatible plugin.
Message Text
Arc must span more than 0 degrees and less than 180 degrees, and cannot cross a pole.
Message Text
Invalid box: variable1 > variable2
Cause
Invalid box coordinates were passed to a geospatial query operation such as a box query. For example, the south boundary of the box is above the north boundary.
Response
Correct your code or data.
Message Text
Bad box specification
Cause
An attempt is made to construct a cts:box from a malformed KML Envelope or GML LongLatBox. In particular, the child elements that should be simple values have children of their own.
Response
Fix the GML or KML elements.
Message Text
Bad word break rules: variable1
Cause
The word break rules are invalid for some reason.
Response
Check your word break rules.
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Unexpected character found variable1
Cause
The XQuery lexer found a character where the XQuery language does not permit it to be.
Response
Fix your query to use correct grammar.
Message Text
Invalid circle
Cause
The radius of the cts:circle is too large. The circle cannot cover the entire earth.
Response
Correct your code.
Message Text
Invalid classifier specification element
Cause
An invalid classifier was passed to cts:classify. For example, the element supplied as the classifier parameter is not of type cts:classifier. The classifier is usually created by calling cts:train.
Response
Correct your code.
Message Text
Error in collation variable1
Cause
An invalid or non-existent collation URI was specified.
Response
Correct the collation URI. For more information about collations, see "Encodings and Collations" in the Search Developer's Guide.
Message Text
Commit finds missing fragments
Message Text
Invalid depth (should be "0", "1", or "infinity")
Message Text
Invalid depth (should be "0" or "infinity")
Cause
An invalid value was supplied for depth to a locking function such as xdmp:lock-acquire. The only values allowed are "0" and "infinity".
Message Text
Invalid directory URI
Cause
In invalid directory name was supplied to xdmp:directory-create. For example, an empty string or badly formed URI was passed.
Response
Correct your code.
Message Text
Invalid classifier specification element: document id variable1 not found
Cause
A document used in the training set for a supports type classifier is not a valid document.
A supports type classifier contains a list of document elements which identify the specific training nodes, using an internal key. The internal key is only valid across queries for nodes in the database. If training and classification are done in different queries when the training documents are not in the database, XDMP-BADDOCID is thrown.
Response
Possible solutions include:
Place your training set in the database.
Perform training and classification in the same query.
Use a weights classifier. Weights classifiers do not have this restriction.
Message Text
Bad entity dictionary format: line 'variable1'
W3C XQuery Standard Equivalent: err:XQST0089
Message Text
An "at" variable may not have the same name as the bound variable
Cause
The same variable name is used as both the for variable and its associated positional variable in the at clause. For example:
for $bad-choice at $bad-choice...
Response
Correct your code by using different variables in the for and its at clause.
Message Text
All forests must not be in read-only or flash-backup mode when backing up with journal archiving
Cause
This occurs when trying to do a full database backup with journal archiving enabled and at least one forest is in read-only or flash-backup mode.
Response
Make sure all forests have their update status set to all or delete-only when taking a full database backup with journal archiving.
Message Text
All forests must be in flash-backup mode when running xdmp:start-journal-archiving
Cause
This occurs when running xdmp:start-journal-archiving and at least one forest is not in flash-backup update state.
Message Text
Invalid geometry : variable1
Cause
The provided geometry violates one or more of the required constraints.
Message Text
Invalid geometry type
Cause
The geometry has an unrecognized type.
Message Text
Group separator must be a single character/codepoint.
Cause
The group separator passed to xdmp:format-number contains more than one character or codepoint.
Response
Correct your code to use a single character/codepoint group separator.
Message Text
Bad hex string: variable1 is invalid hex string
Cause
A string that was not a valid hex-encoded binary string was passed as a parameter where one was expected.
Response
Correct your code.
Message Text
Bad journal name: variable1
Cause
This error means a journal file with an unexpected filename was encountered.
Response
If you have a current maintenance contract with MarkLogic, you can contact MarkLogic support.
Message Text
The journal archive is invalid: variable1
Cause
Journal archive file read a bad header frame when resuming journal archiving. This will happen if header stored checksum does not match with its calculated checksum.
Response
Set journaling option to "fast" or "strict" for the database this forest is attached to
Message Text
Invalid classification labels element
Cause
Labels were badly formed.
Message Text
Invalid classification labels element
Cause
An element that is not a cts:label was encountered in the label set passed to cts:train, or a child node that is not a cts:class was encountered on a cts:label.
Message Text
Invalid classification label value: must be 1 or -1
Cause
An invalid value was given on the val attribute of a cts:label element supplied to cts:train. If present, the val must be 1 or -1.
Message Text
Bad tokenizer key language variable1
Message Text
Cannot override stemmer/tokenizer for language variable1
Message Text
The lexer could not be initialized: variable1 lexer invalid
Cause
The lexer was misconfigured or cannot be used for that language.
Response
Check your language configuration.
Message Text
Invalid linestring
Cause
Fewer than two vertices were given when constructing a linestring with cts:linestring.
Response
Correct your code.
Message Text
Incorrect Lock Token
Cause
The file locking token supplied to the app server when acquiring a lock does not match the locking token supplied when releasing the lock. Your WebDAV client may not be working properly.
The WebDAV protocol supports locking of files. When locking a file, a WebDAV client can supply a lock token. When the client is ready to release the lock, the same lock token is supplied. XDMP-BADLOCKTOKEN is thrown when these locking tokens do not match.
Response
Correct the mismatch. If you need assistance determining the cause of the mismatch and have a current maintenance contract, contact MarkLogic Technical Support.
Message Text
The second argument level should be one of the following: emergency, alert, critical, error, warning, notice, info, config, debug, fine, finer, or finest. The default level is "info".
Cause
The second argument of xdmp:log($msg,$level) level is not specified correctly.
Response
Correct your code.
Message Text
Invalid option: 'map' cannot be used with 'array' option
Message Text
Backup data directory was created from a different machine type: variable1 (variable2)
Cause
You attempted to restore from a backup created for a different platform. Backup files are platform-specific. You may not restore a backup to a machine type different from the host where the backup was created.
Response
Restore to a host whose platform matches that of the host that created the backup.
Message Text
Illegal nullable in tuple selector: first tuple selector cannot be nullable: variable1
Cause
The first lexicon selected in cts:value-tuples was given with the option "nullable". This is not allowed.
Response
Remove the "nullable" option from the first lexicon, or reorder the lexicons so that a nullable on is not the first.
Message Text
Invalid occurrence indicator: variable1
Cause
The min-occurs option value is greater than the max-occurs option value in your query. These options to the cts:query constructors constrain searches to return results only if the search terms appear a minimum or a maximum number of times.
Response
Correct your query constructor options.
Message Text
Ordchar argument must be either "yes" or an ordinal character starting followed by a dash "-".
Cause
The ordinal number parameter to xdmp:format-number is not one of:
An empty sequence
The string "yes"
An ordinal string, beginning with a dash ("-").
Response
Correct your code.
Message Text
Invalid processing instruction name "variable1" at variable2 line variable3
Cause
An unrecognized Processing Instruction was encountered while parsing XML data, on line variable3 of the data with URI variable2. The following is an example of an XML processing instruction:
<?xml version="1.0" encoding="UTF-8" ?>
Response
Correct the processing instruction and try the operation again.
Message Text
The plugin does not match the expected version number. expected: variable1, found: variable2, host: variable3
Cause
The plugins loaded on two hosts report different version numbers.
Response
Redeploy your native plugins directory.
Message Text
Bad point specification
Cause
The set of points describing a region or arc in one of the geospatial builtins is invalid. For example, an empty sequence was passed instead of a valid point.
Response
Correct your code.
Message Text
Invalid polygon
Cause
Fewer than three vertices were given when constructing a polygon with cts:polygon.
Response
Correct your code.
Message Text
Malformed property
Cause
Document properties are malformed.
Response
If the error occurs when you are creating properties, correct your code. If the error occurs during operations that use previously supplied properties, then the document properties may be corrupted. If you have a current maintenance contract with MarkLogic, you can contact MarkLogic Technical Support for assistance.
Message Text
The cts reference cannot be used in this context: variable1
Cause
A cts reference was passed to a function that cannot use it.
Response
Use the correct cts reference constructor.
W3C XQuery Standard Equivalent: err:FORX0004
Message Text
Invalid replacement string: variable1
Cause
An invalid replacement string was supplied to fn:replace. The error is usually one of these cases:
The replacement string contains a "$" character that is not immediately followed by a digit 0-9 and not immediately preceded by a "\".
The replacement string contains a "\" character that is not part of a "\\" pair and not immediately followed by a "$" character.
Response
Correct your code.
Message Text
Cannot synchronize as database replica version variable1 mismatches the master version variable2
Message Text
Not all hosts contained the same restore path
Message Text
restore-to-time was less than the earliest full backup time in the folder
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Only use 'return' at the end of a FLWOR expression or typeswitch clause
W3C XQuery Standard Equivalent: err:XQST0012
W3C XSLT Standard Equivalent: err:XTSE0220
Message Text
Invalid schema "variable1" at "variable2" exception_stack
Cause
The schema variable1 at schema URI variable2, used in an XQuery or XSLT schema import, does not meet the validity requirements of XML Schema Part I, as defined by W3C. In a valid schema, all definitions are valid, complete, and unique.
Response
Review and correct your schema. Check for duplicate or erroneous definitions.
Message Text
Invalid scope (should be exclusive or shared)
Response
Correct your code.
Message Text
Bad security database version
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Semicolons are not necessary as a statement separator in XQuery.
Cause
A semicolon was found where the XQuery grammar does not allow one. You might be trying to terminate a statement with a semicolon, like Java and C++ require - but this is not valid in XQuery.
Response
Correct your XQuery. You might find that using a comma (",") is what you want rather than a semicolon.
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Semicolons are not necessary as a statement separator in XQuery. Did you mean to use ','?
Cause
A semicolon was found where the XQuery grammar does not allow one. You might be trying to terminate a statement with a semicolon, like Java and C++ require - but this is not valid in XQuery.
Response
Correct your XQuery. You might find that using a comma (",") is what you want rather than a semicolon.
Message Text
Bad startup token for variable1, variable2 before last journal start variable3
Cause
An inconsistency was discovered between forest label and journal files. MarkLogic was not able to resolve the inconsistency and run recovery on the forest.
Response
Delete both the label and journal files for the forest, and restart the forest. Update your version of MarkLogic to a more recent version.
Message Text
The stemmer could not be initialized: variable1 stemmer invalid
Cause
The stemmer was misconfigured or cannot be used for that language.
Response
Check your language configuration.
Message Text
Invalid tolerance: variable1
Cause
The provided tolerance is invalid. Tolerance must be a positive real number.
Response
Correct your code.
Message Text
Cannot parse binary data as WKB object: WKB 'variable1' is not parsable
Cause
geo:parse-wkb is called with a binary node that cannot be parsed as a WKB object. The data is either malformed or an unsupported WKB type.
Response
Make sure that the data is valid and contains only supported WKB types.
Message Text
Cannot parse string as WKT object: WKT 'variable1' is not parsable
Cause
geo:parse-wkt is called with a string that cannot be parsed as a WKT string. The string is either malformed or an unsupported WKT type.
Response
Make sure that the WKT string is valid and contains only supported WKT types.
Message Text
Base64 binary value too big to be serialized to a string
Cause
Base64 binary values 3GB or larger cannot be serialized to a string.
Response
Use a smaller value.
Message Text
Binary node too big
Cause
Constructed internal binary nodes must be smaller than 4GB.
Response
Use a large binary or external binary instead.
Message Text
Binary read returned empty
Cause
Either the binary node is empty or you used incorrect offset/count.
Response
Check the binary node and your code.
Message Text
Wrong binary size variable1
Cause
Found a large binary file with wrong size during replication. The server will re-replicate the file.
Response
Refer to the full text of the error for additional information. For more assistance, contact MarkLogic Technical Support if you have a current maintenance contract.
Message Text
Bounds must be in strictly ascending order
Response
Correct your latitude or longitude bounds values to be in ascending order.
Message Text
Unable to bulk synchronize forests when merge is disabled
Cause
If merges are disabled, bulk replication will not run since it could cause an excessive number of stands.
Response
Enable merges on the database.
Message Text
Unable to bulk synchronize forest when forest is not open
Cause
The forest must be open to allow bulk synchronization to occur.
Response
Open the forest and try again.
Message Text
Canceled variable1 variable2
Cause
This message usually indicates that an operation such as a merge, backup or query was explicitly canceled. The message includes information about what operation was canceled. Cancellation may occur through the Admin Interface or by calling an explicit cancellation function, such as xdmp:request-cancel.
Message Text
Cannot decrypt: variable1
Cause
There is a key encryption key mismatch
Response
Make sure the text is actually encrypted. If this text was originally encrypted on a different cluster, importing encryption keys from that cluster may allow decryption.
Message Text
Cannot encrypt: variable1
Cause
There is a key encryption key mismatch
Response
Make sure that there are not keystore configuration issues.
Message Text
Geospatial operation not supported on that type of object
Cause
An attempt is made to perform some geospatial operation on a geospatial object that does not support that operation. For example, it is not possible to serialize a cts:box in WKT format, as WKT does not support that type.
Response
Change the application to avoid the unsupported operation.
Message Text
Cannot decode fragset kind variable1
Message Text
Cannot decode locator orderer kind variable1
Message Text
Cannot decode query kind variable1
Message Text
Cannot decode scalar type variable1
W3C XQuery Standard Equivalent: err:FORG0001
Message Text
Invalid cast: variable1 cast as variable2
Cause
An expression or declaration attempted to cast a value to an incompatible type. For example, passing a value to a constructor of a type illegal for the data type being constructed.
Response
Correct your code.
Message Text
A cycle was detected in the variable (cell) update
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Invalid character reference variable1
Cause
variable1 is an invalid character reference. A character references identifies a character by its Unicode codepoint in either decimal or hexadecimal. XDMP-CHARREF may occur if the codepoint value is outside the valid range of values for Unicode or the reference is otherwise malformed.
Response
Correct your code.
Message Text
Character searches not enabled
Message Text
Object nodes cannot have two children with the same name
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Invalid child link node variable1
Cause
A child fragment in a fragmented document is missing.
Response
The document must be reloaded.
W3C XSLT Standard Equivalent: err:XTDE0420
Message Text
variable1 nodes cannot have variable2 node children
Cause
You attempted to insert a node of type variable1 as a child of a node of type variable2 where such insertion is not allowed. This may be occurring through an XQuery built-in, such as xdmp:insert-child, or via an XSLT transformation. One example of such invalid insertion is attempting to add an attribute or namespace node as an immediate child of a document node.
Response
Correct your code.
Message Text
Object nodes cannot have sequence children
Message Text
Object nodes cannot have unnamed children
W3C XQuery Standard Equivalent: err:XQST0054
W3C XSLT Standard Equivalent: err:XTDE0640
Message Text
Circularly defined variable or parameter variable1
Cause
The variable or parameter variable1 depends upon itself.
For example, this error will occur if the initialization of a variable includes a call to function which references the variable.
Response
Correct your code.
Message Text
Invalid Clarked qname "variable1"
Message Text
Detected clock skew: host variable1 skewed by variable2 seconds
Cause
Clock skew is typically due to not having NTP properly functioning on all hosts in the cluster.
Response
Review your NTP configuration/settings
W3C XQuery Standard Equivalent: err:FOCH0001
Message Text
Codepoint not legal
Response
Correct your code.
W3C XQuery Standard Equivalent: err:FOCH0002
Message Text
Unsupported collation: Collation hash variable1 not recognized
Cause
Your database configuration probably includes an invalid collation. For example, the following collation includes contradictory requirements because "S1" specifies case insensitive, but "CU" specifies upper case first:
http://marklogic.com/collation/en/S1/CU/AS/T0020
Response
The exact steps required to correct the problem depend upon the circumstances under which the error is encountered. If the error occurs during startup or as part of an upgrade and you have a current maintenance contract with MarkLogic, you can contact MarkLogic Technical Support for assistance.
Message Text
Incompatible string arguments
Cause
The string arguments to the SPARQL function have incompatible language tags.
Response
Use identical language tags, or strings without language tags.
W3C XQuery Standard Equivalent: err:XQST0038
Message Text
Collation URI variable1 is not valid
Cause
Your XQuery prolog contains more than one default collation declaration, or the default collation declaration specifies an unknown collation.
Response
Correct your code.
Message Text
String objects have different collations
Cause
The String objects have different collations, and cannot be compared.
Response
Consider constructing new String objects, specifying the collation required for comparison.
W3C XQuery Standard Equivalent: err:FODC0004
Message Text
Available collections provides no mapping for URI
Message Text
Collection lexicon not enabled
Message Text
Incompatible collated string arguments
Cause
The string arguments to the function have incompatible collations
Response
Use identical collations, or strings without collations.
W3C XQuery Standard Equivalent: err:XQDY0072
Message Text
XML comments cannot end with a hyphen
Cause
The text in a comment node ends with a hyphen. For example:
comment { "ends with a hyphen -" }Response
Remove the trailing hyphen or add additional text after the hyphen.
W3C XQuery Standard Equivalent: err:XQDY0072
Message Text
XML comments cannot contain two adjacent hyphens
Cause
The text in a comment node contains two adjacent hyphens. For example:
comment { "a -- b" }Response
Correct your code. For example, remove one of the hyphens.
Message Text
Commit option cannot be used in library modules
Cause
Commit option was specified in an XQuery library module.
Response
Move the commit option to the main module.
Message Text
Commit option cannot be specified with transaction mode option
Cause
Commit option was specified in combination with transaction mode option.
Response
Remove the transaction mode option.
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Items not comparable: variable1 variable2 variable3
Message Text
Node has complex content
Cause
An attempt was made to atomize an XML element node that cannot be atomized. The element node has complex content that cannot be converted to an atomic value. Some code is attempting to convert the node to an atomic value.
Response
The code should not explicitly atomize the node by calling fn:data on it. The code should not implicitly atomize the node by passing it as a parameter to a function expecting an atomic value.
Message Text
Compressed tree cache full on host variable1
W3C XQuery Standard Equivalent: err:FORG0006
Message Text
Cannot compute variable2((variable1, variable3))
Message Text
Conflicting updates variable1 and variable2
Cause
The application attempted to perform multiple updates to the same document within the same transaction.
A single statement may not perform more than one update to the same document. For example, you cannot update a node and add a child element to that node in the same statement.
Response
Revise your application code to perform the conflicting operations in two separate statements. For example, use the semicolon transaction delimiter, or execute the second update inside an xdmp:eval with the isolation option set to different-transaction.
For more information, see Understanding Transactions in MarkLogic Server in the Application Developer's Guide.
Message Text
Isolation option value conflicts with transaction mode option
Cause
Isolation option value conflicts with transaction mode option
Response
Remove the transaction mode option.
Message Text
No constraint for variable1
Cause
Your search string included a constraint name that was not found.
Response
Ensure you provide a mapping for the constraint.
W3C XQuery Standard Equivalent: err:XPDY0002
Message Text
Expression depends on the context where none is defined
W3C XQuery Standard Equivalent: err:XPDY0002
Message Text
Context item is not a node
Cause
You tried to operate on the context item as a node when it is an atomic type.
Response
Correct your query.
Message Text
Failed to create soft links for conversion: variable1 'variable2': variable3
Message Text
Invalid xdmp:copy-on-validate option value, must be "true" or "false"
Message Text
Forest cannot be copied into the same location as the current data directory: variable1, variable2
Message Text
read variable1:File corrupt, variable2
Cause
File corruption was detected reading a database file.
Response
Check the operating system error log for file system or storage hardware problems. See the MarkLogic technical note on troubleshooting file corruption issues.
Message Text
Credential variable1 not valid for URL variable2
Message Text
Unable to decrypt credential variable1 variable2
Cause
There is a key encryption key mismatch for this credential
Response
Make sure the text is actually encrypted. If this credential was originally encrypted on a different cluster, importing encryption keys from that cluster may allow decryption. Alternatively, you can update the credential's sensitive information.
Message Text
Credential not valid for signing: variable1
Message Text
Credential is not encrypted
Message Text
Credential in combination with other authentication
Cause
A credential ID was specified along with some other authentication information (user, password, client certificate).
Response
Use either a credential, or authentication, but not both.
W3C XQuery Standard Equivalent: err:XPST0112
Message Text
Function is context dependent: variable1
Cause
You cannot dynamically call a function passed as a value if it depends on aspects of the context in order to execute. Only built-in functions can depend on the context in this way.
Response
You might be able to use another version of the same function where you can explicitly provide the information otherwise used from the context. Or you might want to wrap your call to the function in an explicit inline function such as function($a,$b) { starts-with($a,$b) }.
Message Text
MarkLogic Converters not found
Cause
MarkLogic Converters package is not installed on one or more host.
Response
Install MarkLogic Converters package.
Message Text
Database variable1 is disabled
Cause
This is an internal error, indicating corruption in the memory manager.
Response
If you have a current maintenance contract with MarkLogic, you can contact MarkLogic Technical Support.
Message Text
Invalid Date variable1
Cause
The requested date is before year -9999 or after 9999
Response
Dates outside the range of year -9999 to 9999 are not supported
Message Text
Invalid dateTime variable1
Cause
The value is not a valid dateTime
Response
Review the valid formats for dateTime values.
W3C XQuery Standard Equivalent: err:FORG0008
Message Text
Both arguments to xs:dateTime have timezones
Cause
Evaluated fn:dateTime() where both arguments contain an explicit timezone and the timezones are not equivalent.
Response
When using fn:dateTime ensure that if timezones are specified, they are equivalent in both the date and time arguments, or only present in at most one of the date and time arguments.
W3C XQuery Standard Equivalent: err:FODT0001
Message Text
Overflow in date/time arithmetic
Cause
The date time resulting from a calculation exceeds the range of year -9999 to year 9999
Response
The date time resulting from a calculation exceeds the range of year -9999 to year 9999
Message Text
Failed to parse the dateTime string with the given pattern.
Cause
The dateTime format string was unable to be parsed.
Response
Review the format picture and dateTime string for validity.
Message Text
URI variable1 found in forests variable2 and variable3 with ts=variable4
Cause
The same URI occurs in multiple forests. This may occur if some forests are unavailable during document insert.
Response
Remove the unwanted duplicate document.
Message Text
Assignment policy is not a query policy, on database: variable1
Cause
The assignment policy on the database is not a query policy.
Response
Check your database configuration and make sure it uses the query policy before calling this function.
Message Text
Query timestamp not yet known for database variable1
Message Text
Deadlock detected locking variable1
Cause
A deadlock was detected. When this message occurs at the Debug message level, the deadlock was successfully resolved. When the message occurs at the Notice level, the deadlock was unresolvable.
Deadlocks occur when two transactions are each waiting for the other to release a lock and neither can continue until the other releases the lock. Deadlocks are a normal part of database operations.
MarkLogic Server is designed to automatically detect and resolve deadlocks. When a deadlock is detected, one of the deadlocked transactions is retried, allowing the other to acquire the lock and continue. When this expected behavior occurs, XDMP-DEADLOCK is written to the log file as a Debug message, to indicate that a deadlock occurred and was resolved.
If the deadlock cannot be resolved by repeated retries, the XDMP-DEADLOCK message is written to the log file as a Notice message.
Response
If XDMP-DEADLOCK appears as an infrequent Debug message, no action is required. Deadlocks are a normal part of database operations, and the system successfully resolved the deadlock.
If XDMP-DEADLOCK appears frequently as a Debug message, you may have a performance issue. Revise your query or content structure to reduce the frequency of the deadlock.
If XDMP-DEADLOCK appears as a Notice message, the system was unable to resolve the deadlock. Examine the error message for details about the contentious resource. Revise your query or content structure to avoid the deadlock.
Message Text
Cannot construct from blob: variable1
Message Text
Decompounded word searches not enabled
Message Text
Decompounded word searches cannot be run unstemmed
W3C XQuery Standard Equivalent: err:FOAR0002
Message Text
Decimal overflow
W3C XQuery Standard Equivalent: err:FOTY0015
Message Text
Functions cannot be compared using deep-equal()
Message Text
default-collation option not allowed in this function
Message Text
default-coordinate-system option not allowed in this function
Message Text
Failed to find default calendar. Make sure that calendars.xml is not accidentally modified in your configuration.
Message Text
Failed to find default country. Make sure that countries.xml is not accidentally modified in your configuration.
Message Text
Default namespace is defined
Message Text
Default XQuery version is not recognized: "variable1" (must be "0.9-ml", "1.0", "1.0-ml" or "app-server")
Message Text
Cannot delete constructed nodes
Message Text
Forest variable1 can only perform deletes
Cause
An update or insertion operation was attempted on a delete-only forest. Only read and delete operations are available on documents in a delete-only forest.
Response
Move the target document to a forest which permits update operations, or test whether or not the forest allows updates before attempting the update operation. To test the forest status, use the admin:forest-get-updates-allowed function.
Message Text
Cannot delete external nodes
Message Text
Action on directory failed due to error in processing one of its children: variable2
Message Text
Source and Destination are the same
Message Text
Data Frame buffered read error: variable1
Message Text
Data Frame buffered write error: variable1
Message Text
variable1 and variable2 have different range index types
Cause
A user can specify multiple values in a range query. This error occurs if all the specified values are not of the same data-type.
Response
All values supplied to a range query must be of the same data-type.
Message Text
Cannot process timestamped requests with same-statement isolation
Message Text
Directories cannot be created by adding property only
Message Text
Directory property cannot be deleted or replaced
Message Text
Directory already exists
Cause
xdmp:directory-create called with the name of a directory that already exists; or, the directory target of a WebDAV MKCOL directive already exists.
Response
Correct the code or remove the pre-existing directory.
Message Text
Cannot access directory: variable1
Message Text
Directory cannot be deleted because it is not empty
Message Text
Directory URI path must end with '/'
Response
Correct the code by adding a '/' to the end of the path part of the directory URI. For example:
xdmp:directory-create("the_dir/")Message Text
Service disabled on variable1: variable2
Cause
This message usually indicates the server is shutting down. For example, when you use the Admin Interface to change a configuration parameter that requires a restart, an automatic shutdown and restart occurs. During this shutdown, XDMP-DISABLED may be logged.
Response
If this message appears during an expected shutdown, no action is required. The system is performing as expected.
If this message appears in a context in which shutdown is unexpected, examine the logs for other errors to determine the root cause of the shutdown.
Message Text
Discarding token variable1
Message Text
Disallowed foreign request: variable1
W3C XQuery Standard Equivalent: err:FOAR0001
Message Text
Division by zero
Cause
Denominator was found to be zero.
Response
Check that denominator is not zero before dividing.
Message Text
Invalid attribute value character variable1 or missing close quote at variable2 line variable3
Message Text
Unexpected character found: variable1 at variable2:variable3:variable4
Cause
The document contains syntax errors.
Response
Fix the syntax errors in the document.
Message Text
Incomplete markup in entity value variable1 at variable2 line variable3
Message Text
Unescaped newline characters in document string literal: "variable1" at variable2:variable3:variable4
Cause
The document string literal contains unescaped newline characters.
Response
Escape newline characters using "\n", or use the three quote form of string literal available in turtle.
Message Text
CDATA section outside of content at variable1 line variable2
Message Text
Invalid character reference variable1 at variable2 line variable3
Message Text
Unexpected character variable1 in comment at variable2 line variable3
Cause
Invalid syntax encountered while parsing an XML comment.
Response
Correct the content.
Message Text
Doctype declaration after element content at variable1 line variable2
W3C XQuery Standard Equivalent: err:XQDY0025
Message Text
Two attributes with the same name at variable1 line variable2
Message Text
Unexpected character variable1 in end tag at variable2 line variable3
Message Text
Invalid entity reference variable1 at variable2 line variable3
Cause
The given entity has not been defined, or references an external entity and external entities have been disabled.
Response
Fix the entity reference. Repair options can escape the entity without raising an error.
Message Text
Document exists at destination
Message Text
Invalid hex character reference variable1 at variable2 line variable3
Message Text
Entity reference too deep variable1 at variable2 line variable3
Cause
The XML parser encountered an entity reference that was expanded from another entity reference which was itself expanded from an entity reference and so on, exceeding the maximum allowable depth. This limit is to protect from the billion laughs attack.
<!DOCTYPE lolz [
<!ENTITY lol "lol">
<!ELEMENT lolz (#PCDATA)>
<!ENTITY lol1 "&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;">
<!ENTITY lol2 "&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;&lol1;">
<!ENTITY lol3 "&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;">
<!ENTITY lol4 "&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;">
<!ENTITY lol5 "&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;&lol4;">
<!ENTITY lol6 "&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;&lol5;">
<!ENTITY lol7 "&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;&lol6;">
<!ENTITY lol8 "&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;&lol7;">
<!ENTITY lol9 "&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;&lol8;">
]>
<lolz>&lol9;</lolz>
Response
Correct the content or DTD and re-try the operation.
W3C XQuery Standard Equivalent: err:FODC0005
Message Text
Available documents provides no mapping for URI
Message Text
Expecting end tag variable1 at variable2 line variable3
Message Text
No namespace binding for prefix variable1 at variable2 line variable3
Message Text
Document not found
Cause
No document exists with the document URI specified in an operation such as a document copy, move, or delete.
Response
Correct the URI or code and re-try the operation.
Message Text
No namespace binding for prefix: "variable1" at variable2:variable3:variable4
Cause
The document prefix has not been bound to a namespace URI.
Response
Fix the document to include a prefix binding.
Message Text
Recursive entity reference variable1 at variable2 line variable3
Cause
The XML parser encountered an entity reference that is self-referential. It is possible to create recursive entity references in a DTD. For example, an input document of this form will throw XDMP-DOCRECURSE if read in by xdmp:document-get because the entities ONE and TWO refer to each other:
<?xml version="1.0"?>
<!DOCTYPE RecursiveDTD[
<!ENTITY ZERO "A">
<!ENTITY ONE "&TWO;">
<!ENTITY TWO "&ONE;">
]>
<data>&TWO;</data>
Response
Correct the content or DTD and re-try the operation.
Message Text
Invalid root text variable1 at variable2 line variable3
Cause
Text appears at the root of an XML document. For example:
<?xml version="1.0"?>
text at root
<data>text not at root</data>
Response
Repair the content and re-try the operation. For example, insert a root element:
<?xml version="1.0"?>
<added-root>
text at root
<data>text not at root</data>
</added-root>
Message Text
Unexpected character variable1 in start tag at variable2 line variable3
Message Text
Unexpected end tag variable1 at variable2 line variable3
Message Text
Unexpected end of file at variable1 line variable2 (variable3 starting at line variable4)
Message Text
variable1 at variable2:variable3:variable4
Cause
The document contains syntax errors.
Response
Fix the syntax errors in the document.
Message Text
Invalid URI format: "variable1" at variable2:variable3:variable4
Cause
A URI in the document has invalid syntax.
Response
Correct the URI, or parse using "repair" mode.
Message Text
Invalid UTF-8 escape sequence at variable1 line variable2 -- document is not UTF-8 encoded
Message Text
Invalid UTF-8 escape sequence variable1 at variable2:variable3:variable4 -- document is not UTF-8 encoded
Cause
A bad UTF-8 byte code sequence was found in the document.
Response
Encode your document in UTF-8 correctly.
Message Text
Expecting mandatory whitespace at variable1 line variable2
Message Text
Invalid XML character codepoint variable1 at variable2 line variable3 -- document contains non-XML character
Cause
The XML document contains a codepoint that is not legal XML.
Response
Consider running xdmp:tidy to convert the document to legal XHTML, specifically to replace illegal XML codepoints with benign codepoints.
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Missing $ before variable variable1
Message Text
Database replication is suspended for forest variable1
Cause
Database replication is suspended for that forest
Response
Resume database replication for that forest
W3C XQuery Standard Equivalent: err:XQDY0025
Message Text
Two attributes with the same name
W3C XQuery Standard Equivalent: err:XQST0032
Message Text
Only one base-uri declaration allowed per module
Cause
The XQuery module includes two base-uri declarations.
Response
Remove one of the declarations.
W3C XQuery Standard Equivalent: err:XQST0067
Message Text
Only one construction declaration allowed per module
Cause
The XQuery module includes two construction declarations.
Response
Remove one of the declarations.
W3C XQuery Standard Equivalent: err:XQST0055
Message Text
Only one copy-namespaces declaration allowed per module
Cause
The XQuery module includes two copy-namespace declarations.
Response
Remove one of the declarations.
W3C XQuery Standard Equivalent: err:XQST0038
Message Text
Only one default collation declaration allowed per module
Cause
The XQuery module includes two default collation declarations.
Response
Remove one of the declarations.
W3C XQuery Standard Equivalent: err:XQST0069
Message Text
Only one empty order declaration allowed per module
Cause
The XQuery module includes two empty order declarations.
Response
Remove one of the declarations.
W3C XQuery Standard Equivalent: err:XQST0071
W3C XSLT Standard Equivalent: err:XTDE0430
Message Text
Duplicate namespace declaration variable1
Cause
The XQuery module includes two namespace declarations for the same prefix.
Response
Remove one of the declarations.
W3C XQuery Standard Equivalent: err:XQST0065
Message Text
Only one ordering declaration allowed per module
Cause
The XQuery module includes two ordering declarations.
Response
Remove one of the declarations.
Message Text
Only one "variable1" declaration allowed per module
Cause
The XQuery module includes two prolog declarations that are the same.
Response
Remove one of the declarations.
Message Text
Duplicate rule name in ruleset "variable1": "variable2"
Cause
The ruleset has a rule with the same name as another rule in one of the transitively imported rulesets.
Response
MarkLogic tries to avoid duplicate rules as they inefficient and pointless during inference. Either remove the duplicate rule, or if it is actually different rename it.
W3C XQuery Standard Equivalent: err:XQST0068
Message Text
Only one "variable1" declaration allowed per module
Cause
The XQuery module includes two boundary space declarations.
Response
Remove one of the declarations.
Message Text
Only one validation declaration allowed per module
Cause
The XQuery module includes two validation declarations.
Response
Remove one of the declarations.
Message Text
Transaction with Xid variable1 already exists
Cause
The Xid specified by the XA transaction manager already exists. This indicates that the transaction manager is misbehaving.
Response
Contact your transaction manager vendor with a bug report.
W3C XQuery Standard Equivalent: err:FODT0002
Message Text
Overflow in duration arithmetic
Message Text
Dynamic host with no group
Cause
Environment variable MARKLOGIC_CONNECT_ADDR is specified but MARKLOGIC_GROUP is not.
Response
Specify a group name with MARKLOGIC_GROUP.
Message Text
Connections from dynamic hosts not allowed to variable1
Cause
A dynamic host attempted to connect and dynamic host connections are not allowed.
Response
Enable the "Allow Dynamic Host Connections" trace event on all groups in the cluster.
Message Text
Dynamic hosts not allowed in group variable1
Cause
A dynamic host attempted to join a group that does not allowed it.
Response
Enable the "Allow Dynamic Hosts" trace event on the group.
W3C XQuery Standard Equivalent: err:FORG0006
Message Text
Effective Boolean Value is undefined for variable1
Cause
The sequence cannot be converted into a boolean value using the implicit XQuery effective boolean value operation.
Response
Use a comparison, universal quantification, or otherwise to determine the correct truth for your condition.
Message Text
Ambiguous geospatial variable1 element-attribute index for variable2/@variable3 variable4
Cause
The options provided are not sufficient to uniquely identify an element-attribute geospatial point index.
Response
Specify type, coordinate-system, and/or precision options to uniquely identify an element-attribute geospatial point index.
Message Text
Collations are irrelevant to the geospatial variable1 element-attribute index for variable2/@variable3 variable4
Cause
The options to the query include a collation, but the geospatial point index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
No geospatial variable1 element-attribute index for variable2/@variable3 variable4 variable5
Cause
The query requires a geospatial point index that does not exist.
Response
Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the geospatial variable1 element-attribute index for variable2/@variable3 variable4
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.
Response
Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.
Message Text
No element-attribute word lexicon for variable1/@variable2 variable3
Cause
The query requires a lexicon that does not exist.
Response
Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.
Message Text
Ambiguous geospatial variable1 element-attribute-pair index for variable2/@variable3 variable2/@variable4 variable5
Cause
The options provided are not sufficient to uniquely identify an element-attribute-pair geospatial point index.
Response
Specify type, coordinate-system, and/or precision options to uniquely identify an element-attribute-pair geospatial point index.
Message Text
Collations are irrelevant to the geospatial variable1 element-attribute-pair index for variable2/@variable3 variable2/@variable4 variable5
Cause
The options to the query include a collation, but the geospatial point index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
No geospatial variable1 element-attribute-pair index for variable2/@variable3 variable2/@variable4 variable5 variable6
Cause
The query requires a geospatial point index that does not exist.
Response
Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the geospatial variable1 element-attribute-pair index for variable2/@variable3 variable2/@variable4 variable5
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.
Response
Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.
Message Text
No element-attribute-pair word lexicon for variable1/@variable2 variable1/@variable3 variable4
Cause
The query requires a lexicon that does not exist.
Response
Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.
Message Text
Ambiguous variable1 element-attribute-pair range index for variable2/@variable3 variable2/@variable4 variable5
Cause
The options provided are not sufficient to uniquely identify an element-attribute-pair range index.
Response
Specify type, collation, coordinate-system, and/or precision options to uniquely identify an element-attribute-pair range index.
Message Text
Collations are irrelevant to the variable1 element-attribute-pair range index for variable2/@variable3 variable2/@variable4 variable5
Cause
The options to the query include a collation, but the range index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
Coordinate systems are irrelevant to the variable1 element-attribute-pair range index for variable2/@variable3 variable2/@variable4 variable5
Cause
The options to the query include a coordinate system, but the range index is not a geospatial data type.
Response
Do not specify a coordinate system in the query's options.
Message Text
No variable1 element-attribute-pair range index for variable2/@variable3 variable2/@variable4 variable5 variable6
Cause
The query requires a range index that does not exist.
Response
Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the variable1 element-attribute-pair range index for variable2/@variable3 variable2/@variable4 variable5
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.
Response
Either enable positions on the range index or do not specify "ordered" or "proximity" options.
Message Text
Ambiguous variable1 element-attribute range index for variable2/@variable3 variable4
Cause
The options provided are not sufficient to uniquely identify an element-attribute range index.
Response
Specify type, collation, coordinate-system, and/or precision options to uniquely identify an element-attribute range index.
Message Text
Collations are irrelevant to the variable1 element-attribute range index for variable2/@variable3 variable4
Cause
The options to the query include a collation, but the range index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
Coordinate systems are irrelevant to the variable1 element-attribute range index for variable2/@variable3 variable4
Cause
The options to the query include a coordinate system, but the range index is not a geospatial data type.
Response
Do not specify a coordinate system in the query's options.
Message Text
No variable1 element-attribute range index for variable2/@variable3 variable4 variable5
Cause
The query requires a range index that does not exist.
Response
Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the variable1 element-attribute range index for variable2/@variable3 variable4
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.
Response
Either enable positions on the range index or do not specify "ordered" or "proximity" options.
Message Text
Ambiguous geospatial variable1 element-child index for variable2/variable3 variable4
Cause
The options provided are not sufficient to uniquely identify an element-child geospatial point index.
Response
Specify type, coordinate-system, and/or precision options to uniquely identify an element-child geospatial point index.
Message Text
Collations are irrelevant to the geospatial variable1 element-child index for variable2/variable3 variable4
Cause
The options to the query include a collation, but the geospatial point index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
No geospatial variable1 element-child index for variable2/variable3 variable4 variable5
Cause
The query requires a geospatial point index that does not exist.
Response
Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the geospatial variable1 element-child index for variable2/variable3 variable4
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.
Response
Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.
Message Text
No element-child word lexicon for variable1/variable2 variable3
Cause
The query requires a lexicon that does not exist.
Response
Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.
Message Text
Ambiguous variable1 element-child range index for variable2/variable3 variable4
Cause
The options provided are not sufficient to uniquely identify an element-child range index.
Response
Specify type, collation, coordinate-system, and/or precision options to uniquely identify an element-child range index.
Message Text
Collations are irrelevant to the variable1 element-child range index for variable2/variable3 variable4
Cause
The options to the query include a collation, but the range index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
Coordinate systems are irrelevant to the variable1 element-child range index for variable2/variable3 variable4
Message Text
No variable1 element-child range index for variable2/variable3 variable4 variable5
Cause
The query requires a range index that does not exist.
Response
Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the variable1 element-child range index for variable2/variable3 variable4
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.
Response
Either enable positions on the range index or do not specify "ordered" or "proximity" options.
Message Text
Ambiguous geospatial variable1 element index for variable2 variable3
Cause
The options provided are not sufficient to uniquely identify an element geospatial point index.
Response
Specify type, coordinate-system, and/or precision options to uniquely identify an element geospatial point index.
Message Text
Collations are irrelevant to the geospatial variable1 element index for variable2 variable3
Cause
The options to the query include a collation, but the geospatial point index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
No geospatial variable1 element index for variable2 variable3 variable4
Cause
The query requires a geospatial point index that does not exist.
Response
Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the geospatial variable1 element index for variable2 variable3
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.
Response
Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.
Message Text
No element word lexicon for variable1 variable2
Cause
The query requires a lexicon that does not exist.
Response
Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Cannot use variable1 as an element name
Message Text
Ambiguous geospatial variable1 element-pair index for variable2/variable3 $2/variable4 variable5
Cause
The options provided are not sufficient to uniquely identify an element-pair geospatial point index.
Response
Specify type, coordinate-system, and/or precision options to uniquely identify an element-pair geospatial point index.
Message Text
Collations are irrelevant to the geospatial variable1 element-pair index for variable2/variable3 variable2/variable4 variable5
Cause
The options to the query include a collation, but the geospatial point index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
No geospatial variable1 element-pair index for variable2 variable3 variable4 variable5
Cause
The query requires a geospatial point index that does not exist.
Response
Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the geospatial variable1 element-pair index for variable2/variable3 variable2/variable4 variable5
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.
Response
Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.
Message Text
No element-pair word lexicon for variable1 variable2 variable3
Cause
The query requires a lexicon that does not exist.
Response
Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.
Message Text
Ambiguous variable1 element-pair range index for variable2/variable3 $2/variable4 variable5
Cause
The options provided are not sufficient to uniquely identify an element-pair range index.
Response
Specify type, collation, coordinate-system, and/or precision options to uniquely identify an element-pair range index.
Message Text
Collations are irrelevant to the variable1 element-pair range index for variable2/variable3 variable2/variable4 variable5
Cause
The options to the query include a collation, but the range index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
Coordinate systems are irrelevant to the variable1 element-pair range index for variable2/variable3 variable2/variable4 variable5
Cause
The options to the query include a coordinate system, but the range index is not a geospatial data type.
Response
Do not specify a coordinate system in the query's options.
Message Text
No variable1 element-pair range index for variable2 variable3 variable4 variable5
Cause
The query requires a range index that does not exist.
Response
Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the variable1 element-pair range index for variable2/variable3 variable2/variable4 variable5
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.
Response
Either enable positions on the range index or do not specify "ordered" or "proximity" options.
Message Text
Ambiguous variable1 element range index for variable2 variable3
Cause
The options provided are not sufficient to uniquely identify an element range index.
Response
Specify type, collation, coordinate-system, and/or precision options to uniquely identify an element range index.
Message Text
Collations are irrelevant to the variable1 element range index for variable2 variable3
Cause
The options to the query include a collation, but the range index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
Coordinate systems are irrelevant to the variable1 element range index for variable2 variable3
Cause
The options to the query include a coordinate system, but the range index is not a geospatial data type.
Response
Do not specify a coordinate system in the query's options.
Message Text
No variable1 element range index for variable2 variable3 variable4
Cause
The query requires a range index that does not exist.
Response
Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the variable1 element range index for variable2 variable3
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.
Response
Either enable positions on the range index or do not specify "ordered" or "proximity" options.
Message Text
Node is empty: variable1
W3C XQuery Standard Equivalent: err:XTDE1420
Message Text
Empty sequence not allowed as a base node
Message Text
Empty entity dictionary: no entities found in graph
Cause
The triples in the graph do not follow the patterns necessary to perform the mapping.
Response
Make sure you are using the correct graph URI, the correct SKOS URI (http://www.w3.org/2004/02/skos/core#), and that all your intended entities are a skos:Concept with a skos:prefLabel.
Message Text
Isolation option is empty: variable1
Message Text
Root option is empty: variable1
Message Text
User-id option is empty
Message Text
Default XQuery Version option is empty (must be "0.9-ml", "1.0", "1.0-ml" or "app-server"): variable1
W3C XQuery Standard Equivalent: err:XQST0087
Message Text
Unsupported character encoding: variable1
Message Text
There is no started document.
Message Text
Transaction already ended, variable1
Message Text
There is no started element.
Message Text
Attempt to create a session when calling variable1, which doesn't allow sessions.
Cause
The endpoint attempts to create a session but the declaration doesn't allow sessions.
Response
Correct your code
Message Text
Attempt to create a session with no SessionID when calling variable1.
Cause
The request doesn't contains a SessionID but the endpoint attempts to create a session.
Response
Correct your code
Message Text
variable1 : variable2 is invalid : variable3
Cause
The declaration of the endpoint is invalid.
Response
Correct the declaration
Message Text
variable1 has an invalid value per the endpoint declaration.
Cause
The request contains a parameter with invalid value per the endpoint declaration.
Response
Correct your code or endpoint declaration
Message Text
variable1 is a parameter that doesn't allow multiple values.
Cause
The request contains multiple values for a parameter that can only take one.
Response
Correct the request
Message Text
variable1 is a parameter the request must provide a value for.
Cause
The request contains no value for a parameter that is not nullable.
Response
Correct the request
Message Text
Found SessionID in the request when calling variable1.
Cause
The request contains a SessionID but the endpoint doesn't allow a session.
Response
Correct your code or endpoint declaration
Message Text
No SessionID in the request when calling variable1.
Cause
The request doesn't contain a SessionID but the endpoint requires a session.
Response
Correct your code or endpoint declaration
Message Text
No content type in the request for variable1.
Cause
The request doesn't contain a content type as expected by the endpoint declaration when anyDocument datatype is used.
Response
Correct your code or endpoint declaration
Message Text
variable1 is an unknown parameter.
Cause
The request contains a parameter that is not in the endpoint declaration.
Response
Correct your code or endpoint declaration
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
End tag variable2 does not match start tag variable1
Message Text
Entity enrichment libraries not installed for host variable1
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Invalid entity reference variable1
Message Text
Cannot evaluate library module: variable1
Cause
The specified library module cannot be evaluated.
Response
This error sometimes occurs when a file exists with the same path under the Modules directory and under the App Server root, and if the one under the Modules directory cannot evaluate for some reason (for example, because it is a library module). If this is the case, either fix the module under the Modules directory or use a different name for the module that does not exist under the Modules directory.
Message Text
No query to eval
Message Text
Thread control limits exceeded: host=variable1 limit=variable2 value=variable3
Cause
An app server/xdbc server request exceeded one or more thread control limits set in its endpoint decl file or using request limit APIs. Resource-hungry requests which lead to bad performance on server frequently cause limits exceeded.
Response
If you determine the cause of exceeding the limits is an inefficient or incorrect request, tune your request.
If you determine the cause of this error is inadequate processing limits, you may be able to configure more generous limits through the endpoint decl file or using request limit APIs for current request.
Message Text
Expanded tree cache full on host variable1 uri variable2
Cause
The expanded tree cache ran out of space, preventing completion of the query.
The expanded tree cache stores XML fragments during query processing. The expanded tree cache must be large enough to hold a copy of all expanded XML fragments needed concurrently during query evaluation. Depending on what the query does and how it is constructed, the set of concurrent fragments may not include every fragment used by the query.
Response
This error may be addressed by modifying your query or your cache configuration.
Tune your query to require fewer expanded XML fragments. For example, tune the query to return fewer results or paginate the results.
Tune your query to require fewer concurrent cached fragments.
Increase the size of the expanded tree cache, using the setting under Groups > Default > Configure. Since increasing the cache size may strain other system resources, you should first attempt to modify or tune your query.
If the error occurs only when processing large documents, consider fragmenting your content.
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Invalid expression
Cause
XDMP-EXPR occurs when the operands of an expression have incompatible types. For example, attempting to add a numeric value and a string, or when the actual type of an expression does not match a required expected type.
(: generates XDMP-EXPR :)
let $x = 1 + "abc" ...
XDMP-EXPR may also occur as the side-effect of another syntax or semantic error.
Response
Correct your code.
Message Text
xdmp:value only accepts simple expressions
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
MarkLogic extension syntax used, variable1 are not supported in variable2 mode
Cause
The XQuery syntax used is only available with MarkLogic syntax extensions enabled.
Response
MarkLogic extension syntax can be enabled by using a version declaration of "1.0-ml".
Message Text
Undefined external function variable1
Cause
No implementation can be found for the external function declared.
Response
External functions are not currently supported by MarkLogic - you should provide the body of the function using XQuery.
Message Text
Time limit exceeded
Cause
A query or other operation exceeded its processing time limit. Inefficient queries frequently cause timeouts.
Surrounding messages in the log file may pinpoint the operation which timed out. In the example below, the timeout occurs during re-indexing:
Warning: XDMP-FORESTERR: Error in reindex of forest some_forest:
XDMP-REFRAGMENT: Error refragmenting fn:doc("some_doc"):
XDMP-EXTIME: Time limit exceeded
Response
If you determine the cause of the timeout is an inefficient or incorrect query, tune your query.
If you determine the cause of the time is an inadequate processing limit, you may be able to configure a more generous limit through the Admin Interface.
For more information on configuring timeouts, see the Administrator's Guide.
Message Text
Cannot import extension: variable1
W3C XQuery Standard Equivalent: err:XPDY0003
Message Text
Undefined external parameter variable1
Cause
The external parameter has not had a value assigned to it.
Response
Provide a value for the parameter when calling op:result, xdmp:sparql etc. If you are not using these functions, then MarkLogic has no method to provide values for external parameters - you should assign the parameters a value directly in the query.
W3C XQuery Standard Equivalent: err:XPDY0002
Message Text
Undefined external variable variable1
Cause
The external global variable has not had a value assigned to it.
Response
Provide a value for the variable when calling xdmp:eval, xdmp:invoke etc. If you are not using these functions, then MarkLogic has no method to provide values for external variables - you should assign the global variable a value directly in the query.
Message Text
Limit of external variables exceeded variable1
Message Text
Fatal: variable1
W3C XQuery Standard Equivalent: err:XPST0081
Message Text
Prefix not found in the statically known namespaces: variable1
Message Text
Ambiguous geospatial variable1 field index for variable2 variable3
Cause
The options provided are not sufficient to uniquely identify a field geospatial point index.
Response
Specify type, coordinate-system, and/or precision options to uniquely identify a field geospatial point index.
Message Text
Collations are irrelevant to the geospatial variable1 field index for variable2 variable3
Cause
The options to the query include a collation, but the geospatial point index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
No geospatial variable1 field index for variable2 variable3 variable4
Cause
The query requires a geospatial point index that does not exist.
Response
Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the geospatial variable1 field index for variable2 variable3
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.
Response
Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.
Message Text
No field word lexicon for variable1 variable2
Response
Define a word lexicon and wait for reindexing to complete before using the lexicon functions on the field.
Message Text
Ambiguous variable1 field range index for variable2 variable3
Cause
The options provided are not sufficient to uniquely identify a field range index.
Response
Specify type, collation, coordinate-system, and/or precision options to uniquely identify a field range index.
Message Text
Collations are irrelevant to the variable1 field range index for variable2 variable3
Cause
The options to the query include a collation, but the range index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
Coordinate systems are irrelevant to the variable1 field range index for variable2 variable3
Cause
The options to the query include a coordinate system, but the range index is not a geospatial data type.
Response
Do not specify a coordinate system in the query's options.
Message Text
No variable1 field range index for variable2 variable3 variable4
Cause
The query requires a range index that does not exist.
Response
Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the variable1 field range index for variable2 variable3
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.
Response
Either enable positions on the range index or do not specify "ordered" or "proximity" options.
Message Text
Inconsistent file sizes for variable1: variable2
Cause
The files mentioned in the message should all have the same size except for BinaryKeys, which may have the size of 0. Inconsistent file sizes may indicate a corrupted stand.
Response
Restore the corrupted stand from backup or otherwise recreate it. Please also check your system logs for evidence of file system errors.
W3C XQuery Standard Equivalent: err:XQST0106
Message Text
A function declaration's annotations cannot contain more than one annotation named %fn:private or %fn:public.
Cause
The function declaration contains duplicate %fn:public or %fn:private annotations, or contains both these annotations.
Response
Remove one or more annotations.
Message Text
Backup failed for forest variable1: exception_stack
Message Text
Forest must be attached to a database and merge timestamp in the database must be set to non-zero value when restoring with journal archiving and restore-to-time is zero
Message Text
Forest variable1 is disabled
Cause
The forest is disabled.
Response
Enable the forest.
Message Text
Error in variable1 of forest variable2: exception_stack
Cause
An error occurred while processing the named forest, such as during a re-index or checkpoint operation. The underlying error messages are displayed after the forest name.
Response
Refer to the underlying errors for additional information.
Message Text
Incremental backup failed for forest variable1: exception_stack
Message Text
Forest variable1 not mounted: exception_stack
Cause
XDMP-FORESTMNT is usually seen as a Debug level message when mounting of a forest fails at startup or during a forest restart.
When any instance of MarkLogic Server in a cluster starts up or a forest restarts, each host tries to mount all the forests configured for the entire cluster. A forest is successfully mounted once MarkLogic Server reads the forest information from the forest. If the mounting of a forest fails, XDMP-FORESTMNT is logged and the system retries the mount.
Response
If the message is reported at the Debug level and is eventually followed by a successful mount report, no action is required.
If this message occurs repeatedly, while attempting to mount a remote forest, you may have a network connectivity issue or the machine hosting the forest on local disk may be down.
Message Text
Specified forest variable1 not in database
Message Text
Forest variable1 has no backup since last restore
Message Text
Forest variable1 not available: exception_stack
Cause
The named forest is unavailable for the current operation. The exception_stack shows the underlying errors that caused XDMP-FORESTNOT.
Response
Review the errors in the exception_stack to identify and address the underlying cause. For example, the full error stack might look like:
XDMP-FORESTNOT: Forest Security not available:
XDMP-FORESTERR: Error in startup of forest Security:
XDMP-NOJOURNAL: No journal for recovery token {...}In this case, MarkLogic Server was started by a non-root user, preventing the system from accessing the Security forest.
Message Text
Forest is not in a database: variable1
Cause
This occurs during replication or journal replay if a forest is not assigned to a database.
Response
Assign the forest to a database.
Message Text
Forest variable1 is not local to host variable2
Cause
The server cannot find the forest in question on the current host.
Response
Retry the operation.
Message Text
$m with identifier variable1
Message Text
Forest variable1 has a variable2 operation in progress
Cause
The system attempted to start one forest operation (backup, restore, remove, clear, etc.) while another, exclusive operation was already in progress. For example, starting a new backup while a previous backup is still in progress.
Response
Resolution depends upon the context of the overlapping operations. If you need assistance determining the underlying cause and have a current maintenance contract with MarkLogic, you can contact MarkLogic Technical Support.
Message Text
Restore failed for forest variable1: exception_stack
Message Text
Retired forests don't allow new inserts variable1
Message Text
Bad state transition on Forest variable1 state 'variable2' => 'variable3'
Message Text
Forest variable1 unexpectedly taken by host variable2
Cause
More than one host attempted to write to the same forest label. XDMP-FORESTTAKEN most often occurs when the host reporting the error loses connection with the rest of cluster, yet is still up. The failure sequence may be:
The problem host loses connection with the rest of the cluster and its networked storage. This might be due to excessive load or network connectivity problems.
The cluster detects that the problem host is offline and fails its forests over to other hosts in the cluster.
The problem host rejoins the cluster and discovers its forests have been taken by another host. The problem host then reports
XDMP-FORESTTAKEN and restarts.
Response
If the host reporting XDMP-FORESTTAKEN is actually temporarily disconnected from its cluster, the system is performing as expected. No action is required.
If the cluster disconnection is unexpected, investigate the cause of the interruption. Possible causes include network interrupts, heavy load, or thread starvation on the reporting host.
If the cluster disconnection is due to regular, expected load, consider changing the host timeout or XDQP timeout. For more information, see Configuring Failover for a Forest in the Scalability, Availability, and Failover Guide. Increasing these timeouts increases how long it takes the system to detect and respond to a real outage.
Message Text
Task status unknown for forest variable1 on host variable2
Message Text
Forest variable1 variable2 operation timed out
Message Text
Invalid format (must be "xml", "text", or "binary"): variable1
Cause
Occurs when parsing a document and specifying the document format. The format must be one of "xml", "text", or "binary".
Response
Use a valid document format string, "xml", "text", or "binary".
Message Text
Found stand in forest variable1: variable2
Message Text
Found stands in forest variable1: variable2
Message Text
Cannot cross fragment boundary
Message Text
Fragment with protected path doc("variable1")//variable2
Cause
Fragment with protected path
Response
Check element level security and fragmentation setting for any path overlap.
Message Text
Fragset not found
Cause
When a lexicon function has a query constraint, a request is made to the D-nodes to construct a fragset with the results. If that fragset is not available when later requested the error is thrown. The operation is retried. In normal operations this error is not expected, but may be seen when many facet-heavy operations occur at one time.
Response
The application or system provisioning need to be adjusted.
Message Text
Fragment of variable1 too large for in-memory storage: exception_stack
Cause
The document is too large to load into the database as a single fragment.
Response
Develop and configure a fragmentation strategy or break up the document into smaller pieces.
Message Text
A cycle was detected in the function closure
Cause
A function cannot be member of its own closure, either directly or indirectly.
Response
Do not add the function as a member of itself.
W3C XQuery Standard Equivalent: err:XQST0048
Message Text
Function variable1 not in target namespace variable2
W3C XQuery Standard Equivalent: err:XQST0060
W3C XSLT Standard Equivalent: err:XTSE0740
Message Text
Functions must be declared in a non-empty namespace
Cause
The function was declared using a name in no namespace.
Response
Use a prefix or a default function namespace to put the function in your chosen namespace.
W3C XQuery Standard Equivalent: err:XQST0045
W3C XSLT Standard Equivalent: err:XTSE0080
Message Text
Functions may not be declared in a reserved namespace
Cause
A function was declared in a reserved namespace.
Response
Choose a different namespace for your function.
W3C XQuery Standard Equivalent: err:XPST0008
Message Text
Forward reference to global variable variable1
Cause
A global variable has been referenced before its declaration.
Response
Move the global variable declaration before its reference.
Message Text
Scalar type must be either point or long-lat-point.
Cause
Incorrect "type" option is passed into the geospatial cts reference or query call. Geospatial point range indexes can only be of type "point" or "long-lat-point". Element pair and element attribute pair geospatial point indexes can only be of type "point".
Response
Correct the code.
Message Text
Geohashes cannot be computed for this coordinate system: variable1
Cause
Geohashes can only be calculated for a geographic coordinate system. This error occurs if you attempt to calculate geohashes using a non-geographic coordinate system, such as "raw."
Response
Use a geographic coordinate system, such as "wgs84."
Message Text
Goehash error variable1
Cause
Tolerance is too big for the geohash precision.
Response
Use double precision or use a smaller tolerance or use smaller geoshash precision.
Message Text
Geospatial region index error: variable1 variable2: variable3
Cause
User inserted a document that could not be indexed by the geospatial region index, and the region index is configured to reject invalid values.
Response
Change the data. If the data cannot be changed and you still want to insert the data, then configure the geospatial region index to accept invalid values.
Message Text
No geospatial region index for variable1 variable2
Cause
The query requires a geospatial region index that does not exist.
Response
Make sure the geospatial region index exists and that it uses the coordinate system specified in the query. If the geospatial region index was added recently, make sure reindexing is enabled and has completed.
Message Text
Too many entries in geospatial region index variable1
Message Text
Element variable1 contains invalid geospatial value
Message Text
GetOverlappedResult variable1: variable2
Message Text
Ambiguous geospatial variable1 index for variable2 variable3
Cause
The options provided are not sufficient to uniquely identify a geospatial point index.
Response
Specify type, coordinate-system, and/or precision options to uniquely identify a geospatial point index.
Message Text
Collations are irrelevant to the geospatial variable1 index for variable2 variable3
Cause
The options to cts:reference include a collation, but the geospatial point index is not a string data-type.
Response
Do not specify a collation in the cts:reference's options.
Message Text
No geospatial variable1 index for variable2 variable3 variable4
Cause
The query requires a geospatial point index that does not exist.
Response
Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the geospatial variable1 index for variable2 variable3
Cause
User has specified "ordered" or "proximity" options on cts:value-tuples when positions are not enabled on the geospatial point index.
Response
Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options on cts:value-tuples.
Message Text
GSS Error: variable1
Message Text
Error in GZIP compression
Message Text
Error in GZIP decompression
Message Text
File is too big to be gzipped
Message Text
Retry hash locking. Forests config hash does not match.
Cause
Hash locking sometimes need to retry when forest is added to or removed from a database.
Response
Retry until hash locking occurs.
Message Text
Transaction with identifier variable1 is heuristically committed
Cause
The XA transaction has already been heuristically committed.
Response
Your transaction manager should be handling this error automatically. This usually arises because an administrator explicitly committed a prepared XA transaction without the transaction manager.
Message Text
Transaction with identifier variable1 is heuristically rolled back
Cause
The XA transaction has already been heuristically rolled back.
Response
Your transaction manager should be handling this error automatically. This usually arises because an administrator explicitly rolled back a prepared XA transaction without the transaction manager.
Message Text
Hex binary value too big to be serialized to a string
Cause
Hex binary values 2GB or larger cannot be serialized to a string.
Response
Use a smaller value.
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Invalid hex character reference variable1
Message Text
Host variable1 down: exception_stack
Message Text
Host is offline or not responding
Message Text
Only valid for an HTTP Server
Cause
Occurs when an API that is only supposed to work on an HTTP Server is called in a non-HTTP context.
Response
Fix the application.
Message Text
HTTP CONNECT fails host=variable1:variable2 code=variable3 message="variable4" details=variable5
Cause
Handshake to create HTTP Proxy Tunnel fails.
Response
Check the proxy URL and status of proxy server.
Message Text
Can only PUT/POST binary or text data
Cause
Occurs when data that is neither text nor binary is passed as PUT/POST data.
Response
Fix the application.
Message Text
Only valid for a HTTP request with the multipart/mixed or multipart/related content type
Cause
Occurs when an API that is only supposed to work for a multipart(mixed or related) request is called for other types of request.
Response
Fix the application.
Message Text
Only valid for an HTTP PUT or POST request, not for variable1
Cause
Occurs when an API that is only supposed to work for a HTTP PUT or POST request is called for other types of request.
Response
Fix the application.
Message Text
Failed to convert the date with the given arguments.
Message Text
ignore-amps option not allowed in this function
W3C XQuery Standard Equivalent: err:FOFD1340
W3C XSLT Standard Equivalent: err:XTDE1340
Message Text
Illegal picture format: Numeric presentation marker must end in '1' such as 001
Cause
If a numeric or date/time picture string contains a zero digit then the last digit must be a '1' and correspond to the same unicode range as the zero digit (The codepoint must be one greater than the codepoint used for the zero digit).
Response
When entering the format picture for numeric or date/time formatting functions you must1) use Unicode characters corresponding to the digits '0' and '1'2) they must be in the same Unicode range3) the '1' digit must be the last numeric digit.
W3C XQuery Standard Equivalent: err:FOFD1340
W3C XSLT Standard Equivalent: err:XTDE1340
Message Text
Illegal picture format: Minimum width cannot be more than maximum width
Cause
When specifying a minimum and maximum width such as [M,2-3], the minimum width must be greater or equal to the maximum width
Response
Specify a minimum width greater than or equal to the maximum width or omit both.
W3C XQuery Standard Equivalent: err:FOFD1340
W3C XSLT Standard Equivalent: err:XTDE1340
Message Text
Illegal picture format
Cause
An unexpected character or format in the picture format string.
Response
Check the format string for invalid format or characters.
W3C XQuery Standard Equivalent: err:FOFD1340
W3C XSLT Standard Equivalent: err:XTDE1340
Message Text
Illegal picture format: Variable component in the picture format must close with ']'
Cause
A '[' was found before a matching ']' or no matching ']' was found before the end of the picture string.
Response
Fix the picture string so there are properly matching '[' and ']' characters.
W3C XQuery Standard Equivalent: err:FOFD1340
W3C XSLT Standard Equivalent: err:XTDE1340
Message Text
Illegal picture format: ']' in literal component of the picture must have a following ']'
Cause
*REVIEW: The description is incorrect. should read: Illegal picture format: ']' in literal component of the picture must have a preceding '[' Cause: A ']' was encountered without a matching preceding '['.
Response
Edit the picture string to have matching '[' and ']' or escape the ']' with ']]'
W3C XQuery Standard Equivalent: err:FOFD1340
W3C XSLT Standard Equivalent: err:XTDE1340
Message Text
Illegal picture format. One of the variable markers doesn't have closing square brackets.
Cause
The picture string is missing a closing ']'.
Response
Correct the picture string to properly match '[' and ']'.
Message Text
Binary and Text documents cannot have Processing Instructions or Comments
W3C XQuery Standard Equivalent: err:FOFD1340
W3C XSLT Standard Equivalent: err:XTDE1340
Message Text
Illegal specifier variable1 in the picture format
Cause
An unrecognized specifier was found in the format picture string.
Response
Check and edit the picture format string for valid specifiers.
W3C XQuery Standard Equivalent: err:FOFD1350
W3C XSLT Standard Equivalent: err:XTDE1350
Message Text
Illegal specifier in the picture format
Cause
Caused by including a format specifier inappropriate for the function. For example, using an Hour specifier '[H]' in fn:format-date
Response
Check and correct format specifiers so they are appropriate to the function used.
W3C XQuery Standard Equivalent: err:XQST0047
Message Text
Namespace "variable1" was named in a previous module import, use a comma-separated list of module locations
W3C XQuery Standard Equivalent: err:XQST0059
Message Text
Import module namespace variable1 does not match target namespace variable2 of imported module variable3
W3C XQuery Standard Equivalent: err:XQST0059
Message Text
Cannot import module for namespace URI variable1 without location URI
W3C XQuery Standard Equivalent: err:XQST0088
Message Text
Cannot import module with null namespace
Message Text
Cannot import Main Module variable1
Message Text
Invalid Module Import path: variable1
Message Text
Incompatible collation settings: variable1 and variable2
Message Text
Incompatible fields: variable1 variable2
Cause
You ran a field query with multiple fields having different tokenization rules.
Response
Break the field query into separate field queries.
Message Text
Cannot use variable1 kernel function with variable2 classifier
Message Text
Document incomplete
Message Text
variable1 and variable2 are inconsistent coordinate systems
Cause
A user may specify multiple coordinate-system options for index references, lexicon calls, and queries. This error occurs if the user has specified multiple inconsistent coordinate systems for the same index.
Message Text
variable1 and variable2 are inconsistent geospatial point format options
Cause
A user may specify multiple geospatial point formats for index references, lexicon calls, and queries. This error occurs if the user has specified multiple inconsistent geospatial point format options for the same index.
Message Text
Inconsistent module imports? variable1
Message Text
Inconsistent options variable1 variable2
Message Text
variable1 and variable2 are inconsistent coordinate system precision options
Cause
A user may specify multiple precision options for index references, lexicon calls, and queries. This error occurs if the user has specified multiple inconsistent coordinate system precision options for the same index.
Message Text
variable1 and variable2 are inconsistent range indexes
Cause
A user can specify multiple range indexes in cts:values and related functions. This error occurs if all the specified range indexes do not have the same scalar type, collation, and coordinate system.
Response
All range indexes supplied to cts:values or a related function must be consistent.
Message Text
variable1 and variable2 are inconsistent scalar types
Cause
A user may specify multiple types for index references, lexicon calls, and queries. This error occurs if the user has specified multiple inconsistent types for the same index.
Message Text
Cannot use cached-incremental option with non-zero score function.
Message Text
Attributes not allowed on element variable1
Message Text
Index reference attribute contains an invalid value: variable1
Message Text
Index reference element contains unknown child: variable1
Message Text
Index reference requires a coordinate system: variable1
Message Text
Index reference element variable1 contains unknown child
Message Text
An indexable path must end with a name test: variable1
Cause
User has supplied a path expression that does not end with a name test.
Response
Correct the syntax of path expression such that it ends with a name test.
Message Text
An indexable path must not begin with a self axis: variable1
Cause
User has supplied a path expression that starts with a dot '.'.
Response
Correct the syntax of path expression such that it starts either in an element or a child axis or a descendent axis.
Message Text
Index reference element variable1 contains misplaced text
Message Text
Index reference element contains an invalid value: variable1
W3C XQuery Standard Equivalent: err:FOAR0002
Message Text
A value of +INF or -INF not allowed here
Message Text
The size limit for inferred triples in a ruleset store has been exceeded
Cause
The number of triples inferred by a sem:ruleset-store() during query execution has exceeded the maximum size configured.
Response
Increase the size of the inference memory configured for the sem:ruleset-store() using the "size=" option. You can also configure a higher default inference size using admin:appserver-set-max-inference-size() or the AppServer configuration section of the Admin UI.
Message Text
Cannot move variable1.Document already in forest variable2
Message Text
Request inference size exceeds the maximum allowed.
Message Text
Initialization error: variable2 variable3: variable1
Message Text
InMemoryStand::recoverRangeIndexes: invalid size variable1
Message Text
The size limit for an in-memory triple store has been exceeded
Cause
The number of triples passed to a call to sem:in-memory-store() has exceeded the maximum size allowed.
Response
Use fewer triples in a call to sem:in-memory-store().
Message Text
In-memory storage fullvariable1
Cause
An in-memory list for the index structure filled up and had to be written to disk.
Response
This is a normal artifact when the memory structure fills up. This is a retryable exception and will normally recover seamlessly, causing no problems. If the message occurs infrequently, you can ignore it. If the message occurs frequently, you can raise the cache sizes in the Group configuration, but normally this is not necessary.
Message Text
In-memory geospatial region index storage full variable1
Cause
The in-memory geospatial region index filled up. The stand will write to disk. This message is informational.
Response
This is a normal artifact when the memory structure fills up. This is a retryable exception and will normally recover seamlessly, causing no problems. If the message occurs infrequently, you can ignore it. If the message occurs frequently, you can raise the in-memory geospatial region index size in the Database configuration.
Message Text
In-memory range-index storage fullvariable1
Message Text
In-memory list storage fullvariable1
Cause
The in-memory list storage filled up. The stand will write to disk. This message is informational.
Response
This message is informational. No action is required.
Message Text
In-memory tree storage fullvariable1
Message Text
In-memory triple storage fullvariable1
Message Text
In-memory reverse-index storage fullvariable1
Cause
An error was returned to MarkLogic while it was processing input to create a document. Details about the error are not known.
Response
Check the contents of the input source. Upgrade to a more recent version of MarkLogic for more error details.
Message Text
Internal error: variable1
Cause
A MarkLogic internal error has occurred.
Response
Report this error to MarkLogic as a bug.
Message Text
Internal error [2] in formatter
Cause
A MarkLogic internal error has occurred.
Response
Report this error to MarkLogic as a bug.
Message Text
Internal error [3] in formatter
Cause
A MarkLogic internal error has occurred.
Response
Report this error to MarkLogic as a bug.
Message Text
Internal error [4] in formatter
Cause
A MarkLogic internal error has occurred.
Response
Report this error to MarkLogic as a bug.
Message Text
Internal error [5] in formatter
Cause
A MarkLogic internal error has occurred.
Response
Report this error to MarkLogic as a bug.
Message Text
Internal error [6] in formatter
Cause
A MarkLogic internal error has occurred.
Response
Report this error to MarkLogic as a bug.
Message Text
Internal error [7] in formatter
Cause
A MarkLogic internal error has occurred.
Response
Report this error to MarkLogic as a bug.
Message Text
Invalid data specified. variable1
Message Text
Invalid percentage: must be between 0 and 1 (inclusive)
Cause
The percentage is invalid.
Response
Correct your code.
Message Text
Invalid trailing search pattern: variable1
Message Text
The api declaration with path variable1 is invalid.
Cause
The api declaration JSON document is ill-formatted.
Response
Correct the format of the api declaration
Message Text
Path is invalid as data directory: variable1
Message Text
Expecting an encoding of either hex or base64.
Message Text
Invalid lower bound: variable1
Cause
The lower bound has a data type that doesn't match the partition key.
Response
Check your configuration.
Message Text
Invalid range boundaries: variable1
Cause
The lower bound is not smaller than the upper bound.
Response
Check your configuration.
Message Text
The node does not represent a valid triple
Cause
The node is not an element or document node with element child, or it that element does not contain an "s", "p", or "o" child element.
Response
Correct the triple format.
Message Text
The JavaScript object or map:map does not represent a valid triple
Message Text
The object node does not represent a valid triple
Message Text
Invalid upper bound: variable1
Cause
The upper bound has a data type that doesn't match the partition key.
Response
Check your configuration.
W3C XQuery Standard Equivalent: err:XTDE1420
Message Text
URI(s) can only be of types xs:string, xs:anyURI, xs:untypedAtomic or base URI of a node.
Message Text
Invalid activeLock element: variable1
Message Text
Transaction with identifier variable1 references database variable2, but the current database is variable3
Cause
The transaction specified does not reference the specified database.
Response
You may be calling a REST service with a transaction and database specified that do not match.
Message Text
Invalid authorization attribute: variable1
Message Text
Invalid authorization method: variable1
Message Text
Invalid binding for key 'variable1'
Cause
Bindings for cts:parse must have values that are strings or range index references.
Response
Put appropriate values into the binding map.
Message Text
Invalid callback function for 'variable1'
Cause
The key was bound to a callback function which was not valid.
Response
Fix the callback function or the callback bindings.
Message Text
Invalid character class for default-script: variable1
Message Text
The minimum number of clusters cannot be greater than maximum number
Message Text
Server has invalid config files: variable1
Message Text
Invalid coordinate system variable1
Cause
An invalid coordinate system name was specified.
Response
Correct the coordinate system name.
Message Text
Invalid Database Online event
Cause
An error occurred during execution of the database online trigger event handler. This error most often occurs when the cpf:restart trigger runs under an invalid user id.
During installation, the Content Processing Framework configures the cpf:restart trigger to run as the admin user at the time of installation. If the configured user id is removed, the XDMP-INVDATABASEONLINEEVENT error is logged.
Response
If you suspect the cpf:restart trigger is running under an invalid user id, check and correct the user id in the trgr:database-online-event/trgr:user element. See the Triggers Module of the XQuery API Reference.
Message Text
Invalid trigger data event definition
Message Text
Invalid dictionary variable1
Message Text
Invalid geohash variable1
Cause
The specified string is not a valid geohash.
Response
Correct your code.
Message Text
variable1 is an invalid geohash type.
Cause
The provided geohash type is invalid.
Response
Correct your code.
Message Text
Invalid geospatial operation variable1
Cause
The specified geospatial operation is not valid.
Response
Correct your code.
Message Text
Invalid gzip file
Message Text
HTTP Options not allowed when not loading from an HTTP source
Message Text
Invalid LockDiscovery document: variable1
Message Text
Error while processing a log file: variable1 variable2
Cause
Encountered error while processing a log file.
Response
Check the file is completed/available and retry again.
Message Text
Error while processing a remote log variable1 variable2
Cause
Unexpected error encountered in this remote log file.
Response
Retry or process this file from its host locally.
Message Text
Invalid manifest attribute: variable1
Message Text
Invalid manifest node: variable1
Message Text
Invalid manifest namespace: variable1 node has namespace: variable2
Message Text
Invalid manifest (expect an array of objects): variable1
Message Text
The minimum number of clusters cannot be less than 1
Message Text
No module to invoke
Message Text
Invalid invoke path: variable1
Message Text
Invalid options node
Message Text
Invalid option name: variable1
Message Text
Invalid options node: variable1
Message Text
Invalid option namespace: variable1 node has namespace: variable2
Message Text
Invalid option value: option 'variable1' has unexpected value 'variable2'
Message Text
Invalid page range: page start variable1 is greater than page end variable2
Message Text
Invalid Partition Query: doc(variable1)
Message Text
Invalid query at 'variable1'
Message Text
Invalid protocol scheme: variable1
Message Text
Invalid task in Task Server
Message Text
Insufficient number of terms from nodes
Message Text
An invalid format was found while parsing a URL Template: variable1
Message Text
Invalid trigger definition
Message Text
Invalid trigger module definition
Message Text
Invalid transaction option: variable1
Message Text
Invalid zip file
Message Text
I/O error: variable2 variable3: variable1
Cause
A host operating system I/O function returned an unexpected error. The host operating system function, file name, and error message are included in the error report.
Response
See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.
Message Text
Conversion from an IRI to a QName failed: variable1
Cause
The IRI provided does not contain a fragment identifier, and therefore cannot be turned into a QName.
Response
Use an IRI that can be converted.
Message Text
Isolation option not allowed in this function
Message Text
Journal full before in-memory stand for forest variable1variable2
Message Text
Journal not open: variable1 (variable2)
Cause
An unexpected error occurred while journaling a transaction. No open journal file could be found. The server will retry and may succeed.
Response
Check for other error messages that may indicate the root cause of the problem. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Try increasing the journal size in the database configuration. The journal should be at least the in-memory list size plus the in-memory tree size. Use of range indexes or lexicons further increases the required journal space.
Message Text
The journal has exceeded its limit for in-process transaction records: txn_size=variable1MB, current_size=variable2MB, limit=variable3MB
Cause
A fixed limit of 1/16th of the journal size is a maximum for information about prepared uncommitted transactions. This size limit has been exceeded by the transaction being committed. No more transactions will be allowed to move to being prepared, until the transactions currently using this space have committed or rolled back successfully.
Response
Explicitly commit or rollback XA transactions waiting in a prepared state. Increase your journal size to allow more space for prepared uncommitted transactions.
Message Text
Suppress warning when joining host
Message Text
Cannot specify auxiliary databases when enabling journal archiving.
Cause
When backing up with journal archiving, you cannot include auxiliary databases with the backup. This is to prevent journal archive files for auxiliary databases being scattered among several different database backups.
Response
Backup auxiliary databases separately with a full database backup and journal archiving set to true.
Message Text
Expecting all forests to be attached and belong to the same database when enabling journal archiving.
Cause
This error occurs when taking a full backup with journal archiving and not having all forests attached or belonging to the same database.
Response
When taking a full backup with journal archiving, make sure all forests are attached and belong to the same database.
Message Text
Expecting the lag limit to be greater than 5 seconds.
Cause
This error occurs when taking a full database backup with journal archiving and the lag limit is set to less than 5 seconds.
Response
When taking a full database backup with journal archiving set the lag limit to 5 seconds or more.
Message Text
Expecting full backup folder and journal archive folder to have the same timestamp when restoring. Got variable1 for full backup folder. Got variable2 for journal archive folder.
Cause
You can store your archived journals and full database backup data in separate locations using the admin API. This message occurs when the restoring from separate full database backup and journal archiving locations. It indicates the journal archive folder does not have a timestamp that matches the full backup folder, which means that it is likely that full backup and archived journals are from separate backups.
Response
When restoring from a full database backup, the system will choose the earliest timestamped backup folder from the restore-to-time value. For the journal archiving path, unless the folder timestamp is explicitly specified, the timestamp chosen for the full backup path will be applied to the journal archiving path.In the case of a flash backup, it is possible for the full database backup folder and the journal archive folder to have different timestamps. In this case, you must specifically select the journal archive timestamped folder when restoring with the admin API.Ex:Error if timestamps don't match - xdmp:database-restore(xdmp:forest("Documents"),"/space/backup",(),true(),"/space/ja")Ok if timestamps don't match - xdmp:database-restore(xdmp:forest("Documents"),"/space/backup",(),true(),"/space/ja/20120206-1152597588850")If you are not trying to restore from flash backup, it is likely that the two folders contain unrelated data. Therefore, modify your journal archiving path to find a folder containing journal archiving data with the correct timestamp. If you did not explicitly choose a different journal archiving location, then the journal archives are likely stored in the same path as the full backup.
Message Text
Journal consumer has been shut down
Message Text
Journaling is set to off: variable1
Cause
Certain operations require journaling to be enabled in order to function
Response
Error message indicates a corrupt journal file. Perhaps a journal archive file from an old system was switched in with a journal archive file from a current system. In this case, the internal structure of the header frame may have changed between versions or the checksum formulas may have changed. Best solution is to take another full backup with journal archiving enabled in order to resume journal archiving.
Message Text
Inconsistent "datatype" property: variable1
Cause
The JSON Schema has a value for a "datatype" property that is inconsistent with the "type" or "format" property.
Response
The JSON Schema is invalid and needs fixing.
Message Text
Invalid node kind: 'variable2' at property 'variable1' using
Cause
The JSON Schema has an illegal kind of node for a property or a subschema, such as an object node when an array node was expected.
Response
The JSON Schema is invalid and needs fixing.
Message Text
Invalid JSON Schema root
Cause
The JSON Schema is a document node with multiple child nodes.
Response
The JSON Schema is invalid and needs fixing.
Message Text
Invalid value for "type" property: variable1
Cause
The JSON Schema has an illegal value for a "type" property.
Response
The JSON Schema is invalid and needs fixing.
Message Text
Unexpected character 'variable1' in JSON at line variable2 char variable3
Message Text
Unexpected codepoint variable1 in JSON at line variable2 char variable3
Message Text
Document is not JSON
Message Text
Duplicate key variable1 in JSON at line variable2 char variable3
Message Text
Unexpected end of file in JSON at line variable1 char variable2
Message Text
Invalid hex reference variable1 in JSON at line variable2 char variable3
Message Text
Invalid number variable1 in JSON
Message Text
Undefined reference variable1
Cause
The JSON Schema has a "$ref" that does not refer to a JSON schema node.
Response
The "$ref" value may be incorrect. If it is a remote reference, make sure that the referenced JSON schema is in the schemas database at the proper location. If the remote reference uses as relative URI, make sure that the base URI is correct.
Message Text
Invalid schema variable1: exception_stack
Cause
The schema at schema URI variable1, used in a validation episode, is not a valid JSON Schema.
Response
Review and correct your schema.
Message Text
Invalid node: Node not valid against false schema at variable2 using schema variable3
Cause
Validation found an invalid node.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Invalid node value: Expected node of constant value variable3, found variable4 at variable1 using schema variable2
Cause
Validation found a node that did not have the expected fixed value.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Invalid node value: Expected node of one of enumeration values variable3, found variable4 at variable1 using schema variable2
Cause
Validation found a node that did not have one of the expected enumeration values.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Invalid node value: Node value is not valid per format variable3, found variable4 at variable1 using schema variable2
Cause
Validation found a node that was not in the proper format.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Too many items: Expected maximum of variable3 items, found variable4 at variable1 using schema variable2
Cause
Validation found a node that had too many items.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Too many properties: Expected maximum of variable3 properties, found variable4 at variable1 using schema variable2
Cause
Validation found a node that had too many properties.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Insufficient items: Expected minimum of variable3 items, found variable4 at variable1 using schema variable2
Cause
Validation found a node that did not have enough items.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Invalid node value: Node value beyond 'variable4' range, expected variable5 and found variable3 at variable1 using schema variable2
Cause
Validation found a node that was beyond the stated minimum or maximum.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Insufficient properties: Expected minimum of variable3 properties, found variable4 at variable1 using schema variable2
Cause
Validation found a node that did not have enough properties.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Invalid node: Node variable2 not valid against property 'variable1' expected variable4 using schema variable3
Cause
Validation found an invalid node.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Invalid node type: Expected node of type variable3, found variable4 at variable1 using schema variable2
Cause
Validation found a node that did not equal the declared 'const' value.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Invalid node: Array node does not contain unique items at variable1 using schema variable2
Cause
Validation found an invalid array node.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Missing property: Required variable3 property not found at variable1 using schema variable2
Cause
Validation found a node that had too many properties.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Unexpected data: Expected variable3 at variable1 using schema variable2
Cause
Validation found a node that did not match the schema.
Response
The instance is invalid. Fix the content to be valid.
Message Text
Kerberos Error: variable1
Message Text
Key generation for embedded KMS failed
Message Text
Key mismatch, variable1 variable2
Cause
This error is often a side-effect of a corrupted forest or file system error, such as running out of file descriptors or disk space on the forest's file system. Key file corruption may also occur if the disk becomes temporarily unavailable while the system is trying sync one of the MarkLogic Server memory mapped files to disk.
Response
Correct the underlying file system problem and restore the corrupted forest. For example, restore the system to a healthy state from a good backup, or delete the corrupted stand to get the forest to a healthy state and then reload missing documents.
If you need assistance determining the extent of the corruption and restoring the system to a good state and you have a current maintenance contract with MarkLogic, you can contact MarkLogic Technical Support.
Message Text
Key encryption key variable1 was not found
Message Text
The configured Key Management Service has returned an error: variable1
Cause
The external Key Management Service has returned an error
Response
Validate the Key Management Service configuration.
Message Text
Bad architecture in label: variable1 instead of variable2 in variable3
Message Text
Bad forest label magic number: variable1 instead of variable2
Message Text
Bad platform in label: variable1 instead of variable2 in variable3
Message Text
Bad word size: variable1 instead of variable2
Message Text
Forest label does not exist: variable1
Message Text
Unsupported language variable1
Message Text
Language code missing variable1
Message Text
The last-modified property is read-only and cannot be removed
Message Text
variable1 failed on ldap server variable2: variable3
Message Text
variable1 failed on ldap server variable2: variable3
Message Text
"ldaps" cannot use with start tls.
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
NCName required with module declaration
Cause
You have used a "0.9-ml" syntax for declaring a module. Newer syntax requires a prefix to be specified for the module's namespace.
Response
Specify a prefix to be bound to the module's namespace.
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Use := to initialize module variables: variable1
Cause
You have used the "0.9-ml" syntax for initializing global variables.
Response
Use ":=" rather than "{ ... }".
Message Text
String too large to calculate levenshtein distance: variable1
Message Text
Lexer error: variable1
Cause
The XQuery lexer has encountered a fatal error.
Response
Usually this indicates an out of memory condition, although there are other exceptional circumstances for this error.
W3C XQuery Standard Equivalent: err:FORG0001
Message Text
variable1 is not a valid lexical representation of an unsignedInt
W3C XQuery Standard Equivalent: err:FORG0001
Message Text
variable1 is not a valid lexical representation of a number
Message Text
Invalid lexical value variable1
Cause
A typed value cannot be parsed from text because the text does not fit the lexical rules of the type.
Response
Change the text or the type.
Message Text
Value:variable1 exceeded limit:variable2
Message Text
The specified meter name is not supported.
Message Text
List cache full on host variable1
Cause
The query results are too large to fit all of the term lists resulting from the index resolution stage into the list tree cache.
Response
Possible solutions include:
Tune the query to select fewer items during index resolution.
Reduce the size of your forest data, which will lead to fewer results per query.
Ensure appropriate indexes are enabled. For example, enabling positions may improve multi-term and proximity queries.
Increase the size of the list cache in the group configuration.
If you increase your list cache size, be careful not to over-tune your system. If you decide to apply this solution and have a current maintenance contract with MarkLogic, MarkLogic Technical Support can assist you with selecting an appropriate cache size.
The size of all caches, both group and database related, should usually add up to less than half of physical memory.
W3C XQuery Standard Equivalent: err:FOFD1340
W3C XSLT Standard Equivalent: err:XTDE1340
Message Text
Literal in the picture format contains odd number of square brackets.
Message Text
A conflicting lock exists on this document
Message Text
Cannot update lock documents
Message Text
Document or Directory is locked
Message Text
Error sending mail: variable1
Message Text
Invalid multipart: variable1
Cause
Invalid multipart for JSON email format.
Response
Change the part to be text or JavaScript object.
Message Text
Invalid attachment
Cause
Attachment is not encoded text.
Response
Change attachment to encoded text.
Message Text
Invalid email body: variable1
Cause
Invalid email body for JSON email format.
Response
Change the body to be either text or JavaScript object.
Message Text
Invalid multipart boundary: variable1
Cause
Invalid multipart boundary for JSON email format.
Response
Change the boundary to be text.
Message Text
Invalid encoding: variable1
Cause
Encoding not supported.
Response
Change encoding to base64 or hex.
Message Text
Invalid header: variable1
Cause
Invalid value for rfc822 header.
Response
Change content of the header.
Message Text
No recipients
Cause
Tried to send mail without any recipients.
Response
Enter one or more recipients and try again.
Message Text
Main module failed to parse
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Ambiguous function name, possible functions include: variable1
Cause
Multiple functions match the given function localname.
Response
Fully qualify the function with a prefix or EQName syntax.
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Sequence containing more than one item
Message Text
Invalid hash table element
Message Text
A cycle was detected in the map entry
Cause
A map cannot be member of itself, either directly or indirectly.
Response
Do not add the map as a member of itself.
Message Text
Invalid hash table entry element
Message Text
Error mapping file: variable1 variable2: variable3
Message Text
Invalid xdmp:mapping option value, must be "true" or "false"
Message Text
Invalid match pattern passed to xdmp:match-priority: variable1
W3C XQuery Standard Equivalent: err:FORX0003
Message Text
Pattern matches zero-length string
Message Text
Maximum number of atoms exceeded
Message Text
Maximum number of fragments exceeded
Message Text
Maximum number of strings exceeded
Message Text
Task Server exceeded maximum number of tasks: variable1
Cause
The actions of spawn and or cpf has caused the tasks in the task server queue to be greater than the maximum number allowed.
Response
Examine Task Server utilization and consider either increasing the task queue size or throttling back the workload being put on Task Server.
Message Text
Trigger or task spawn exceeded maximum depth: variable1
Cause
Recursive trigger execution has exceeded the depth limit set.
Response
This usually indicates an infinite recursion in your triggers. Otherwise the trigger depth limit can be changed.
Message Text
Canceled because of memory usage on host variable1, requestMemory=variable2, totalMemory=variable3, memoryLimit=variable4, opID=variable5, opMem=variable6
Cause
The request was cancelled because its memory usage was too high.
Response
Retry the operation.
Message Text
Memory exhausted
Cause
Insufficient contiguous memory address space.
Response
A detailed technical note on troubleshooting out-of-memory issues is available from MarkLogic Technical Support. In brief, you may need to:
Change your swap space allocation. A 2:1 ratio between virtual and physical memory is recommended.
Tune your MarkLogic Server cache settings.
If you run MarkLogic Server on a 32-bit platform, consider moving to a 64-bit platform.
If you are running on 32-bit Windows, increase the virtual address space addressable by applications from 2G to 3G by adding the
/3G switch to your
boot.ini file. Microsoft has a Support note available about this switch.
Message Text
Not merging due to disk space limitations, need=variable1MB, have=variable2MB
Cause
There was not enough disk space to complete the merge operation.
Response
You need to free space on or add space to the device in which the forest is stored. If your forest is also in the error state (XDMP-FORESTERR), then you can perform the following to get it out of the error state:
Disable automatic merges on the forest.
Restart the forest.
Delete some documents from the forest.
Start a manual merge on the forest.
Message Text
Merge timestamp must be set to non-zero value when restoring with journal archiving and restore-to-time is zero
Message Text
Merge timestamp must be set to a time less than the restore-to-time when restoring with journal archiving.
Message Text
variable1 cannot be used until the cluster is upgraded to effective version variable2.
Message Text
Missing one or more required keys/fields variable1
Cause
A required key was missing from the object
Response
The object is invalid. Add the missing key.
W3C XQuery Standard Equivalent: err:XPDY0002
Message Text
Missing context item
Message Text
Missing file variable1
Message Text
Missing files variable1
Cause
The named files should be present in your stand, but are missing. This may indicate a corrupted stand.
Response
Restore the corrupted stand from backup or otherwise recreate it. Please also check your system logs for evidence of file system errors.
Message Text
No xs:import for namespace: variable1 on attribute 'variable2'
Message Text
No xs:import for namespace: variable1 on element 'variable2'
Message Text
Missing stand in forest variable1: variable2
Message Text
Missing stands in forest variable1: variable2
Message Text
Mixed variable1
W3C XQuery Standard Equivalent: err:XPTY0018
Message Text
Path expressions cannot return a mix of nodes and atomic values
W3C XQuery Standard Equivalent: err:XQST0059
Message Text
Module variable1 not found
Cause
The module document being requested does not exist or the user does not have execute permissions on the module.
Response
Make sure the module exists and grants execute permissions if it is stored in a database.
Message Text
Module variable1 is not a text document
Message Text
fn:zero-or-one called with a sequence containing more than one item
Message Text
Cannot process different-database requests with same-statement isolation
Message Text
Multiple matches for variable1 at variable2 and variable3
Message Text
Ending of the boundary is incorrect
Cause
Occurs when a part is not corrected ended.
Response
Fix the application.
Message Text
All parts are already processed
Cause
Occurs when trying to stream the next part body after all parts are processed.
Message Text
The current HTTP request is in multipart mode
Cause
Occurs when an API that is only supposed to work for an HTTP request in non-multipart mode is called for multipart mode.
Message Text
Body of the current part is not read yet
Cause
Occurs if try to read the headers of the next part when the body of the current part is not read yet.
Message Text
Headers of the current part is not read yet
Cause
Occurs if try to read the body of the current part when the headers are not read yet.
Message Text
Invalid multipart encoding, mismatched counts: variable2 parts, but variable1 nodes
Message Text
Document nodes cannot have multiple roots
Message Text
Cannot evaluate multiple statements
Message Text
Document must have at least one update permission. Assigned permissions: variable1
Cause
When creating a document as a user without the admin role, the document must include at least one update permission. You can specify permissions explicitly in your update built-in call (for example, xdmp:document-insert), or with the set of default permissions for the user performing the update operation.
Response
When loading a document, ensure the named role has update permissions. Documents created by non-admin users must be created with at least one update permission. If the document has no permissions, then only users with the admin role will be able to update or delete the document.
You can create the permissions in several ways, including:
Passing them as option parameters to functions such as
xdmp:document-load and
xdmp:document-insert.
Setting default permissions on a user or role.
Using the permissions APIs, such as
xdmp:document-add-permissions or
xdmp:document-set-permissions.
For more information, see the Understanding and Using Security Guide or the Application Developer's Guide.
Message Text
Do not understand element marked mustUnderstand
W3C XQuery Standard Equivalent: err:FOAR0002
Message Text
Expression contains a NaN (not-a-number)
Message Text
Invalid NCName "variable1"
Message Text
Cannot create a nested multi-statement transaction inside a multi-statement transaction.
Cause
An eval or invoke with transaction-mode update was attempted in a multi-statement transaction.
Response
Use transaction-mode update-auto-commit instead.
Message Text
Timestamp too new for forest variable1 (variable2)
Cause
When a transaction commits, it advances the commit timestamp. After the transaction commits and advances the commit timestamp, however, any queries running at the advanced commit timestamp wait for all transactions with earlier timestamps to commit, during which time they will get this exception.
Response
XDMP-NEWSTAMP is a retryable exception, so retrying the query is appropriate after this exception. You can retry after the App Server request timeout is reached (the default is 30 seconds) until the Group retry timeout is reached (the default is 180 seconds). If you have an XCC application that uses DocInsertStream, you should automatically handle and retry the insert; that is, if you get a retryable exception when using DocInsertStream, you should try the operation again, not treat the exception as an error.
Message Text
The aggregate does not exist: variable1:variable2, host: variable3
Cause
The specified aggregate function cannot be found.
Response
Use an aggregate function that exists.
Message Text
Canceled restore. Forest variable1 did not have archived journals.
Cause
Error occurs when restoring to a point in time from a full database backup with journal archiving. At least one forest does not have archived journals in its Journals directory.
Response
When restoring to a point in time from a full database backup with journal archiving:1) All forests must have been backed up with journal archiving enabled.2) The Journals directory must contain archived journals.
Message Text
The two arcs do not intersect
W3C XQuery Standard Equivalent: err:FONS0005
Message Text
Base uri undefined in the static context
Message Text
Cannot compute bearing from point to itself
Message Text
No bootstrap host in cluster variable1
Cause
There is no bootstrap host in this cluster.
Response
Add a bootstrap host to this cluster.
Message Text
No cluster with identifier variable1
Message Text
No context document
Message Text
Credential does not exist: variable1
Message Text
No database with identifier variable1
Message Text
Database does not have a foreign forest map: variable1
Cause
This occurs during database replication and is normally transient
Response
Normally resolves on its own
Message Text
variable1 nodes cannot be followed by variable2 nodes
Message Text
Invalid node kind variable1, expected variable2
Message Text
Invalid match pattern passed to xdmp:node-matches: variable1
Message Text
variable1 nodes cannot be preceded by variable2 nodes
Message Text
variable1 nodes cannot be replaced with variable2 nodes
Message Text
The stemming dictionary could not be loaded: variable1 dictionary at variable2 not loaded
Cause
The specified stemming dictionary cannot found or there was some problem with it.
Response
Check your language configuration.
Message Text
No such directory: variable1
Cause
Directory does not exist.
Response
Check directory and try again.
W3C XQuery Standard Equivalent: err:FODC0001
Message Text
The node is in a tree whose root is not a document node
Cause
The node is in a tree whose root is not a document node.
Response
Make sure node is in a tree whose root is a document node.
Message Text
No domestic forest: variable1
Cause
This occurs during database replication, either as a transient problem or due to incomplete matching of foreign forests to domestic forests
Response
Configure database replication to match all database forests
Message Text
No element node: variable1
Message Text
No forests with empty partition number allow updates
Message Text
There is still a started document.
Message Text
There is still a started element.
Message Text
Document is not of executable mimetype. URI: variable1
Message Text
Field not defined: variable1
Cause
You ran a field query with an undefined field.
Response
Try the query again after defining the field and appropriate indexes.
Message Text
No forest with identifier variable1
Message Text
Database variable1 contains no forests
Cause
You tried to upload to a database that is not attached to a forest.
Response
Add at least one forest to the database and try again.
Message Text
No forwardable kerberos ticket
Message Text
No group with identifier variable1
Message Text
No group configuration
Message Text
No host with identifier variable1
Cause
The server cannot find the host specified by the identifier.
Response
In many cases, this error is the result of setting up a cluster again, and not using all of the same instances to do so. While the exception is logged on a host that is part of your now-current cluster, the cause of the error is, in fact, the result of another MarkLogic instance that is likely NO LONGER in your cluster trying to make contact with your host. Your host is noting that it has no idea who this instance is. The proper resolution is to verify whether this cluster is properly configured. The most likely action is to identify the host associated with the IP address mentioned in the error message, locate that machine, and determine whether the MarkLogic instance running there should be the part this or any cluster. If you find it is merely an old instance no longer part of any active work, the MarkLogic instance can be shut down, which will stop the error message from being recorded. It is still advised to determine whether or not this MarkLogic instance should still exist, as later restarting the host will likely result in a restart of MarkLogic, which will then cause the error to return.
Message Text
No job with identifier variable1
Message Text
No journal for recovery token variable1
Cause
MarkLogic Server cannot find the journal files for a forest.
This could be caused by a bad disk drive, by two hosts attempting to mount the same forest, or by other disk-related corruption.
Response
The following procedures may resolve the problem. If you have a current maintenance contract with MarkLogic, you can contact MarkLogic Technical Support for assistance.
Restore from backup.
Shut down MarkLogic Server, delete the journals, delete the label file in the forest directory (
not in the stand directories), and restart MarkLogic Server.
Message Text
Invalid classification label value: missing class name
Message Text
The lexer does not exist: variable1:variable2, host: variable3
Cause
The specified lexer function cannot be found.
Response
Use a lexer function that exists.
Message Text
The shared library cannot be loaded: variable1, host: variable2
Cause
The specified shared library cannot be loaded.
Response
Check spelling. Read the extended error message for further details of the error.
Message Text
Lock on thie document or directory no longer exists
Message Text
No matches for variable1 in variable2
Message Text
No merge with identifier variable1
W3C XQuery Standard Equivalent: err:XQST0016
Message Text
The modules feature has been disabled
W3C XQuery Standard Equivalent: err:FONS0004
Message Text
No namespace binding for prefix
Message Text
Node has complex type with non-mixed complex content
Cause
An attempt was made to atomize an XML element node that cannot be atomized. The in-scope XML schema specifies that the element node has non-mixed complex content. Some code is attempting to convert the node to an atomic value. Element nodes with non-mixed complex content cannot be converted to atomic values.
Response
If the schema is correct, fix the code so it does not attempt to atomize the element node. The code should not explicitly atomize the node by calling fn:data on it. The code should not implicitly atomize the node by passing it as a parameter to a function expecting an atomic value. If the code is correct, fix the schema so that the complex type for the element node is mixed.
Message Text
Insufficient number of nodes
Message Text
Wildcards can only be at the end of the node name
Message Text
Not a variable
Message Text
Bad parameter position, function has variable1 parameters, but got variable2
Cause
The parameter position provided was too high or too low for the function.
Response
Correct the position.
Message Text
No parent node
Message Text
No forests with partition number variable1 allow updates
Message Text
Database variable1 has no range assignment policy partition key
Message Text
Server unable to build program from request
Cause
The requested XQuery document does not exist or the user does not have execute permissions on the module.
Response
Make sure the module exists. If the module is stored in a modules database, make sure the module execute permissions.
W3C XQuery Standard Equivalent: err:XQST0128
Message Text
The specified feature cannot be disabled: variable1
Message Text
No valid query could be created for 'variable1'
Cause
The key was bound to an index, field, or callback, which could not produce a valid query in this context. Either the bindings have a problem, or the key is being misused.
Response
Fix the bindings or the query, as appropriate.
Message Text
No quorum: variable1
Cause
Unable to communicate with at least 50% of hosts in cluster
Message Text
No request with identifier variable1
W3C XQuery Standard Equivalent: err:XQST0120
Message Text
The specified feature is not supported: variable1
Message Text
Database does not have root directory
W3C XQuery Standard Equivalent: err:XQST0009
Message Text
The schema import feature has been disabled
W3C XQuery Standard Equivalent: err:XQST0075
Message Text
The schema validation feature has been disabled
Message Text
No searchable term found in the search pattern: variable1
Message Text
No server with identifier variable1
Message Text
The stemmer does not exist: variable1:variable2, host: variable3
Cause
The specified stemmer function cannot be found.
Response
Use a stemmer function that exists.
Message Text
No such cluster variable1
Cause
The cluster does not exist or the cluster is not coupled with the local cluster.
Response
Make sure the cluster id is correct and the cluster is coupled with the local cluster.
Message Text
No such configuration variable1
Message Text
No such database variable1
Cause
The database you are trying to operate on does not exist (or you misspelled the name of an existing database).
Response
Either create a new database with this name and try again, or use a different, existing, database.
Message Text
No such dictionary variable1
Message Text
No such forest variable1
Cause
Called xdmp:forest with an invalid forest name argument.
Response
Check the spelling of the forest name passed to xdmp:forest. Check that the forest has been created.
Message Text
No such group variable1
Cause
Called xdmp:group with an invalid group name.
Response
Check spelling and existence of group name passed to xdmp:group.
Message Text
No such host variable1
Cause
Called xdmp:host with an invalid host name.
Response
Check the spelling of the host name. Check that you defined the host.
Message Text
No such server variable1
Response
Check the spelling of the server name passed to xdmp:server . Check that the server was created.
Message Text
The current HTTP request is not in multipart mode
Cause
Occurs when an API that is only supposed to work for an HTTP request in multipart mode is called for none-multipart mode.
W3C XQuery Standard Equivalent: err:XPTY0019
Message Text
variable1 is not a node
Cause
You are trying to use data that is not a node when a node is required.
Response
Rewrite your query so it submits a node.
Message Text
This host's group does not contain a configured Task Server
Cause
The task server does not exist or is improperly configured for this group.
Response
Use the Admin Interface to check the task server configuration for this group.
W3C XQuery Standard Equivalent: err:XPST0051
Message Text
Invalid cast to non-atomic type variable1
Message Text
Transaction with Xid variable1 is not the current transaction
Message Text
The path passed to xdmp:logfile-scan() is not a file.: variable1
Message Text
Character class not found: no character class for 'variable1'
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Not a singleton function value
Cause
A dynamic function call can only be made against a sequence consisting of a single function item.
Response
Use the head function to choose the first function in the sequence, or iterate over all the functions using for or !.
Message Text
No tidy in this MarkLogic Server instance
Message Text
Document not locked
Message Text
No TEMP or TMP environment variable
W3C XQuery Standard Equivalent: err:FORG0005
Message Text
fn:exactly-one called with a sequence containing zero or more than one item
Message Text
The shared library does not contain a "marklogicPlugin" function: variable1, host: variable2
Cause
The "marklogicPlugin" registration function cannot be found in the shared library.
Response
Implement the registration function in shared libraries designed to be used as MarkLogic native plugins.
Message Text
Transaction with identifier variable1 is not a prepared XA transaction
Message Text
Element variable1 is not a query (expecting a cts:query)
Message Text
This API works only with the range assignment policy.
Message Text
No transaction
Message Text
Transaction with identifier variable1 is not a remembered completed XA transaction
Message Text
Node does not have simple content: variable1
Message Text
variable1 not supported for variable2
Message Text
No transaction with identifier variable1
Cause
No transaction with the given ID exists on this host.
Response
You may be connecting to a different host than the one where the transaction was created, as transactions are host specific. It may be that the transaction has already been committed or rolled back.
Message Text
A user must be authenticated to perform this task
Message Text
No zip support in this MarkLogic Server instance
W3C XQuery Standard Equivalent: err:XPST0022
Message Text
Namespace declaration attribute variable1 must be a URILiteral
Cause
A namespace declaration attribute (for example, xmlns) must have a value that is a URI Literal value.
Response
If you want to compute the URI Literal value, use a computed element constructor or the xdmp:with-namespaces function to compute the value.
W3C XQuery Standard Equivalent: err:XPTY0117
Message Text
Namespace sensitive cast: variable1 cast as variable2
Cause
An expression or declaration attempted to cast a node to a namespace sensitive type like xs:QName and types derived from xs:NOTATION.
Response
Use fn:data() or fn:resolve-QName() instead.
Message Text
Object nodes cannot have sequence children: variable1
Message Text
Obsolete Stand variable1 not deleted for variable2 seconds
Cause
As a normal part of the operations in the server, stands are sometimes marked obsolete so they can be deleted later. For example, if stands are merged into a new stand, the old stands are marked obsolete. Typically, these stands will be deleted within seconds or minutes but, if there are long-running transactions or other activities like backups still using obsolete stands, they cannot be deleted until those processes complete. If obsolete stands are not deleted within an hour, the server will log this message for informational purposes.
Response
If the system has long-running transactions that are expected or backups that take more than an hour, these messages can be ignored. If not, these messages could be a reflection of other problems in the system and they can be used to help diagnose when unexpected long-running processes may have started to occur.
Message Text
Forest variable1 is offline
Message Text
Config files are old, variable1 has newer config files
Message Text
Backup data directory contains an incompatible journal: variable1
Message Text
The journal archive is too old to be updated from the active journals: variable1
Cause
There are 2 active journal files. When one fills up, it begins to overwrite the other. When a system fails, the archived journal may not be caught up with the active journal. When resuming journal archiving, the archived journals at startup rely on streaming frames from the active journal to get caught up with any that it missed. When the active journal overwrites itself, it may overwrite frames that the archived journal needs. If this is the case, it is not possible for the archived journal to get caught up with the active journal, and journal archiving must stop.
Response
You must do a new full backup with journal archiving. This error message is deprecated since the active journal now waits to roll over if it is going to overwrite frames needed by the archived journal. However, this message is still included for completeness.
Message Text
variable1 has a more recent version of the embedded KMS
Response
Retry the operation after the embedded KMS has completed synchronizing. If hosts are unavailable wait for all to be online before retrying.
Message Text
Timestamp too old for forest variable1 (variable2)
Cause
A timestamp less than the oldest timestamp preserved in the database was specified for a point-in-time query or rollback.
Note: If the merge timestamp is set to the default of 0 and the database has completed all merges since the last update or delete, then query statements that specify any timestamp older than the current system timestamp will throw the XDMP-OLDSTAMP exception. The error occurs because a merge timestamp value of 0 specifies that no obsolete fragments are to be retained.
Response
Modify the query or rollback operation timestamp. For example, change the timestamp parameter passed to xdmp:eval, xdmp:invoke, or xdmp:spawn.
Message Text
Documents can only have one binary node
Cause
The document already contains a binary node
Response
Check why a second binary node is being added into the document or use the existing binary node.
Message Text
Open URL error: variable1: variable2
Message Text
An internal error was encountered communicating with Ops Director: variable1
Message Text
An internal error was encountered communicating with Ops Director: variable1 variable2 variable3 variable4 variable5
Message Text
No valid endpoint was found to connect to Ops Director: variable1
Message Text
Not a valid JSON structure in: variable1
Message Text
An invalid request error was returned as a response to communicating with Ops Director: method variable1, variable2
Message Text
The response received from Ops Director is invalid: variable1
Message Text
The maximum number of retries exceeded while connecting to Ops Director: variable1
Message Text
An attempt to connect to Ops Director using https requires SSL: variable1, $2
Message Text
Tidy option nodes can only have name attributes: variable1
Message Text
Invalid option variable1
Message Text
This option value cannot contain spaces: option 'variable1' cannot have spaces in 'variable2'.
W3C XQuery Standard Equivalent: err:XPST0081
Message Text
Prefix required on option name
Message Text
Invalid 'order by' value variable1
Message Text
Ordering clause element contains unknown child: variable1
Message Text
Ordering clause node variable1 contains unknown child
Message Text
Ordering clause element variable1 contains misplaced text
Message Text
Order specification element contains unknown child: variable1
Message Text
Order specification node variable1 contains unknown child
Message Text
Order specification element variable1 contains misplaced text
Message Text
write variable1:Out of order, variable2
Message Text
Invalid xdmp:output option parameter
Message Text
Operation not allowed on the currently executing transaction with identifier variable1
Message Text
Parent directory variable1 is missing for creation of child
Message Text
Invalid parent link node doc("variable1")//variable2
Cause
A parent fragment in a fragmented document is missing.
Response
The document must be reloaded.
W3C XQuery Standard Equivalent: err:XPST0003
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Syntax error: cannot back up
Message Text
Some write locks are not held for session variable1
Cause
Participant of the distributed transaction does not have the lock for a fragment that is being updated in the transaction.
Response
This is an unexpected error that is likely the side effect of other system stability issues occurring on your system. Check for network connectivity or host stability issues across all nodes in your cluster.
Message Text
Incorrect passphrase
Message Text
Ambiguous geospatial variable1 path index for variable2 variable3
Cause
The options provided are not sufficient to uniquely identify a path geospatial point index.
Response
Specify type, coordinate-system, and/or precision options to uniquely identify a path geospatial point index.
Message Text
Collations are irrelevant to the geospatial variable1 path index for variable2 variable3
Cause
The options to the query include a collation, but the geospatial point index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
No geospatial variable1 path index for variable2 variable3 variable4
Cause
The query requires a geospatial point index that does not exist.
Response
Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the geospatial variable1 path index for variable2 variable3
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.
Response
Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.
Message Text
No path word lexicon for variable1 variable2
Cause
The query requires a lexicon that does not exist.
Response
Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.
Message Text
Attributes not allowed on element variable1
Message Text
Path-namespaces attribute contains an invalid value: variable1
Message Text
Path-namespaces element contains unknown child: variable1
Message Text
Path-namespaces element variable1 contains unknown child
Message Text
Path-namespaces element variable1 contains misplaced text
Message Text
Path-namespaces element contains an invalid value: variable1
Message Text
Ambiguous variable1 path range index for variable2 variable3
Cause
The options provided are not sufficient to uniquely identify a path range index.
Response
Specify type, collation, coordinate-system, and/or precision options to uniquely identify a path range index.
Message Text
Collations are irrelevant to the variable1 path range index for variable2 variable3
Cause
The options to the query include a collation, but the range index is not a string data-type.
Response
Do not specify a collation in the query's options.
Message Text
Coordinate systems are irrelevant to the variable1 path range index for variable2 variable3
Cause
The options to the query include a coordinate system, but the range index is not a geospatial data type.
Response
Do not specify a coordinate system in the query's options.
Message Text
No variable1 path range index for variable2 variable3 variable4
Cause
The query requires a range index that does not exist.
Response
Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the variable1 path range index for variable2 variable3
Cause
User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.
Response
Either enable positions on the range index or do not specify "ordered" or "proximity" options.
Message Text
Given value doesn't match with the specified pattern for parsing dateTime string.
W3C XQuery Standard Equivalent: err:XQDY0026
Message Text
XML processing instructions cannot contain '?>'
Message Text
Illegal character in the picture format
Message Text
Fast locking cannot be used with place keys.
Message Text
Invalid position
Message Text
This pre-release version of MarkLogic Server has expired
Message Text
prevent-deadlocks option not allowed in this function
Message Text
Processing an update from an update with different-transaction isolation could deadlock
Message Text
Prefix required on pragma name
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Prolog options in the wrong order
Message Text
Top-level property element cannot be deleted or replaced
Message Text
Protected query element not indexed
Cause
Protected query element not indexed
Response
Check element level protection on the query and try again.
Message Text
Protected triple element not indexed
Cause
Protected triple element not indexed
Response
Check element level protection on the triple and try again.
Message Text
Invalid QName "variable1"
Message Text
Invalid lexical form for QName key
Message Text
Invalid lexical form for QName
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
A non-QName value must be a string literal to be cast to a QName
Message Text
QName URI is not empty variable1
Message Text
Query has too many nesting levels
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Invalid UTF-8 escape sequence -- query is not UTF-8 encoded variable1
Cause
A bad UTF-8 byte code sequence was found in the XQuery.
Response
Encode your query in UTF-8 correctly.
Message Text
Invalid XML character -- query contains non-XML character
Message Text
Attributes not allowed on element variable1
Message Text
Query attribute contains an invalid value: variable1
Message Text
Query element contains unknown child: variable1
Message Text
Error querying for index differences variable1: exception_stack
Message Text
Query requires a coordinate system: variable1
Message Text
Query element variable1 contains unknown child
Message Text
Query requires a geospatial operation: variable1
Message Text
The range query must have one or more cts:values: variable1
Message Text
Query element variable1 contains misplaced text
Message Text
Query element contains an invalid value: variable1
Message Text
Range index error: variable1 variable2: exception_stack
Cause
User inserted a document where certain data doesn't match the data-type of the corresponding range index. Also user didn't set the invalid-values option in the range index configuration.
Response
Either change the data-type of the index or data. If both of those cannot be changed and you still want to insert the data, set the invalid-values option in the index configuration.
Message Text
Range index element contains unknown child: variable1
Message Text
Range indexes cannot store NaNs
Message Text
Range index element variable1 contains unknown child
Message Text
Range index element variable1 contains misplaced text
Message Text
Unsupported range index type: variable1
Message Text
Range index element contains an invalid value: variable1
Message Text
Ranges partially overlap: variable1 and variable2
Cause
The two ranges partially overlap.
Response
Check your configuration.
Message Text
Bad RDF Value comparison
Message Text
variable1:Invalid read, variable2
Cause
An inconsistency was detected while reading a memory-mapped index file. Details about the inconsistency are included in the error report. A memory-mapped index file may be corrupt.
Response
Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear an inconsistency in memory. Merging on the affected forest may clear an inconsistency on disk. Reindexing the affected forest may clear an inconsistency on disk.
Message Text
Error reading configuration file: variable1
Message Text
ReadFile variable1: variable2
Cause
The server encountered a problem that prevented reading a file.
Response
Resolve the problem with the file. If the file is not in UTF-8 and you are using xdmp:filesystem-file, try xdmp:document-get, which has options for converting from other character encodings.
Message Text
Forest variable1 can only perform reads
Message Text
Forest %1 is read-only or flash-backup when %2 committing transaction %3
Message Text
Forest label is read only: variable1
Message Text
Error rebalancing variable1: exception_stack
Message Text
Host hung recently
Cause
The host was probably hung recently.
Response
The system will get back to normal shortly.
Message Text
Recovery error on forest variable1 after variable2 redo records -- variable3 exception_stack
Message Text
Recursive remove directory variable1 failed for variable2
Cause
An error has occurred when trying to recursively remove a directory.
Response
This is an indication that there is likely a problem with the underlying file system. Inspect the file system on which the error occurred and take action as necessary to address the problem.
Message Text
Redefined element declaration: variable1
Message Text
Redefined attribute group: variable1
W3C XQuery Standard Equivalent: err:XQST0045
Message Text
Redefined builtin variable1
Message Text
Redefined complex type: variable1
W3C XQuery Standard Equivalent: err:XQST0045
Message Text
Redefined constructor variable1
W3C XQuery Standard Equivalent: err:XQST0066
Message Text
Redefined default element namespace
W3C XQuery Standard Equivalent: err:XQST0066
Message Text
Redefined default function namespace
Message Text
Redefined element declaration: variable1
W3C XQuery Standard Equivalent: err:XQST0034
Message Text
Redefined function variable1
Message Text
Redefined named model group: variable1
W3C XQuery Standard Equivalent: err:XQST0047
Message Text
Redefined module variable1
W3C XQuery Standard Equivalent: err:XQST0033
Message Text
Redefined prefix variable1
W3C XQuery Standard Equivalent: err:XQST0070
Message Text
Redefined reserved prefix variable1
W3C XQuery Standard Equivalent: err:XQST0070
Message Text
Redefined reserved URI variable1
W3C XQuery Standard Equivalent: err:XQST0058
Message Text
Redefined schema variable1
Message Text
Redefined simple type: variable1
W3C XQuery Standard Equivalent: err:XQST0039
W3C XSLT Standard Equivalent: err:XTSE0670
Message Text
Redefined variable variable1
W3C XQuery Standard Equivalent: err:XQST0039
W3C XSLT Standard Equivalent: err:XTSE0580
Message Text
Redefined variable variable1
W3C XQuery Standard Equivalent: err:XQST0039
W3C XSLT Standard Equivalent: err:XTSE0630
Message Text
Redefined variable variable1
Message Text
Cannot have both @ref and @name on xs:attribute
Message Text
Cannot have both @ref and @name on xs:element
Message Text
Collation is not specified for the cts reference.
Cause
No "collation" option is passed into the cts reference call.
Response
Correct the code.
Message Text
Coordinate system is not specified for the cts reference.
Cause
No "coordinate-system" option is passed into the cts reference call.
Response
Correct the code.
Message Text
Path expression is not specified for the cts path reference.
Cause
No path expression argument is passed into the cts path reference call.
Response
Correct the code.
Message Text
Scalar type is not specified for the cts reference.
Cause
No "type" option is passed into the cts reference call.
Response
Correct the code.
Message Text
Error refragmenting variable1: exception_stack
W3C XQuery Standard Equivalent: err:FORX0002
Message Text
Invalid regular expression
W3C XQuery Standard Equivalent: err:FORX0001
Message Text
Invalid regular expression flags
Message Text
Registered queries require the "unfiltered" option
Message Text
Error reindexing variable1: exception_stack
Message Text
Relative pathname: variable1
Message Text
Relative URI base argument to resolve-uri
Message Text
Host variable1(variable2) is remote to host variable3(variable4)
Message Text
Replication is currently not allowed: variable1
Message Text
Replica forest variable1 does not allow updates
Message Text
This request is already in a multi-statement transaction
Message Text
Requests are currently forbidden
Message Text
Concurrent request limit for user has been reached
W3C XQuery Standard Equivalent: err:XQST0126
Message Text
The all-extensions feature is not allowed in a require-feature option: variable1
Message Text
Invalid UTF-8 escape sequence -- requests are not UTF-8 encoded
Message Text
Unable to decrypt credential during resecure
Cause
An encrypted secret could not be resecured because it failed to decrypt. This could be due to the passed string not actually being encrypted, or due to not having access to the key that was originally used for encryption.
Response
Make sure the text is actually encrypted. If this credential was originally encrypted on a different cluster, importing encryption keys from that cluster may allow decryption.
W3C XQuery Standard Equivalent: err:FORG0002
Message Text
Invalid argument to fn:resolve-uri()
Message Text
Unable to restore replica forest variable1 because the master forest variable2 is not also restored, or is not acting master.
Message Text
result option not allowed in this function
Message Text
Nothing to rethrow
Message Text
variable1 returned variable2 which is not of type variable3
Message Text
Reverse index bad query: variable1
Message Text
Ambiguous variable1 range index for variable2 variable3
Cause
The options provided are not sufficient to uniquely identify a range index.
Response
Specify type, collation, coordinate-system, and/or precision options to uniquely identify a range index.
Message Text
Collations are irrelevant to the variable1 range index for variable2 variable3
Cause
The options to cts:reference include a collation, but the range index is not a string data-type.
Response
Do not specify a collation in the cts:reference's options.
Message Text
Coordinate systems are irrelevant to the variable1 range index for variable2 variable3
Cause
The options to cts:reference include a coordinate system, but the range index is not a geospatial data type.
Response
Do not specify a coordinate system in the cts:reference's options.
Message Text
No variable1 range index for variable2 variable3 variable4
Cause
The query requires a range index that does not exist.
Response
Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.
Message Text
Positions are not enabled on the variable1 range index for variable2 variable3
Cause
User has specified "ordered" or "proximity" options on cts:value-tuples when positions are not enabled on the range index.
Response
Either enable positions on the range index or do not specify "ordered" or "proximity" options on cts:value-tuples.
Message Text
Too many entries in range index variable1
Message Text
Recovery Manager invalid operation: variable1
Message Text
Journal record too large: variable1
Message Text
Transaction rollback
Message Text
Bad rollback time: rollback timestamp (variable1) must be between database merge timestamp (variable2) and current timestamp (variable3)
Message Text
Rollback requires database merge timestamp to be set
Message Text
It's not http compatible to resolve entities embedded in document
Cause
Document is inserted through XCC in HTTP compatible mode, while ResolveEntities is set to true
Response
Disable HTTP compatible mode in XCC or set ResolveEntities to false
Message Text
Invalid syntax for a rule definition: variable1
Cause
Rule definitions only allow a subset of SPARQL syntax.
Response
Restrict your rule definitions to use the correct syntax subset.
Message Text
The ruleset file cannot be found: variable1
Cause
The ruleset file referenced cannot be found.
Response
MarkLogic searches for rulesets in the schemas database configured for the queried database, as well as in the MarkLogic install directory for standard rulesets shipped the product. Check that the ruleset you are trying to use exists and has the correct name.
Message Text
One of the attributes any-of [variable1] or all-of [variable2] must be specified in rule: variable3
Message Text
The attribute 'variable1' in rule: 'variable2' must not be empty or blank.
Message Text
The attribute 'variable1' in rule: variable2 must be explicitly provided.
Message Text
At most one matching attribute of 'variable1', 'variable2', 'variable3' is allowed in rule: variable4.
Message Text
The value of expression 'variable1' is required to be non-empty in rule: variable2
Message Text
The value of expression 'variable1' is required to be non-zero in rule: variable2
Message Text
Only one of the attributes 'variable1' or 'variable2' may be supplied in rule: variable3
Message Text
Attempted evaluate an invalid regular expression: 'variable1' in rule: variable2 - error: variable3
Message Text
The expression 'variable1' evaluated to multiple values in rule: variable2
Message Text
The requested method name: 'variable1' is invalid in rule: variable2
Message Text
Repeated values are not allowed for the variable1 attribute in rule: variable2.
Message Text
Attempted to set a system variable name: 'variable1' in rule: variable2
Message Text
Arcs must not be part of same great circle
Response
The error is reporting a state of nature. It is up to the application to decide what to make of that state of nature.
Message Text
Cannot variable1 -- variable2
Message Text
Namespace "variable1" does not match namespace in schema at "variable2"
W3C XQuery Standard Equivalent: err:XQST0057
Message Text
Cannot declare a prefix for the empty namespace URI in a schema import
Message Text
Searches not enabled
Cause
One or more of the following configuration settings are required by the search, but are not enabled on the database: stemmed searches, word searches, field value searches.
Response
Use the Admin Interface to check and correct the database configuration.
If the database settings appear correct, ensure that any database re-indexing operations are completing correctly. In rare cases, this error has been seen when there is a re-indexing failure.
Message Text
Security database unavailable: exception_stack
Message Text
Security timestamp too old
Message Text
variable1:Invalid lseek64, variable2
Cause
A host operating system file function returned an unexpected error while MarkLogic was accessing a file. The host operating system function, file name, and error message are included in the error report.
Response
See the host operating system documentation for the precise meaning of the error message. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.
Message Text
Error in server variable1
Cause
There is an app server or task server with that identifier, but not on this host. The identified host is not in the same group as the identified app server or task server.
Response
Choose a server identifier from the group the host belongs to.
Message Text
Cannot put in a server field a database node, a streaming result sequence, or an object containing a database node or streaming result sequence
Message Text
Another request in the same session has concurrently started a multi-statement transaction
Message Text
No module to spawn
Message Text
Invalid spawn path: variable1
Message Text
Cannot update server-maintained properties
Cause
An attempt was made to update a server-maintained property, and user code cannot update those properties (for example, prop:last-modified, prop:content-length, and prop:directory).
Response
Change your code to not update these properties.
Message Text
Grammar error in SPARQL: variable1
Response
Fix grammar error(s).
Message Text
An aggregate function cannot be used in this position
Cause
You have used an aggregate function outside of a SELECT expression, HAVING clause, or ORDER BY clause.
Response
Move the use of the aggregate function to a permitted position.
Message Text
RDF Dataset is set inappropriately
Cause
Dataset is set in both the query and the options, making the SPARQL request not compliant with SPARQL 1.1 specification.
Response
Check the query and the options
Message Text
Unescaped newline characters in SPARQL string literal: "variable1"
Cause
The SPARQL string contains unescaped newline characters.
Response
Escape newline characters using "\n", or use the three quote form of triple string literal.
Message Text
The BIND variable is already bound by an earlier clause in the group graph pattern: variable1
Cause
A variable bound by a BIND clause is already bound by an earlier clause in the group graph pattern, and its value cannot be changed.
Response
Use a different variable name in the BIND clause, or remove the clause entirely.
Message Text
Variable value supplied by the calling environment: variable1
Cause
A variable bound by a VALUES or BIND clause is already bound in the map passed into the call to sem:sparql() or sem:sparql-triples().
Response
Use a different variable name in the VALUES or BIND clause, or remove the clause entirely.
Message Text
Graph already exists: variable1
Cause
The graph to create already exists.
Message Text
Invalid format in Graph Document: variable1
Cause
Graph Document already exists but does not conform to schema.
Response
Check the Graph Document.
Message Text
Inequality operations are not supported on values of unknown type, unsupport type, or schema invalid values: variable1
Message Text
No such RDF Graph: variable1
Cause
The graph does not exist.
Message Text
Incompatible string arguments
Cause
The string arguments to the SPARQL function have incompatible language tags.
Response
Use identical language tags, or strings without language tags.
Message Text
Cannot use SPARQL Update on in-memory sem:store
Cause
Run SPARQL Update against in-memory sem:store
Message Text
Cannot execute multiple SPARQL Update statements with same-statement isolation
Message Text
The VALUES clause contains a row with the wrong number of values: variable1
Cause
All the rows of a VALUES clause must contain the same number of values.
Response
Add extra values or use UNDEF.
Message Text
Parser stack overflow
Message Text
Stack overflow
Message Text
Unsupported stand version variable1 for variable2
Cause
The version of this stand is outside the range supported by this version of Marklogic. Newer MarkLogic versions understand stands written from older MarkLogic versions, but older MarkLogic versions do not necessarily understand stands from newer MarkLogic versions.
Response
Check the compatibility of versions of MarkLogic you are switching between. The capability of MarkLogic understanding stands written by newer versions is limited. Generally patch versions are compatible, but major versions are not.
Message Text
A document node must be the first node.
Message Text
There can be only one root node.
Message Text
static-check option not allowed in this function
Message Text
Stemmed word searches not enabled
W3C XQuery Standard Equivalent: err:XPTY0020
Message Text
Context item is not a node
W3C XQuery Standard Equivalent: err:FOTY0014
Message Text
You cannot take the string value of a function
Message Text
Sub-databases have different timestamps
Message Text
Detected stale XSLT module: variable1
Cause
An XSLT module on the filesystem, or a module that uses an XSLT module, has been detected as being out of date.
Response
If XDMP-TAINTEDCACHEMODULE appears as an infrequent Debug message, no action is required. Cache invalidation is a normal part of database operations.
If XDMP-TAINTEDCACHEMODULE appears frequently as a Debug message, you may have a performance issue. You should avoid modifying your modules so frequently, so that you get the advantage of module caching.
Message Text
The target path already exists: "variable1"
Message Text
Modules database for Task does not exist
Message Text
An error was encountered in Telemetry background process: variable1
Cause
An unexpected error happened communicating with Telemetry.
Response
Please check Telemetry configuration or KMS if encryption is enabled.
Message Text
An error was encountered during Telemetry initialization process: variable1
Cause
Telemetry failed to initialize during server initialization.
Response
Please check whether Telemetry Staging directory is created correctly.
Message Text
An internal error was encountered communicating with Telemetry: variable1
Message Text
An internal error was encountered communicating with Telemetry: variable1 variable2 variable3 variable4 variable5
Message Text
No valid endpoint was found to connect to Telemetry: variable1
Message Text
Not a valid JSON structure in: variable1
Message Text
An invalid request error was returned as a response to communicating with Telemetry: method variable1, variable2
Message Text
The response received from Telemetry is invalid: variable1
Message Text
The maximum number of retries exceeded while connecting to Telemetry: variable1
Message Text
An attempt to connect to Telemetry using https requires SSL: variable1, $2
Message Text
Server unable to build program from non-text document
Cause
MarkLogic server is unable to construct a program from the module at the indicated location. Possible causes include:
There is no module at the indicated location.
The module was not loaded as a text file.
An imported module could not be found.
Response
Verify your module location is consistent with the root configured into your app server.
Make sure you upload modules into the app server as text. Usually, using the .xqy suffix and no type is sufficient.
Ensure your app server and your code are in agreement. For example, if you place your code in the file system, your app server should reference it in the file system, not in a database. If you place your code in a database, ensure your app server references the same database.
Message Text
An error occurred trying to run tidy: code=variable1 message='variable2'
Message Text
Request time limit exceeds the maximum allowed.
W3C XQuery Standard Equivalent: err:FODT0003
Message Text
Invalid timezone value
Message Text
There is no node to build.
Message Text
Document text size exceeds variable1 document text size limit of variable2 megabytes
W3C XQuery Standard Equivalent: err:XPST0017
Message Text
Too few args, expected variable1 but got variable3
Cause
The function call provided too few arguments for the function.
Response
Check the documentation for expected arguments, and provide the correct number.
Message Text
Too few labels, expected variable1 but got variable2
W3C XQuery Standard Equivalent: err:XPST0017
Message Text
Too many args, expected variable2 but got variable3
Cause
The function call provided too many arguments for the function.
Response
Check the documentation for expected arguments, and provide the correct number.
Message Text
Document contains too many atoms
Cause
A document cannot contain more than 2^32 (4294967296) total unique tokens.
Response
Make your document smaller and/or break the document into multiple smaller documents.
Message Text
Too many character classes: variable1
Message Text
Document contains too many characters
Cause
A document cannot contain more than 2^32 (4294967296) total characters of unique tokens.
Response
Make your document smaller and/or break the document into multiple smaller documents.
Message Text
Too many labels, expected variable1 but got variable2
Message Text
Document contains too many node names
Cause
A document cannot contain more than 2^32 (4294967296) total unique node names.
Response
Make your document smaller and/or break the document into multiple smaller documents.
Message Text
Document contains too many variable1 nodes
Cause
A document cannot contain more than 2^28 (268435456) total nodes (text nodes, element nodes, attribute nodes, and so on).
Response
Make your document smaller and/or break the document into multiple smaller documents.
Message Text
Too many positions
Cause
When calculating a positions vector for a query against a particular document, the intermediate positions vector for that document will become larger than the allowable maximum. This is generally the result of combinatorial positions calculations from large and-queries or near-queries within nested element-queries, particularly for large documents with repeating element structures. When one of the terms within an and-query is a very common word (e.g. "the"), this is more likely to happen. The error will only be thrown if the "too-many-positions-error" option is used in the search.
Response
(1) Don't use the "too-many-positions-error" option. This will lead to a false positive with unfiltered search: either filter, or accept the false positives. (2) Improve the data modeling so that the searchable unit is a document, so that positions need not be used to select a particular subscope from many repeating subscopes. (3) Remove common words from and-queries to reduce the number of possibilities that must be examined. Common words often arises when queries are automatically expanded from user phrases. (4) Apply one of the trace events that increases the limit and restart the cluster. This should be applied with great care: it will increase time and space required to resolve queries, which may negatively impact overall system performance. Trace events: "Posting Positions 2X", "Posting Positions 4X", "Posting Positions 1M", "Posting Positions 2M", "Posting Positions 4M", "Posting Positions Max".
Message Text
Too many stands
Cause
The forest has reached the 64-stand limit.
Response
This error can occur if the system has not been allowed to merge and has accumulated more stands than the stand limit. Make sure that merging is enabled, and that your MERGE MAX SIZE is not set to such a low number that the system cannot merge (the default of 48GB is recommended for MERGE MAX SIZE). Merging reduces the number of stands in a forest, and merging is needed to get past this error.
Message Text
Too many values passed in
Cause
The function call provided too many values for an argument.
Response
Provide fewer values to the argument of the function call.
Message Text
Document contains too much text
Cause
A document cannot contain more than 2^28 (268435456) memorywords, which are used to encode atom IDs. This translates to roughly 200 million text nodes, depending on how big the text nodes are. This limit is for a document constructed in memory; when you save a document to the database, the limit is 512MB per fragment.
Response
Make your document smaller and/or break the document into multiple smaller documents.
W3C XQuery Standard Equivalent: err:XPDY0050
Message Text
Invalid treat: variable1 treat as variable2
Message Text
Could not find trigger module: variable1
Message Text
Invalid trigger path: variable1
Message Text
Invalid triple element
Cause
Invalid triple element.
Response
Check element and try again.
Message Text
Wrong number of operators specified for the triple index function, variable1 operators supplied
Cause
The wrong number of operator string have been given.
Response
Use either one operator or three.
Message Text
Invalid triples document
Cause
Invalid triples document.
Response
Check triples document and try again.
Message Text
Triple cache full on host variable1
Message Text
Triple index bad triple: variable1: variable2
Message Text
Triple index not enabled
Cause
The triple index not available for querying. It may need to be enabled or the reindexer may need to finish reindexing after enabling.
Response
Enable the triple index. Confirm that the reindexer has completed reindexing.
Message Text
Too many entries in triple index variable1
Cause
The settings for maximum stand size are set too large, resulting in a stand with more than 2^32 distinct values in the triple index.
Response
Review your settings for maximum stand size.
Message Text
Triple index permutation not enabled
Cause
Forests created on versions of MarkLogic before 9.0-1 did not support some triple index sort orders.
Response
Reindex the database.
Message Text
Triple value cache full: variable1
Message Text
Timestamp overflow
Message Text
Transaction with identifier variable1 already completed
Cause
A statement waiting to execute using an explicit transaction ID has found that the transaction has already been committed or rolled back before it could execute.
Response
Do not commit or rollback the transaction until all statements have finished executing using it.
Message Text
Transaction mode options cannot be used in library modules
Cause
A transaction mode option was specified in an XQuery library module.
Response
Move the transaction mode option to the main module.
Message Text
Invalid transaction-mode value: must be "auto", "query", or "update"
Cause
A transaction mode was specified with an incorrect value.
Response
Correct the transaction mode.
Message Text
The TupleIterator tuple member accessor is not defined for that type
Cause
The wrong TupleIterator accessor has been called for the type of that tuple member.
Response
Use the correct accessor for the type.
Message Text
TupleIterator index out of bounds: variable1
Cause
The specified index is greater than the width of the tuple.
Response
Add code to handle smaller tuple widths than expected.
Message Text
Encoder capacity exceeded. host: variable1
Cause
The Encoder has a limit of 512Mb of data permitted in one message.
Response
This may indicate a bug in your encoding algorithm.
Message Text
An error occurred in the user-defined function plugin: variable1
Cause
A user defined function from a plugin reported an error.
Response
Consult the error message.
Message Text
The plugin API value has expired
Cause
Plugin API values like Map and Sequence have defined lifetimes, after which they cannot be used.
Response
Copy the values you need out of the plugin API values.
Message Text
Invalid OutputSequence usage: variable1
Cause
The methods of OutputSequence have been called in an order that does not make sense.
Response
Fix the code using the OutputSequence instance.
Message Text
Member access on a Sequence object when Sequence::done() is true.
Cause
The Sequence object has moved past the end of the sequence. This can happen because it is an empty sequence, or because Sequence::next() has been called until the end of Sequence has been reached.
Response
Only access Sequence members if Sequence::done() returns false.
Message Text
Unknown xdmp:tidy option or bad option value: variable1
W3C XQuery Standard Equivalent: err:XPST0081
W3C XSLT Standard Equivalent: err:XTSE0280
Message Text
Prefix variable1 has no namespace binding
Cause
A namespace prefix appears in your code for which there is no declared namespace binding.
Response
Declare your namespaces explicitly.
Message Text
variable1:Uncaught throw
Message Text
Undefined aggregate function variable1
Cause
You have used an aggregate function name that does not exist.
Response
Examine your code for typos, or ensure that the requisite aggregate is defined.
Message Text
Undefined complex type variable1
W3C XQuery Standard Equivalent: err:XPST0017
Message Text
Undefined function variable1
Cause
You have used a function name that is not in scope.
Response
Examine your code for typos, missing namespace qualifications, or missing module imports.
W3C XQuery Standard Equivalent: err:XQST0059
Message Text
Undefined schema "variable1"
W3C XQuery Standard Equivalent: err:XQST0059
Message Text
Undefined schema "variable1" at "variable2" resolved to "variable3"
W3C XQuery Standard Equivalent: err:XPST0051
Message Text
Undefined simple type variable1
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Undefined type variable1
W3C XQuery Standard Equivalent: err:XPST0008
Message Text
Undefined variable variable1
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Unexpected token variable1
Message Text
Unexpected stands in forest variable1: missing=variable2 found=variable3
Cause
There is an inconsistency between the Forest's label and its stands at mount time.
Response
If you have an active maintenance contract, you can contact MarkLogic Technical Support.
Message Text
Invalid syntax for path index: variable1 exception_stack
Cause
Only a subset of XPath 2.0 syntax is allowed in index creation. User has supplied a path expression that has some non-permitted syntax.
Response
Check the syntax of path expression. Only a sub-set of XPath 2.0 grammar is allowed in index creation.
Message Text
Unknown character class: variable1
Message Text
Unknown directory variable1 in backup directory
W3C XQuery Standard Equivalent: err:XQST0123
Message Text
Unknown required feature: variable1
Message Text
Unknown file variable1 in backup directory
Message Text
An unknown URL template expansion variable was encountered connecting to Ops Director: variable2
Message Text
Unlocked, variable1
Cause
During a read or write operation, the system encountered an unlocked node or other resource where a lock was expected. For example, during cts:eval, the system expects a read lock on the node being evaluated.
Response
Correct your code. The context for the error is included in the message. To learn more about locking in MarkLogic Server, see the Application Developer's Guide.
Message Text
Invalid format for unpath
Cause
xdmp:unpath function supports a subset of XPath syntax. User has specified a path expression that uses XPath operators xdmp:unpath does not support.
Response
Refer to MarkLogic Server documentation for the xdmp:unpath supported XPath syntax.
Message Text
Query variable1 is not registered
Message Text
Expression is unsearchable
Message Text
Unsupported lexicon type: variable1
Cause
The type of the lexicon input is not supported.
Response
Correct your code.
Message Text
Unsupported data type
Cause
The data type of the first item is not supported.
Response
Correct your code.
Message Text
Number formatter doesn't support this language.
Cause
User has specified an unsupported language.
Response
Use one of the supported languages.
Message Text
Unwilling foreign replica: forest variable1 does not accept update from forest variable2 in cluster variable3 (variable4)
Cause
This occurs during database replication when a forest in the replica database receives an update from an unexpected forest in the master database. Typically, this is due to the asynchronous nature of replication and communication within the cluster and the issue will resolve automatically.
Response
If the issue does not resolve automatically within a few minutes and you have a current maintenance contract with MarkLogic, you can contact MarkLogic Technical Support.
Message Text
Unwilling replica: forest variable1 does not accept update from forest variable2 (variable3)
Cause
This occurs during local-disk fail-over forest replication when a replica forest receives an update from an unexpected forest. Typically, this is due to the asynchronous nature of replication and communication within the cluster and will resolve automatically.
Response
If the issue does not resolve within a few minutes and you have a current maintenance contract with MarkLogic, you can contact MarkLogic Technical Support.
Message Text
Cannot update constructed nodes
Message Text
Cannot process updates from queries with same-statement isolation
Cause
A transaction being run as a query attempted to perform an update. For example, using xdmp:apply to execute an update function when the xdmp:apply is in a query transaction.
This error also occurs if you use xdmp:eval or xdmp:invoke with same-statement isolation in a query transaction. You may only use same-statement isolation with update transactions.
For more information, see the discussion of Isolation option to xdmp:eval/invoke in the Application Developer's Guide.
Response
Possible solutions to this error include:
Use
different-transaction isolation in the problem
xdmp:eval or
xdmp:invoke.Use
xdmp:eval instead of
xdmp:apply if you know the applied function may be an update.
If the problem occurs with
xdmp:apply, and you know the applied function will perform an update, force the transaction to be an update. For example:
let $force-update :=
if (fn:true())
then ()
else xdmp:document-insert('/fake.xml', <fake></fake>)Message Text
Cannot apply an update function from a query
Cause
A dynamic function call was made to a function that might perform database updates. This is not allowed from a statement executing under a query (read-only) transaction.
Response
Execute the calling statement under an update transaction. Define the function so that it does not update the database.
Message Text
Invalid xdmp:update option value, must be "true" or "false"
Message Text
No forests allow updates variable1
Message Text
Cannot process timestamped updates
Message Text
Cannot update external nodes
Message Text
Invalid URI format: variable1
Message Text
URI lexicon not enabled
W3C XQuery Standard Equivalent: err:XTDE1420
Message Text
Failed to resolve URI(s)
Message Text
Cannot use app server LDAP configuration with user specified URL
Cause
An LDAP operation was attempted that specified both a server URL and requested that the app server configuration be used.
Response
Either specify an empty URL, or don't use the app server configuration
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Use 'declare' rather than 'define' (declare variable1)
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Use 'empty-sequence()' rather than 'empty()'
Message Text
User change is only allowed for a different transaction
Message Text
Invalid UTF-8 escape sequence
Cause
A string contains an invalid UTF-8 byte sequence.
Response
Encode the string in UTF-8 correctly.
W3C XQuery Standard Equivalent: err:XQDY0027
Message Text
Instance of abstract element: Element variable1 is abstract using schema variable2
Cause
Validation determined that an element in the instance was declared as abstract in the schema. This means that the specific element name should not appear in a valid document. Typically such an element is a substitution group head and the document should contain specific members of that substitution group instead.
Response
Fix the instance to that it does not contain abstract elements.
W3C XQuery Standard Equivalent: err:XQDY0027
Message Text
Instance of abstract type: Type variable1 of element variable2 is abstract using schema variable3
Cause
Validation determined that an element had a complex type declared in the schema as abstract. This may reflect the case where the intention is that the instance include an xsi:type selecting a specific concrete subtype.
Response
Fix the element in the instance to be valid, perhaps by adding an xsi:type attribute.
W3C XQuery Standard Equivalent: err:XQTY0030
Message Text
Argument to validate expression must be document or element node
Cause
An attempt was made to validate something that was not a document node, element node, or (in XSLT) an attribute node.
Response
Fix the application to avoid validation of inappropriate items.
W3C XQuery Standard Equivalent: err:XQDY0027
Message Text
Invalidly derived type: Element variable1 xsi:type variable2 not validly derived from variable3 using schema variable4
Cause
Validation detected an element with an xsi:type attribute where the type referred to in that attribute was not validly derived from the declared type of the element. This could be because the type is not a subtype of the declared type at all, or because the schema prohibits the derivation explicitly.
Response
Fix the instance to use an appropriate type in the xsi:type attribute, or fix the schema to allow the derivation, if appropriate.
W3C XQuery Standard Equivalent: err:XQST0061
Message Text
A validated document node must contain exactly one root element
Cause
Validation was attempted on a document node that was a binary document, a text document, or had more than one root element.
Response
Validation only applies to XML documents.
W3C XQuery Standard Equivalent: err:XQDY0027
W3C XSLT Standard Equivalent: err:XTTE1555
Message Text
Bad field specification: Bad field specification variable1 at variable2 using schema variable3
Cause
Validation detected an identity constraint definition whose field was not a valid XPath expression.
Response
Fix the identity constraint definition in the schema.
W3C XQuery Standard Equivalent: err:XQDY0027
W3C XSLT Standard Equivalent: err:XTTE1555
Message Text
Bad field type: Bad type for field variable1 at variable2 using schema variable3
Cause
Validation detected an identity constraint definition whose field failed to select a single element node with simple content.
Response
The instance is invalid. Fix the instance.
W3C XQuery Standard Equivalent: err:XQDY0027
Message Text
Invalid fixed type: variable1 lexical value variable2 invalid for expected fixed value variable3 at variable4 using schema variable5
Cause
Validation detected an attribute or element that was declared to have a fixed value in the schema, but the attribute or element did not have that value.
Response
The instance is invalid. Replace the offending value with the correct fixed value.
W3C XQuery Standard Equivalent: err:XQDY0027
W3C XSLT Standard Equivalent: err:XTTE1555
Message Text
Bad key: Non-referring key field variable1 at variable2 using schema variable3
Cause
Validation detected a key constraint that failed to select any elements.
Response
The instance is invalid. Make sure that all key values refer properly.
W3C XQuery Standard Equivalent: err:XQDY0027
W3C XSLT Standard Equivalent: err:XTTE1555
Message Text
Bad referenced key: Bad referenced key for keyref variable1 at variable2 using schema variable3
Cause
Validation detected a keyref constraint that failed to refer to node value for a key.
Response
The instance is invalid. Make sure that all elements with keyref constraints properly refer to node value for a key.
Message Text
Invalid schema "variable1" at "variable2": exception_stack
Cause
The schema variable1 at schema URI variable2, used in a validation episode, does not meet the validity requirements of XML Schema Part I, as defined by W3C. In a valid schema, all definitions are valid, complete, and unique.
Response
Review and correct your schema. Check for duplicate or erroneous definitions.
W3C XQuery Standard Equivalent: err:XQDY0027
W3C XSLT Standard Equivalent: err:XTTE1555
Message Text
Bad selector specification: Bad selector specification variable1 at variable2 using schema variable3
Cause
Validation encountered an identity constraint definition with a selector that was not a valid XPath expression.
Response
The schema is invalid. Ensure that the XPath expressions on the identity constraint selectors are valid.
W3C XQuery Standard Equivalent: err:XQDY0027
Message Text
Invalid node type: variable1 lexical value variable2 invalid for expected type variable3 at variable4 using schema variable5
Cause
Validation encountered an element or attribute simple value that was not lexically valid per the declared type.
Response
The instance is invalid. Ensure that the content of the element or attribute has the correct lexical form for its declared type.
W3C XQuery Standard Equivalent: err:XQDY0027
W3C XSLT Standard Equivalent: err:XTTE1555
Message Text
Duplicate ID: ID value variable1 is a duplicate at variable2 using schema variable3
Cause
Validation determined that the same ID was used more than once in a document.
Response
The document is invalid. Make sure there is only one definition of each ID.
W3C XQuery Standard Equivalent: err:XQDY0027
W3C XSLT Standard Equivalent: err:XTTE1555
Message Text
Duplicate key: Duplicate key variable1 for identity constraint variable2 at variable3 using schema variable4
Cause
Validation determined that a uniqueness constraint was violated. For some identity constraint definition declared with unique keys, a key was used in the document more than once.
Response
The document is invalid. Make sure each key that is supposed to be unique is defined only once in the document.
W3C XQuery Standard Equivalent: err:XQDY0027
W3C XSLT Standard Equivalent: err:XTTE1555
Message Text
Validated node was not valid: variable1 (variable2)
Cause
Validation failed for some reason not specifically called out. For example, if an attribute is declared as having a fixed value and the type xs:ID, this error occurs. The error gives more information for the reason for the failure.
Response
Depending on the specific reason for the error, the instance may be invalid and need fixing, or the schema may be invalid and need fixing.
W3C XQuery Standard Equivalent: err:XQDY0027
Message Text
Missing required attribute: Found variable1 but required variable2 at variable3 using schema variable4
Cause
Validation detected an element that was missing a required attribute.
Response
The instance is invalid. Add the required attribute to the element.
W3C XQuery Standard Equivalent: err:XQDY0027
Message Text
Missing required elements: Expected variable1 at variable2 using schema variable3
Cause
Validation detected an element that was missing a required child element.
Response
The instance is invalid. Add the missing element.
W3C XQuery Standard Equivalent: err:XQDY0027
Message Text
Nilled element has content: Element variable1 nilled but has content
Cause
Validation detected an element that was declared as nillable and had an xsi:nil element, but which had child elements or text content anyway.
Response
The instance is invalid. Either remove the xsi:nil attribute or remove the non-nilled content from the element.
W3C XQuery Standard Equivalent: err:XQDY0084
Message Text
Missing element declaration: Expected declaration for node variable1 in non-lax mode using schema variable2
Cause
Validation failed because an element or attribute was found without a corresponding declaration. In some cases this can occur because an element somewhere within the subtree of the element was missing a declaration. This can be either because the schema is missing the declaration, the proper schema could not be located, or the element or attribute is incorrect (misspelled, for example).
Response
Fix the schema or the content or the schema location as appropriate.
W3C XQuery Standard Equivalent: err:XQDY0027
W3C XSLT Standard Equivalent: err:XTTE1555
Message Text
No ID for IDREF: IDREF value variable1 has no corresponding ID using schema variable2
Cause
Validation detected the use of an IDREF with no corresponding ID in the document.
Response
The document is invalid. Make sure that every reference to an ID matches up with some ID in the document.
W3C XQuery Standard Equivalent: err:XQDY0027
W3C XSLT Standard Equivalent: err:XTTE1555
Message Text
No matching key for keyref: No matching key for keyref variable1 for identity constraint variable2 at variable3 using schema variable4
Cause
Validation detected a keyref value that had no corresponding key value in the document.
Response
The document is invalid. Make sure that every keyref matches some key in the document.
W3C XQuery Standard Equivalent: err:XQDY0027
Message Text
Element not nillable: Element variable1 disallows @xsi:nil using schema variable2
Cause
Validation detected an element with xsi:nil set to true where the element declaration does not allow for nilled instances.
Response
The instance is invalid. Either remove the xsi:nil attribute or add appropriate content to the element to make it valid with respect to its declaration.
W3C XQuery Standard Equivalent: err:XQDY0084
W3C XSLT Standard Equivalent: err:XTSE1520
Message Text
Missing type definition: Expected type definition for variable1 for node variable2 using schema variable3
Cause
Validation could not find a type definition for an element or attribute. This could be because the element or attribute is spelled incorrectly or misplaced, because the schema lacked a definition, or because the proper schema could not be located.
Response
Fix the instance, the schema, or the schema location as appropriate.
W3C XQuery Standard Equivalent: err:XQDY0027
Message Text
Invalid node: Found variable1 but expected variable2 at variable3 using schema variable4
Cause
Validation detected unexpected content (element, attribute, or text).
Response
The instance is invalid. Fix the content to be valid. Check the name of the element or attribute reported as unexpected, or remove the unexpected text.
W3C XQuery Standard Equivalent: err:XQDT0027
Message Text
Validation failed: variable1 exception_stack
Cause
Reserved for XQDT error.
Response
Reserved for XQDT error.
W3C XQuery Standard Equivalent: err:XQST0048
Message Text
Variable variable1 not in target namespace variable2
W3C XQuery Standard Equivalent: err:XQST0116
Message Text
A variable declaration's annotations cannot contain more than one annotation named %fn:private or %fn:public.
Message Text
Windows registry error: variable1 variable2: variable3
Message Text
Windows service error: variable1: variable2
Cause
MarkLogic Server, running as a service on the Windows platform, received an unexpected error. variable1 names the internal operation which encountered an error, and variable2 describes the specific problem. For example:
XDMP-WINSVCERR OpenSCManager Access is denied.
In this example, an access denied error occurred while the server was attempting to connect to the Windows Service Control Manager. The underlying cause was starting the server without Windows Administrator privileges.
Response
Corrective action varies, depending upon the specific Windows service error encountered. Contact MarkLogic Technical Support if you are uncertain how to proceed and have a current maintenance contract.
Message Text
No word lexicon for variable1
Cause
The query requires a lexicon that does not exist.
Response
Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.
Message Text
Unstemmed word searches not enabled
Message Text
variable1:Invalid write, variable2
Cause
An inconsistency was detected while writing an index file. Details about the inconsistency are included in the error report.
Response
Restarting MarkLogic on the host may clear an inconsistency in memory. Merging on the affected forest may clear an inconsistency on disk. Reindexing the affected forest may clear an inconsistency on disk.
W3C XQuery Standard Equivalent: err:XPTY0004
Message Text
Wrong number of arguments specified, expected variable1 but got variable2
Cause
The dynamic function call provided the wrong number of arguments for the function.
Response
Check the documentation for expected arguments, and provide the correct number.
Message Text
cluster variable1(variable2) thinks it is really cluster variable3(variable4)
Cause
A host connects to another host and thinks that host is in the same cluster. But the cluster id does not match. This can happen if some hosts are using an older configuration and other hosts are using a new configuration.
Response
Check if configurations on the hosts are correct.
Message Text
Host variable1(variable2) thinks it is really host variable3(variable4)
Message Text
Operation not allowed on the XA transaction with identifier variable1
Response
Commit the transaction using the transaction manager that started it. In exceptional circumstances, an administrator can call xdmp:transaction-rollback to remove the transaction from the system.
Message Text
XDBC client version is incompatible with server: client version: variable1
Message Text
Bad XDQP Locality for connection from variable1 variable2 in cluster variable3 on variable4 port
Message Text
XDQP cannot communicate with different platform/architecture
Message Text
XDQP connection disconnected, variable1
Cause
The internal cluster protocol connection (XDQP) between two nodes in the cluster was unexpectedly closed. This is a retryable exception.
Response
Normally, the nodes in the cluster will automatically reconnect without manual intervention. This is a retryable exception, and if a client application runs into the exception it can retry the request. If there is a problem with one of the nodes, then the other node cannot reconnect and the problem node will be dropped from the cluster. After the problem node is dropped, correct the problem and reconnect the affected node to the cluster.
Message Text
Invalid XDQP request, variable1
Cause
XDQP is a MarkLogic internal protocol used for communicating between e-node and d-node hosts. Possible causes of this error include:
Another application is using the port assigned to XDQP.
A query, join, or other operation in your MarkLogic application attempted to pass more than 160M of data in a single remote request.
Response
If you suspect another application is using the XDQP port, disable the application or move it to another port.
If you suspect your application is exceeding the 160M transmission limit, refactor your operation to pass data in smaller chunks. For example, optimize your query to fetch fewer unwanted results from the d-node.
Message Text
Invalid XDQP response, variable1
Cause
XDQP is a MarkLogic internal protocol used for communicating between e-node and d-node hosts. Possible causes of this error include:
Another application is using the port assigned to XDQP.
A query, join, or other operation in your MarkLogic application attempted to return more than 160M of data in a single remote request.
Response
If you suspect another application is using the XDQP port, disable the application or move it to another port.
If you suspect your application is exceeding the 160M transmission limit, refactor your operation to pass data in smaller chunks. For example, optimize your query to fetch fewer unwanted results from the d-node.
Message Text
Too many XDQP listeners on host variable1
Cause
The maximum number of hosts connecting to this host through XDQP has been exceeded. No more than 255 other hosts may connect to this host through XDQP. Hosts in local clusters connect to every other host in the cluster. Hosts in foreign clusters connect to hosts with replica forests. Hosts in foreign clusters also connect through bootstrap hosts.
Response
Avoid creating large single clusters of hosts. Instead use super-clusters and super-databases. For example, 1024 hosts can be organized into 32 clusters of 32 hosts. See the MarkLogic Administrators Guide Chapter about Super Databases and Clusters.
Message Text
No XDQP results, variable1
Message Text
No XDQP session on host variable1, variable2
Cause
An XDQP message referenced an XDQP session that does not exist. This can happen if an XDQP session timed out (for example, if the network is really busy) or if an XDQP session was terminated (for example, if a node restarted).
Response
If the message shows as a debug message in the ErrorLog.txt file, and if there are a small number of these messages, then it indicates that there was a transient problem that corrected itself. If you see many messages for a large period of time, it might be an indication of a system that is resource bound, and you should find the cause of the resource contention and correct it.
Message Text
XDQP version mismatch: variable1
Cause
XDQP is a MarkLogic internal protocol used for communicating between e-node and d-node hosts. This message indicates the two hosts involved in the communication are running incompatible versions of MarkLogic Server.
Response
Check the compatibility of the versions of MarkLogic Server running on the affected hosts and upgrade or downgrade one host, if appropriate.
Message Text
No transaction with Xid variable1
Cause
A transaction with the given Xid was not found.
Response
This usually indicates an error in the transaction manager being used. You should report this as a bug to the transaction manager vendor.
Message Text
Invalid XML character variable1
W3C XQuery Standard Equivalent: err:XQTY0105
Message Text
Functions cannot be used in the content of an element constructor
W3C XQuery Standard Equivalent: err:XQDY0044
Message Text
Cannot create xmlns attribute with computed attribute constructor
W3C XQuery Standard Equivalent: err:XPST0003
Message Text
Processing instructions may not have the target 'XML'
W3C XQuery Standard Equivalent: err:XTDE1420
Message Text
XPath 2.0 prohibits a sequence of more than one nodes as a base node
W3C XQuery Standard Equivalent: err:XQST0031
Message Text
XQuery version is not recognized: "variable1" (must be "0.9-ml", "1.0" or "1.0-ml")
Message Text
Declared XQuery version (variable1) does not match this parser (variable2)
Message Text
All modules in a module sequence must use the same XQuery version: first="variable1", this="variable2"
Message Text
Fragmented schema
Message Text
No namespace binding for prefix in schema reference: Prefix in reference to 'variable1' not bound
W3C XQuery Standard Equivalent: err:FORG0004
Message Text
fn:one-or-more called with a sequence containing zero items
Message Text
Error closing zip file
Message Text
Mismatched counts: variable2 parts, but variable1 nodes
Message Text
File in zip is encryped: variable1
Message Text
Duplicate names not allowed in zip files: variable1
Message Text
File not found in zip: variable1
Message Text
Path of a ZIP part is empty
Message Text
File is too big to add to zip
Message Text
Error adding file to zip
