In this section error messages are explained whose cause is sometimes difficult to determine.
Error code | Explanation |
---|---|
10005 | The number of response elements does not match the number of request elements in the request. |
20005 | The logged-in user needs to have the
permissionGlobalUserEdit permission to set a user’s or a
group’s owner. |
20006 | The logged-in user is not allowed to
add users to or remove users from groups because he does not have the
permissionGlobalUserEdit permission. |
20007 | The logged-in user is not allowed to
grant global or file-specific permissions because he does not have the
permissions required for this action (permissionGlobalRoot or
permissionRoot , respectively). |
20008 | The logged-in user is not allowed to
revoke global or file-specific permissions because he does not have the
permissions required for this action (permissionGlobalRoot or
permissionRoot , respectively). |
20009 | The logged-in user does not have the
required permission (permissionGlobalUserEdit ) to lock or
unlock another user. |
20012 | The user is not permitted to perform the transaction. |
20013 | The logged-in user must have the
permissionGlobalExport permission in order to use the
debugExport version function or to access one of the version
parameters encodedExportBlob , exportBlob , or
exportFiles . |
20014 | The logged-in user is not allowed to
read the version parameters because he does not have the
permissionRead permission for the file to which the version
belongs. |
20015 | The logged-in user is not allowed to
read the parameters of the file because he does not have the
permissionRead permission for the file. |
20016 | The user does not have the necessary permissions to create a file from the specified file format in this folder. These permissions are the global creation permission of the format and the file creation permission in the folder concerned. |
20020 | The logged-in user has tried to release a file’s draft version without being permitted to do so. |
20021 | The logged-in user has tried to cut off the workflow of a file and start a new one without being permitted to do so. |
33008 | The value of the specified identifier is no URL and cannot be converted to an URL. |
36001 | On execution of a custom command, the configured command name associated with it could not be found. |
36024 | This message is related to the Portal Manager. In a command expecting exactly one of the named values, none of these values has been specified. |
36025 | This message is related to the Portal Manager. In a command expecting exactly one of the named values, none of these values has been specified. |
40005 | The user is not the file administrator and therefore has to be the editor in order to perform the workflow action. |
40009 | The user has already signed the file. He cannot sign a second time as he is not the file administrator and the workflow does not allow multiple signatures. |
40010 | The file cannot be committed or signed. It can only be released. |
40011 | The commit operation cannot
be carried out as the file has not yet been edited by all groups in the
editing workflow. Only the file administrator and a super user have
permission to still submit or commit the file. |
40012 | The file cannot be committed or released as the draft version is incomplete. |
40013 | The user is neither the administrator of the file nor a super user; therefore, she cannot release the file prematurely. |
40014 | The user is neither the administrator of the file nor a super user. Therefore, he cannot release the file prematurely. |
40015 | The user is neither the file administrator nor a super user; therefore he has to be a member of the last entitled group in order to release the file. |
40016 | There is a committed version so that only members of the remaining entitled groups may reject the file. |
40017 | An attempt was made to use a signature field more than once. This is not permitted. |
50009 | The specified name contains invalid characters. The following characters can be used in names: A-Z, a-z, 0-9, and _. |
50014 | A field which does not exist was
specified for a sortKey field. |
50015 | An invalid value was specified for the
sortOrder field. |
50024 | The presetAttributes
specification is not correct. A valid list could not be compiled. |
50025 | The specified name contains invalid characters. The following characters can be used in names: A-Z, a-z, 0-9, and _. |
50034 | The specified name contains invalid characters. The following characters can be used in names: A-Z, a-z, 0-9, and _. |
50037 | The specified name contains invalid characters. The following characters can be used in names: A-Z, a-z, 0-9, and _. |
50038 | The named value which has been
specified in the list of presetAttributes is not permitted for
this field. |
50040 | The specified tag contains invalid characters. |
50042 | The permitted file name extensions can
be configured in the mimeTypes system configuration
entry. |
50043 | The specified definition contains a nonexistent field or a nonexistent user group. |
50044 | The specified name contains invalid characters. The following characters can be used in names: A-Z, a-z, 0-9, and _. |
50045 | An unknown update type was specified in an update record. |
50063 | Job names must not begin with
system or the underscore character. Permitted characters in job
names are a - z, A - Z, 0 - 9, and the underscore. |
55000 | The string is made up of two characters in the range from 0 to 9, a to z, or A to Z. The characters are used for encryption. |
55001 | This error is generated if the server receives a payload in a version not supported by the XML interface. The way the server behaves in such cases is explained in the XML Reference manual. |
55003 | The link belongs to a tag in which an anchor must not be specified. |
55004 | The link belongs to a tag which does not support the specification of a frame target. |
55005 | The target folder specified in the copy or move procedure cannot be accepted as a target. The reason can be one of the following: a file with the name of the file concerned already exists; it is not a folder, you do not have sufficient permissions, it is inside the hierarchy branch to be moved or may not have any subfolders with the format of the source file. |
55006 | A file with the same name already exists in the directory. |
55011 | The specified name contains invalid characters. The following characters can be used in names: A-Z, a-z, 0-9, and _. |
55015 | The specified file name extension or
the extension used in the operation is not included in the
validContentTypes of the format assigned to the file. |
55023 | The specified format cannot be used
for this file. It does not exist or is not contained in the
validSubObjClasses of the format for the folder containing the
file. |
55036 | The specified field name could not be assigned to a link because the field does not exist in the version to which the link belongs. |
55046 | This error is generated, if a user tries to generate a thumbnail image for a file whose type is neither image nor resource. |
55047 | The specified character set does not exist or has not been defined. |
55054 | For the createAndLoad file
command a file with more than two components was specified or the path is
absolute or references the parent directory. |
55055 | At the attempt to access a temporary directory after the Upload Wizard was called, a path consisting of several parts was specified. This is not permitted. |
60014 | This is an internal error. Please contact our customer support. |
60015 | This is an internal error. Please contact our customer support. |
60016 | This message is related to the Portal Manager. The specified path does not exist. |
60033 | The specified templete is required for the export. However, it does not exist or has not been released. |
80001 | A folder can only be deleted after the files it contains have been deleted. |
80009 | The specified field cannot be deleted, as it is still being used in the specified file format. |
80010 | The specified field cannot be deleted, as it is still being used for signatures in the specified workflows. |
80011 | The workflow cannot be deleted, as it
is referenced in the specified file format in the preset
workflowName field. |
80014 | The field value for the specified users must be modified in order to be able to delete the enumeration value. |
85013 | For the time the exported documents are being switched live, requests in the request queue of the Search Engine Server are temporarily not processed. |
85015 | The request to the XML interface was not processed because a preceeding request marked as preclusive failed. |
85020 | You have tried to edit the main content of a version. This is not possible if the file to which the version belongs is based on a format in which a main content layout has been specified. |
85028 | Fields are automatically added to the base field set when they are deleted from other field sets or added to the file format. |
85031 | The version is a committed or released version and thus cannot be modified. |
85033 | The named fields cannot be added to
the mandatoryAttributes list because they are not contained in
the file format’s list of fields. |
85034 | The named fields cannot be added to
the presetAttributes list because they are not contained in
the file format’s list of fields. |
85035 | The named fields cannot be added to
the presetFromParentAttributes list because they are not
contained in the file format’s list of fields. |
85036 | File formats were specified for subfiles even though the file type specified for the format does not permit any subfiles. |
85037 | You have tried to assign a main content layout to a file format defining layouts, images, or resources. Main content layouts, however, cannot be used with these file types. |
85038 | You have tried to preset the main content in a file format definition. This is not possible if a main content layout has been specified. |
85039 | You have tried to preset the main content in a file format definition with the value of the main content of the folder containing the file. This is not possible if a main content layout has been specified. |
85041 | Context links must point to NPS files. |
90007 | The specified field occurs in the XML document, however, it is not contained in the file format to which the document belongs. |
100000 | The specified additional (custom) command could not be executed. |
100001 | The additional (custom) command could not write to a binary file. |
100016 | The specified values cannot be used.
The value of the master.maxSlaves configuration entry must be
greater than the master.minIdleSlaves value. |
100029 | This is a database error. The system failed to write to the job execution queue. |
100030 | This is a database error. |
100031 | This is a database error. |
100032 | This is a database error. |
100037 | This is a database error. |
100038 | This is a database error. |
100039 | A NPS application tried to access a nonexistent file for reading. This error can occur if, for example, the streaming interface tries to deliver a file associated with a ticket and this file has been deleted. |
100040 | This is a database error. |
100043 | This is a database error. |
100044 | This is a database or system
error. Please contact our customer support. |
100052 | The file in which the logins and passwords of all users are stored could not be created. |
100054 | This is a database error. |
100055 | This is a database error. |
100056 | This is a database error. |
100110 | This is a database error. |
100111 | The draft version could not be created since there is no default file name extension. |
100112 | This is a database error. |
100113 | This is a database error. |
100114 | This is a database error. |
100115 | This is a database error. |
100116 | This is a database error. |
100119 | This is an internal system error. |
100121 | This is a database error. |
100123 | The specified type is no internal representation of a task type. |
100148 | This is a database error. |
100149 | This is a database error. |
100150 | This is a database error. |
100151 | This is a database error. |
100152 | The application could not access the specified control file. The file might not exist, or the application lacks read permission. |
100153 | This is a database error. |
100154 | This is a database error. |
100164 | During indexing by the Search Engine Server the external processor was not found or the program file was not executable. |
100165 | During indexing by the Search Engine Server, the attempt to transmit data to the external processor via a pipe failed. |
100166 | During indexing by the Search Engine Server, the attempt to read the external processor’s output via a pipe failed. |
100167 | This is a database error. |
100168 | This error can have several causes. Possibly the path contains non-existent directories, or the access permissions are insufficient. |
100172 | During the initialization of the Verity search engine, no collections were found. They are searched for in the instance-specific data/collections directory. |
100184 | With the SES, actions to be performed
are coded into the names of request files. Only two actions, index
and delete , exist. With respect to such a file, an inconsistence
occurred. The error is written to the system log, and the file concerned is
ignored. |
100185 | This is a database error. |
100188 | The attempt to create a streaming ticket failed. Possibly the tickets directory does not exist or the application is not permitted to access it. |
100197 | The restriction in length is due to the file or operating system. |
100209 | This error is related to the Template
Engine. During the export more errors occurred than the value of the
acceptableExportFailures system configuration entry
tolerates. |
100210 | The Portal Manager or the application which produced this message is misconfigured. It is also possible that the Portal Manager has not been started. |
100219 | This is a database error. |
109010 | Channel check function error. |
109012 | Version assignment function error. |
109016 | The stated errors occurred while
sudo was executed. |
109017 | The stated errors occurred while the
generateThumbnail function was executed. |
109018 | The stated errors occurred while the
usersWhere procedure in the file usermanAPI.tcl was
executed. |
109021 | The stated errors occurred while the
groupsWhere procedure in the file usermanAPI.tcl was
executed. |
109500 | The link function cannot be executed because the list of fields contains the wrong number of elements. |
109501 | The link function could not be executed properly. |
109503 | Thumbnails must be stored as JPEG images. |
109511 | This error is generated and the cause of the error is specified in detail if the Tcl-Code in one of the following functions produces an error: value assignment function, value display function, completion check, version assignment function, creation check for files in a folder, workflow assignment function. |
120012 | This error can occur if saved data have been deleted or users have worked with the server during the dump procedure. |
130007 | This is a fatal database error that causes the process of the NPS application concerned to be terminated. The database action concerned has not been performed. |
140021 | In NPSOBJ instructions only the alias
names of Tcl commands can be used. To these names the actual procedure
calls must be assigned in the appropriate system configuration entry
(tclSystemExecuteCommands or tclFormatterCommands , for
example). |