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
| Nr | Code | Message | Action |
|---|---|---|---|
| 0 | NoError | Operation successfully completed. | None |
| -1 | SystemFailure | An 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. |
| -2 | AccessDenied | Access 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. |
| -3 | DBNoConnection | No 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. |
| -4 | AccessDeniedPasswordLock | The 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. |
| -5 | AccessDeniedPasswordAgedOut | Your password has expired. Please enter a new password or contact your system administrator. | Enter a new password or contact your system administrator. |
| -6 | AccessDeniedUserDisabled | Your account has been disabled. Please see your system administrator. | Contact your system administrator to enable your account. |
| -10 | NewPasswordPasswordTooLarge | The provided password is too long. | Enter a new, shorter password or contact your system administrator. |
| -11 | NewPasswordPasswordTooSmall | The provided password is too short [min. length:{length}]. | Enter a password that meets the minimum length requirement or contact your system administrator. |
| -12 | NewPasswordPasswordHistory | The provided password was used before. Please choose a different password. | Choose a different password or contact your system administrator. |
| -13 | NewPasswordPasswordCompexity | The provided password does not meet the complexity pattern. Please enter a new password. [pattern:{pattern}] | Change your password or contact your system administrator. |
| -14 | AccessDeniedProfileMismatch | The access is denied because no profile match was found. {reason} | Contact your system administrator to verify user management. |
| -15 | AccessDeniedNoContext | Access is denied. No context or application information is available. Please contact your system administrator. | Try to sign in again or contact your system administrator. |
| -16 | AccessDeniedNoAppInfo | Access 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. |
| -17 | ContextExpired | The supplied authentication context is expired. Please sign in again. | Try to sign in again. |
| -18 | AccessDeniedInvalidApplicationName | Access is denied. The application name is invalid. Contact your system administrator. [expected:{expectedapplicationname}, actual:{actualapplicationname}] | |
| -20 | NotImplemented | The method or operation is not implemented: {reason} | None: the requested functionality has not been implemented yet. |
| -21 | InfoShareAggregate | Multiple errors occurred. | Contact your system administrator and have them retrieve the error from server-side logging. |
| -25 | InfoShareInvalidOperation | A method call is invalid for the object's current state: {reason} | Check the reason parameter for more information about the error. |
| -30 | ErrorMessageMissing | The 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. |
| -31 | InvalidRegionalSettings | Please 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. |
| -101 | FolderNotEmpty | The folder cannot be deleted because it is not empty. Please remove all objects first. | Ensure that the folder is empty, then try again. |
| -102 | ObjectNotFound | The {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. |
| -103 | SetupFailure | Setup Failure: {reason} | A failure was found in the setup. |
| -104 | UsergroupNotEmpty | The user group cannot be deleted because it still contains users. | Ensure that the user group/department is empty, then try again. |
| -105 | LOVProblem | The value is not present in the corresponding list of value. | Contact your system administrator. |
| -106 | InvalidElementName | The identifier "{object}" is invalid. {reason} | The specified object was not found in the repository. Check if the specified object exists. |
| -107 | SecurityProblem | You have no access to the object "{object}". | Check your rights to modify the object. |
| -108 | DuplicateValueError | The value "{value}" already exists. | Use a unique value. |
| -109 | ObjectAlreadyExist | The object "{object}" already exists. | You are trying to create an object that already exists. Use a unique value. |
| -110 | XMLParseError | The 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. |
| -111 | XMLIncorrectIdError | Incorrect identifier found in the XML file. Please verify the identifier and try again. | Verify the identifier and try again. |
| -112 | ObjectModifiedByOthers | The 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. |
| -113 | InvalidValue | The given value "{value}" is invalid. {reason} | Verify the metadata you specified. Check the reason parameter for more information about the error. |
| -114 | CardAccessDenied | Access to the object is denied. | Check your rights to modify the object. |
| -115 | Referenced | Impossible 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. |
| -116 | ObjectNoLongerExists | The "{object}" does not exist. | The specified object has been deleted. Check if the object exists. If it does, contact your system administrator. |
| -117 | ObjectNotPartOfUserGroup | You 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. |
| -118 | AdministratorRightRequired | Administrative rights are required. | Only administrator-level users can perform this operation. Check your rights to modify the object. |
| -119 | LngIsCheckedOut | The object "{object}" is checked out by '{username}'. | The object is checked out by another user. Check the status of the object. |
| -120 | LngIsReleased | The object "{object}" is released. {reason} | Check the status of the object. |
| -121 | InvalidOutputConfiguration | The output configuration is invalid. | Contact your system administrator. |
| -122 | InvalidPassword | The given password is invalid. | Check the password you provided. |
| -123 | NotAllOutOfDate | Impossible 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. |
| -124 | DocumentToBeApproved | The status of the object is "To be approved". | |
| -125 | LanguageIsMandatory | The language identifier must be supplied. | Ensure that the item has a language. |
| -126 | FieldCannotBeSet | The field '{field}' cannot be set or is a system field. | Check the field name you are trying to modify. |
| -127 | ObjectAlreadyMoved | The object was already moved by another user. | Check if the object still exists in the provided location. |
| -128 | CannotBeMovedToItSelf | A 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). |
| -129 | InvalidDocTypeforFolder | The 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. |
| -130 | LngHasSystemLock | The object is locked by the system for starting reuse. | Try again later. |
| -131 | SearcherNotStarted | Your search request failed. The full-text search service is not running. Please contact your system administrator. {reason} | Contact your system administrator.. |
| -132 | LngIsCheckedOutBySameUser | You already checked out this object. | The object is probably already checked out by you. Check its status. |
| -133 | LngNotCheckedOut | The object is not checked out. | The object isn’t checked out yet, or the action requires a check-out. Check out the object. |
| -134 | InvalidStatusTransition | The 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. |
| -135 | SearcherSyntaxError | Your 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. |
| -136 | AlreadyAnAuthLngForVersion | Target 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. |
| -137 | FolderDoesnotExist | The folder identifier that was supplied does not exist. | Check if you provided correct data. |
| -138 | InvalidConditionSyntax | One or more condition names and/or values stored inside the XML instance are syntactically incorrect. | Check the syntax of the condition(s). |
| -139 | ObjectStillInUse | The 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. |
| -140 | ObjectInUse | The object is used by another user. | The object is in use by another user and cannot be accessed. Try again later. |
| -141 | InvalidStatusTransitionDueToPlugins | The 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. |
| -142 | InvalidVersionNr | The 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. |
| -143 | InvalidLanguage | The specified language "{value}" is invalid. {reason} | Check the language identifier for your object. |
| -144 | InvalidResolution | Invalid or no resolution specified. | Check the resolution for your object. |
| -145 | VersionIsMandatory | The version number must be supplied. | Check the version for your object. A version is required to access version-level and language-level information. |
| -146 | ObjectNotProcessed | The 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. |
| -147 | InvalidCharacters | The {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. |
| -150 | StatusConfModifiedByOtherUser | The status configuration has been modified by another user in the meanwhile. | Try again later with refreshed data. |
| -151 | StatusConfInvalid | The supplied status configuration is invalid. | Check the validity of the available XML or contact your system administrator. |
| -152 | StatusUsedInTransitions | The status that you try to delete is still in use in the status configuration. | Check if any objects are available in the specified status. |
| -153 | StatusUsedInInboxDefinitions | The status that you try to delete is still in use in the inbox definition. | Check if any objects are available in the specified status. |
| -154 | InCorrectInboxDefinition | Contents 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. |
| -155 | DocumentNotFound | Document is not present in the Repository. | The electronic document is not present in the repository. Provide such a file. |
| -156 | InvalidLogicalId | An 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. |
| -157 | InvalidField | Field {object} does not exist. | Check the provided fields for your chosen card type. |
| -158 | CannotMoveToItsChildren | The 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. |
| -159 | UserAlreadyExists | A user with the name you specified already exists in the system. | Verify the uniqueness of the data provided. |
| -160 | FolderAlreadyExists | A folder with the name you specified already exists. Please use a different folder name. | Specify a different folder name. |
| -161 | QueryFolderWithoutQuery | The 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. |
| -162 | RequiredParameterNotFound | The 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. |
| -163 | XMLIncorrectLngError | The 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. |
| -164 | NoBranchingAllowed | You are not allowed to create a branch on this version. | You attempted to branch the latest version of an object. Doing this is unnecessary. |
| -165 | TooManyValues | The 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. |
| -166 | NotEnoughValues | The field "{field}" does not have enough values. | A required metadata field is not filled in. Ensure that no mandatory fields are empty. |
| -167 | InvalidFileName | Invalid file name "{object}". | Check the provided filename. The filename can be an incorrect registry key or an incorrect parameter coming from a configuration XML. |
| -168 | VersionContainsBranch | The 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. |
| -169 | ValueTooLong | The value exceeds the limit of {maxlength} characters. | Check the length of the value you entered. |
| -170 | MissingPublication | The {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. |
| -171 | MissingLanguages | You 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. |
| -200 | LngIsCheckedOutOrReleased | The 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. |
| -201 | NewPasswordDiffersFromConfirmPassword | The 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. |
| -203 | ErrorLoadingXML | Error 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. |
| -204 | ErrorLoadingXSL | Error 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. |
| -205 | InCompleteResult | The result is incomplete. | Try again. |
| -206 | InvalidProcessingInstruction | The 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. |
| -207 | MissingProcessingInstruction | The 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. |
| -208 | ExtraProcessingInstruction | Extra 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. |
| -209 | ObjectUsedAsResource | The 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. |
| -210 | InvalidStartBaseline | The given StartBaseline doesn't exists. | Check if the specified start Baseline exists. |
| -211 | StartBaselineNotReleased | The given StartBaseline is not released. | Check the status of your start Baseline. |
| -212 | BaselineAlreadyReleased | The 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. |
| -213 | NotAllObjectsVersioned | There is no version chosen in the Baseline XML for one or more objects. | Make sure that all objects have a matching explicit version. |
| -214 | NotAllObjectsReleased | Not all objects are released in the source language(s) or in the required resolution. | Check the status of all objects in the Baseline report. |
| -215 | NotAllObjectsExist | Not all objects used in the Baseline exist in the database. | Check the existence of all objects in the Baseline report. |
| -216 | ObjectUsedOnFrozenBaseline | The 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. |
| -217 | DuplicateVariableAssignment | Variable 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. |
| -218 | VariableNotAssigned | The 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. |
| -219 | MissingObjectFragments | The 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. |
| -220 | PrimaryIndexTermMandatory | The primary Index term is mandatory. | Insert a primary index term. |
| -221 | SecondaryIndexTermMandatoryWhenTertiary | Secondary index term mandatory when a tertiary term is set. | Insert a secondary index term when you provide a tertiary term. |
| -222 | IndexTermAssignedWithoutAnchor | Index term assigned without an anchor. | Check if the index term isn’t already assigned to the complete object. |
| -223 | InvalidIndexTerm | Invalid Index Term. | The index term is invalid. Verify that the index term is a valid term. |
| -224 | SecurityRuleViolatedInSubFolders | Revoking 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. |
| -225 | SecurityRuleViolatedInParentFolder | Granting 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. |
| -226 | SecurityRuleViolatedInTargetFolder | You 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. |
| -227 | ErrorRunningPlugin | The 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 |
| -228 | PluginDuplicateValue | The 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. |
| -229 | PluginMissingConrefBegin | The 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. |
| -250 | InvalidReusableObjectReference | The 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. |
| -251 | ReuseNotOnLatestVersion | Element reuse may only be started from the latest version of a library topic. | Contact your system administrator. |
| -252 | LanguageNotAvailableUnderLatestVersionOfReusableObject | Language 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. |
| -253 | NoReleasedSourceDocumentFound | Translation Management could not be started. No released object found in the source language(s). | Check the status of your objects. |
| -254 | SystemFieldCannotBeSet | Unable to set a system field. | Check the field you are trying to update. |
| -255 | NotEnoughRights | You do not have enough rights to start the application. | Check if the account that you are using to sign in has enough rights. |
| -256 | SuccessfullyLoggedOut | You have successfully been logged out. | You clicked the logout button. Click the login button to login again. |
| -257 | InvalidConfigurationPart | The {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. |
| -258 | NoErrorNumber | An 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. |
| -259 | RegisterEvent | The 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. |
| -263 | TerminatedWithErrorsOrWarnings | The 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. |
| -264 | SecurityRuleViolatedOnOwnerAccess | Owner should have read access on the object. | Ensure that the owner has read access to the object, then try again. |
| -265 | InvalidFolderType | Invalid folder type. | For updating a query folder or a reference folder, the specific functions must be used. |
| -270 | UpdateViolatedWorkflow | You 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. |
| -271 | CreateViolatedWorkflow | You 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. |
| -272 | TerminologyUpdateFailed | The terminology update can only be performed on the highest version in the branch. | Check the status of the object. |
| -273 | InvalidStatusTransitionDueToCheckout | The object "{object}" cannot be moved to the requested status because it is checked out. | Check in the object, then try again. |
| -274 | OnlyPossibleOnSourceLanguage | Moving 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. |
| -275 | NotPossibleOnFrozenBaseline | The 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. |
| -277 | ReplaceAllLanguagesNotAllowed | You 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. |
| -278 | InvalidStatusForAction | The 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. |
| -279 | ObjectIsReleased | The object "{object}" is released. {reason} | The object is released. |
| -280 | InvalidObjectType | Invalid object type "{object}". Expected "{expected}" type. | The object has an invalid object type. |
| -281 | FreezeFailureMasterRefMissing | Unable 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. |
| -282 | ObjectUsedAsMasterRef | The 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). |
| -283 | LogicalIdTooLong | The identifier "{value}" exceeds the limit of {length} characters. | The identifier exceeds the maximum character limit. Check the length of the identifier. |
| -284 | TranslationMgmtFromLanguageMissing | There is no "FromLanguage" specified in the Translation Management XML for the requested language(s) "{value}". | Contact your system administrator. |
| -285 | InboxConfModifiedByOtherUser | The Inbox configuration has been modified by another user in the meanwhile. | Try again later with refreshed data. |
| -286 | BaselineNotReleased | The Baseline is not frozen. | Freeze the Baseline. You must freeze the Baseline before releasing a publication. |
| -287 | ReplaceLanguageNotAllowed | You 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. |
| -288 | NotSupportedObjectType | Object type "{objecttype}" is not supported. | None: the specified object type is not supported for this action |
| -100001 | InternalError | Internal error: {reason} | Contact your system administrator, or examine reason to solve the problem. |
| -100002 | InternalWarning | Internal warning: {reason} | Contact your system administrator, or examine reason to solve the problem. |
| -101001 | ConfigurationInvalidCombination | Invalid 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. |
| -101002 | ConfigurationRequiredParameterNotFound | The 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. |
| -101003 | ConfigurationRegistryCannotReadApplicationNameKey | Application name "{applicationname}" cannot be read or does not exist in "{location}". | Contact your system administrator. |
| -101004 | ConfigurationResourceDirectoryDoesNotExist | Resource 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. |
| -101005 | ConfigurationResourceFileDoesNotExist | Resource 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. |
| -101006 | ConfigurationRequiredParameterValueNotCorrect | The required parameter "{parameter}" contains an incorrect value "{value}". {reason} | Contact your system administrator. |
| -101007 | DatabaseConfigurationInvalidColumn | Invalid 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. |
| -101008 | InvalidDatabaseConfiguration | Invalid 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. |
| -101009 | NotSupported | The object is not supported: {reason} | |
| -102001 | InvalidObject | The {object} {value} does not exist. [{paramname}:"{paramvalue}"] | The object does not exist. Check the provided data. |
| -102002 | MissingCardTypeDefinition | The "{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. |
| -102003 | ObjectNotInitialized | The {objecttype} "{object}" cannot be returned, because it is not initialized. | |
| -102004 | ObjectAlreadyInitialized | The "{object}" cannot be set, because it is already initialized. | |
| -102005 | InvalidValueLevelCard | Value "{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. |
| -102006 | MissingValueLevelCard | Value 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. |
| -102007 | NotEnoughValuesLevelCard | Value "{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. |
| -102008 | TooManyValuesLevelCard | Value "{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. |
| -102009 | ObjectIsReadOnly | Unable 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. |
| -102010 | ObjectTooLong | The {object} {value} exceeds the limit of {length} characters. | Check the number of characters in the value of this object. |
| -102011 | InvalidFilterValueForLov | Filtering 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. |
| -102012 | InvalidFilterValue | Filtering 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. |
| -102013 | InvalidOperatorForFieldType | Filter 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. |
| -102014 | InvalidNumberOfFilterValuesForOperator | The 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}] | |
| -102015 | FilterQuerySyntaxError | Encountered database limitation when filtering on field "{fieldname}" with filter value "{filtervalue}". {reason} [f:{fieldid} fe:{fieldelement} ft:{fieldtype} fo:{filteroperator}] | |
| -102016 | PopulatingAnUpdatedFieldValue | Populating 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}] | |
| -102020 | InvalidTableFilterValue | Filtering on column "{name}" returns an empty result set because filter value "{filtervalue}" does not exist. {reason} [t:{tablename} col:{columnname} coltype:{columntype}] | |
| -102021 | InvalidOperatorForColumnType | Filter operator "{filteroperator}" is not allowed on column "{columnname}". {reason} [t:{tablename} col:{columnname} coltype:{columntype}] | |
| -102022 | InvalidNumberOfTableFilterValuesForOperator | The 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}] | |
| -102023 | TableFilterQuerySyntaxError | Encountered database limitation when filtering on column "{columnname}" with filter value "{filtervalue}". {reason} [t:{tablename} col:{columnname} coltype:{columntype} fo:{filteroperator}] | |
| -103001 | NoRegisteredCrawlerFound | No 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. |
| -103002 | ObjectNotMarkedForDeletion | Deleting the object "{object}" failed, because it was not marked for deletion. | |
| -104001 | InvalidInformationForType | Provided information "{object} v {version} {language} {resolution}" is not of type "{type}". | Check the type of the supplied object. |
| -104002 | InvalidCardIdForType | Provided information "{cardid}" is not of type "{type}". | Check the type of the supplied object. |
| -104003 | InvalidFieldForType | The provided field "{field}" is not defined on type "{type}". | Check the field you are trying to update. |
| -104004 | LovValueUsedOnConfigurationXml | The 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. |
| -105001 | InvalidParameter | The parameter {object} with value "{value}" is invalid. {reason} | Check if all supplied parameters are valid (use the information in the reason parameter). |
| -105002 | SchemaValidationFailure | The XML of {object} did not pass schema {schemaId} validation. {reason} | Check the supplied XML using the information in the reason parameter. |
| -105003 | InvalidParameterCombination | Parameters {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. |
| -105004 | MissingXmlElement | The required element "{elementName}" was not found in "{object}". | Check the supplied XML using the information in the reason parameter. |
| -105005 | MissingXmlAttribute | The required attribute "{attributeName}" was not found on the "{elementName}" element in "{object}". | Ensure that the specified XML element has the specified required attribute. |
| -105006 | InvalidValueTypeForFieldType | Value type "{valuetype}" is not allowed on field "{fieldname}". {reason} [f:{fieldid} fe:{fieldelement} ft:{fieldtype}] | |
| -105007 | FieldAlreadySpecified | The field "{fieldelement}" can only be specified once on level "{level}". | Ensure that each field is provided only once per level. |
| -105008 | PreferenceSetAlreadySpecified | The preference set "{preferencesetname}" can only be specified once. | Ensure that the preference set is specified only once. |
| -105009 | PreferenceItemAlreadySpecified | The preference item "{preferenceitemname}" can only be specified once. | Ensure that each preference item is specified only once. |
| -105010 | InvalidCombination | Invalid combination of {object1} "{value1}" and {object2} "{value2}". | |
| -106001 | ObjectHasBeenReplaced | Unable 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. |
| -106002 | UserCannotCreateObject | User "{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. |
| -106003 | BaselineStillInUse | The 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. |
| -106004 | CannotMoveBaseFolder | Folder "{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/. |
| -106005 | MissingReadAccessOnSourceFolder | You 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. |
| -106006 | MissingWriteAccessOnSourceFolder | You 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. |
| -106007 | CannotCreateContentFolderInFavorites | The 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. |
| -106008 | CannotMoveFolderToFavorites | Moving 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. |
| -106009 | CannotDeleteEvent | The 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. |
| -106010 | NoWriteAccessOnSystemObject | You have no write access to system {objecttype} "{object}". {reason} | Check the information in the reason parameter to solve the problem. |
| -106011 | InvalidCurrentMetadata | The 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}] | |
| -106012 | InvalidCurrentFolder | The 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. |
| -106013 | MissingMetadataBinding | There 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. |
| -106014 | MetadataBindingHandlerInitializationFailure | The 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. |
| -106015 | MetadataBindingHandlerExecutionFailure | The metadata binding handler "{handlername}" returned the following error: "{reason}" | Check the information in the reason parameter to solve the problem. |
| -106016 | MetadataBindingHandlerDisposalFailure | The metadata binding handler "{handlername}" returned the following error while disposing: "{reason}" | Check the information in the reason parameter to solve the problem. |
| -106020 | TargetXmlFileHandlerInitializationFailure | The 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. |
| -106021 | TargetXmlFileHandlerExecutionFailure | The target xml file handler "{handlername}" returned the following error: "{reason}" | Check the information in the reason parameter to solve the problem. |
| -106022 | TargetXmlFileHandlerDisposalFailure | The target xml file handler "{handlername}" returned the following error while disposing: "{reason}" | Check the information in the reason parameter to solve the problem. |
| -106023 | LeaseNotAvailable | No 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. |
| -106024 | PublicationNotDeployed | You 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. |
| -106025 | CannotDeleteAnnotationWithReplies | The annotation cannot be deleted, because the annotation "{annotationid}" has "{relpyCount}" replies." | |
| -106026 | FeatureNotEnabled | The feature "{featurename}" is not enabled. Please contact your system administrator. | |
| -106027 | NotEnoughPrivileges | You do not have enough privileges for this action. {reason} | Check the information in the reason parameter to solve the problem. |
| -106028 | InvalidUserForAction | The current user {username} cannot perform this action. {reason} | Check the information in the reason parameter to solve the problem. |
| -106029 | ObjectInReleasedPublication | The object "{objectname}" is part of a released publication. {reason} | |
| -106030 | ObjectIsNotReleased | The object "{objectname}" is not released, its current status is "{status}". {reason} | |
| -106031 | PublicationInUse | The publication "{publication}" with version "{version}" is used in the project "{project}". | |
| -107001 | API20FirstError | First error of the InfoShare.API20 starts with 107001 | |
| -108001 | ActionProtectedField | Usage of field "{field}" during a "{action}" action is not allowed. {reason} | Check the field name you are using. |
| -109001 | InvalidSolrConnection | Unable to connect to {baseurl}. {reason} [retries:{retries} timeout:{timeout}] | Contact your system administrator to double-check the SolrLucene configuration. |
| -109002 | BadSolrLuceneRequest | Invalid {action} request. {reason} [statuscode:{statuscode}] [{responseuri}] [retries:{retries} timeout:{timeout}] | |
| -109003 | NoWebResponse | Unable to get WebResponse for {responseuri} | Contact your system administrator to double-check the SolrLucene configuration. |
| -109010 | InvalidSearchSyntax | Your 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. |
| -109011 | InvalidSearchOperatorForFilterField | Filter fields does not support the search operator {searchoperator}. Use one of the following operators: {operators} | Check the search operators used in the search syntax. |
| -110001 | PluginHostFailure | An unexpected system failure occurred in the plug-in host system. "{reason}" | Check the information in the reason parameter to solve the problem. |
| -110002 | PluginInitializationFailure | Plug-in initialization failed. "{reason}" | Check the information in the reason parameter to solve the problem. |
| -110003 | PluginExecutionFailure | The plug-in "{pluginname}" returned the following error: "{reason}" | Check the information in the reason parameter to solve the problem. |
| -110004 | PluginDisposalFailure | The plug-in "{pluginname}" returned the following error while disposing: "{reason}" | Check the information in the reason parameter to solve the problem. |
| -111001 | PluginConnectionToExternalSystemFailure | "{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. |
| -111002 | PluginIntegrationWithExternalSystemFailure | "{name}" received an error from the external system. Error details: "{reason}" | Check the information in the reason parameter to solve the problem. |
| -111003 | ProcessingXmlFailure | Processing the XML file "{filepath}" failed. {reason} | Check the information in the reason parameter to solve the problem. |
| -115001 | TaskExecutionTimeOut | The execution of background task {taskid} with "{eventType}" timed out after {timeOut} minutes [tid:{taskid} u:{userId} p:{progressId} a:{attempt} hid:{historyId}] | |
| -115002 | TaskExecutionForceStopped | The execution of background task {taskid} with "{eventType}" was stopped [tid:{taskid} u:{userId} p:{progressId} a:{attempt} hid:{historyId}] | |
| -115003 | TaskLeaseExpired | The lease period for background task {taskid} with "{eventType}" has expired after {leaseTimeout} minutes [tid:{taskid} u:{userId} p:{progressId} a:{attempt} hid:{historyId}] | |
| -115004 | BackgroundTaskHandlerInitializationFailure | Background 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. |
| -115005 | BackgroundTaskHandlerDisposalFailure | The background task handler "{eventType}" returned the following error while disposing: "{reason}" | Check the information in the reason parameter to solve the problem. |
| -120000 | ReviewEndDateExpired | Review end date expired | |
| -120003 | ThumbnailCreationFailed | Thumbnail creation failed for object with mime type "{mimeType}" | |
| -120004 | LanguageResolutionNotAvailable | The 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. |
| -120008 | PublicationOutputFileMissing | No file is attached to this publication output. | |
| -120009 | ConfirmationPasswordInvalid | The new password does not match the confirmation password. Please retry. | |
| -120010 | InvalidOldPassword | The old password is invalid. | |
| -120014 | LanguageObjectNotFound | Cannot 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}"] | |
| -120015 | VersionObjectNotFound | Cannot show properties for this object. Please make sure that it has a version. The {object} does not have version {value}. | |
| -120016 | MissingDefaultLanguage | You are not allowed to create new object without default language [Default language: {value}]. Please make sure that default language is selected. | |
| -120017 | LanguageObjectNotFoundInAnyVersion | Object is invalid. Language object was not found in any version. Please delete the object and create a new one. | |
| -120018 | LanguageObjectNotFoundInVersion | Object version is invalid. Language object was not found in version {value}. Please delete the version and create a new one. | |
| -120019 | VersionObjectNotFoundInObject | Object is invalid. Version was not found in object. Please delete the object and create a new one. | |
| -120020 | LanguageOrResolutionNotFoundInVersion | Object version is invalid. Language or Resolution object was not found in version {value}. Please delete the version and create a new one. | |
| -121001 | InvalidFileNameFormat | File name "{filename}" has an invalid format | |
| -121002 | MissingEDTForFile | No electronic document type found for file "{filename}" | Ensure that there is an electronic document type containing the file extension of the specified file name. |
| -121003 | IncompleteForm | The form "{formId}" is not complete. | Ensure that all mandatory fields are filled in. |
| -121004 | ShowFormIsRequired | Showing a property window is required. | |
| -121005 | CopyPublicationOutputFailed | The publication output "{object}" copy cannot be created. | |
| -125001 | UrlConnectTimeOut | Connecting to "{url}" timed out | |
| -125002 | UrlConnectTimeOutAfterSeconds | Connecting to "{url}" timed out after {timeout} seconds | |
| -140000 | LoadingMetadataConfigurationFailed | Loading the metadata configuration failed. "{reason}" | Ensure that the metadata configuration file contains valid XML. |
| -140001 | ResolvingReferenceFailed | Resolving 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. |
| -140002 | FormDefinitionNotFound | The 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. |
| -140003 | LoadingFormDefinitionFailed | The 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. |
| -140004 | ResolveVariableFailed | An error occurred while resolving the variable "{name}". {reason} | Check the information in the reason parameter to solve the problem. |
| -140005 | ResolvingFormMetadataFailed | An error occurred while resolving metadata for the form "{formid}". {reason} | Check the information in the reason parameter to solve the problem. |
| -140006 | LoadingListDefinitionFailed | The 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. |
| -140007 | ListDefinitionNotFound | The 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. |
| -140008 | ResolvingListMetadataFailed | An 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. |
| -140009 | ResolvingMetadataFailed | An error occurred while resolving metadata. {reason} | Check the information in the reason parameter to solve the problem. |
Conditional Text
| Nr | Code | Message | Action |
|---|---|---|---|
| -1020 | ConditionEvaluationError | Error during condition evaluation. | |
| -1021 | ConditionParseError | Error during condition parsing. | |
| -1100 | InvalidProductDefinition | The product definition is invalid: {reason} | |
| -1200 | SchemaConfigurationError | Error while reading schema: {reason} | |
| -1201 | SchemaValidationError | XML validation failed: {reason} | |
| -1300 | InvalidInputParameters | Invalid value for inputparameter "{parameter}": {reason} | |
| -1301 | NoProductDefintionSpecified | No product definition specified to evaluate conditions. | |
| -1400 | InvalidConditionName | Condition name "{conditionname}" is invalid. {reason} | |
| -1401 | InvalidConditionValue | Condition value "{conditionvalue}" is invalid. {reason} | |
| -1402 | ConditionNameContainsInvalidChars | Condition name "{conditionname}" contains one of the following invalid characters: {invalidchars} | |
| -1403 | ConditionValueContainsInvalidChars | Condition value "{conditionvalue}" contains one of the following invalid characters: {invalidchars} | |
| -1501 | UnexpectedToken | Found unexpected token "{token}", expected "{expected}" at position {position} in condition "{conditionparselocation}". | |
| -1502 | MissingConditionName | Missing condition name, found "{token}" at position {position} in condition "{conditionparselocation}". | |
| -1503 | MissingConditionValue | Missing condition value, found "{token}" at position {position} in condition "{conditionparselocation}". | |
| -1504 | MissingOpenBracket | Missing "(", found "{token}" at position {position} in condition "{conditionparselocation}". | |
| -1505 | MissingCloseBracket | Missing ")", found "{token}" at position {position} in condition "{conditionparselocation}". | |
| -1506 | MissingOperator | Missing operator, found "{token}" at position {position} in condition "{conditionparselocation}". | |
| -1800 | InitializationFailure | Initialization failed. {reason} |
Publish
| Nr | Code | Message | Action |
|---|---|---|---|
| -2005 | NoVersionSelected | No version selected for object "{object}". | For this object no version is specified in the Baseline. Ensure that a version of the object is selected. |
| -2006 | ObjectMissing | The 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. |
| -2007 | ObjectNotReleased | The 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. |
| -2008 | InvalidAccordingToDTD | The 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. |
| -2009 | VariableNotResolved | The variable "{variable}" used in object "{object} v {version} {language}" could not be resolved. | Ensure that the right resource file is attached to the publication. |
| -2010 | ConrefNotResolved | The 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. |
| -2011 | HyperlinkTargetMissing | The hyperlink "{hyperlink}" used in object "{object} v {version} {language}" could not be resolved. | Ensure that the referenced object is included in the map. |
| -2012 | LinkTargetMissing | The link "{link}" used in object "{object} v {version} {language}" could not be resolved. | Ensure that the referenced object exists. |
| -2013 | DuplicateVariableAssignmentInPublication | The 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. |
| -2014 | PublicationIsValidReleaseCandidate | This 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. |
| -2015 | PublicationIsDraft | This 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. |
| -2016 | PublicationContainsNoStatusReport | This 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. |
| -2017 | ResolutionUnavailable | Image "{object} v {version} {language} {resolution}" is unavailable. | Check if the object exists. |
| -2018 | DuplicateKeyDefinitionInPublication | The 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. |
| -2020 | StatusReport | This report contains only information about the objects used in this output. | None: this is an informational message shown in the Publish report. |
| -2021 | StatusReportSharedBaseline | The 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 |
| -2022 | StatusReportDifferentResolution | The 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 |
| -2023 | StatusReportDifferentLanguage | The 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 |
| -2024 | StatusReportCondionalFiltering | Conditional 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
Nr | Code | Message | Action |
|---|---|---|---|
| -23002 | StoreResultInvalidContext | Unable to store the result: Invalid context. | |
| -23003 | StoreResultInvalidFile | Unable 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 |
| -23004 | StoreResultInvalidPubOutput | Unable to store the result: Invalid publication output. | Check if the publication output exists. |
| -24000 | PluginDetectedRejectReleaseCandidate | One of the publish post process plugins ended with RejectReleaseCandidate | This 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. |
| -24001 | PluginDetectedUserCancel | One of the publish post process plugins detected that the publish job was cancelled by the user | None: 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 |
| -24002 | CannotLocatePublishResultFile | File 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. |
| -24003 | FileNameTooLong | The 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. |
| -24004 | FilePathTooLong | The 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. |