Loading TOC...
Messages and Codes Reference Guide (PDF)

Messages and Codes Reference Guide — Chapter 12

INFO Messages

INFO-ACTIVETICKET

Message Text

Cannot delete or unload active ticket

Cause

- User tries to delete a flow with an active ticket (documents loading is still in progress) - User tries to unload a database with an active ticket (documents loading is still in progress)

Response

- Unload database after documents loading is done (ticket is inactive) - Delete a flow after documents loading is done (ticket is inactive) - Stop the documents loading first, then unload the database or delete the flow

INFO-CONFLICTINGURI

Message Text

Cannot overwrite existing document variable1

Cause

The document with the specified URI already exists

Response

- Specify another URI when loading the document- When loading a document with the same URI, use either the "Replace" (old document is replaced) or "Ignore" (new document is ignored, old document is not replaced) options

INFO-DUPLICATENAME

Message Text

Cannot create database, database or forest name(s) already in use: variable1

Cause

Name given for a database or forest name already in use

Response

Use a different name for your database or forest

INFO-INACTIVETICKET

Message Text

Cannot modify inactive ticket

Cause

Modification was attempted on a ticket that was set to an inactive state.

Response

Once a ticket completes, it should be treated as an archival document only. Check your code to make sure that only active tickets are modified. If the problem persists, contact MarkLogic support.

INFO-INVALIDCOLLECT

Message Text

Invalid collector: variable1

Cause

A long-running Information Studio collector has produced an invalid response.

Response

If this occurs when running a custom collector, ensure that it is returning the correct HTTP response codes. If this happens to a built-in collector, contact MarkLogic support.

INFO-INVALIDDB

Message Text

Invalid database: variable1

Cause

Information Studio has attempted to access an invalid or non-existent database.

Response

Make sure the database exists and is visible in the Administrative interface.

INFO-INVALIDPOLICY

Message Text

Invalid policy

Cause

Cannot save an invalid policy.

Response

Before registering a policy document, run infodev:check-options on it.

INFO-INVALIDSTATUS

Message Text

Invalid status code: variable1

Cause

A ticket has been set to an invalid status code.

Response

Check your code to see if an invalid ticket status is being set anywhere. If not, contact MarkLogic support.

INFO-NOSUCHERROR

Message Text

No such error: variable1

Cause

Information Studio has attempted to access a non-existent error document.

Response

While reading errors stored in a ticket, an error document was not found where expected. Make sure the ticket exists and is available, and contact MarkLogic support if problems persist.

INFO-NOSUCHFLOW

Message Text

No such flow: variable1

Cause

Information Studio has attempted to access a non-existent flow.

Response

Make sure that the flow in question exists and is visible from the main Information Studio page.

INFO-NOSUCHPOLICY

Message Text

No such policy: variable1

Cause

User tries to return a policy that does not exist

Response

Provide a policy name that exists, check spelling of name you attempted to return.

INFO-NOSUCHTICKET

Message Text

No such ticket: variable1

Cause

An Information Studio operation has attempted to access a non-existing ticket.

Response

Make sure the ticket in question exists and has a sufficient retention policy to remain available for as long as needed.

INFO-RESTRICTEDDB

Message Text

Cannot modify settings for built-in database: variable1

Cause

Information Studio attempted to view or modify settings of a restricted database.

Response

Certain databases, such as Fab or Security, cannot be accessed via Information Studio APIs.

INFO-UNLOADFAILED

Message Text

Unable to unload data for ticket: variable1

Cause

Information Studio was unable to unload a collection of documents.

Response

Manually remove unwanted documents and contact MarkLogic support with details leading to this error.

« Previous chapter
Next chapter »
Powered by MarkLogic Server 7.0-4.1 and rundmc | Terms of Use | Privacy Policy