Documentation Center

Error codes

Provides an overview of all errors that can be returned by Web Services API.

Introduction

The number, the code and the message correspond with the error information specified in the resource file isAuthor.en.xml

General

NrCodeMessageAction
0NoErrorOperation successfully completed.None
-1SystemFailureAn unexpected system failure occurred. {reason}Unexpected/Undocumented error. First check the reason parameter for more information about the error. If no additional information is available in the reason parameter, look in the log file of your application for more information.
-2AccessDeniedAccess is denied.If you believe you should have access, try to sign in again. There are two possible explanations: (1) you entered an incorrect user name or password or (2) the context has expired.
-3DBNoConnectionNo connection could be made to the database. {reason}Verify that the database is not down and that the correct connection string was specified. If the database is up and the connection string is correct, check the reason parameter for more information about the error.
-4AccessDeniedPasswordLockThe maximum number of sign-in attempts has been reached. Please contact your system administrator to unlock your account.Contact your system administrator to unlock your account.
-5AccessDeniedPasswordAgedOutYour password has expired. Please enter a new password or contact your system administrator.Enter a new password or contact your system administrator.
-6AccessDeniedUserDisabledYour account has been disabled. Please see your system administrator.Contact your system administrator to enable your account.
-10NewPasswordPasswordTooLargeThe provided password is too long.Enter a new, shorter password or contact your system administrator.
-11NewPasswordPasswordTooSmallThe provided password is too short [min. length:{length}].Enter a password that meets the minimum length requirement or contact your system administrator.
-12NewPasswordPasswordHistoryThe provided password was used before. Please choose a different password.Choose a different password or contact your system administrator.
-13NewPasswordPasswordCompexityThe provided password does not meet the complexity pattern. Please enter a new password. [pattern:{pattern}]Change your password or contact your system administrator.
-14AccessDeniedProfileMismatchThe access is denied because no profile match was found. {reason}Contact your system administrator to verify user management.
-15AccessDeniedNoContextAccess is denied. No context or application information is available. Please contact your system administrator.Try to sign in again or contact your system administrator.
-16AccessDeniedNoAppInfoAccess is denied. No context or application information is available. Please contact your system administrator.Verify that you entered a correct TriDKApp registry entry. The parameters in this TriDKApp indicate the location of the database and other configuration settings.
-17ContextExpiredThe supplied authentication context is expired. Please sign in again.Try to sign in again.
-18AccessDeniedInvalidApplicationNameAccess is denied. The application name is invalid. Contact your system administrator. [expected:{expectedapplicationname}, actual:{actualapplicationname}] 
-20NotImplementedThe method or operation is not implemented: {reason}None: the requested functionality has not been implemented yet.
-21InfoShareAggregateMultiple errors occurred.Contact your system administrator and have them retrieve the error from server-side logging.
-25InfoShareInvalidOperationA method call is invalid for the object's current state: {reason}Check the reason parameter for more information about the error.
-30ErrorMessageMissingThe method or operation returned an error which could not be read or converted. Please verify the server side logging.Contact your system administrator and have them retrieve the error message from server-side logging.
-31InvalidRegionalSettingsPlease contact your system administrator. The user "{username}" hosting the application on the Web/App server "{hostname}" is using unsupported date time settings. Conversion of hardcoded value "{value}" resulted in unexpected value "{result}". Please adjust the short date time format in the Regional Settings of the designated user on the specified Web/App server and restart the application/server.Ask your system administrator to adjust the short date time format in the Regional Settings of the designated user on the specified Web/App server, and to restart the application/server.
-101FolderNotEmptyThe folder cannot be deleted because it is not empty. Please remove all objects first.Ensure that the folder is empty, then try again.
-102ObjectNotFoundThe {object} {value} does not exist. [{paramname}:"{paramvalue}"]The specified object was not found in the repository. Check if the specified object still exists. If it does, contact your system administrator.
-103SetupFailureSetup Failure: {reason}A failure was found in the setup.
-104UsergroupNotEmptyThe user group cannot be deleted because it still contains users.Ensure that the user group/department is empty, then try again.
-105LOVProblemThe value is not present in the corresponding list of value.Contact your system administrator.
-106InvalidElementNameThe identifier "{object}" is invalid. {reason}The specified object was not found in the repository. Check if the specified object exists.
-107SecurityProblemYou have no access to the object "{object}".Check your rights to modify the object.
-108DuplicateValueErrorThe value "{value}" already exists.Use a unique value.
-109ObjectAlreadyExistThe object "{object}" already exists.You are trying to create an object that already exists. Use a unique value.
-110XMLParseErrorThe object "{object}" contains invalid XML. {reason}Verify the well-formedness and validity of the specified XML. Check the reason parameter for more information about the error.
-111XMLIncorrectIdErrorIncorrect identifier found in the XML file. Please verify the identifier and try again.Verify the identifier and try again.
-112ObjectModifiedByOthersThe object "{object}" has been modified by another user in the meanwhile.The provided original values don't match the values in the database. Probably another user already updated the object, or you provided invalid original values.
-113InvalidValueThe given value "{value}" is invalid. {reason}Verify the metadata you specified. Check the reason parameter for more information about the error.
-114CardAccessDeniedAccess to the object is denied.Check your rights to modify the object.
-115ReferencedImpossible to delete the object because it is referenced by one or more objects. Generate a report to find the reference(s). Remove the reference(s) and try again.Generate a report to find the reference(s). Remove the reference(s) and try again.
-116ObjectNoLongerExistsThe "{object}" does not exist.The specified object has been deleted. Check if the object exists. If it does, contact your system administrator.
-117ObjectNotPartOfUserGroupYou do not have write access to the selected object "{object}".The user has no write access to the user group owning the object. Check your rights to modify the object.
-118AdministratorRightRequiredAdministrative rights are required.Only administrator-level users can perform this operation. Check your rights to modify the object.
-119LngIsCheckedOutThe object "{object}" is checked out by '{username}'.The object is checked out by another user. Check the status of the object.
-120LngIsReleasedThe object "{object}" is released. {reason}Check the status of the object.
-121InvalidOutputConfigurationThe output configuration is invalid.Contact your system administrator.
-122InvalidPasswordThe given password is invalid.Check the password you provided.
-123NotAllOutOfDateImpossible to delete the object. Not all language-level objects are "Out of date".You can only delete a version of an object if all languages of that object version are out of date. Check the statuses of the languages.
-124DocumentToBeApprovedThe status of the object is "To be approved". 
-125LanguageIsMandatoryThe language identifier must be supplied.Ensure that the item has a language.
-126FieldCannotBeSetThe field '{field}' cannot be set or is a system field.Check the field name you are trying to modify.
-127ObjectAlreadyMovedThe object was already moved by another user.Check if the object still exists in the provided location.
-128CannotBeMovedToItSelfA folder cannot be moved under itself.Check if you are not trying to insert a folder in one of its children (which would create a circular link).
-129InvalidDocTypeforFolderThe object cannot be created in the given folder due to the folder content type {foldertype}.Check the content type of the folder or the item you are trying to insert.
-130LngHasSystemLockThe object is locked by the system for starting reuse.Try again later.
-131SearcherNotStartedYour search request failed. The full-text search service is not running. Please contact your system administrator. {reason}Contact your system administrator..
-132LngIsCheckedOutBySameUserYou already checked out this object.The object is probably already checked out by you. Check its status.
-133LngNotCheckedOutThe object is not checked out.The object isn’t checked out yet, or the action requires a check-out. Check out the object.
-134InvalidStatusTransitionThe object "{object}" cannot be moved to the selected status because it is not allowed by the current workflow.The object does not meet all criteria for being moved to the selected status. Check if the status transition you are trying to perform is valid for the object and for the current status of the object.
-135SearcherSyntaxErrorYour search request failed. Check the syntax of the search or refine your criteria. {reason}The full-text search service detected invalid characters in your query. Check the syntax of the provided metadata XML.
-136AlreadyAnAuthLngForVersionTarget languages will be created automatically. If you want to add more than one translation manually, please disable translation management.If you want to add more than one translation manually, disable translation management.
-137FolderDoesnotExistThe folder identifier that was supplied does not exist.Check if you provided correct data.
-138InvalidConditionSyntaxOne or more condition names and/or values stored inside the XML instance are syntactically incorrect.Check the syntax of the condition(s).
-139ObjectStillInUseThe object cannot be deleted, because it is still used by one or more objects. Please generate a report or a full-text search to see where it is used.Generate a report or perform a full-text search to see where the object is used.
-140ObjectInUseThe object is used by another user.The object is in use by another user and cannot be accessed. Try again later.
-141InvalidStatusTransitionDueToPluginsThe object cannot be moved to the new status because some validation plug-ins were not executed successfully.Check which validation plug-ins must be executed to move to the next step, and check their effect on the object.
-142InvalidVersionNrThe version number "{version}" is not valid. {reason}The version number that was provided is not valid. Check the version number you provided for your object.
-143InvalidLanguageThe specified language "{value}" is invalid. {reason}Check the language identifier for your object.
-144InvalidResolutionInvalid or no resolution specified.Check the resolution for your object.
-145VersionIsMandatoryThe version number must be supplied.Check the version for your object. A version is required to access version-level and language-level information.
-146ObjectNotProcessedThe object "{object}" was not processed.During a batch operation, some objects were not processed. Check the log to find out why these objects failed to process.
-147InvalidCharactersThe {object} "{value}" contains invalid characters or character sequences: {chars}Check if the supplied metadata for your object contains any of the indicated characters or character sequences, and remove them if so.
-150StatusConfModifiedByOtherUserThe status configuration has been modified by another user in the meanwhile.Try again later with refreshed data.
-151StatusConfInvalidThe supplied status configuration is invalid.Check the validity of the available XML or contact your system administrator.
-152StatusUsedInTransitionsThe status that you try to delete is still in use in the status configuration.Check if any objects are available in the specified status.
-153StatusUsedInInboxDefinitionsThe status that you try to delete is still in use in the inbox definition.Check if any objects are available in the specified status.
-154InCorrectInboxDefinitionContents of the inbox cannot be retrieved because the inbox definition is incorrect. Please contact your system administrator.Check the validity of the available XML or contact your system administrator.
-155DocumentNotFoundDocument is not present in the Repository.The electronic document is not present in the repository. Provide such a file.
-156InvalidLogicalIdAn invalid logical id was entered.The supplied document identifier is invalid. This message can appear for two reasons: (1) No object exists with the specified identifier. Check if the supplied identifier is correct. (2) The identifier provided to the create statement contains invalid characters. Remove the illegal characters from the identifier.
-157InvalidFieldField {object} does not exist.Check the provided fields for your chosen card type.
-158CannotMoveToItsChildrenThe destination folder is the same folder or is a subfolder of the folder you want to move.Make sure that you are not trying to insert circular links.
-159UserAlreadyExistsA user with the name you specified already exists in the system.Verify the uniqueness of the data provided.
-160FolderAlreadyExistsA folder with the name you specified already exists. Please use a different folder name.Specify a different folder name.
-161QueryFolderWithoutQueryThe query folder contains an invalid query or no query at all: {reason}Check if the provided metadata XML specification is valid. Check the reason parameter for more information about the error.
-162RequiredParameterNotFoundThe required parameter "{object}" was not found. {reason}A required parameter is missing. One possible explanation is that the plug-in configuration parameters are missing. Verify your plug-in configuration XML in the Administrator screen.
-163XMLIncorrectLngErrorThe language encoded inside the submitted XML instance does not correspond with the language in the Repository.The language parsed out of the provided XML file does not match the one provided in the metadata. Check both.
-164NoBranchingAllowedYou are not allowed to create a branch on this version.You attempted to branch the latest version of an object. Doing this is unnecessary.
-165TooManyValuesThe field "{field}" has too many values.You are trying to add multiple values in a single-value metadata field. Check if you are not entering a value containing the standard Content Manager field separator “, “ (comma-space) into a single-value field.
-166NotEnoughValuesThe field "{field}" does not have enough values.A required metadata field is not filled in. Ensure that no mandatory fields are empty.
-167InvalidFileNameInvalid file name "{object}".Check the provided filename. The filename can be an incorrect registry key or an incorrect parameter coming from a configuration XML.
-168VersionContainsBranchThe version cannot be deleted because it still contains branches.Delete the branches of this version. You cannot delete this version while it still contains branches.
-169ValueTooLongThe value exceeds the limit of {maxlength} characters.Check the length of the value you entered.
-170MissingPublicationThe {object} {value} is not attached to a publication or the publication is invalid.Do one of the following: (1) Check if the supplied object is attached to a publication; (2) Check if the supplied publication identifier exists in the repository.
-171MissingLanguagesYou are not allowed to remove languages from the object "{object}". The following languages are missing: {value}You are not allowed to remove the (working) languages from the object. Add the languages again.
-200LngIsCheckedOutOrReleasedThe object {object} you are trying to modify is already checked out or is released.Check the status of the object that you are trying to access.
-201NewPasswordDiffersFromConfirmPasswordThe provided passwords did not match. Please enter the same password in both fields.The new password differs from the confirm password. Ensure that the confirm password matches the new password.
-203ErrorLoadingXMLError loading the XML for the object "{object}": {reason}Ensure that the provided XML file is well-formed and valid. Check the reason parameter for more information about the error.
-204ErrorLoadingXSLError loading XSL for the object "{object}": {reason}Ensure that the provided XSL file is well- formed and valid. Check the reason parameter for more information about the error.
-205InCompleteResultThe result is incomplete.Try again.
-206InvalidProcessingInstructionThe processing-instruction contains invalid information: {object} {value}.The provided object data contains a processing instruction with invalid information. Verify that you are submitting the object data under the matching object.
-207MissingProcessingInstructionThe processing-instruction contains no {object} or is missing.The supplied object data contains an incomplete processing instruction. Verify that the processing instruction contains the following information: ishref, version and lang.
-208ExtraProcessingInstructionExtra processing-instruction found. {reason}The supplied object data contains an additional processing instruction. Verify that there is only one processing instruction containing the following information: ishref, version and lang.
-209ObjectUsedAsResourceThe object "{object}" cannot be deleted, because it is used as a resource on the publication "{title} v.{version}".Generate a full-text search to see where the object is used.
-210InvalidStartBaselineThe given StartBaseline doesn't exists.Check if the specified start Baseline exists.
-211StartBaselineNotReleasedThe given StartBaseline is not released.Check the status of your start Baseline.
-212BaselineAlreadyReleasedThe Baseline is already frozen.The Baseline is already released. You are not allowed to modify a released Baseline. Check the status of the specified Baseline.
-213NotAllObjectsVersionedThere is no version chosen in the Baseline XML for one or more objects.Make sure that all objects have a matching explicit version.
-214NotAllObjectsReleasedNot all objects are released in the source language(s) or in the required resolution.Check the status of all objects in the Baseline report.
-215NotAllObjectsExistNot all objects used in the Baseline exist in the database.Check the existence of all objects in the Baseline report.
-216ObjectUsedOnFrozenBaselineThe object is used on a frozen Baseline and cannot be deleted.None: you are not allowed to delete a version or any language of a version that is used on a frozen Baseline.
-217DuplicateVariableAssignmentVariable has more than one assignment.The variable has more than one assignment in this publication. Check if the variable is present in more than one resource specified for this publication.
-218VariableNotAssignedThe variable has no assignment.Check for a resource in which the variable is assigned to the value you want, and add that resource to the publication.
-219MissingObjectFragmentsThe fragments used in a fragment link are missing in the object "{object}".Check the fragment links and the object. Check if the correct version of the object is selected.
-220PrimaryIndexTermMandatoryThe primary Index term is mandatory.Insert a primary index term.
-221SecondaryIndexTermMandatoryWhenTertiarySecondary index term mandatory when a tertiary term is set.Insert a secondary index term when you provide a tertiary term.
-222IndexTermAssignedWithoutAnchorIndex term assigned without an anchor.Check if the index term isn’t already assigned to the complete object.
-223InvalidIndexTermInvalid Index Term.The index term is invalid. Verify that the index term is a valid term.
-224SecurityRuleViolatedInSubFoldersRevoking read access is not allowed: One or more subfolders have granted read access to this user group. Please revoke the read access on the subfolders first.You are trying to revoke read access on a folder, but one of the user groups still has read access to a subfolder. Revoke the read access of the subfolders before trying again.
-225SecurityRuleViolatedInParentFolderGranting read access to user groups that have no read access on the parent folder is not allowed. The read access on the subfolder must be the same or stronger than the read access on the parent folder.Check the read access of the parent folder. The read access on the subfolder must be the same or stronger.
-226SecurityRuleViolatedInTargetFolderYou cannot move the object: the target folder security settings are conflicting with the ones of the source folder.First change the read access of your target folder, then try again.
-227ErrorRunningPluginThe plug-in "{pluginname}" returned the following error: "{reason}"Do one of the following: (1) Use the specified reason parameter to solve the problem; (2) Check if the plug-in is configured correctly
-228PluginDuplicateValueThe plug-in "{pluginname}" encountered the value "{value}" more than once for field "{field}".The plug-in encountered a duplicate value in the XML and is configured to raise an error. Do the following: (1) Check if the plug-in is configured correctly and should throw an error; (2) Check the content of the blob/document.
-229PluginMissingConrefBeginThe plug-in "{pluginname}" returned the following error: The conref range used in object "{object} v {version} {language}" on the "{xmlelementname}" element is missing a conref attribute; it only contains a conrefend with value "{xmlattributevalue}". {reason}Check the content of the blob/document. The conref range used on the specified element contains only a conrefend attribute. Do one of the following: (1) Add the missing conref attribute; (2) Convert the conref range to a simple conref.
-250InvalidReusableObjectReferenceThe object data contains a reference to a non-existing reusable reference.Check if the reusable objects provided in your reusable object link statements exist in this database.
-251ReuseNotOnLatestVersionElement reuse may only be started from the latest version of a library topic.Contact your system administrator.
-252LanguageNotAvailableUnderLatestVersionOfReusableObjectLanguage not found for the reused element.The language document is not available in the latest version of the reusable object. Check if a translation has been submitted.
-253NoReleasedSourceDocumentFoundTranslation Management could not be started. No released object found in the source language(s).Check the status of your objects.
-254SystemFieldCannotBeSetUnable to set a system field.Check the field you are trying to update.
-255NotEnoughRightsYou do not have enough rights to start the application.Check if the account that you are using to sign in has enough rights.
-256SuccessfullyLoggedOutYou have successfully been logged out.You clicked the logout button. Click the login button to login again.
-257InvalidConfigurationPartThe {object} "{value}" is configured incorrect. Please contact your system administrator.The application part you are trying to run is missing or configured incorrectly. Do one of the following: (1) Contact your system administrator. (2) Check the configuration file. (3) Install the application part mentioned in the error.
-258NoErrorNumberAn error was raised, but no error number was available.Something went wrong during the logging of an error. Save or download the error and contact your system administrator.
-259RegisterEventThe event "{eventtype}" is raised. The corresponding background process is launched.If you want, in the event monitor associated with this event, follow the progress of the action you initiated.
-263TerminatedWithErrorsOrWarningsThe action is completed but errors or warnings are logged...The action (typically taken on multiple items) has ended, but not all processing went successfully. Check the log for more information.
-264SecurityRuleViolatedOnOwnerAccessOwner should have read access on the object.Ensure that the owner has read access to the object, then try again.
-265InvalidFolderTypeInvalid folder type.For updating a query folder or a reference folder, the specific functions must be used.
-270UpdateViolatedWorkflowYou are not allowed to update this object in this stage of the workflow. The object is currently in the status {status}.Check the status of the object.
-271CreateViolatedWorkflowYou have either insufficient rights to create new objects in this status or no initial status is defined.Do the following: (1) Check the write access of the object; (2) Check if an initial status is defined.
-272TerminologyUpdateFailedThe terminology update can only be performed on the highest version in the branch.Check the status of the object.
-273InvalidStatusTransitionDueToCheckoutThe object "{object}" cannot be moved to the requested status because it is checked out.Check in the object, then try again.
-274OnlyPossibleOnSourceLanguageMoving a translated object from a released status to a draft status is not possible.None: because translation management is triggered whenever an object is moved to a released status, it is not possible to reset the status of an object for which one or more translations are already available.
-275NotPossibleOnFrozenBaselineThe object cannot be moved to the new status because it is part of a frozen Baseline.None: if a version of an object belongs to a frozen Baseline, it is not possible to change it anymore.
-277ReplaceAllLanguagesNotAllowedYou are not allowed to replace ALL existing languages "{oldvalue}" with a completely new value "{newvalue}". At least one language should be in the old and new value.None: for illustrations, you can specify multiple languages for the same resolution. However, one of the languages is considered the source language and should not be removed when adding or removing other languages.
-278InvalidStatusForActionThe status of this object prevents to complete this operation.None: this type of operation is not possible when the object is in this particular status.
-279ObjectIsReleasedThe object "{object}" is released. {reason}The object is released.
-280InvalidObjectTypeInvalid object type "{object}". Expected "{expected}" type.The object has an invalid object type.
-281FreezeFailureMasterRefMissingUnable to freeze Baseline. No map is added to publication "{title} v.{version}". [c:{cardid} ce:{cardelement}]Check the metadata of the publication. Before releasing the publication (and freezing the Baseline), a map must have been added to the publication.
-282ObjectUsedAsMasterRefThe object "{object}" cannot be deleted, because it is added as map on the publication "{title} v.{version}".Generate a report to find the reference(s).
-283LogicalIdTooLongThe identifier "{value}" exceeds the limit of {length} characters.The identifier exceeds the maximum character limit. Check the length of the identifier.
-284TranslationMgmtFromLanguageMissingThere is no "FromLanguage" specified in the Translation Management XML for the requested language(s) "{value}".Contact your system administrator.
-285InboxConfModifiedByOtherUserThe Inbox configuration has been modified by another user in the meanwhile.Try again later with refreshed data.
-286BaselineNotReleasedThe Baseline is not frozen.Freeze the Baseline. You must freeze the Baseline before releasing a publication.
-287ReplaceLanguageNotAllowedYou are not allowed to replace existing language "{oldvalue}".If an illustration has only one language, you cannot replace this source language with another language. Do one of the following: (1) Add the extra language to the same illustration, indicating that this illustration is valid for both languages; (2) Create another illustration with the same resolution, but a different language.
-288NotSupportedObjectTypeObject type "{objecttype}" is not supported.None: the specified object type is not supported for this action
-100001InternalErrorInternal error: {reason}Contact your system administrator, or examine reason to solve the problem.
-100002InternalWarningInternal warning: {reason}Contact your system administrator, or examine reason to solve the problem.
-101001ConfigurationInvalidCombinationInvalid combination of "{object1}" "{value1}" and "{object2}" "{value2}" in "{location}".Contact your system administrator, or check the given object/value combinations for the specified Configuration XML or registry key.
-101002ConfigurationRequiredParameterNotFoundThe required parameter "{object}" was not found in "{location}".Contact your system administrator, or check the given object/value combinations for the specified Configuration XML or registry key.
-101003ConfigurationRegistryCannotReadApplicationNameKeyApplication name "{applicationname}" cannot be read or does not exist in "{location}".Contact your system administrator.
-101004ConfigurationResourceDirectoryDoesNotExistResource directory "{resourcedirectory}" cannot be read or does not exist in "{location}".Do one of the following: (1) Contact your system administrator; (2) Check if the registry string ResourceDir for the Application contains a valid directory.
-101005ConfigurationResourceFileDoesNotExistResource file "{resourcefile}" cannot be read or does not exist in "{location}".Do one of the following: (1) Contact your system administrator; (2) Check if the directory specified in the registry string ResourceDir for the Application contains the file specified in the error description.
-101006ConfigurationRequiredParameterValueNotCorrectThe required parameter "{parameter}" contains an incorrect value "{value}". {reason}Contact your system administrator.
-101007DatabaseConfigurationInvalidColumnInvalid database configuration: "{databaseerror}". Make sure that all necessary, upgrade script are executed successfully.Do one of the following: (1) Contact your system administrator; (2) Check if all necessary upgrade scripts have been executed successfully.
-101008InvalidDatabaseConfigurationInvalid database configuration: {reason}. Make sure that all necessary, upgrade script are executed successfully.Do one of the following: (1) Contact your system administrator; (2) Verify that all necessary upgrade scripts have been executed successfully.
-101009NotSupportedThe object is not supported: {reason} 
-102001InvalidObjectThe {object} {value} does not exist. [{paramname}:"{paramvalue}"]The object does not exist. Check the provided data.
-102002MissingCardTypeDefinitionThe "{object}" contains no card type definition for card type "{value}".The field set contains no definition for the specified card type. Check the provided data.
-102003ObjectNotInitializedThe {objecttype} "{object}" cannot be returned, because it is not initialized. 
-102004ObjectAlreadyInitializedThe "{object}" cannot be set, because it is already initialized. 
-102005InvalidValueLevelCardValue "{value}" is invalid for the "{fieldname}" field of object "{object}". {reason} [c:{cardid} ce:{cardelement} ct:{cardtype} f:{fieldid} fe:{fieldelement} ft:{fieldtype} fmin:{fieldmin} fmax:{fieldmax}]Check the supplied metadata for the specified field, using the information in the reason parameter. Use the parameters between brackets to identify the field and the object.
-102006MissingValueLevelCardValue is missing for the "{fieldname}" field of object "{object}". {reason} [c:{cardid} ce:{cardelement} ct:{cardtype} f:{fieldid} fe:{fieldelement} ft:{fieldtype} fmin:{fieldmin} fmax:{fieldmax}]A value is missing for a field of the object. Check if you have supplied a value for the specified field. Use the parameters between brackets to identify the field and the object.
-102007NotEnoughValuesLevelCardValue "{value}" contains not enough values for the "{fieldname}" field of object "{object}". Parsing your value with separator "{valueseparator}" results in {fieldvaluecount} values not exceeding {fieldmin}. {reason} [c:{cardid} ce:{cardelement} ct:{cardtype} f:{fieldid} fe:{fieldelement} ft:{fieldtype} fmin:{fieldmin} fmax:{fieldmax}]Check if you have supplied enough values for the specified field. Use the parameters between brackets to identify the field and the object.
-102008TooManyValuesLevelCardValue "{value}" contains too many values for the "{fieldname}" field of object "{object}". Parsing your value with separator "{valueseparator}" results in {fieldvaluecount} values exceeding {fieldmax}. {reason} [c:{cardid} ce:{cardelement} ct:{cardtype} f:{fieldid} fe:{fieldelement} ft:{fieldtype} fmin:{fieldmin} fmax:{fieldmax}]

Check if you have supplied too many values for the specified field.

-102009ObjectIsReadOnlyUnable to complete your request, you are not allowed to alter {object} "{objectname}". {reason} [c:{cardid} ce:{cardelement} ct:{cardtype}]Check the write access of this object.
-102010ObjectTooLongThe {object} {value} exceeds the limit of {length} characters.Check the number of characters in the value of this object.
-102011InvalidFilterValueForLovFiltering on field "{fieldname}" returns an empty result set because filter value "{filtervalue}" does not exist. {reason} [f:{fieldid} fe:{fieldelement} ft:{fieldtype} fd:{fielddomainelement}]Check if the supplied filter value exists in the list of values (LOV) associated with the specified field. Use the parameters between brackets to identify the field and the LOV.
-102012InvalidFilterValueFiltering on field "{fieldname}" returns an empty result set because filter value "{filtervalue}" does not exist. {reason} [f:{fieldid} fe:{fieldelement} ft:{fieldtype} ct:{cardtype}]Check the filter value. For example, if the field is associated with a user, the supplied filter value must be a valid username.
-102013InvalidOperatorForFieldTypeFilter operator "{filteroperator}" is not allowed on field "{fieldname}". {reason} [f:{fieldid} fe:{fieldelement} ft:{fieldtype}]Not every operator can be used with every type of field. Check the allowed filter operators in Understanding metadata filter operators.
-102014InvalidNumberOfFilterValuesForOperatorThe number of filter values for field "{fieldname}" does not correspond to the requested filter operator "{filteroperator}". Parsing your filter value with separator "{valueseparator}" results in {filtervaluecount} values while expecting {expectedcount} filter values for filter operator "{filteroperator}". {reason} [f:{fieldid} fe:{fieldelement} ft:{fieldtype}] 
-102015FilterQuerySyntaxErrorEncountered database limitation when filtering on field "{fieldname}" with filter value "{filtervalue}". {reason} [f:{fieldid} fe:{fieldelement} ft:{fieldtype} fo:{filteroperator}] 
-102016PopulatingAnUpdatedFieldValuePopulating the already updated field "{fieldname}" is not allowed. The updated value "{currentvalue}" would get lost when refreshing with database value "{value}". [c:{cardid} ce:{cardelement} ct:{cardtype} f:{fieldid} fe:{fieldelement}] 
-102020InvalidTableFilterValueFiltering on column "{name}" returns an empty result set because filter value "{filtervalue}" does not exist. {reason} [t:{tablename} col:{columnname} coltype:{columntype}] 
-102021InvalidOperatorForColumnTypeFilter operator "{filteroperator}" is not allowed on column "{columnname}". {reason} [t:{tablename} col:{columnname} coltype:{columntype}] 
-102022InvalidNumberOfTableFilterValuesForOperatorThe number of filter values for column "{columnname}" does not correspond to the requested filter operator "{filteroperator}". Parsing your filter value with separator "{valueseparator}" results in {filtervaluecount} values while expecting {expectedcount} filter values for filter operator "{filteroperator}". {reason} [t:{tablename} col:{columnname} coltype:{columntype}] 
-102023TableFilterQuerySyntaxErrorEncountered database limitation when filtering on column "{columnname}" with filter value "{filtervalue}". {reason} [t:{tablename} col:{columnname} coltype:{columntype} fo:{filteroperator}] 
-103001NoRegisteredCrawlerFoundNo registered crawler found for hostname "{hostname}" and catalog "{catalog}".Check the provided hostname and catalog name. If the provided hostname and catalog name combination is correct, use the register command of the Crawler to add this hostname and catalog name combination.
-103002ObjectNotMarkedForDeletionDeleting the object "{object}" failed, because it was not marked for deletion. 
-104001InvalidInformationForTypeProvided information "{object} v {version} {language} {resolution}" is not of type "{type}".Check the type of the supplied object.
-104002InvalidCardIdForTypeProvided information "{cardid}" is not of type "{type}".Check the type of the supplied object.
-104003InvalidFieldForTypeThe provided field "{field}" is not defined on type "{type}".Check the field you are trying to update.
-104004LovValueUsedOnConfigurationXmlThe value "{lovvalueelement}" you try to delete is still used on "{configurationxml}" [le:{lovelement} lve:{lovvalueelement} lv:{lovvalue}]Check the specified configuration, then try to delete the value again.
-105001InvalidParameterThe parameter {object} with value "{value}" is invalid. {reason}Check if all supplied parameters are valid (use the information in the reason parameter).
-105002SchemaValidationFailureThe XML of {object} did not pass schema {schemaId} validation. {reason}Check the supplied XML using the information in the reason parameter.
-105003InvalidParameterCombinationParameters {object1} and {object2} with value "{value}" is not a valid combination. {reason}Check the provided parameters. More information about the conflict can be found in the reason parameter.
-105004MissingXmlElementThe required element "{elementName}" was not found in "{object}".Check the supplied XML using the information in the reason parameter.
-105005MissingXmlAttributeThe required attribute "{attributeName}" was not found on the "{elementName}" element in "{object}".Ensure that the specified XML element has the specified required attribute.
-105006InvalidValueTypeForFieldTypeValue type "{valuetype}" is not allowed on field "{fieldname}". {reason} [f:{fieldid} fe:{fieldelement} ft:{fieldtype}] 
-105007FieldAlreadySpecifiedThe field "{fieldelement}" can only be specified once on level "{level}".Ensure that each field is provided only once per level.
-105008PreferenceSetAlreadySpecifiedThe preference set "{preferencesetname}" can only be specified once.Ensure that the preference set is specified only once.
-105009PreferenceItemAlreadySpecifiedThe preference item "{preferenceitemname}" can only be specified once.Ensure that each preference item is specified only once.
-105010InvalidCombinationInvalid combination of {object1} "{value1}" and {object2} "{value2}". 
-106001ObjectHasBeenReplacedUnable to complete your request, because the {object} has been replaced with another one. {reason}Check the status of the provided object using the information in the reason parameter.
-106002UserCannotCreateObjectUser "{username}" having write access to "{writeaccess}" cannot create an object in usergroup "{usergroup}". {reason} [ce:{cardelement} ct:{cardtype}]Check if you have write access to the user group in which you want to create an object.
-106003BaselineStillInUseThe Baseline cannot be deleted, because it is still used by one or more publication. {reason}Perform a publication metadata search with this Baseline to check which publication(s) is/are referencing this Baseline.
-106004CannotMoveBaseFolderFolder "{object}" cannot be moved, because it is a basefolder. [c:{cardid} ce:{cardelement}]You cannot move the base folders Data/, System/, Favorites/ and Editor templates/.
-106005MissingReadAccessOnSourceFolderYou are missing read access to move the folder or one of its subfolders. [folderc:{foldercardid} subfolderc:{subfoldercardid}]Check if you have read access to the folder you want to move, and to all of its subfolders.
-106006MissingWriteAccessOnSourceFolderYou are missing write access to move the folder or one of its subfolders. [folderc:{foldercardid} subfolderc:{subfoldercardid}]Check if you have write access to the folder you want to move, and to all of its subfolders.
-106007CannotCreateContentFolderInFavoritesThe folder "{foldername}" with content type "{foldertype}" cannot be created in folder "{favoritesfolder}" or one of its subfolders.Check the type of the folder you want to create. In a Favorites folder and in its subfolders, you can only create reference folders.
-106008CannotMoveFolderToFavoritesMoving folders to "{favoritesfolder}" folder or one of its subfolders is not possible.None: you cannot move a folder to a Favorites folder or to one of its subfolders.
-106009CannotDeleteEventThe progress information cannot be deleted, because the event "{progressid}" has status "{status}".Check the status of the event. Either the event is still busy, or it has failed. You are not allowed to delete busy or failed events.
-106010NoWriteAccessOnSystemObjectYou have no write access to system {objecttype} "{object}". {reason}Check the information in the reason parameter to solve the problem.
-106011InvalidCurrentMetadataThe supplied expected metadata value "{requiredvalue}" does not match the current database value "{actualvalue}" so we rolled back your operation. To make the operation work you should make sure your value matches the latest database value. [f:{fieldid} fe:{fieldelement} ft:{fieldtype}] 
-106012InvalidCurrentFolderThe supplied from folder "{requiredvalue}" does not match the current folder "{actualvalue}".Check if current folder is the specified from folder, then try to move the objects again.
-106013MissingMetadataBindingThere is no metadata binding specified for field "{field}"Check if the extension configuration in the database has a metadata binding configuration for the specified field.
-106014MetadataBindingHandlerInitializationFailureThe initialization of the metadata binding handler failed. "{reason}"Do one of the following: (1) Check the information in the reason parameter to solve the problem; (2) Contact your system administrator to check if the handler is present in the expected Plugin directory on the file system.
-106015MetadataBindingHandlerExecutionFailureThe metadata binding handler "{handlername}" returned the following error: "{reason}"Check the information in the reason parameter to solve the problem.
-106016MetadataBindingHandlerDisposalFailureThe metadata binding handler "{handlername}" returned the following error while disposing: "{reason}"Check the information in the reason parameter to solve the problem.
-106020TargetXmlFileHandlerInitializationFailureThe initialization of the target xml file handler failed. "{reason}"Do one of the following: (1) Check the information in the reason parameter to solve the problem; (2) Contact your system administrator to check if the handler is present in the expected Plugin directory on the file system.
-106021TargetXmlFileHandlerExecutionFailureThe target xml file handler "{handlername}" returned the following error: "{reason}"Check the information in the reason parameter to solve the problem.
-106022TargetXmlFileHandlerDisposalFailureThe target xml file handler "{handlername}" returned the following error while disposing: "{reason}"Check the information in the reason parameter to solve the problem.
-106023LeaseNotAvailableNo database token available for lease. "{reason}" [ce:{cardelement} fe:{fieldelement} tokenname:{tokenname} tokenvalue:{tokenvalue}]Try again later. Only one service is allowed to send out translation jobs or roll back topics at a time.
-106024PublicationNotDeployedYou are not allowed to unpublish publication "{objectName}", because it is not deployed.Check which of the following is the case: (1) the output format for this publication output is not publishing to Dynamic Delivery; (2) the publication output was not published successfully to Dynamic Delivery; (3) the publication output was already successfully unpublished.
-106025CannotDeleteAnnotationWithRepliesThe annotation cannot be deleted, because the annotation "{annotationid}" has "{relpyCount}" replies." 
-106026FeatureNotEnabledThe feature "{featurename}" is not enabled. Please contact your system administrator. 
-106027NotEnoughPrivilegesYou do not have enough privileges for this action. {reason}Check the information in the reason parameter to solve the problem.
-106028InvalidUserForActionThe current user {username} cannot perform this action. {reason}Check the information in the reason parameter to solve the problem.
-106029ObjectInReleasedPublicationThe object "{objectname}" is part of a released publication. {reason} 
-106030ObjectIsNotReleasedThe object "{objectname}" is not released, its current status is "{status}". {reason} 
-106031PublicationInUseThe publication "{publication}" with version "{version}" is used in the project "{project}". 
-107001API20FirstErrorFirst error of the InfoShare.API20 starts with 107001 
-108001ActionProtectedFieldUsage of field "{field}" during a "{action}" action is not allowed. {reason}

Check the field name you are using.

-109001InvalidSolrConnectionUnable to connect to {baseurl}. {reason} [retries:{retries} timeout:{timeout}]Contact your system administrator to double-check the SolrLucene configuration.
-109002BadSolrLuceneRequestInvalid {action} request. {reason} [statuscode:{statuscode}] [{responseuri}] [retries:{retries} timeout:{timeout}] 
-109003NoWebResponseUnable to get WebResponse for {responseuri}Contact your system administrator to double-check the SolrLucene configuration.
-109010InvalidSearchSyntaxYour search request failed. Check the syntax of the search or refine your criteria. {reason}Check the search syntax using the information in the reason parameter.
-109011InvalidSearchOperatorForFilterFieldFilter fields does not support the search operator {searchoperator}. Use one of the following operators: {operators}Check the search operators used in the search syntax.
-110001PluginHostFailureAn unexpected system failure occurred in the plug-in host system. "{reason}"Check the information in the reason parameter to solve the problem.
-110002PluginInitializationFailurePlug-in initialization failed. "{reason}"Check the information in the reason parameter to solve the problem.
-110003PluginExecutionFailureThe plug-in "{pluginname}" returned the following error: "{reason}"Check the information in the reason parameter to solve the problem.
-110004PluginDisposalFailureThe plug-in "{pluginname}" returned the following error while disposing: "{reason}"Check the information in the reason parameter to solve the problem.
-111001PluginConnectionToExternalSystemFailure"{name}" could not connect to the external system due to the following error: "{reason}"Check the information in the reason parameter to solve the problem.
-111002PluginIntegrationWithExternalSystemFailure"{name}" received an error from the external system. Error details: "{reason}"Check the information in the reason parameter to solve the problem.
-111003ProcessingXmlFailureProcessing the XML file "{filepath}" failed. {reason}Check the information in the reason parameter to solve the problem.
-115001TaskExecutionTimeOutThe execution of background task {taskid} with "{eventType}" timed out after {timeOut} minutes [tid:{taskid} u:{userId} p:{progressId} a:{attempt} hid:{historyId}] 
-115002TaskExecutionForceStoppedThe execution of background task {taskid} with "{eventType}" was stopped [tid:{taskid} u:{userId} p:{progressId} a:{attempt} hid:{historyId}] 
-115003TaskLeaseExpiredThe lease period for background task {taskid} with "{eventType}" has expired after {leaseTimeout} minutes [tid:{taskid} u:{userId} p:{progressId} a:{attempt} hid:{historyId}] 
-115004BackgroundTaskHandlerInitializationFailureBackground task handler initialization failed. "{reason}"Do one of the following: (1) Check the information in the reason parameter to solve the problem; (2) Contact your system administrator to check if the handler is present in the expected Plugin directory on the file system.
-115005BackgroundTaskHandlerDisposalFailureThe background task handler "{eventType}" returned the following error while disposing: "{reason}"Check the information in the reason parameter to solve the problem.
-120000ReviewEndDateExpiredReview end date expired 
-120003ThumbnailCreationFailedThumbnail creation failed for object with mime type "{mimeType}" 
-120004LanguageResolutionNotAvailableThe language or resolution is not available.The language and/or resolution that was provided is not valid. Check the provided language (and resolution) for your object.
-120008PublicationOutputFileMissingNo file is attached to this publication output. 
-120009ConfirmationPasswordInvalidThe new password does not match the confirmation password. Please retry. 
-120010InvalidOldPasswordThe old password is invalid. 
-120014LanguageObjectNotFoundCannot show properties for this object. Please make sure that it has a version and a language created. The {object} {value} does not exist. [{paramname}:"{paramvalue}"] 
-120015VersionObjectNotFoundCannot show properties for this object. Please make sure that it has a version. The {object} does not have version {value}. 
-120016MissingDefaultLanguageYou are not allowed to create new object without default language [Default language: {value}]. Please make sure that default language is selected. 
-120017LanguageObjectNotFoundInAnyVersionObject is invalid. Language object was not found in any version. Please delete the object and create a new one. 
-120018LanguageObjectNotFoundInVersionObject version is invalid. Language object was not found in version {value}. Please delete the version and create a new one. 
-120019VersionObjectNotFoundInObjectObject is invalid. Version was not found in object. Please delete the object and create a new one. 
-120020LanguageOrResolutionNotFoundInVersionObject version is invalid. Language or Resolution object was not found in version {value}. Please delete the version and create a new one. 
-121001InvalidFileNameFormatFile name "{filename}" has an invalid format 
-121002MissingEDTForFileNo electronic document type found for file "{filename}"Ensure that there is an electronic document type containing the file extension of the specified file name.
-121003IncompleteFormThe form "{formId}" is not complete.Ensure that all mandatory fields are filled in.
-121004ShowFormIsRequiredShowing a property window is required. 
-121005CopyPublicationOutputFailedThe publication output "{object}" copy cannot be created. 
-125001UrlConnectTimeOutConnecting to "{url}" timed out 
-125002UrlConnectTimeOutAfterSecondsConnecting to "{url}" timed out after {timeout} seconds 
-140000LoadingMetadataConfigurationFailedLoading the metadata configuration failed. "{reason}"Ensure that the metadata configuration file contains valid XML.
-140001ResolvingReferenceFailedResolving reference for "{reference}" failed.Ensure that the metadata configuration file contains a matching identifier for each reference. Remember that some parts can be filtered out by ishconditions.
-140002FormDefinitionNotFoundThe form "{formid}" does not exist.Ensure that the metadata configuration file contains the specified FormId. Remember that some parts can be filtered out by ishconditions.
-140003LoadingFormDefinitionFailedThe form "{formid}" could not be loaded. {reason}Do one of the following: (1) Check the information in the reason parameter to solve the problem; (2) Ensure that the XML structure in the metadata configuration file is valid for the specified FormId. Remember that some parts can be filtered out by ishconditions.
-140004ResolveVariableFailedAn error occurred while resolving the variable "{name}". {reason}Check the information in the reason parameter to solve the problem.
-140005ResolvingFormMetadataFailedAn error occurred while resolving metadata for the form "{formid}". {reason}Check the information in the reason parameter to solve the problem.
-140006LoadingListDefinitionFailedThe list "{listid}" could not be loaded. {reason}Do one of the following: (1) Check the information in the reason parameter to solve the problem; (2) Check if the metadata configuration file contains the specified ListId. Remember that some parts can be filtered out by ishconditions.
-140007ListDefinitionNotFoundThe list "{listid}" does not exist.Check if the metadata configuration file contains the specified ListId. Remember that some parts can be filtered out by ishconditions.
-140008ResolvingListMetadataFailedAn error occurred while resolving metadata for the list "{listid}". {reason}Do one of the following: (1) Check the information in the reason parameter to solve the problem; (2) Check if the metadata configuration file contains the specified ListId. Remember that some parts can be filtered out by ishconditions.
-140009ResolvingMetadataFailedAn error occurred while resolving metadata. {reason}Check the information in the reason parameter to solve the problem.

Conditional Text

NrCodeMessageAction
-1020ConditionEvaluationErrorError during condition evaluation. 
-1021ConditionParseErrorError during condition parsing. 
-1100InvalidProductDefinitionThe product definition is invalid: {reason} 
-1200SchemaConfigurationErrorError while reading schema: {reason} 
-1201SchemaValidationErrorXML validation failed: {reason} 
-1300InvalidInputParametersInvalid value for inputparameter "{parameter}": {reason} 
-1301NoProductDefintionSpecifiedNo product definition specified to evaluate conditions. 
-1400InvalidConditionNameCondition name "{conditionname}" is invalid. {reason} 
-1401InvalidConditionValueCondition value "{conditionvalue}" is invalid. {reason} 
-1402ConditionNameContainsInvalidCharsCondition name "{conditionname}" contains one of the following invalid characters: {invalidchars} 
-1403ConditionValueContainsInvalidCharsCondition value "{conditionvalue}" contains one of the following invalid characters: {invalidchars} 
-1501UnexpectedTokenFound unexpected token "{token}", expected "{expected}" at position {position} in condition "{conditionparselocation}". 
-1502MissingConditionNameMissing condition name, found "{token}" at position {position} in condition "{conditionparselocation}". 
-1503MissingConditionValueMissing condition value, found "{token}" at position {position} in condition "{conditionparselocation}". 
-1504MissingOpenBracketMissing "(", found "{token}" at position {position} in condition "{conditionparselocation}". 
-1505MissingCloseBracketMissing ")", found "{token}" at position {position} in condition "{conditionparselocation}". 
-1506MissingOperatorMissing operator, found "{token}" at position {position} in condition "{conditionparselocation}". 
-1800InitializationFailureInitialization failed. {reason} 

Publish

NrCodeMessageAction
-2005NoVersionSelectedNo version selected for object "{object}".For this object no version is specified in the Baseline. Ensure that a version of the object is selected.
-2006ObjectMissingThe object "{object} v {version} {language} {resolution}" is not available in the Repository.The object cannot be found in the repository. Check if the object exists in the repository.
-2007ObjectNotReleasedThe object "{object} v {version} {language} {resolution}" is not released, its current status is "{status}".The object still has a draft status. Change the status of the object to a Released-type status.
-2008InvalidAccordingToDTDThe object "{object} v {version} {language}" is invalid against its DTD. ({parseerror})The XML could not be validated against its DTD. Ensure that the XML is valid against the DTD.
-2009VariableNotResolvedThe variable "{variable}" used in object "{object} v {version} {language}" could not be resolved.Ensure that the right resource file is attached to the publication.
-2010ConrefNotResolvedThe conref "{conref}" used in object "{object} v {version} {language}" could not be resolved.Check if the referenced element exists in the version included in your publication.
-2011HyperlinkTargetMissingThe hyperlink "{hyperlink}" used in object "{object} v {version} {language}" could not be resolved.Ensure that the referenced object is included in the map.
-2012LinkTargetMissingThe link "{link}" used in object "{object} v {version} {language}" could not be resolved.Ensure that the referenced object exists.
-2013DuplicateVariableAssignmentInPublicationThe value for variable "{variable}" assigned in "object {object} v {version} {language}" is also assigned elsewhere.A variable can only have one value. Check the resource files that define the variable, and remove or modify all but one of them.
-2014PublicationIsValidReleaseCandidateThis publication is a valid release candidate.None: this is an informational message which is shown in the Publish report to indicate that the current Publication Output can be released.
-2015PublicationIsDraftThis publication is a draft.This is an informational message which is shown in the Publish report to indicate that the current Publication Output contains unreleased objects or invalid references. Resolve the unresolved references and, if you want, release the unreleased objects.
-2016PublicationContainsNoStatusReportThis publication contains no status report.None: this is an informational message which is shown in the Publish report to indicate that the Publication Output was not yet published.
-2017ResolutionUnavailableImage "{object} v {version} {language} {resolution}" is unavailable.Check if the object exists.
-2018DuplicateKeyDefinitionInPublicationThe value for key definition "{key}" assigned in "object {object} v {version} {language}" is also assigned elsewhere.Ensure that you only have one definition for the specified key.
-2020StatusReportThis report contains only information about the objects used in this output.None: this is an informational message shown in the Publish report.
-2021StatusReportSharedBaselineThe Baseline is shared with other publications. Draft objects that are part of the Baseline but not included in this output will prevent the release of this output.None: this is an informational message shown in the Publish report
-2022StatusReportDifferentResolutionThe resolution used in the output format differs from the working resolution of the publication. Draft images in the working resolution will prevent the release of this output.None: this is an informational message shown in the Publish report
-2023StatusReportDifferentLanguageThe working language of the publication is not used in the output. Draft objects in the working language will prevent the release of this output.None: this is an informational message shown in the Publish report
-2024StatusReportCondionalFilteringConditional filtering removed some objects from this output. Draft objects not included in this output will prevent the release of this output.None: this is an informational message shown in the Publish report

Post-processing of the publish

NrCodeMessageAction
-23002StoreResultInvalidContextUnable to store the result: Invalid context. 
-23003StoreResultInvalidFileUnable to store the result: Invalid file location.

General exception indicating that something went wrong in one of the previous post-publish plug-ins and, as a result, no publish result was created.

For example: the IshRunDITAOT plug-in failed during the creation of a PDF. In that case, check the event log details for the action "SHELL command output" or "DITA-OT logging " for more information about the issue.

-23004StoreResultInvalidPubOutputUnable to store the result: Invalid publication output.Check if the publication output exists.
-24000PluginDetectedRejectReleaseCandidateOne of the publish post process plugins ended with RejectReleaseCandidateThis message appears in the event log during a publish action when one of the publish post-process plug-ins decides that the resulting publication output is not good enough to be a release candidate. Check the details in the event log to identify the issue, then fix it and republish the publication.
-24001PluginDetectedUserCancelOne of the publish post process plugins detected that the publish job was cancelled by the userNone: this message appears in the event log during a publish action when one of the publish post-process plug-ins detected that the publish job was cancelled by the user
-24002CannotLocatePublishResultFileFile matching the pattern "{filePattern}" was not found in the folder "{folder}"This message appears in the event log during a publish action when the publish result file cannot be found in the specified folder. Probably something went wrong during the generation of the publication output. Check the event log details for the action DITA-OT output for more information about the issue.
-24003FileNameTooLongThe file name "{fileName}" would become too long (maxlength: {maxLength})Ensure that the exportlocation configured in the background task configuration for the publish is not too big.
-24004FilePathTooLongThe file path "{filePath}" would become too long (maxlength: {maxLength})Ensure that the exportlocation configured in the background task configuration for the publish is not too big.