IT blok - Michal Šika

kutilovo živobytí

Documentum 6.6 – chybové zprávy – část 4.

V poslední části výčtu chybových hlášení systému Documentum verze 6.6 od EMC si ukážeme chyby DM_RELTYPE – DM_XFRM v abecedním pořadí. Jedná se jak o ERROR tak i o WARNING chybová hlášení.
Doufám, že se vám podaří najít odpovídající řešení vašich problémů… Tento post navazuje na předchozí část.

DM_RELTYPE DM_ROUTER DM_SCNFG
DM_SERVER DM_SESSION DM_SIGN
DM_STORAGE DM_SYSOBJECT DM_TYPE_MGR
DM_UPGRADE_MGR DM_USER DM_VERITY_COLL
DM_VERSION DM_WORKFLOW DM_XFRM

DM_RELTYPE

ERROR: [DM_RELTYPE_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmRelation_Type type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_RELTYPE_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmRelation_Type type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_RELTYPE_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmRelation_Type object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report a bug. Also, Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_RELTYPE_F_INT1]

SEVERITY: FATAL
DESCRIPTION: S The following database query %s could not be executed.
CAUSE: Inconsistency between the server and the sysobject type.
ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site $Id: dmrouter.e,v 5.0 1998/01/10 02:08:11 sol_ora Exp $ dmRouter class errors
PARAMS:

ERROR: [DM_RELTYPE_E_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_RELTYPE_E_CANT_VALIDATE_SYSTEM]

SEVERITY: ERROR
DESCRIPTION: Server could not create server defined relation types.
CAUSE: Server was not successful in creating the system defined relation types.
ACTION: Most likely database error.
PARAMS:

ERROR: [DM_RELTYPE_E_NEED_PRIVS]

SEVERITY: ERROR
DESCRIPTION: SS The current user %s has insufficient privileges to save or destroy %s relation_type.
CAUSE: A user with insufficient privileges tried to save or destroy a relation_type object.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_RELTYPE_E_NOT_EMPTY]

SEVERITY: ERROR
DESCRIPTION: S There are dm_relation object using %s relation_type object.
CAUSE: User tried to destroy a dm_relation_type object that still has dm_relation object using it.
ACTION: Either drop all dm_relation of this type before tring this operation.
PARAMS:

ERROR: [DM_RELTYPE_E_INVALID_SECURITY]

SEVERITY: ERROR
DESCRIPTION: S Invalid security %s for relation.
CAUSE: A user has defined an invalid relation_type security.
ACTION: Change to a valid relation_type security.
PARAMS:

ERROR: [DM_RELTYPE_E_CANT_CREATE_SYSTEM]

SEVERITY: ERROR
DESCRIPTION: S Can not system defined create relation type %s
CAUSE: Can not create relation type that start with DM_ prefix. Reservered for server use.
ACTION: Try another name.
PARAMS:

ERROR: [DM_RELTYPE_E_ALREADY_EXISTS]

SEVERITY: ERROR
DESCRIPTION: S Relation_Type with %s name already exists.
CAUSE: A user tried to define a relation_type that already exists. All relation_type names must be unique.
ACTION: Try another unique name.
PARAMS:

ERROR: [DM_RELTYPE_E_MUST_HAVE_NAME]

SEVERITY: ERROR
DESCRIPTION: A new relation_type must have a name.
CAUSE: All relation_types must have a name during creation.
ACTION: Set the name and try to save again.
PARAMS:

nahoru

DM_ROUTER

ERROR: [DM_ROUTER_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dm_router type.
CAUSE: Unknown.
ACTION: Look at the error message logged by the type manager. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_ROUTER_F_INIT4]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error converting the dm_router type.
CAUSE: Unknown.
ACTION: Look at the error message logged by the type manager. Report this message and any parameters to your Documentum Site Representative. $Id: dmserver.e,v 5.10 2003/05/05 02:56:51 rogert Exp $ Generic server error message Use this as the repository for errors from action procs, etc.
PARAMS:

ERROR: [DM_ROUTER_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dm_router type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_ROUTER_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_router object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_TASK_INDEX]

SEVERITY: ERROR
DESCRIPTION: I Invalid task index %d specified.
CAUSE: You tried to remove or inserttask with an invalid index number.
ACTION: Retry with a valid task index.
PARAMS:

ERROR: [DM_ROUTER_E_NEED_BEGIN]

SEVERITY: ERROR
DESCRIPTION: S Router named %s needs to have at least one begin task.
CAUSE: A router must have one or more begin tasks.
ACTION: Make sure that at least one task_type is begin.
PARAMS:

ERROR: [DM_ROUTER_E_NEED_BROWSE]

SEVERITY: ERROR
DESCRIPTION: SS User %s need to have browse permission on %s document.
CAUSE: A document is about to be queued to a user that does not have browse access.
ACTION: Change security on the document to allow browse permission for users of this task.
PARAMS:

ERROR: [DM_ROUTER_E_USER_NOT_IN_LIST]

SEVERITY: ERROR
DESCRIPTION: SSS User %s must be a task owner or user of %s list of %s task.
CAUSE: Specified user must be a task owner or user of the specified list.
ACTION: Try again with a valid user.
PARAMS:

ERROR: [DM_ROUTER_E_MUSTBE_SUPERVISOR]

SEVERITY: ERROR
DESCRIPTION: SS Current user %s must be the supervisor to perform %s operation on this router.
CAUSE: The current user must be the router supervisor to perform this operation.
ACTION: None.
PARAMS:

ERROR: [DM_ROUTER_E_MUSTBE_TASK_USER]

SEVERITY: ERROR
DESCRIPTION: SSS Current user %s must be the task user for %s task to perform %s operation on this router.
CAUSE: The current user must be the task user to perform this operation.
ACTION: none.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_TASK_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSS Invalid %s %s for task number %s.
CAUSE: Specified task has invalid next_task_type or dependency_task_type or task_type. With broadcast routers, the only next_tasks_type supported is all.
ACTION: Change the erroneous next_task_type or dependency_task_type or task_type.
PARAMS:

ERROR: [DM_ROUTER_E_CANT_ACQUIRE]

SEVERITY: ERROR
DESCRIPTION: IS Could not acquire task number %d of %s router.
CAUSE: Previous errors, prevented the server to acquire the specified task.
ACTION: Look at the previous error messages.
PARAMS:

ERROR: [DM_ROUTER_E_CANT_COPY_ROUTER]

SEVERITY: ERROR
DESCRIPTION: S Router %s is in use and can not be copied.
CAUSE: A router that is active or halted can not be copied (checkin, saveasnew)
ACTION: None.
PARAMS:

ERROR: [DM_ROUTER_E_CANT_DEQUEUE]

SEVERITY: ERROR
DESCRIPTION: SSS Cannot dequeue task number %s of router named %s for user %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_TASK_STATE]

SEVERITY: ERROR
DESCRIPTION: SSS State of task number %s is %s, expected to be %s.
CAUSE: In order to perform the current operation the state of the specified task must match the expected state. ACTION:Either wait for the task state to change, or change the state of the task before performing this operation.
ACTION:
PARAMS:

ERROR: [DM_ROUTER_E_CANT_RUN_METHOD]

SEVERITY: ERROR
DESCRIPTION: SL Could not run external method named: %s, error return is %d.
CAUSE: Server could not run the external method.
ACTION: Report the error to user sysadmin.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_TASK_NUM]

SEVERITY: ERROR
DESCRIPTION: S Invalid task number %s specified.
CAUSE: An invalid task number has been specified. A task number is invalid if: a) it is out of range with the given router, b) it is an invalid specification (ie non-numeric).
ACTION: Specify a valid task number.
PARAMS:

ERROR: [DM_ROUTER_E_BAD_PACKAGE2]

SEVERITY: ERROR
DESCRIPTION: DSSS Package identified by %s and label <%s> does not have the relate permit because of %s %s.
CAUSE: User does not have relate permission to the package.
ACTION: Have the owner of document to provide relate permission or use another document with relate permission.
PARAMS:

ERROR: [DM_ROUTER_E_NO_STEP_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S Router %s is a broadcast router and can not have a step task.
CAUSE: User tried to define a broadcast router with a step task.
ACTION: Not supported.
PARAMS:

ERROR: [DM_ROUTER_E_SIGN_OFF_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Task Number %s could not be signed off.
CAUSE: Server could not sign-off the specified task number. Previous errors have caused the sign-off to abort.
ACTION: Check the previous error message for the appropriate action.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_TASK_OWNER]

SEVERITY: ERROR
DESCRIPTION: SS Invalid task owner name %s specified for task number %s.
CAUSE: During save operation, an invalid task owner was found to be specified for the given task.
ACTION: Please specify a valid Documentum user or group name.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_TASK_STATE3]

SEVERITY: ERROR
DESCRIPTION: SSSSS State of task %s is %s, expected to be %s or %s or %s.
CAUSE: In order to perform the current operation the state of the specified task must match the expected state. ACTION:Either wait for the task state to change, or change the state of the task before performing this operation.
ACTION:
PARAMS:

ERROR: [DM_ROUTER_E_CANT_SAVES]

SEVERITY: ERROR
DESCRIPTION: S Cannot save router name %s since its state is active.
CAUSE: In order to save a router its state must be either dormant or halted.
ACTION: Place router in one of these states before proceeding.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_ROUTER_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Invalid router type %s specified.
CAUSE: Invalid router type specified. Expected to see: route slip, broadcast, or general.
ACTION: Specify a valid router type.
PARAMS:

ERROR: [DM_ROUTER_E_MUSTBE_USER_OR_SUPER]

SEVERITY: ERROR
DESCRIPTION: SSS Current user %s must be the router supervisor or task user for %s task to perform %s operation on this router.
CAUSE: The current user must be the task user or the router supervisor to perform this operation.
ACTION: None.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_TASK_LIST3]

SEVERITY: ERROR
DESCRIPTION: SS Task list %s for task number %s must be empty.
CAUSE: The specified task list must be empty. All begin tasks must have empty dependency_list, and all end tasks must have empty next_tasks_list.
ACTION: Set these lists to empty.
PARAMS:

ERROR: [DM_ROUTER_E_TARGET_NOT_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: Target tasks not required.
CAUSE: Tried to do a forward where no target task is required. This can happen when forwarding a task where next_tasks_type is ALL.
ACTION: Respecify the operation without target tasks.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_SUPERVISOR]

SEVERITY: ERROR
DESCRIPTION: S Invalid user name %s specified as supervisor.
CAUSE: Invalid supervisor name specified during save operation.
ACTION: Please specify a valid user name.
PARAMS:

ERROR: [DM_ROUTER_E_NOT_A_ROUTER]

SEVERITY: ERROR
DESCRIPTION: D The object identified by %s is not a router.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_TASK_LIST]

SEVERITY: ERROR
DESCRIPTION: SSS Task list %s for task number %s has invalid task number %s. CAUSE:Specified task list has invalid task numbers.
CAUSE:
ACTION: Make sure that they are all numeric and valid task numbers from the current router, and do not point to the current task number.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_ROUTER_STATE]

SEVERITY: ERROR
DESCRIPTION: SS Current router state is %s, expected to be %s.
CAUSE: In order to perform the current operation router state must match the expected state. ACTION:Either wait for the router state to change, or change the state of the router before performing this operation.
ACTION:
PARAMS:

ERROR: [DM_ROUTER_E_CANT_DELETE_REMOVED]

SEVERITY: ERROR
DESCRIPTION: S Could not delete removed tasks for %s router.
CAUSE: User tried to resume a halted router with queued removed tasks.
ACTION: Look into the previous message for possible database errors.
PARAMS:

ERROR: [DM_ROUTER_E_CANT_PERFORM]

SEVERITY: ERROR
DESCRIPTION: SSS Current user %s must be the router supervisor or task owner(user) or sysadmin for %s task to perform %s operation on this router.
CAUSE: The current user must be either: router supervisor, or task owner, or task user or sysadmin to perform this operation.
ACTION: None.
PARAMS:

ERROR: [DM_ROUTER_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: S Cannot destroy router named %s since its state is active or halted.
CAUSE: In order to destroy a router its state must be one of dormant or finished.
ACTION: Place router in one of these states before proceeding.
PARAMS:

ERROR: [DM_ROUTER_E_CANT_QUEUE]

SEVERITY: ERROR
DESCRIPTION: SSS Cannot queue task number %s of router named %s for user %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_ROUTER_E_CANT_QUEUER]

SEVERITY: ERROR
DESCRIPTION: SS Cannot queue router named %s for user %s.
CAUSE: It is probable that failure of database operation caused this error.
ACTION: Consult the other recent error messages for more help.
PARAMS:

ERROR: [DM_ROUTER_E_TASKOWNER_NOT_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: S The task owner parameter is not allowed on the %s operation unless you are the supervisor.
CAUSE: Tried to perform a reassign as a non-supervisor. Task owner parameter is only allowed if the current user is the supervisor.
ACTION: None.
PARAMS:

ERROR: [DM_ROUTER_E_CANT_FIND_METHOD]

SEVERITY: ERROR
DESCRIPTION: S Can not find the external method named: %s
CAUSE: Server could not find a method with the specified name. Method problem no longer exists.
ACTION: Check dm_method object.
PARAMS:

ERROR: [DM_ROUTER_E_MAX_CURRENT_TASK_LIST]

SEVERITY: ERROR
DESCRIPTION: S You have reached the maximum size of the current task list on router named %s.
CAUSE: Router tried to add a task to current task list which is already full with active tasks.
ACTION: Redefine the router.
PARAMS:

ERROR: [DM_ROUTER_E_TASK_NOT_IN_LIST]

SEVERITY: ERROR
DESCRIPTION: SSS Task Number %s must be in %s list: %s
CAUSE: Specified task number must be in the specified list.
ACTION: Use a task in the specified list.
PARAMS:

ERROR: [DM_ROUTER_E_DUPLICATE_TASKNUM]

SEVERITY: ERROR
DESCRIPTION: SS Duplicate task number %s is encountered in %s router.
CAUSE: All task numbers must be unique.
ACTION: Respecify the task number and try again.
PARAMS:

ERROR: [DM_ROUTER_E_METHOD_FAILED]

SEVERITY: ERROR
DESCRIPTION: SL Method named: %s failed with the following return value: %d.
CAUSE: External method failed with the specified error code. The error returned is application specific.
ACTION: See your local site admin.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_TASK_STATE2]

SEVERITY: ERROR
DESCRIPTION: SSSS State of task %s is %s, expected to be %s or %s.
CAUSE: In order to perform the current operation the state of the specified task must match the expected state. ACTION:Either wait for the task state to change, or change the state of the task before performing this operation.
ACTION:
PARAMS:

ERROR: [DM_ROUTER_E_NOT_VALIDATED]

SEVERITY: ERROR
DESCRIPTION: S Router named %s must be validated before execution.
CAUSE: When a router is changed it must be validated before execution.
ACTION: Validate the router before executing the router.
PARAMS:

ERROR: [DM_ROUTER_E_BAD_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: DS Package identified by %s and label <%s> does not exist.
CAUSE: User has specified an invalid document with the specified ID and label.
ACTION: Respecify a valid id and label.
PARAMS:

ERROR: [DM_ROUTER_E_BAD_TASK_ATTRC]

SEVERITY: ERROR
DESCRIPTION: SSII In router named %s, count of %s: %d does not match the count of task_num: %d.
CAUSE: Tried to save a router with invalid task attribute count.
ACTION: Most likely the user tried to manipulate task attributes with append or insert or remove methods instead of appendtask, inserttask or removetask.
PARAMS:

ERROR: [DM_ROUTER_E_CANT_DEQUEUER]

SEVERITY: ERROR
DESCRIPTION: SS Cannot dequeue router named %s for user %s.
CAUSE: It is probable that failure of database operation caused this error.
ACTION: Consult the other error messages on your message queue for more help.
PARAMS:

ERROR: [DM_ROUTER_E_SIGN_OFF_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: S Task Number %s must be signed off.
CAUSE: User must sign-ogg the specified task before forwarding.
ACTION: sign-off.
PARAMS:

ERROR: [DM_ROUTER_E_NEED_TARGET]

SEVERITY: ERROR
DESCRIPTION: SS Need one or more target task to perform %s operation on %s task.
CAUSE: In order to perform the specified operation at least one target task is required.
ACTION: Retry the operation with one or more target tasks.
PARAMS:

ERROR: [DM_ROUTER_E_INVALID_TASK_LIST1]

SEVERITY: ERROR
DESCRIPTION: SSS Task list %s for task number %s should only have one task number, but the following were found: %s.
CAUSE: Specified task list should have only one task number. a) for route_slip: next_task_list and dependency_list should only have one task number. b) for broadcast: dependency_task_list should only have one task number.
ACTION: Respecify the task list.
PARAMS:

ERROR: [DM_ROUTER_E_MORE_END]

SEVERITY: ERROR
DESCRIPTION: SI Router named %s has %d end tasks. Only one end task is allowed in each router.
CAUSE: Each router can only have one end task.
ACTION: Remove the additional end tasks and try again.
PARAMS:

ERROR: [DM_ROUTER_E_NEED_END]

SEVERITY: ERROR
DESCRIPTION: S Router named %s needs to have one end task.
CAUSE: A router can only have one end task.
ACTION: Make sure that only one end task is specified.
PARAMS:

ERROR: [DM_ROUTER_I_BAD_PACKAGE]

SEVERITY: INFO
DESCRIPTION: DS Package identified by %s and label <%s> does not exist.
CAUSE: User has specified an invalid document with the specified ID and label.
ACTION: Respecify a valid id and label.
PARAMS:

ERROR: [DM_ROUTER_I_BAD_PACKAGE2]

SEVERITY: INFO
DESCRIPTION: DSSS Package identified by %s and label <%s> does not have the relate permit because of %s %s.
CAUSE: User has specified an invalid document with the specified ID and label.
ACTION: Respecify a valid id and label.
PARAMS:

ERROR: [DM_ROUTER_I_NO_EXTERNAL_METHODS]

SEVERITY: INFO
DESCRIPTION: SS Can not find any external method for router named: %s and operation: %s
CAUSE: During validation, could not find any external method for pre/post processing of forward/reverse/queue operations.
ACTION: Look for dm_method for any external names that should match a router external method definition.
PARAMS:

ERROR: [DM_ROUTER_W_ALREADY_ACQUIRED]

SEVERITY: WARNING
DESCRIPTION: S Task Number %s is already acquired.
CAUSE: Tried to queue an acquired task. An acquired task is not requeued.
ACTION: None.
PARAMS:

nahoru

DM_SCNFG

ERROR: [DM_SCNFG_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the server_config type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_SCNFG_F_INIT4]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error converting the dm_server_config type.
CAUSE: Unknown.
ACTION: Look at the error message logged by the type manager. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_SCNFG_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The server_config type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_SCNFG_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_serverconfig to version %d.
CAUSE: Type conversion failed.
ACTION: Report the problem. Storage errors (c) Copyright Documentum, Inc., 1991 – 1995. All rights reserved
PARAMS:

ERROR: [DM_SCNFG_F_SYBASE_INIT1]

SEVERITY: FATAL
DESCRIPTION: I In-place conversion is not supported for the Sybase database with version stamp %d.
CAUSE: For Sybase database, in-place conversion is only supported for version 2.0.5 or upper
ACTION: You need to use dump and load method to upgrade your database.
PARAMS:

ERROR: [DM_SCNFG_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmServer_Config object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report a bug. Also, Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_SCNFG_F_INT1]

SEVERITY: FATAL
DESCRIPTION: S The following database query %s could not be executed.
CAUSE: Inconsistency between the server and the server_config type.
ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_SCNFG_E_INCONSISTENT_TARGET_ATTRS]

SEVERITY: ERROR
DESCRIPTION: The value count of projection attributes (projection_targets,projection_proxval,projection_notes,projection_enable) are not consistent.
CAUSE: Fail to maintain same value count while editing these attributes.
ACTION: Add or remove attribute values to make them consistent.
PARAMS:

ERROR: [DM_SCNFG_E_CANT_FETCH_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a server_config – Invalid object ID %s
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_SCNFG_E_INCR_LENGTH_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: L While upgrading to version %d: Failed when trying to increase the length of a dm_server_config attribute because the attribute is too long.
CAUSE: The IncreaseLength function was called on an attribute which was too long. A previous upgrade step may have failed.
ACTION: Contact your Documentum Site Representative.
PARAMS:

ERROR: [DM_SCNFG_E_CANT_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Cannot save %s server_config.
CAUSE: One or more operations has failed during this save. Consult the following error message(s) for more help.
ACTION: Try again after fixing previous problems.
PARAMS:

ERROR: [DM_SCNFG_E_CANT_CREATE]

SEVERITY: ERROR
DESCRIPTION: Cannot create a server_config object.
CAUSE: Could not create a server_config object. Most likely the server is out of memory.
ACTION: Restart your session and talk to your sysadmin.
PARAMS:

ERROR: [DM_SCNFG_E_NEED_PRIV_FOR_REINIT]

SEVERITY: ERROR
DESCRIPTION: S The current user (%s) needs to have superuser or sysadmin privilege to reinit the server.
CAUSE: Must have Superuser or SysAdmin privilege to reinit server.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_SCNFG_E_NEED_PRIV_FOR_GETTOKEN]

SEVERITY: ERROR
DESCRIPTION: Superuser privilege is required to execute command gettoken
CAUSE: Must have Superuser privilege to issue gettoken,session,….
ACTION: try as a super-user. PARAMETER: None
PARAMS:

ERROR: [DM_SCNFG_E_NEED_PRIV_FOR_GETLOGIN]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser privilege to login as user %s.
CAUSE: Must have Superuser privilege to issue getlogin,session,other_user.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_SCNFG_E_NO_CONFIG_NAME]

SEVERITY: ERROR
DESCRIPTION: No configuration name is specified.
CAUSE: User has not specified a configuration object.
ACTION: Specify a unique name.
PARAMS:

ERROR: [DM_SCNFG_E_MAX_TICKET_TIMEOUT_RANGE]

SEVERITY: ERROR
DESCRIPTION: II Invalid value (%d) for max_login_ticket_timeout. It must be at least (%d).
CAUSE: Specified value for max_login_ticket_timeout is less than 1.
ACTION: Specify a value greater than 1. PARAMETER: User specified value for attribute max_login_ticket_time and the minimum value allowed for max_login_ticket_timeout.
PARAMS:

ERROR: [DM_SCNFG_E_DUPLICATED_APP_SERVER_NAME]

SEVERITY: ERROR
DESCRIPTION: S The repeating attribute app_server_name contains a duplicate for %s.
CAUSE: Failed to maintain unique app_server_name values while editing these attributes.
ACTION: Remove attribute values to make app_server_name unique.
PARAMS:

ERROR: [DM_SCNFG_E_INVALID_SESSC]

SEVERITY: ERROR
DESCRIPTION: I Concurrent session count %d must be positive.
CAUSE: User tried to specify an invalid concurrent session count.
ACTION: Specify a positive number.
PARAMS:

ERROR: [DM_SCNFG_E_INVALID_SECURE_MODE]

SEVERITY: ERROR
DESCRIPTION: S Invalid value (%s) specified for secure_connect_mode. Valid values are native, secure, and dual.
CAUSE: Specified value for secure_connect_mode is invalid. Valid values are native, secure, and dual.
ACTION: Reset secure_connect_mode to one of the valid values. PARAMETER: User specified value for attribute secute_connect_mode.
PARAMS:

ERROR: [DM_SCNFG_E_INVALID_DEFAULT_ACL]

SEVERITY: ERROR
DESCRIPTION: IS Invalid value %d set for default_acl of the serverconfig %s.
CAUSE: Invalid value is set to default_acl.
ACTION: Provide a valid value (FOLDER: 1, TYPE: 2, USER: 3)
PARAMS:

ERROR: [DM_SCNFG_E_INVALID_SRV_CONFIG]

SEVERITY: ERROR
DESCRIPTION: SS You have specified an invalid server config (%s) for the %s command.
CAUSE: If you specify a server config object name in the command, it must be an existing one.
ACTION: You must specify an existing server config object name.
PARAMS:

ERROR: [DM_SCNFG_E_INVALID_PROXVAL]

SEVERITY: ERROR
DESCRIPTION: II The projection_proxval[%d] contains invalid value %d.
CAUSE: Invalid value is set for proximitity.
ACTION: Reset proxval value to the valid value.
PARAMS:

ERROR: [DM_SCNFG_E_NEED_WRITE_PERMIT_FOR_LOCK]

SEVERITY: ERROR
DESCRIPTION: SD The current user (%s) needs to have WRITE permit to lock the sysobject (%s).
CAUSE: Must have WRITE permit to lock the sysobject if the user doesnt have SysAdmin privilege.
ACTION: Consult your system administrator. Note that starting from 5.3 SP1, this error is replaced with NEED_VERSION_PERMIT_FOR_LOCK.
PARAMS:

ERROR: [DM_SCNFG_E_NEED_VERSION_PERMIT_FOR_LOCK]

SEVERITY: ERROR
DESCRIPTION: SD The current user (%s) needs to have VERSION permit to lock the sysobject (%s).
CAUSE: Must have VERSION permit to lock the sysobject if the user doesnt have SysAdmin privilege.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_SCNFG_E_TICKET_TIMEOUT_RANGE]

SEVERITY: ERROR
DESCRIPTION: III Invalid value (%d) is specified for login_ticket_timeout. It must be between %d and %d.
CAUSE: Specified value for login_ticket_timeout is is out of range [1, max_login_ticket_timeout].
ACTION: Specify a value in the allowed range. PARAMETER: User specified value for attribute login_ticket_time, the minimum value allowed for login_ticket_timeout, and the current value of max_login_ticket_timeout.
PARAMS:

ERROR: [DM_SCNFG_E_NEED_VALID_USER_FOR_GETLOGIN]

SEVERITY: ERROR
DESCRIPTION: S The user (%s) needs to be a valid user.
CAUSE: Must have Superuser privilege to issue getlogin,session,other_user.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_SCNFG_E_NEED_PRIV_FOR_LOCK]

SEVERITY: ERROR
DESCRIPTION: SD The current user (%s) needs to have sysadmin privilege to lock a non-sysobject (%s).
CAUSE: Must have SysAdmin privilege to lock a non-sysobject.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_SCNFG_E_QRY_CACHE_FILE_NAME]

SEVERITY: ERROR
DESCRIPTION: A filename-generation error has occurred caching results of a cached query.
CAUSE: A filename could not be generated to hold your cached query results. This is an unlikely situation that could be caused by caching too many queries in a session.
ACTION: If you are an end user, you may be running an application that is caching too many queries. Try turning caching off for your session in your dmcl.ini. If you are an application programmer check all the queries in your application and make sure that the ones your are caching are good candidates for caching. Most queries should be run with readquery.
PARAMS:

ERROR: [DM_SCNFG_E_MAX_TICKET_TIMEOUT_TOO_SMALL]

SEVERITY: ERROR
DESCRIPTION: II Value (%d) specififed for max_login_ticket_time is smaller than login_ticket_timeout (%d). Please first reset login_ticket_timeout to a smaller value and then try again.
CAUSE: this message is displayed when sysadmin tries to set max_login_ticket_timeout to a value that is smaller than the value of login_ticket_timeout. PARAMETER: The current value of login_ticket_timeout and the value specified for max_login_ticket_timeout.
ACTION: Set login_ticket_timeout to a smaller value first and try again.
PARAMS:

ERROR: [DM_SCNFG_E_INVALID_PORT]

SEVERITY: ERROR
DESCRIPTION: II The projection_port[%d] contains invalid value %d.
CAUSE: Invalid value is set for port.
ACTION: Reset port value to the valid value.
PARAMS:

ERROR: [DM_SCNFG_E_DUPLICATED_TARGET_VALUES]

SEVERITY: ERROR
DESCRIPTION: SI The projection attributes contain duplicated target %s with port %d.
CAUSE: Fail to maintain unique target value while editing these attributes.
ACTION: Remove attribute values to make target unique.
PARAMS:

ERROR: [DM_SCNFG_E_INCR_LENGTH_NONEXISTANT_ATTR]

SEVERITY: ERROR
DESCRIPTION: L While upgrading to version %d: Failed while trying to increase the length of a non-existant attribute in dm_server_config.
CAUSE: Attributes for which the length is being increased should already be in existence before they are lengthened. A previous upgrade step may have failed.
ACTION: Contact your Documentum Site Representative.
PARAMS:

ERROR: [DM_SCNFG_E_INCR_LENGTH_FAILED]

SEVERITY: ERROR
DESCRIPTION: L While upgrading to version %d: The upgrade failed on widening dm_server_configs attribute lengths.
CAUSE: The database server may have problems widening the column length
ACTION: Check database server log or use sql script(under dba) to upgrade.
PARAMS:

ERROR: [DM_SCNFG_E_NEED_PRIV_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser or sysadmin privilege to save or destroy %s server_config object.
CAUSE: Must have Superuser or SysAdmin privilege to save/destroy server_config objects.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_SCNFG_E_CANT_FIND]

SEVERITY: ERROR
DESCRIPTION: S Cannot find %s server_config object.
CAUSE: Could not find the server_config object with the specified name.
ACTION: This is probably caused by invalid name.
PARAMS:

ERROR: [DM_SCNFG_E_QRY_CACHE_FILE_WRITE]

SEVERITY: ERROR
DESCRIPTION: A file write error has occurred caching results of a cached query.
CAUSE: A failure has occurred while writing your cached query results to the cache file.
ACTION: The probable cause is that your file system is full. You may be caching too many query results, or very large result sets. Try flushing your cache and starting over, or turn off caching in your dmcl.ini. Make sure all the queries that are being cached are appropriate candidates for caching.
PARAMS:

ERROR: [DM_SCNFG_E_INCONSISTENT_APP_SERVER_ATTRS]

SEVERITY: ERROR
DESCRIPTION: The value count of app_server attributes (app_server_name, app_server_uri) is not consistent.
CAUSE: Failed to maintain same value count while editing these attributes.
ACTION: Add or remove attribute values to make them consistent.
PARAMS:

ERROR: [DM_SCNFG_E_QRY_CACHE_FILE]

SEVERITY: ERROR
DESCRIPTION: A file error has occurred caching results of a cached query.
CAUSE: The file created to hold your cached query results could not be opened.
ACTION: This is an unexpected error that may be cause by a file system problem. Report this problem to your Documentum System Administrator. Meanwhile, to get past the immediate problem, turn caching off for your session in your dmcl.ini.
PARAMS:

ERROR: [DM_SCNFG_E_MAX_WF_THREADS]

SEVERITY: ERROR
DESCRIPTION: II Invalid value (%d) is specified for wf_agent_worker_threads. It must be between 1 and %d.
CAUSE: Specified value for wf_agent_worker_threads is invalid. It must be between 0 and 1000
ACTION: Reset wf_agent_worker_threads to a value between 0 and 1000. PARAMETER: User specified value for attribute wf_agent_worker_threads and its maximum.
PARAMS:

ERROR: [DM_SCNFG_E_NEED_VALID_USER_FOR_GETTOKEN]

SEVERITY: ERROR
DESCRIPTION: S The user (%s) must be a valid user or group.
CAUSE: A valid user or group must be specified. If a group, it must be prefixed with DM_GROUP=.
ACTION: Make sure that the specified user or group is valid in the docbase. If a group is specified, make sure it is prefixed with DM_GROUP=
PARAMS:

ERROR: [DM_SCNFG_W_QRY_CACHE_USER]

SEVERITY: WARNING
DESCRIPTION: S Query caching is disabled for your session. User %s is using your cache directory.
CAUSE: To create the directory name for your cache, your Documentum user name is turned into a string of length eight, followed by a dot, followed by a string of length three. Another users user name has be decomposed into the same directory name. You cannot share the same cache. Query caching is disabled for your session.
ACTION: Change your client local area to a directory that the other user (named in the message) will not use.
PARAMS:

ERROR: [DM_SCNFG_W_QRY_CACHE_DIR]

SEVERITY: WARNING
DESCRIPTION: An error has occurred creating or validating your query cache path. Query caching is disabled for your session.
CAUSE: This is an unexpected error. The types of things that could cause it include: 1) Your client local area path is invalid. 2) There was an error creating or accessing the qrycache directory. 3) There was an error creating or accessing the directory, the directory, or the directory. 4) There was an error while accessing an existing query cache map file.
ACTION: Check your client local area. Look for the qrycache path and the , , and paths for your host, docbase, and user name. Make sure they all have accessible permissions. Check the cache.map file, if it exists. Consult your System Administrator. You may have to delete the directory structure up to the client local area to get the query cache to reinitialize. If the problem is with the client local area itself, see your System Administrator.
PARAMS:

ERROR: [DM_SCNFG_W_QRY_CACHE_QRY]

SEVERITY: WARNING
DESCRIPTION: An unexpected internal error has occurred while initializing your query cache. Query caching is disabled for your session.
CAUSE: An internally generated query required to validate your query cache has failed to run properly. There should be additional error messages that indicate the nature of that failure.
ACTION: Gather all error messages associated with this failure and consult your Documentum System Administrator. There may be a problem with the dm_docbase_config in your docbase. You could also ignore this error query caching is turned off for your session.
PARAMS:

nahoru

DM_SERVER

ERROR: [DM_SERVER_F_INCR_LENGTH_FAILED]

SEVERITY: FATAL
DESCRIPTION: SLSL While upgrading %s to version %d: The upgrade failed to widen the %s attribute to %d.
CAUSE: Upgrading a type by increasing an attribute width failed.
ACTION: Please call Documentum technical support. ARGUMENT: The first argument is the name of the type being upgraded. The second is the version stamp we are trying to upgrade to. The third argument is the name of the attribute being widened. The fourth argument is the length we were trying to make the attribute.
PARAMS:

ERROR: [DM_SERVER_F_NOT_LISTENING]

SEVERITY: FATAL
DESCRIPTION: The server failed to initialize or reinitialize and is not listening for incoming connections on any port. The server will shutdown.
CAUSE: A networking error occurred which could not be recovered from.
ACTION: Contact technical support. $Id: dmsess.e,v 5.34 2003/05/30 14:34:00 swei Exp $ dmSession class errors Session warning codes.
PARAMS:

ERROR: [DM_SERVER_E_SHUT_DOWN]

SEVERITY: ERROR
DESCRIPTION: S The shutdown method has failed for the following reason: %s
CAUSE: The user probably did not have sufficient privilege to run this command.
ACTION: Run the method as a super-user. ARGUMENT: none
PARAMS:

ERROR: [DM_SERVER_E_LISTEN_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS The server failed to register itself on network address (%s). Error %s.
CAUSE: Unable to register on the network address/port
ACTION: Check the network configuration
PARAMS:

ERROR: [DM_SERVER_E_START_NETWISE]

SEVERITY: ERROR
DESCRIPTION: SS The server failed to start due to an error returned by the Netwise networking subsystem. Failed API: %s. Error %s.
CAUSE: This is a generalized networking error so it could be anything.
ACTION: Use the Netwise documentation to determine the error based on the API that failed.
PARAMS:

ERROR: [DM_SERVER_E_SHARED_MEMORY]

SEVERITY: ERROR
DESCRIPTION: IS Unable to create shared memory segment of size %d. Operating system error: %s
CAUSE: Possibly related to running out of either system semaphores or shared memory.
ACTION: Use the ipcs and ipcrm to locate and remove any unused shared memory segments. Ensure machine is configured with enough resources
PARAMS:

ERROR: [DM_SERVER_E_SSL_HANDSHAKE_FAILED]

SEVERITY: ERROR
DESCRIPTION: II Secure connection failed during handshake on connection (%d). Netwise returns error code (%d).
CAUSE: This may be caused by some unknown program trying to connect to Content Server secure port.
ACTION: May ignore it if this is seen occassionally only. Report to custmer support if this is seen frequently. ARGUMENT: The first argument is the connection ID and the second is error code from Netwise.
PARAMS:

ERROR: [DM_SERVER_E_INIT_MEQ_FAIL]

SEVERITY: ERROR
DESCRIPTION: S %s : Failed to initialize method execution queue.
CAUSE: Method Execution Queue initialization failed.
ACTION: Contact Documentums technical support.
PARAMS:

ERROR: [DM_SERVER_E_INVALID_VSTAMP]

SEVERITY: ERROR
DESCRIPTION: IS The operation failed because an invalid version stamp (%d) is found for %s.
CAUSE: Initialization failed due to invalid vstamp.
ACTION: Contact support and see why vstamp is bad and how to correct it.
PARAMS:

ERROR: [DM_SERVER_E_RETRY_EXHAUSTED]

SEVERITY: ERROR
DESCRIPTION: The server failed to re-register on the network after exhausted the list of alternative TCP/IP service names
CAUSE: All ports are in use or there is a severe networking error
ACTION:
PARAMS:

ERROR: [DM_SERVER_E_VSTAMP_SETTING_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Failed to update version stamp for application: %s
CAUSE: Content Server tries to update version stamp, but failed.
ACTION: Check server log file and look for any SQL failure. ARGUMENT: The name of the application.
PARAMS:

ERROR: [DM_SERVER_E_NO_MTHDSVR_BINARY]

SEVERITY: ERROR
DESCRIPTION: S %s : Method server binary is not accessible.
CAUSE: The method server binary mthdsvr is not under $DM_HOME/bin or it does not have the proper permission.
ACTION: Make sure method server binary mthdsvr is under $DM_HOME/bin and set execution permission for it.
PARAMS:

ERROR: [DM_SERVER_E_REORG_TABLE]

SEVERITY: ERROR
DESCRIPTION: S The REORGANIZE_TABLE method failed due to a database error: %s
CAUSE: The REORGANIZE_TABLE method failed after trying to execute a DBMS command.
ACTION: Refer to the database manual concerning the function you were trying to perform. ARGUMENT: The DBMS error.
PARAMS:

ERROR: [DM_SERVER_E_SOCKOPT]

SEVERITY: ERROR
DESCRIPTION: SI setsockopt failed for (%s) with error (%d)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_E_INI_FILE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SS Error initializing process due to the inability to get startup parameters from the named init_file: %s. Error reason: %s. Documentum server processes and utilities use a init_file for holding process startup information. The name of this file is given as a command line flag. This error generally indicates that the named file is not accessible.
CAUSE: The named init_file could not be read to extract startup parameters.
ACTION: Checked the named init_file to make sure it exists and is readable.
PARAMS:

ERROR: [DM_SERVER_E_NEED_ARCHIVE_DQL]

SEVERITY: ERROR
DESCRIPTION: Need a DQL predicate to perform archive/restore operation.
CAUSE: The archive/restore request does not have a DQL predicate.
ACTION: Resubmit the archive/restore request with a DQL predicate.
PARAMS:

ERROR: [DM_SERVER_E_RUN_NETWISE]

SEVERITY: ERROR
DESCRIPTION: SS The server encountered an error returned by the Netwise networking subsystem. Failed API: %s. Error %s.
CAUSE: This is a generalized networking error so it could be anything.
ACTION: Use the Netwise documentation to determine the error based on the API that failed.
PARAMS:

ERROR: [DM_SERVER_E_UNABLE_TO_PROCESS_METHOD_RESULTS]

SEVERITY: ERROR
DESCRIPTION: S Unable to process method results for method %s
CAUSE: An operation failed because the server was unable to process the results from a method.
ACTION: Look in the server log and method server log for more information. Run the method directly to confirm it works. ARGUMENT: The name fo the method.
PARAMS:

ERROR: [DM_SERVER_E_LAUNCH_FAILED2]

SEVERITY: ERROR
DESCRIPTION: S Unable to create connection for process because the creation of the execution context failed. Operating system error: %s
CAUSE: Possibly related to resource overload
ACTION: Check load on system
PARAMS:

ERROR: [DM_SERVER_E_RESTORE1]

SEVERITY: ERROR
DESCRIPTION: Need loadfile or DQL predicate to start restore operation.
CAUSE: User specified a restore operation w/o a loadfile name or DQL predicate.
ACTION: Respecify the restore method and specify at least load file or a DQL predicate.
PARAMS:

ERROR: [DM_SERVER_E_MAKE_SHM_ARG_FAIL]

SEVERITY: ERROR
DESCRIPTION: S %s : Failed to construct attach arguments.
CAUSE: Probably out of memory.
ACTION: Check and add more swap space or reduce the system load.
PARAMS:

ERROR: [DM_SERVER_E_REGISTER_FAIL]

SEVERITY: ERROR
DESCRIPTION: IS The server failed to register itself on port (%d). Error %s.
CAUSE: This error occurs when there is a network/administration error
ACTION: Check that the required network administration is correctand if so check the Netwise documentation to determine the error.
PARAMS:

ERROR: [DM_SERVER_E_LAUNCH_FAILED]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to create connection for process at machine %s as user %s because the creation of the execution context failed. Operating system error: %s
CAUSE: Possibly related to resource overload
ACTION: Check load on system
PARAMS:

ERROR: [DM_SERVER_E_CRT_SHM_OBJ_FAIL]

SEVERITY: ERROR
DESCRIPTION: S %s : Failed to create shared memory object.
CAUSE: Possibly running out of memory.
ACTION: Check and add more swap space or reduce the system load.
PARAMS:

ERROR: [DM_SERVER_E_CRT_SHM_REG_FAIL]

SEVERITY: ERROR
DESCRIPTION: S %s : Failed to create shared memory region.
CAUSE: There are several possibilities: 1) Running out of shared memory segments. 2) The shared memory region already exists.
ACTION: In case of 1), contact your SA to configure more shared memory segments. In case of 2), use ipcs/ipcrm to remove the existing shared memory segment.
PARAMS:

ERROR: [DM_SERVER_E_EXEC_SQL]

SEVERITY: ERROR
DESCRIPTION: S The execsql method failed due to a database error: %s
CAUSE: The execsql method failed after trying to execute a DBMS command.
ACTION: Refer to the database manual concerning the function you were trying to perform. ARGUMENT: The DBMS error.
PARAMS:

ERROR: [DM_SERVER_E_PREDICATE_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: I The predicate condition specified is too long for the archive/restore operation. The predicate must be a legal value for the QUEUE methods message argument, which currently cannot exceed %d bytes.
CAUSE: The predicate string is too long to fit into a QUEUE operation.
ACTION: Rewrite the archive/restore request so that the predicate fits into a smaller string. Note that the archiver also enforces predicate length restrictions on archive and restore operations that are likely to be more restrictive than this error condition.
PARAMS:

ERROR: [DM_SERVER_E_REGISTER_IN_USE]

SEVERITY: ERROR
DESCRIPTION: IS The server failed to register itself as there is already a server on port (%d). Error %s.
CAUSE: This error occurs when there is another server running on the requested port
ACTION: Make sure that you have each server configured with its own port number
PARAMS:

ERROR: [DM_SERVER_E_UPDATE_STATS]

SEVERITY: ERROR
DESCRIPTION: S The UPDATE_STATISTICS method failed due to a database error: %s
CAUSE: The UPDATE_STATISTICS method failed after trying to execute a DBMS command.
ACTION: Refer to the database manual concerning the function you were trying to perform. ARGUMENT: The DBMS error.
PARAMS:

ERROR: [DM_SERVER_E_CRT_MTHDSVR_PROC_FAIL]

SEVERITY: ERROR
DESCRIPTION: S %s : Creating method server process failed.
CAUSE: Maybe you are running too many processes on your system.
ACTION: Contact Documentums technical support.
PARAMS:

ERROR: [DM_SERVER_E_NO_MTHD_BUF]

SEVERITY: ERROR
DESCRIPTION: S %s failed to get free method execution request buffer.
CAUSE: Running out of internal method execution buffer.
ACTION: Increase the number of method server worker threads by setting server configuration parameter method_server_threads in server.ini to a greater value.
PARAMS:

ERROR: [DM_SERVER_E_START_NETWISE2]

SEVERITY: ERROR
DESCRIPTION: SI The server failed to start due to an error returned by the Netwise networking subsystem. Failed API: %s. Error code %d.
CAUSE: This is a generalized networking error so it could be anything.
ACTION: Use the Netwise documentation to determine the error based on the API that failed.
PARAMS:

ERROR: [DM_SERVER_E_POOL_FULL]

SEVERITY: ERROR
DESCRIPTION: I Unable to create connection because the internal connection data structure is full. There are %d elements
CAUSE: Software failure
ACTION: Re-start server and call Documentum technical support
PARAMS:

ERROR: [DM_SERVER_W_CANNOT_SECURE_MODE]

SEVERITY: WARNING
DESCRIPTION: Could not start server in secure or dual connect mode because server is not in trusted mode. Starting server in native connect mode.
CAUSE: attribute secure_connect_mode of dm_server_config is set to secure or dual but no valid tcs_license file is provided. Server supports secure or dual connection only when it is in trusted mode.
ACTION: To avoid this message, either set attribute secure_connect_mode of dm_server_config to native or provide a valid tcs_license file.
PARAMS:

ERROR: [DM_SERVER_W_NONE_TO_RESTORE]

SEVERITY: WARNING
DESCRIPTION: All of the objects specified by this restore request are currently online and available. No restore action is necessary.
CAUSE: The restore method predicate specifies no sysobjects that are currently marked as archived and offline. No restore request will be queued.
ACTION: No restore required.
PARAMS:

ERROR: [DM_SERVER_W_CLIENT_SOCKET]

SEVERITY: WARNING
DESCRIPTION: Could not set desired TCP socket options on new client connection. The Connection has been established but may suffer performance degradations.
CAUSE: The call to CookClientSocket – which sets desired TCP options on the client connection – failed. The system will continue and use the the socket connection anyway in the hope that it will prove usable. Previous error messages should have given more detail about what socket attributes could not be set and why.
ACTION: Check previous error messages for further details on the error.
PARAMS:

ERROR: [DM_SERVER_W_DO_METHOD]

SEVERITY: WARNING
DESCRIPTION: S Apply of DO_METHOD failed because of: %s
CAUSE: The DO_METHOD action proc detected an internal error.
ACTION: Correct the error and retry the procedure. ARGUMENT: A description of the error encountered
PARAMS:

ERROR: [DM_SERVER_W_DUMMY1_MESSAGE]

SEVERITY: WARNING
DESCRIPTION: This is here to keep the error numbers from shifting.
CAUSE: This is a dummy message that is never used. Do not ever remove it.
ACTION:
PARAMS:

ERROR: [DM_SERVER_W_NONE_TO_ARCHIVE]

SEVERITY: WARNING
DESCRIPTION: No sysobject will be archived/restored as result of the specified request.
CAUSE: The archive method predicate will cause no sysobject/document to be archive or restored. No archive request will be queued.
ACTION: change the archive request.
PARAMS:

ERROR: [DM_SERVER_I_GETHOSTBYADDR_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: S gethostbyaddr() failed with error %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_SERVER_FORK]

SEVERITY: INFORMATION
DESCRIPTION: I Attempt to fork failed with error (%i)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_MAX_SESSIONS]

SEVERITY: INFORMATION
DESCRIPTION: II Max sessions (%i) too large only (%i) sessions will be allowed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_NETWORK_REGISTER]

SEVERITY: INFORMATION
DESCRIPTION: Attempt to register with network failed. A new TCP/IP service name will be used
CAUSE: This can happen if the port is in use or stuck
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_START]

SEVERITY: INFORMATION
DESCRIPTION: SS %s %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_USER_DEACTIVATED]

SEVERITY: INFORMATION
DESCRIPTION: S User (%s) has been deactivated due to unsuccessful authentication attempts.
CAUSE: Informational message after dm_docbase_config.max_auth_attempt unsuccessful authentication attemps in a row.
ACTION: See sysadmin.
PARAMS: user_name.

ERROR: [DM_SERVER_I_SERVER]

SEVERITY: INFORMATION
DESCRIPTION: S %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_SKIPPING_GETHOSTBYADDR]

SEVERITY: INFORMATION
DESCRIPTION: server.ini parameter gethostbyaddr is set to F, skipping gethostbyaddr().
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_START_ID]

SEVERITY: INFORMATION
DESCRIPTION: SI Docbase %s was not successfully opened. Docbase id: (%d)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_TRACE_GETHOSTBYADDR]

SEVERITY: INFORMATION
DESCRIPTION: S Trace gethostbyaddr(), %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_REGISTERED]

SEVERITY: INFORMATION
DESCRIPTION: SI The server registered using service: (%s) on port: (%d)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_INIT_LOGIN_TICKET_MGR]

SEVERITY: INFORMATION
DESCRIPTION: Initialization of login ticket manager failed.
CAUSE: Initializing login ticket manager is unsuccessful due to a bad login ticket key.
ACTION: This should not happen. If this does happen, one has no other choice but contacting Documentum Engineering.
PARAMS: None.

ERROR: [DM_SERVER_I_TRACE_CACHE]

SEVERITY: INFORMATION
DESCRIPTION: S %s.
CAUSE: this trace is turned on by setting the environment variable TRACE_CACHE to T
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_LISTENING]

SEVERITY: INFORMATION
DESCRIPTION: S The server is listening on network address (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_USER_SESSION_KILLED]

SEVERITY: INFORMATION
DESCRIPTION: IS %d sessions owned by user (%s) have been killed because of the user account deactivation.
CAUSE: Informational message when an user account is deactivated because of unsuccessful authentication attempts.
ACTION: None.
PARAMS: number of session killed and user name.

ERROR: [DM_SERVER_I_SHUTDOWN]

SEVERITY: INFORMATION
DESCRIPTION: S %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_SOCKET]

SEVERITY: INFORMATION
DESCRIPTION: SI %s %i
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_IPV6_DISABLED]

SEVERITY: INFORMATION
DESCRIPTION: S The server can not listen on IPv6 address because %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_ACCEPT_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: I nl_accept failed, retry count = %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_LAUNCH_MTHDSVR]

SEVERITY: INFORMATION
DESCRIPTION: S Launching Method Server %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_CONNECT_STATUS]

SEVERITY: INFORMATION
DESCRIPTION: SI Connection %s (%d)
CAUSE: This happens when anything interesting happens to a client connection
ACTION: You need to look at what the specific error is to determine action
PARAMS:

ERROR: [DM_SERVER_I_OPEN_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: I nl_open failed, retry count = %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_CONFIG_VALUE]

SEVERITY: INFORMATION
DESCRIPTION: ISII Current value %d of server configuration parameter %s should be bigger than %d and smaller than %d, you should correct its value in server.ini file.
CAUSE: The given value for the configuration parameter is either too small or too big.
ACTION: Adjust the value for the configuration parameter.
PARAMS: Current Value, Configuration Parameter Name, Lower limit and Higher limit.

ERROR: [DM_SERVER_I_START_SERVER]

SEVERITY: INFORMATION
DESCRIPTION: SS Docbase %s %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SERVER_I_INSTALL_OWNER_AUTH_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: SI Server is shutdown because installation owner (%s) has exceeded the limit (%d) of unsuccessful authentication attempts.
CAUSE: Informational message when the installation owner has exceeded the limit of unsuccessful authentication attempts in a row.
ACTION: None.
PARAMS: installation owner name and the limit of unsuccessful authenticatio n attempts.

nahoru

DM_SESSION

ERROR: [DM_SESSION_F_EXEC_NO_DATATYPE]

SEVERITY: FATAL
DESCRIPTION: SI No datatype specified in the argument description for %s (%d).
CAUSE: The datatype (S, I, or B) must be specified.
ACTION: Specify the datatype.
PARAMS: The argument name and an internal code showing where the error was generated.

ERROR: [DM_SESSION_F_INT1]

SEVERITY: FATAL
DESCRIPTION: SS The following database query %s could not be executed. The database error is: %s
CAUSE: The problem may be caused by some inconsistence between server and database.
ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_SESSION_F_AUDIT_CACHE_IS_FULL]

SEVERITY: FATAL
DESCRIPTION: I The audit cache is full. The are %d entries in the cache.
CAUSE: There are too many types that need to be cached in the audit cache.
ACTION: Increase the size of the audit cache (gcNumAuditCacheRows in dmshared.cxx).
PARAMS:

ERROR: [DM_SESSION_F_SETUP_DYNAMIC_ROLE_INTERNAL_ERROR]

SEVERITY: FATAL
DESCRIPTION: dmSession::SetupDynamicRoles invocation error
CAUSE: This is an internal error.
ACTION: Contact EMC Technical Support. sql Facility Errors ** Documentum DocuServer ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1996 ** All rights reserved.
PARAMS:

ERROR: [DM_SESSION_F_EXEC_TOOMANYARGS]

SEVERITY: FATAL
DESCRIPTION: II Too many arguments (%d) have been specified for this function.nThe maximum is %d
CAUSE: There is an internal maximum size for the array of arguments for registered procedures.
ACTION: Increase the size of the internal table (DM_RFE_ARGS in dmsess.c).
PARAMS:

ERROR: [DM_SESSION_F_EXEC_TOOMANY]

SEVERITY: FATAL
DESCRIPTION: Too many procedures have been registered for EXECUTE.
CAUSE: There is an internal maximum size for the table of registered procedures.
ACTION: Increase the size of the internal table (DM_SIZEOF_RFE_TABLE in dmsess.c).
PARAMS:

ERROR: [DM_SESSION_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: S The dmi_change_record type could not add the following attribute: %s.
CAUSE: While attempting to add an attribute (adding a column in a table) to dmi_change_record an error was returned.
ACTION: Contact Documentum
PARAMS: This is the name of the attribute being added.

ERROR: [DM_SESSION_F_CRYPTOKEY_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: SI Failed to convert type %s to version %d.
CAUSE: Either the version stamp of the type was not set successfully or the changes done to convert the type failed.
ACTION: Examine the type. Contact documentum support if needed.
PARAMS:

ERROR: [DM_SESSION_F_EXEC_DUPDEFN]

SEVERITY: FATAL
DESCRIPTION: S The function (%s) has already been registered for EXECUTE.
CAUSE: This function is already registered.
ACTION: Find out where it is registered, and decide which registration is valid.
PARAMS:

ERROR: [DM_SESSION_F_EXEC_BAD_DATATYPE]

SEVERITY: FATAL
DESCRIPTION: S An invalid datatype was specified in the argument description (%s).
CAUSE: A datatype of S, I, or B must be specified.
ACTION: Respecify the datatype.
PARAMS: The invalid datatype specified.

ERROR: [DM_SESSION_E_D6_FEATURE_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S You can not use the D6 feature, %s, from a 5.3 client or below.
CAUSE: A pre-D6 client was trying to use a D6 feature like . Fetching a lightweight sysobject, or . Updating a shared parent which are not allowed.
ACTION: Only use D6 specific feature from a D6 DFC or above.
PARAMS:

ERROR: [DM_SESSION_E_SUPERUSER_RESTRICTED]

SEVERITY: ERROR
DESCRIPTION: SS Super user (%s) is not allowed to connect to docbase (%s) using login ticket.
CAUSE: This docbase has its docbase configuration attrubute restrict_superuser_connect set to 1.
ACTION: Try to connect with a password.
PARAMS: The first parameter is the user name. The second is the docbase name.

ERROR: [DM_SESSION_E_ILLEGAL_NUMBER_OF_ID_REQUESTED]

SEVERITY: ERROR
DESCRIPTION: III The number (%d) of IDs requested is either less than or equal to zero or exceeds the limit (%d) set for type with tag (%d).
CAUSE: The caller of NEXT_ID or NEXT_ID_LIST RPC has asked for either an illegal number or more IDs (set in the HOW_MANY parameter) than server can offer for the specified type tag.
ACTION: Set the HOW_MANY parameter to a lower number.
PARAMS:

ERROR: [DM_SESSION_E_FILE_LIB]

SEVERITY: ERROR
DESCRIPTION: S The server failed to set up the file I/O library. Operating System error: %s.
CAUSE: cannot map the C-runtime library calls to servers function call.
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: S Password argument is required for executing method (%s).
CAUSE: password argument must be provided for method export_ticket_key and import_ticket_key.
ACTION: specify an appropriate password.
PARAMS: The name of the method that is missing the password argument.

ERROR: [DM_SESSION_E_NON_EXIST_OBJ]

SEVERITY: ERROR
DESCRIPTION: D The object identified by %s does not exist.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_OUT_OF_TICKET]

SEVERITY: ERROR
DESCRIPTION: Cannot obtain a login ticket because all login ticket entries are in use.
CAUSE: All login ticket entries have been used.
ACTION: Increase the value of server parameter ticket_multiplier in server.ini to configure more login tickets.
PARAMS: None.

ERROR: [DM_SESSION_E_SETUP_ROLES_FOR_RPC]

SEVERITY: ERROR
DESCRIPTION: SD Error initializing dynamic roles for RPC %s (%s).
CAUSE: An internal error was encountered during an attempt to process the role specified in a server call.
ACTION: Check for previous error messages giving more detail on the error.
PARAMS:

ERROR: [DM_SESSION_E_LDAP_CHGPASS_USER]

SEVERITY: ERROR
DESCRIPTION: S The changepassword API failed with the following error: %s
CAUSE: Check the error message returned by the Directory Server.
ACTION: Inform your Directory Server Administrator.
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHECK_SEP]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during user validation using External Password Checking program: (%s). Operation: fprintf of user password Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check that the dm_server_config.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_PASSWORD_CHECK_GETPWNAM]

SEVERITY: ERROR
DESCRIPTION: S Operating System Failure during user validation. Operation: getpwnam(). Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check your server log for more details.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_CHUNKED_ID_IS_NULL]

SEVERITY: ERROR
DESCRIPTION: S The passed-in chunked object ID via operation %s is a null id.
CAUSE: DMCL tried to push a chunk of some object string for applying some function. However, the chunked object ID doesnt match with the chunked ID stored in the session.
ACTION: Make sure the passed-in ID matches with the one set by the previous SET_PUSH_OBJECT_STATUS RPC call. This is an internal error which customer is not supposed to encounter.
PARAMS:

ERROR: [DM_SESSION_E_PLUGIN_LOAD_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Failed to load %s plugin. The following error occured: %s.
CAUSE: The plugin did not load successfully.
ACTION: Check the error reported and change server settings as appropriate to fix problem.
PARAMS: Type of plugin, Error message

ERROR: [DM_SESSION_E_LDAP_BIND_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS The bind call to the Directory Server (%s) failed with error (%s).
CAUSE: Either the password might be incorrect or other reason as described in the error.
ACTION: Try again.
PARAMS:

ERROR: [DM_SESSION_E_CHK_LDAP_BIND]

SEVERITY: ERROR
DESCRIPTION: SS User (%s) with user OS name (%s) couldnt bind to the LDAP server. The authentication failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHECK_SE1]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during user validation using External Password Checking program: (%s). Operation: fprintf of extra param 1. Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check that the dm_server_config.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_DOCBASE_NOT_TRUSTED]

SEVERITY: ERROR
DESCRIPTION: SSS The originating docbase (%s) of login ticket (%s) is not trusted.
CAUSE: Using a login ticket generated by a non-trusted docbase.
ACTION: Either setting trusted_by_default to T in the current docbase, or configuring the originating docbase as trusted.
PARAMS: the name of the issuning docbase and the login ticket string.

ERROR: [DM_SESSION_E_CURSOR_ERROR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the execution of a cursor (%s).
CAUSE: A SQL statement that queries the Documentum schema has failed. This error message indicates that a failure occurred during the parsing of the generated SQL statement by the underlying RDBMS.
ACTION: The error message from the RDBMS is shown in the message. Use that error message to figure out what has happened.
PARAMS:

ERROR: [DM_SESSION_E_LDAP_MULTIPLE_UID]

SEVERITY: ERROR
DESCRIPTION: S The uid (%s) in the Directory Server is not unique.
CAUSE: The setup for the Directory Server does not work for Documentum.
ACTION: Inform your Directory Server Administrator.
PARAMS:

ERROR: [DM_SESSION_E_DOWNREV_SERVER]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to connect to server due to software incompatibility. The client library you are executing requires a server with at least a version of: (%s). The server version is (%s). Your client library version is (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CANT_MAKE_IDENTIFIER]

SEVERITY: ERROR
DESCRIPTION: Could not make new identifier value because of connection failure.
CAUSE: A failure to make a temporary database connection occurred during an attempt to generate a new identifier.
ACTION: None.
PARAMS:

ERROR: [DM_SESSION_E_ACCOUNT_DROPPED]

SEVERITY: ERROR
DESCRIPTION: SS The Operating System account for user (%s) with user OS name (%s) has been dropped
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_BAD_CLIENT_DIRS]

SEVERITY: ERROR
DESCRIPTION: S Could not validate directories needed by client errors were %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_EXPIRED]

SEVERITY: ERROR
DESCRIPTION: SS The Operating System password for user (%s) with user OS name (%s) has expired
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_LDAP_SEARCH]

SEVERITY: ERROR
DESCRIPTION: SS The search in the Directory Server using searchbase (%s) and filter (%s) failed.
CAUSE: The LDAP setup might contain incorrect values.
ACTION: Inform your System Administrator.
PARAMS:

ERROR: [DM_SESSION_E_CHK_LDAP_MULTIPLE_UID]

SEVERITY: ERROR
DESCRIPTION: SS The search for user (%s) with user OS name (%s) found multiple entries in the LDAP server. The authentication failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CANT_CONNECT]

SEVERITY: ERROR
DESCRIPTION: SSSS Could not connect to docbase (%s) at host (%s) because (%s). Network address: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CANT_INSERT_STAMP]

SEVERITY: ERROR
DESCRIPTION: S Cannot insert version stamp in internal table.nDatabase system error was: %s
CAUSE: A failure occurred during database startup. An attempt failed to insert a value into an internal table.
ACTION: Ensure that the database version is consistent with the version of the system being run.
PARAMS: The error string returned by the database system.

ERROR: [DM_SESSION_E_PASSWORD_CHECK_SEU]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during user validation using External Password Checking program: (%s). Operation: fprintf of user name. Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check that the dm_server_config.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_OUT_MEMORY]

SEVERITY: ERROR
DESCRIPTION: SS Running out of memory during creating a %s for (%s).
CAUSE: the underlying system is overloaded or has limited swap space.
ACTION: Configure more swap space or reduce the number of running applications.
PARAMS: The first parameter tells whether server is creating a ticket/token, and the second one is the user name.

ERROR: [DM_SESSION_E_MAKE_DATABASE_CONN]

SEVERITY: ERROR
DESCRIPTION: An unexpected failure occurred during an attempt to create a database connection. Please consult the server log for more details.
CAUSE: An exception occurred while establishing a database connection
ACTION: If sitution presists restart the server process.
PARAMS:

ERROR: [DM_SESSION_E_CANT_ADVANCE_ID]

SEVERITY: ERROR
DESCRIPTION: II Could not advance id generation beyond %i for tag %i
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_ONE_TIME_TICKET_SCOPE]

SEVERITY: ERROR
DESCRIPTION: SS One-time login ticket (%s) is valid for server (%s) only.
CAUSE: The given one-time login ticket has a different scope than the current server.
ACTION: Generate a login ticket with correct scope.
PARAMS: login ticket.

ERROR: [DM_SESSION_E_MAX_HEAP_SIZE]

SEVERITY: ERROR
DESCRIPTION: III Unable to set the session heap size to (%lu). Lower bound: (%lu), upper bound: (%lu). You must use a value in the specified range.
CAUSE: the number specified does not fit in the constrained range
ACTION: retry with a number in the specified range
PARAMS:

ERROR: [DM_SESSION_E_INIT_FAILURE1]

SEVERITY: ERROR
DESCRIPTION: S Failure to complete %s initialization.
CAUSE: The program failed during database startup, calling one of the various initialization procedures that set up parts of the database.
ACTION: Check that the database system has been properly installed.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_BOGUS_STAMP_TABLE]

SEVERITY: ERROR
DESCRIPTION: Internal version stamp table has wrong structure.
CAUSE: A failure has occurred during database startup. An internal table used by the system does not have the expected structure.
ACTION: Ensure that the database version is consistent with the version of the system being run.
PARAMS: None.

ERROR: [DM_SESSION_E_CHANGE_CHECKING_ABORTED]

SEVERITY: ERROR
DESCRIPTION: The root process change-checking step was aborted.
CAUSE: Likely due to an intermittent database failure
ACTION: If the error persists, stop and restart the server. Check to ensure that the database system is running properly.
PARAMS:

ERROR: [DM_SESSION_E_EXCEPTION_OCCURRED]

SEVERITY: ERROR
DESCRIPTION: S An exception occurred while %s.
CAUSE: An exception has occurred.
ACTION: Check the error message of the exception for more information.
PARAMS: The operation which caused the exception.

ERROR: [DM_SESSION_E_NOT_SUPERUSER]

SEVERITY: ERROR
DESCRIPTION: SS The operation you requested, %s, was not executed because the current user, %s, is not superuser
CAUSE: the current user is not superuser
ACTION: run command as superuser user
PARAMS:

ERROR: [DM_SESSION_E_CANT_MAKE_ID]

SEVERITY: ERROR
DESCRIPTION: II Could not satisfy request to make %d ids for the tag %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_RPC_ERROR]

SEVERITY: ERROR
DESCRIPTION: IS RPC error %d occurred: %s
CAUSE: A remote procedure call error occurred attempting to communicate with the server. The error number and description are those provided by Netwise.
ACTION: Check the Netwise documentation for a further explanation of the error.
PARAMS:

ERROR: [DM_SESSION_E_CHUNKED_ID_NOT_MATCHED]

SEVERITY: ERROR
DESCRIPTION: DD The chunked object ID %s passed in does not match with the one %s stored in the session.
CAUSE: DMCL tried to push a chunk of some object string for applying some function. However, the chunked object ID doesnt match with the chunked ID stored in the session.
ACTION: Make sure the passed-in ID matches with the one set by the previous SET_PUSH_OBJECT_STATUS RPC call. This is an internal error which customer is not supposed to encounter.
PARAMS:

ERROR: [DM_SESSION_E_NO_TRANSLATOR]

SEVERITY: ERROR
DESCRIPTION: SS Unable to find character translator for client machine: (%s) with client Locale: (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_ELOC_NOT_CONFIGURED]

SEVERITY: ERROR
DESCRIPTION: The external location used to define the program used to change passwords is not configured.
CAUSE: The program failed during change password, checking the external file.
ACTION: Check that the dm_server_config.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_CONNECT_DOCBROKER]

SEVERITY: ERROR
DESCRIPTION: S Unable to connect to docbase (%s). The Docbroker network addressing lookup failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_INLINE_AUTHENTICATION_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Unable to authenticate user (%s) for docbase (%s) using inline password.
CAUSE: User can not be authenticated. The specified password does not match with the password stored in the user object .
ACTION: Retry with the correct password or inform your System Administrator.
PARAMS:

ERROR: [DM_SESSION_E_CHK_LDAP_SEARCH]

SEVERITY: ERROR
DESCRIPTION: SS The search for user (%s) with user OS name (%s) in the LDAP server failed. The authentication failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHANGE_FAILURE]

SEVERITY: ERROR
DESCRIPTION: The server was unable to change your password
CAUSE: The program failed during change password.
ACTION: Check that the dm_server_config.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_NO_LOG_LOC_DEFINED]

SEVERITY: ERROR
DESCRIPTION: Your server configuration does not define a log location.
CAUSE: The log_location attribute is missing from the server config object.
ACTION: Check the server config object and set the log_location attribute.
PARAMS:

ERROR: [DM_SESSION_E_LDAP_DOWN]

SEVERITY: ERROR
DESCRIPTION: SIS Unable to connect to Directory Server on machine (%s) using port (%d) for docbase (%s).
CAUSE: The Directory Server might be down.
ACTION: Inform your System Administrator.
PARAMS:

ERROR: [DM_SESSION_E_CANT_SAVE_SESSION_TYPE]

SEVERITY: ERROR
DESCRIPTION: Cannot save session type during session initialization.
CAUSE: The program failed during database startup, because the session initialization code did not complete successfully.
ACTION: Check that the database system has been properly installed.
PARAMS: None.

ERROR: [DM_SESSION_E_AUTH_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Authentication failed for user %s with docbase %s.
CAUSE: Authentication failed.
ACTION: Check to see that the user is valid with both the operating system and the database system. Check to see that the passwords supplied on session creation are correct.
PARAMS: The user name and docbase base.

ERROR: [DM_SESSION_E_PASSWORD_CHANGE_1]

SEVERITY: ERROR
DESCRIPTION: SS Failure to validate existence and accessibility of External Password Changing program: (%s). Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check your server log file.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_CHK_PASS_OS_ERROR]

SEVERITY: ERROR
DESCRIPTION: There was an unexpected error during validation of your user credentials. Please see your system administrator or check the server log
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHECK_GETPWNAM2]

SEVERITY: ERROR
DESCRIPTION: SSSS Operating System Failure during user %s validation. (User OS name = %s, Domain = %s, and session id = %s)
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check your server log for more details.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_CANT_FIND_IDENTIFIER_TABLE]

SEVERITY: ERROR
DESCRIPTION: Could not find internal identifier table.
CAUSE: During startup, the internal identifier table could not be found
ACTION: This is an internal error. Report this error message to your Documentum site representative.
PARAMS:

ERROR: [DM_SESSION_E_INVALID_LDAPCERTDIR]

SEVERITY: ERROR
DESCRIPTION: Missing certificate database location object or Invalid LDAP certificate database directory.
CAUSE: Missing certificate db location object or Invalid certificate database directory path.
ACTION: Set certdb_location attribute in LDAP configuration object to location object name(for e.g. ldapcertdb_loc). This location object should point to directory containing the cert7.db certificate database.
PARAMS:

ERROR: [DM_SESSION_E_LOCK_OBJECT]

SEVERITY: ERROR
DESCRIPTION: DS Failed to lock object %s of type %s.
CAUSE: Failed to lock the object by updating the i_vstamp to itself.
ACTION: Examine the associated error from database.
PARAMS: D – ID of the object S – Object type

ERROR: [DM_SESSION_E_REUSE_ONE_TIME_TICKET]

SEVERITY: ERROR
DESCRIPTION: S One-time login ticket (%s) has already been used.
CAUSE: Reuse a one-time login ticket.
ACTION: Generate a new ticket.
PARAMS: login ticket.

ERROR: [DM_SESSION_E_HEAP_CREATION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: LS Unable to create a session heap of size %x. Operating system error: %s
CAUSE: Heap size too large (check session_heap_size in server.ini) or system is low on virtual memory
ACTION: change setting in server.ini an re-start server, increase virtual memory, decrease max_sessions
PARAMS:

ERROR: [DM_SESSION_E_CANNOT_VERIFY_SIGNATURE]

SEVERITY: ERROR
DESCRIPTION: SS Cannot verify the signature of %s (%s).
CAUSE: The ticket/token may be generated using a different LTK than the current one.
ACTION: Discard all old tickets/tokens.
PARAMS: The first parameter tells whether this is a ticket/token while the second one is the ticket/token.

ERROR: [DM_SESSION_E_CANT_COMMIT]

SEVERITY: ERROR
DESCRIPTION: Transaction could not be committed — RPC to server failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_ACCOUNT_LOCKED]

SEVERITY: ERROR
DESCRIPTION: SS The Operating System account for user (%s) with user OS name (%s) has been locked
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_SETUP_TICKET_ATTRIBUTES]

SEVERITY: ERROR
DESCRIPTION: SS Setting up %s attributes for user (%s) failed.
CAUSE: Some arguments to getlogin/gettoken command are invalid.
ACTION: Make sure all getlogin/gettoken arguments are valid.
PARAMS: The first one tells whether this is a ticket/token the second one is the user name.

ERROR: [DM_SESSION_E_SIGN_TICKET]

SEVERITY: ERROR
DESCRIPTION: SS Signing %s (%s) failed.
CAUSE: The login ticket key has not been set correctly.
ACTION: Run apply method reset_ticket_key to reset login ticket key
PARAMS: The first one tells whether this is a ticket/token the second one is the target user name.

ERROR: [DM_SESSION_E_INVALID_APPLICATION_TOKEN]

SEVERITY: ERROR
DESCRIPTION: S Invalid application token (%s).
CAUSE: Either no or invalid application token is provided.
ACTION: Make sure the application token is prefixed with DM_TOKEN.
PARAMS: The parameter is the application token string.

ERROR: [DM_SESSION_E_LAUNCH_BP_TRANSITION]

SEVERITY: ERROR
DESCRIPTION: S Unable to launch the BP transition evaluation process due to the error: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_WRONG_GROUP]

SEVERITY: ERROR
DESCRIPTION: SSS User (%s) is not a member of of the group (%s) that owns the application access control token (%s).
CAUSE: The user is not a member of the group which owns the token.
ACTION: Add the user to the group or create an appropriate token for the user.
PARAMS: The first parameter is the token the second is the group name the third one is the user name.

ERROR: [DM_SESSION_E_AUTH_PLUGIN_LOAD_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS Failed to load Authentication Plugin %s. Reason: %s.
CAUSE: The specified Authentication Plugin could not be loaded.
ACTION: Verify that the plugin has been developed according to the published interface for AuthenticationPlugins and that all components required by the plugin are present.
PARAMS: The file path of the Authentication Plugin and the reason for the failure.

ERROR: [DM_SESSION_E_INIT_FAILURE]

SEVERITY: ERROR
DESCRIPTION: I Failure on procedure number %d in initialization procedure list.
CAUSE: The program failed during database startup, calling one of the various initialization procedures that set up parts of the database.
ACTION: Retired message.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_UPGRADE_MAP_ERROR]

SEVERITY: ERROR
DESCRIPTION: Please shutdown your client session and reconnect to the docbase.
CAUSE: Client sides action proc map is inconsisten with the one form server. The client session wasnt terminated during server upgrade causing this inconsistency.
ACTION: Close the client session and reconnect to the server.
PARAMS:

ERROR: [DM_SESSION_E_NETWORK_TIMEOUT]

SEVERITY: ERROR
DESCRIPTION: The network request timed out the network may be non-operational or the remote service may be temporarily unavailable
CAUSE: network failure
ACTION: insure you are connected to the network and the remote service is operational
PARAMS:

ERROR: [DM_SESSION_E_CHK_LDAP_NOENTRY]

SEVERITY: ERROR
DESCRIPTION: SS The search for user (%s) with user OS name (%s) didnt find any entries in the LDAP server. The authentication failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CANT_SET_DATABASE_IDENTIFIER]

SEVERITY: ERROR
DESCRIPTION: S Cannot set database identifier for document base %s.
CAUSE: A failure occurred during database startup that prevented the system for updating internal database tables.
ACTION: Retired message.
PARAMS: The name of the document base.

ERROR: [DM_SESSION_E_LDAP_AUTH_FAILED]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to authenticate user (%s) for docbase (%s) using LDAP (%s).
CAUSE: User can not be authenticated. The DirectoryServer might be down or an invalid password was used.
ACTION: Retry with the correct password or inform your System Administrator.
PARAMS:

ERROR: [DM_SESSION_E_BAD_INFOID]

SEVERITY: ERROR
DESCRIPTION: S Bad Info ID given: %s
CAUSE: The info id is invalid.
ACTION: It is very likely that the tag (i.e. the first 2 bytes) of the info id is wrong.
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHANGE_SEOP]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during change password using External Password Changing program: (%s). Operation: fprintf of old password. Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check that the dm_server_config.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_EMPTY_CHUNKED_OBJ_STR]

SEVERITY: ERROR
DESCRIPTION: DD Either the chunked object string stored in session for the object %s is empty or the ID doesnt match with %s.
CAUSE: DMCL tried to use the chunked object string for applying some function. However, either the string stored in the session is empty or the chunked object doesnt match with the ID stored in the session.
ACTION: Check the ID and make sure that the object string was pushed by chunks before the function was called. This is an internal error which customer is not supposed to encounter.
PARAMS:

ERROR: [DM_SESSION_E_DECRYPT_KEY_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Decryption failed while importing login ticket key from docbase (%s).
CAUSE: Running out of memory.
ACTION: Be sure the system is not overloaded.
PARAMS: the name of the docbase.

ERROR: [DM_SESSION_E_CHGPASS_CRITERIA]

SEVERITY: ERROR
DESCRIPTION: Unable to change the password because the new password provided did not meet the required criteria for the underlying Operating System. Try again with another password
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_UNEXPECTED_CHK_RES]

SEVERITY: ERROR
DESCRIPTION: SI The return value from the external password validation program (%s) returned an unexpected value: (%d)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CANT_MAKE_TEMP_CONNECTION]

SEVERITY: ERROR
DESCRIPTION: SSSS Could not establish an internal, temporary database connection (database_name = %s, docbase_owner = %s, connection_string = %s) database system error was: %s
CAUSE: A failure occurred during an attempt to establish an internal, temporary database connection. The database system refused the connection attempt.
ACTION: Check the database system error message, and resolve the database problem it describes. This may be temporary repeat the operation. If the problem persists, intervention by your database system administrator may be required.
PARAMS:

ERROR: [DM_SESSION_E_RESET_TICKET_KEY]

SEVERITY: ERROR
DESCRIPTION: S Reset login ticket key failed by user %s.
CAUSE: This may be due to improper user privilege
ACTION: Repeat as a super user PARAMETER: the user name of the current session.
PARAMS:

ERROR: [DM_SESSION_E_ENCODE_KEY_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Encoding failed while exporting login ticket key from docbase (%s).
CAUSE: Running out of memory.
ACTION: Be sure the system is not overloaded.
PARAMS: the name of the docbase.

ERROR: [DM_SESSION_E_LDAPS_INIT]

SEVERITY: ERROR
DESCRIPTION: LDAP SSL initialization failed.
CAUSE: SSL Handshake failed because of missing trusted certificate chain in the cert7.db database.
ACTION: Use certutil to add trusted CA certificates to cert7.db. Please refer to the Server administration guide for more details.
PARAMS:

ERROR: [DM_SESSION_E_OBJECT_FILE_OPEN]

SEVERITY: ERROR
DESCRIPTION: S Unable to open the object stream file: (%s).
CAUSE: Internal error occurred while transferring big object over the wire.
ACTION: Try the same API again.
PARAMS: The object stream file.

ERROR: [DM_SESSION_E_PASSWORD_CHECK_1]

SEVERITY: ERROR
DESCRIPTION: SS Failure to validate existence and accessibility of External Password Checking program: (%s). Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check your server log for more details.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_ADD_DYNAMIC_ROLE]

SEVERITY: ERROR
DESCRIPTION: S Error adding dynamic role %s.
CAUSE: An internal error was encountered during an attempt to add the role as a dynamic group. verify this certificate.
ACTION: Check for previous error messages giving more detail on the error. Validate that the specified group exists and is dynamic.
PARAMS:

ERROR: [DM_SESSION_E_LDAP_AUTHENTICATION_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Unable to authenticate user (%s) for docbase (%s) using LDAP.
CAUSE: User can not be authenticated. The DirectoryServer might be down or an invalid password was used.
ACTION: Retry with the correct password or inform your System Administrator.
PARAMS:

ERROR: [DM_SESSION_E_CANT_INITIALIZE_SESSION]

SEVERITY: ERROR
DESCRIPTION: S Cannot initialize sessions for document base %s.
CAUSE: A failure occurred during database startup that prevented the system from starting a first session to complete database startup.
ACTION: Check that the DM_DBUSER entry for the document base in the initialization has system admin privileges for the DM_DATABASE.
PARAMS: The name of the document base.

ERROR: [DM_SESSION_E_MACHINE_ONLY]

SEVERITY: ERROR
DESCRIPTION: SSS Token (%s) can be used on machine identified by (%s) only you are using it on machine identifed by (%s).
CAUSE: The token is a machine only token and can be used on the specified machine only.
ACTION: Either use a token that is not machine only, or abtain a token for the client machine.
PARAMS:

ERROR: [DM_SESSION_E_CANT_SAVE_TRANS_TYPE]

SEVERITY: ERROR
DESCRIPTION: Cannot save transaction type during session initialization.
CAUSE: The program failed during database startup, because the session initialization code did not complete successfully.
ACTION: Check that the database system has been properly installed.
PARAMS: None.

ERROR: [DM_SESSION_E_SET_SECURITY]

SEVERITY: ERROR
DESCRIPTION: SS An unexpected error occurred while applying security the the file: %s. Operating System Error: %s
CAUSE: OS Failure
ACTION: verify installation and permission of server process
PARAMS:

ERROR: [DM_SESSION_E_DB_PASSWORD_FILE_OPEN]

SEVERITY: ERROR
DESCRIPTION: S Unable to open the database password file: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHANGE_SEU]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during change password using External Password Changing program: (%s). Operation: fprintf of user name. Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check that the dm_server_config.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_CLIENT_AUTHENTICATION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: Failed to authenticate client. Please check server log for more detail.
CAUSE: The client installation sent a certificate that uniquely identifies the client instance. The Content Server was unable to successfully verify this certificate.
ACTION: Check the reason listed in the error message as to why the certificate failed to verify.
PARAMS:

ERROR: [DM_SESSION_E_CHK_LDAP_DOWN]

SEVERITY: ERROR
DESCRIPTION: SS The LDAP server doesnt seem to run. The authentication for user (%s) with user OS name (%s) failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHECK_SE2]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during user validation using External Password Checking program: (%s). Operation: fprintf of extra param 2. Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check that the dm_server_config.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_CONNECT_REJECT]

SEVERITY: ERROR
DESCRIPTION: SSSS Connection request rejected by docbase (%s) at host (%s) because (%s). Network address: (%s).
CAUSE: The server rejected the client connection request.
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_NO_TICKET_KEY]

SEVERITY: ERROR
DESCRIPTION: S Docbase (%s) dose not have a login ticket key.
CAUSE: There are two possible causes: 1) the docbase is a pre-5.3 docbase 2)the login ticket key has not been set correctly for the docbase.
ACTION: 1) Make sure that you are executing this command against 5.3 or higher docbase. 2) If this is a 5.3 or highr docbase, try to execute apply method reset_ticket_key to reset login ticket key for the docbase.
PARAMS: the name of the docbase.

ERROR: [DM_SESSION_E_WRONG_DOCBASE_ID]

SEVERITY: ERROR
DESCRIPTION: IIS The docbase identifier: %d from the RDBMS does not match the DM_DBID: %d for docbase: %s.
CAUSE: A mismatch was detected during database startup between the database identifier stored in the database and the database identifier given in the initialization file (server.ini). This check prevents the docbase from being started with the wrong server.ini file or with a server.ini file that has been altered to specify the wrong docbase id. Otherwise these situations would lead to inadvertant data corruption. Another way to encounter this error is during an attempt to create or recreate a docbase using an existing tablespace that has remnants of an old docbase with a different docbase id. If this is the case, the table dmi_vstamp_s must first be removed manually.
ACTION: Check that the entry for the document base in the initialization file is correct.
PARAMS: %1 The docbase id as recorded in the docbase. %2 The docbase id listed in server.ini file. %3 The docbase name.

ERROR: [DM_SESSION_E_USE_TICKET_FOR_WRONG_USER]

SEVERITY: ERROR
DESCRIPTION: SSSS The %s (%s), created for user (%s), cannot be used for user (%s).
CAUSE: The ticket/token is used for a wrong user.
ACTION: Make sure right ticket/token is used for the user. API command dumploginticket can be used to exmamine the properties of a login ticket.
PARAMS: The first one tells if this is ticket/token the second one is the ticket/token the third one is the owner of the ticket/token the fourth one is the target user.

ERROR: [DM_SESSION_E_LDAPS_CLIENT_INIT]

SEVERITY: ERROR
DESCRIPTION: LDAP SSL Client initialization call failed..
CAUSE: Missing cert7.db database file.
ACTION: Create cert7.db database in the directory that is pointed to by the certificate location object. Use certutil utility to create the certificate database. Please refer to the Server administration guide for more details.
PARAMS:

ERROR: [DM_SESSION_E_MISSING_PARAMETERS]

SEVERITY: ERROR
DESCRIPTION: S You must supply parameters to the apply method (%s)
CAUSE: caller did not supply any arguments to the apply method
ACTION: The application, or user, is in error. Correct as such.
PARAMS:

ERROR: [DM_SESSION_E_BAD_TICKET]

SEVERITY: ERROR
DESCRIPTION: S The following %s is not a valid ticket definition.
CAUSE: User has specified an invalid definition for a ticket.
ACTION: Specify a valid ticket spec. Ticket spec is DM_TICKET=
PARAMS:

ERROR: [DM_SESSION_E_SEC_MODE_UNKNOWN]

SEVERITY: ERROR
DESCRIPTION: Failed to find out the docbase security mode, due to the sessionconfig doesnt exist.
CAUSE: The client is having trouble to connect to the server and is not able to find out the docbase security mode.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SESSION_E_INVALID_APPLICATION_CODE]

SEVERITY: ERROR
DESCRIPTION: S The application_code setting of %s is invalid. Application codes may not contain whitespace. Valid codes may only contain alphanumeric characters or _.
CAUSE: An invalid application_code value has been supplied. application_code can be set in the apiconfig or sessionconfig objects.
ACTION: Ensure that the application_code value only contains alphanumeric or _ characters. No whitespace is allowed.
PARAMS: The value of application_code that is invalid.

ERROR: [DM_SESSION_E_DUMMY1_MESSAGE]

SEVERITY: ERROR
DESCRIPTION: This message is here to keep the error numbers from shifting.
CAUSE: This is a dummy message that is never used. Do not ever remove it.
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_RESTRICTED_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SS The operation you attempted could not be completed because your user credentials are inadequate. You are connected as user (%s) with authentication level of (%s). Ensure you connected successfully.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_DOCBASE_VSTAMP]

SEVERITY: ERROR
DESCRIPTION: LL The version stamp of the docbase is %d and is lower than %d required by the program. Please upgrade the docbase first and run the program again.
CAUSE: Try to run a newer utility on an old docbase.
ACTION: Upgrade the docbase and run the program again.
PARAMS:

ERROR: [DM_SESSION_E_TICKET_REVOKED]

SEVERITY: ERROR
DESCRIPTION: SS The %s (%s) has been revoked.
CAUSE: The ticket/token has expired.
ACTION: Create a new ticket/token to use.
PARAMS: The first parameter tells whether this is a ticket/token while the second one is the ticket/token.

ERROR: [DM_SESSION_E_PASSWORD_CHANGE_LAUNCH]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during launch of the using External Password Change program: (%s). Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check your server log for more details.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_LDAP_NOENTRY]

SEVERITY: ERROR
DESCRIPTION: S The search in the Directory Server for user (%s) didnt produce any results.
CAUSE: The Directory Server doesnt contain a uid with the users name.
ACTION: Inform your System Administrator.
PARAMS:

ERROR: [DM_SESSION_E_TRANSACTION_ERROR]

SEVERITY: ERROR
DESCRIPTION: Transaction invalid due to errors, please abort transaction.
CAUSE: A failure occured in a previous operation that caused the transaction state to be invalid. The transaction must be aborted.
ACTION: Abort current transaction.
PARAMS: None.

ERROR: [DM_SESSION_E_GETSVRCFG_FAIL]

SEVERITY: ERROR
DESCRIPTION: Getting server configuration object failed.
CAUSE: This is usually caused by a system configuration issue, for exmaple, folder access permission settings.
ACTION: Contact your system administrator.
PARAMS: none.

ERROR: [DM_SESSION_E_CANT_UPDATE_STAMP]

SEVERITY: ERROR
DESCRIPTION: S Cannot update version stamp in internal table.nDatabase system error was: %s
CAUSE: A failure occurred during database startup. An attempt failed to update a value into an internal table.
ACTION: Ensure that the database version is consistent with the version of the system being run.
PARAMS: The error string returned by the database system.

ERROR: [DM_SESSION_E_AUTH_PLUGIN_LOAD_NO_ID_ERROR]

SEVERITY: ERROR
DESCRIPTION: S Failed to load Authentication Plugin %s. The plugin did not return an identifier.
CAUSE: The specified Authentication Plugin could not be loaded because it did not return an identifier.
ACTION: For custom plugins, plugin developer must specify a plugin identifier. For Documentum plugins, please contact Documentum.
PARAMS: The file path of the Authentication Plugin.

ERROR: [DM_SESSION_E_DEADLOCK]

SEVERITY: ERROR
DESCRIPTION: Operation failed due to DBMS Deadlock error. This error is given when a server operation is interrupted by a deadlock error in the DBMS. When this error is received the underlying DBMS transaction has been rolled back, so the operation cannot proceed.
CAUSE: A database deadlock occurred in the operation.
ACTION: Retry the operation if appropriate.
PARAMS:

ERROR: [DM_SESSION_E_PROCESS_GROUP_QUERY]

SEVERITY: ERROR
DESCRIPTION: S Error executing query to process recursive group membership for group %s.
CAUSE: A error occurred while running a database query to find the set of groups that the current group is a member of.
ACTION: Check previous error messages for more information.
PARAMS:

ERROR: [DM_SESSION_E_START_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Server did not start session. Please see your system administrator or check the server log.nError message from server was:n%s
CAUSE: The server could not start a session. The error message is the message returned by the server.
ACTION: Check the error message returned from the server.
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHECK_FORK]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during user validation using External Password Checking program: (%s). Operation: fork(). Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check your server log for more details.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_CHK_LDAP_NOSEARCHBASE]

SEVERITY: ERROR
DESCRIPTION: SS The searchbase couldnt be determined. The authentication for user (%s) with user OS name (%s) failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_USED_TOKEN_ON_WRONG_MACHINE]

SEVERITY: ERROR
DESCRIPTION: SSS Application access control token (%s), created for use on machine (%s) only, cannot be used on machine (%s).
CAUSE: The token was acquired for use on a particular machine and will not work when used on a different machine.
ACTION: Create a token that works for the target machine.
PARAMS: The first parameter is the access control token the second one is the MAC address of the current client machine while the third one is the MAC address of the target machine.

ERROR: [DM_SESSION_E_INVALID_USER]

SEVERITY: ERROR
DESCRIPTION: SSS User (%s), with OS User name (%s), has failed to connect to docbase (%s) due to bad login.
CAUSE: The program failed to establish a session for the user.
ACTION: Check to see that the user is valid with both the operating system and the database system. Check to see that the passwords supplied on session creation are correct.
PARAMS: The name of the user and the name of the document base.

ERROR: [DM_SESSION_E_AUTH_PLUGIN_AUTH_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSSS Authentication failed for user %s with docbase %s. Plugin with ID %s returned error: %s
CAUSE: Authentication by plugin failed.
ACTION: Check to see that the user and password are valid. Refer to the error message of the plugin for more information.
PARAMS: The user name, docbase base, plugin identifier and error message.

ERROR: [DM_SESSION_E_GET_GROUP_INFO_DB]

SEVERITY: ERROR
DESCRIPTION: SS Error processing database cursor for group %s. (%s) An Internal error occurred while checking information on a given group name. The error may have been triggered by a problem with a database query. Previous error messages should give more detail on the failure.
CAUSE: An internal error occurred while looking up a group name.
ACTION: Check database error messages for more information.
PARAMS:

ERROR: [DM_SESSION_E_CANNOT_LOAD_LIGHTWEIGHT_TYPE_WITHOUT_PARENT]

SEVERITY: ERROR
DESCRIPTION: S The lightweight type (%s) could not be loaded because its parent type has not been cached yet
CAUSE: A lightweight type can not be loaded before its parent type because we do not send the parent types definition along with the lightweight type.
ACTION: Either retrieve the parent type or its instances before retrieving the lightweight so that the parent is cached before the lightweight type.
PARAMS:

ERROR: [DM_SESSION_E_CANT_KILL_TICKET]

SEVERITY: ERROR
DESCRIPTION: SS User %s does not have sufficient privilege to kill ticket %s.
CAUSE: User tried to kill a ticket with insufficient privilege. Only ticket owner and/or super can kill a ticket.
ACTION: None.
PARAMS:

ERROR: [DM_SESSION_E_CREATE_ENCODER]

SEVERITY: ERROR
DESCRIPTION: SS Creating encoder failed during generating %s for (%s).
CAUSE: The underlying system is overloaded or has limited swap space.
ACTION: Configure more swap space or reduce the number of running applications.
PARAMS: The first one tells whether this is a ticket/token the second one is the user name.

ERROR: [DM_SESSION_E_NULL_TICKET_KEY]

SEVERITY: ERROR
DESCRIPTION: A login ticket key must be provided.
CAUSE: Missing login ticket key argument for apply method IMPORT_TICKET_KEY
ACTION: Specify a login ticket key
PARAMS: None

ERROR: [DM_SESSION_E_CHGPASS_CRITERIA_V]

SEVERITY: ERROR
DESCRIPTION: S The changepassword API failed with the following error: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_AUTH_PLUGIN_LOAD_CHARTRANS_ERROR]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to load Authentication Plugin %s. Plugin requested codepage %s but server does not support translation from codepage %s.
CAUSE: The specified Authentication Plugin could not be loaded because it requested a codepage that the server does not know how to translate into.
ACTION: For custom plugins, plugin developer must specify a different codepage. For Documentum plugins, please contact Documentum.
PARAMS: The plugin identifier, the codepage requested by the plugin and the codepage of the server.

ERROR: [DM_SESSION_E_NT_UNIFIED_LOGON_FAILED]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to authenticate user (%s) in domain (%s) for docbase (%s) using NT Unified Logon. You may explicitly supply password and domain to connect again.
CAUSE: User and domain names can not be validated from the machine where server is running.
ACTION: Retry with password and domain.
PARAMS:

ERROR: [DM_SESSION_E_DB_PASSWORD_FILE]

SEVERITY: ERROR
DESCRIPTION: SS Unable to access database password file: (%s). The operating system error was: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_BAD_PARTITION_SPEC]

SEVERITY: ERROR
DESCRIPTION: III Illegal address partitioning specification — partitions: %i, start: %i, end: %i
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_ACCOUNT_EXPIRED]

SEVERITY: ERROR
DESCRIPTION: SS The Operating System account for user (%s) with user OS name (%s) has expired
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_LDAP_BIND]

SEVERITY: ERROR
DESCRIPTION: The bind call to the Directory Server failed.
CAUSE: The password might be incorrect.
ACTION: Try again.
PARAMS:

ERROR: [DM_SESSION_E_CANT_FIND_SERVICE]

SEVERITY: ERROR
DESCRIPTION: SS Could not connect to Docbase named (%s) due to failure finding service to port mapping for service name name (%s).
CAUSE: The service name could not be mapped into a service number.
ACTION: Check the /etc/services file for the client machine.
PARAMS:

ERROR: [DM_SESSION_E_CANT_BUILD_IDENTIFIER_TABLE]

SEVERITY: ERROR
DESCRIPTION: Could not build internal identifier table.
CAUSE: During startup, the internal identifier table could not be built.
ACTION: This is an internal error. Report this error message to your Documentum site representative.
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHANGE_SENP]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during change password using External Password Changing program: (%s). Operation: fprintf of new password. Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check that the dm_server_config.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_DATABASE_ID_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: Database identifier not found in version stamp table
CAUSE: During startup, the database identifier could not be found in the internal version stamp table
ACTION: This is likely caused by starting up the system on an uninitialized database. Perform database initialization and repeat the operation.
PARAMS:

ERROR: [DM_SESSION_E_NON_LOCAL_SERVER_RUNNING]

SEVERITY: ERROR
DESCRIPTION: There are no running local content servers.
CAUSE: All local content servers are down.
ACTION: Make sure local content servers are up running.
PARAMS:

ERROR: [DM_SESSION_E_STORESTAT_OVERFLOW]

SEVERITY: ERROR
DESCRIPTION: ID The shared memory segment for caching the ONLINE/OFFLINE status of the Documentum Storage areas has reached its maximum size (%d). Update access may be incorrectly given to Offline or ReadOnly storage area (%s).
CAUSE: There is a fixed size array in shared memory used to cache offline or readonly storage area statuses. When this array is filled, no more status values can be added. Even though this does not prevent the marking of storage areas as Offline or Readonly, because the status cannot be stored in memory, the server will treat the storage area as Online until room is freed up in the array. (By moving other storage areas to Online state).
ACTION: Reduce the number of Offline or ReadOnly storage areas.
PARAMS: %d Size of overflowed array %s ID value of storage area that could not be added

ERROR: [DM_SESSION_E_CANT_ALLOCATE_NEXT_TICKET_BATCH]

SEVERITY: ERROR
DESCRIPTION: Could not allocate next ticket batch.
CAUSE: A temp connection to the database failed or an update failed which then caused a failure to allocate a data_ticket value for storing a new data file.
ACTION: Ensure database has adquate connections and is functioning correctly. Check the session and server logs for resource errors, particularly around the establishment of new database connections.
PARAMS:

ERROR: [DM_SESSION_E_KILL_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to kill the session referred to by ID %s failed with operating system error %s. Attempting to clean up after this session.
CAUSE: The session thread/process may have died by itself uncleanly.
ACTION: Attempt to clean up.
PARAMS:

ERROR: [DM_SESSION_E_USED_LOCAL_TICKET_OTHER_DOCBASE]

SEVERITY: ERROR
DESCRIPTION: SSS Login ticket (%s) is created for docbase (%s), cannot be used in docbase (%s).
CAUSE: A login ticket with docbase scope is used on a different docbase.
ACTION: Create a global login ticket to use. PI command dumploginticket can be used to exmamine the properties of a login ticket
PARAMS: The first one is the login ticket, the second one is the ticket originating docbase id, and the target docbase id.

ERROR: [DM_SESSION_E_NO_TRANSACTION]

SEVERITY: ERROR
DESCRIPTION: Transaction was not open commit failed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CHG_PASS_BAD_CRED]

SEVERITY: ERROR
DESCRIPTION: SS The password was unchanged for user (%s) with user_login_name (%s) due to invalid old user_login_name/password
CAUSE: User did not specify his current credentials
ACTION: Use the correct user_os_name, password pair
PARAMS:

ERROR: [DM_SESSION_E_INVALID_TICKET_FORMAT]

SEVERITY: ERROR
DESCRIPTION: Invalid login ticket (%s). A login ticket must have prefix DM_TOCKET=.
CAUSE: The login ticket does not have prefix DM_TICKET=
ACTION: Specify a valid login ticket.
PARAMS: None

ERROR: [DM_SESSION_E_LOG_DIR_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SSS The location defined in your server configuration for log, (%s), specifies a directory, (%s), which cannot be accessed. The Operating System error returned was (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CANNOT_DECODE]

SEVERITY: ERROR
DESCRIPTION: SS Cannot decode %s (%s).
CAUSE: Either the login ticket key has been reset since generation of the ticket/token Or the ticket/token may have been altered.
ACTION: Make sure a correct ticket/token is provided. If not sure, please create a new one.
PARAMS: The first parameter tells whether this is a ticket/token while the second one is the ticket/token.

ERROR: [DM_SESSION_E_NOT_SYSADMIN]

SEVERITY: ERROR
DESCRIPTION: SS The operation you requested, %s, was not executed because the current user, %s, is not sysadmin
CAUSE: the current user is not sysadmin
ACTION: run command as sysadmin user
PARAMS:

ERROR: [DM_SESSION_E_LOOKUP_DOCBASE_ID]

SEVERITY: ERROR
DESCRIPTION: S Could not look up the docbase id for docbase %s. Error finding key value for doc_base_identifier in the type dmi_vstamp.
CAUSE: A failure occurred trying to verify that the docbase server is staring with a valid docbase id. The server requires that the docbase id in the server.ini file match the one recorded in the docbase itself. See DM_SESSION_E_WRONG_DOCBASE_ID error for more information.
ACTION: Check the existence and permissions on the dmi_vstamp_s table.
PARAMS: %1 The docbase name.

ERROR: [DM_SESSION_E_OPEN_TRANSACTION]

SEVERITY: ERROR
DESCRIPTION: S Cannot execute %s operation while in an open transaction. An operation was attempted that manages its own transaction state and cannot be executed while a user transaction is open.
CAUSE: The user session which requested the operation has an outstanding transaction open.
ACTION: Close the current transaction and attempt the operation.
PARAMS:

ERROR: [DM_SESSION_E_ACE_CREATE]

SEVERITY: ERROR
DESCRIPTION: SSS An unexpected error occurred while creating an Operating System ACE. Parameters: %s, %s. Operating system error: %s.
CAUSE: OS Failure
ACTION: verify installation and permission of server process
PARAMS:

ERROR: [DM_SESSION_E_LDAP_FAILOVER_DOWN]

SEVERITY: ERROR
DESCRIPTION: SS Unable to connect to Primary as well as Failover Directory Server on machine (%s) for docbase (%s).
CAUSE: The Directory Server might be down.
ACTION: Inform your System Administrator.
PARAMS:

ERROR: [DM_SESSION_E_NOID]

SEVERITY: ERROR
DESCRIPTION: S No id given for command %s.
CAUSE: An object id is required for this command.
ACTION: Correct the command to specify an object id.
PARAMS: The command as specified.

ERROR: [DM_SESSION_E_CANT_MAKE_TABLE]

SEVERITY: ERROR
DESCRIPTION: SS Unable to make the table %s.nDatabase error was: %s
CAUSE: The server could not create the table specified due to a database error.
ACTION: Follow the corrective procedure for the database manager for the error specified.
PARAMS:

ERROR: [DM_SESSION_E_AUTH_PLUGIN_LOAD_INIT_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS Failed to load Authentication Plugin %s. Plugin initialization returned error: %s.
CAUSE: The specified Authentication Plugin could not be loaded because its dm_init function returned an error.
ACTION: Check the error message returned by the authentication plugin for more information.
PARAMS: The file path of the Authentication Plugin and the error message returned by the plugin.

ERROR: [DM_SESSION_E_DB_CONNECTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: A database failure. The details of the failure are in the argument.
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CANT_READ_DB_PASSWORD]

SEVERITY: ERROR
DESCRIPTION: S The database password cannot be read for document base %s.
CAUSE: The user starting up the server does not have access rights to read the password file.
ACTION: Check that the user starting up the server should have rights to read the password file.
PARAMS: The document base name.

ERROR: [DM_SESSION_E_SESSION_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S The session that was requested to be killed %s could not be found.
CAUSE: The session already terminated
ACTION: None necessary as the session is already terminated
PARAMS:

ERROR: [DM_SESSION_E_LDAP_OPT_THREAD]

SEVERITY: ERROR
DESCRIPTION: The setting of the thread safety option failed.
CAUSE: Unknown.
ACTION: Inform your System Administrator.
PARAMS:

ERROR: [DM_SESSION_E_FIX_OBJ_INCONSISTENCIES_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS An internal error occurred while executing the fix object type table procedure for type %s: %s. Changes for all objects of this type will not be committed.
CAUSE: An internal error occurred during the fix object table inconsistencies procedure.
ACTION: Check the session logs for more information. Try enabling tracing for more details.
PARAMS: The type that was being processed when the error occurred and a description of the error.

ERROR: [DM_SESSION_E_AUTH_PLUGIN_CHGPASS_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS The changepassword API using plugin with ID %s failed with the following error: %s
CAUSE: The authentication plugin failed to change the password.
ACTION: Check the error message returned by the authentication plugin for more information.
PARAMS: The plugin identifier and the error message returned by the plugin.

ERROR: [DM_SESSION_E_SESSION_STAMP_FAILURE]

SEVERITY: ERROR
DESCRIPTION: Version stamp mismatch between session code and database.
CAUSE: The program failed during database startup, because the session initialization code did not complete successfully.
ACTION: Check that the database system has been properly installed.
PARAMS: None.

ERROR: [DM_SESSION_E_ACTION]

SEVERITY: ERROR
DESCRIPTION: This likely means that the server cannot establish a database connection for the user. Check the initialization file to make sure that the database user is specified properly.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CANT_FIND_ID_TABLE]

SEVERITY: ERROR
DESCRIPTION: S Cannot find id table for document base %s.
CAUSE: A failure occurred during database startup that prevented the system from reading internal database tables.
ACTION: Retired message.
PARAMS: The name of the document base.

ERROR: [DM_SESSION_E_LDAP_OPT_RECONNECT]

SEVERITY: ERROR
DESCRIPTION: The setting of the reconnect option failed.
CAUSE: Unknown.
ACTION: Inform your System Administrator.
PARAMS:

ERROR: [DM_SESSION_E_ASSUME_USER_FILE]

SEVERITY: ERROR
DESCRIPTION: SS Unable to access the assume user program file. Error returned from Operating System: (%s). Program file: (%s).
CAUSE: the
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CANT_FIND_DOCUMENT_BASE]

SEVERITY: ERROR
DESCRIPTION: S Document base name %s not in dminfo.sys.
CAUSE: The named document base is not defined in the dminfo.sys file in the directory $DOCU_HOME.
ACTION: Retired message.
PARAMS: The document base name.

ERROR: [DM_SESSION_E_GETJMSCONFIG_FAIL]

SEVERITY: ERROR
DESCRIPTION: Failed to get dm_jms_config objects from docbase.
CAUSE: Failed to fetch dm_jms_config objects from docbase.
ACTION: Check if dm_jms_config type is defined in docbase.
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHECK_PCLOSE]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during user validation using External Password Checking program: (%s). Operation: pclose(). Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check that the dm_server_config.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_CAUSE]

SEVERITY: ERROR
DESCRIPTION: The client could not establish a connection to the service on the named host.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_TRANSACTION_ABORTED]

SEVERITY: ERROR
DESCRIPTION: Transaction aborted by server due to client session timeout. Use abort API to re-establish connection to server.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_CANT_BUILD_SESSION_TYPES]

SEVERITY: ERROR
DESCRIPTION: SS Cannot construct basic session types for user %s in document base %s.
CAUSE: A failure occurred during database startup that prevented the construction of the internal database types used by the session manager.
ACTION: Ensure that the database version is consistent with the version of the system being run.
PARAMS: The name of the user and the name of the document base.

ERROR: [DM_SESSION_E_AUTH_PLUGIN_LOAD_EXCEPT_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS Failed to load Authentication Plugin %s. The following exception occured during initialization: %s.
CAUSE: The specified Authentication Plugin could not be loaded because of an exception during initialization.
ACTION: Check the error message of the exception for more information.
PARAMS: The file path of the Authentication Plugin and the error message.

ERROR: [DM_SESSION_E_CANT_UPDATE_ID_TABLE]

SEVERITY: ERROR
DESCRIPTION: S The internal id table cannot be updated.nDatabase system error was: %s
CAUSE: A failure occurred during processing of an operation that required a new identifier. The internal table that is used to record the most recently allocated id could not be update.
ACTION: Ensure that the database version is consistent with the version of the system being run.
PARAMS: The error string returned by the database system.

ERROR: [DM_SESSION_E_PASSWORD_CHECK_POPEN]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during user validation using External Password Checking program: (%s). Operation: popen(). Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check to see if the machine has enough resources such as swap space and physical memory to create more processes. Check to see if the owner of the server process has a small limit on the number of files or processes that can be cconcurrently opened.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_BAD_INFO]

SEVERITY: ERROR
DESCRIPTION: S Could not read dminfo.sys file for docbase.nError message was: %s
CAUSE: The dminfo.sys file for the docbase could not be read.
ACTION: Retired message.
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHECK_WAITPID]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during user validation using External Password Checking program: (%s). Operation: waitpid(). Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check your server log for more details.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_CANT_ESTABLISH_CONNECTION]

SEVERITY: ERROR
DESCRIPTION: SSS Failure to establish database connection: document base %s, database %s, server %s.
CAUSE: The program failed to establish a database connection during session creation.
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_PASSWORD_CHECK_LAUNCH]

SEVERITY: ERROR
DESCRIPTION: SS Operating System Failure during launch of the using External Password Check program: (%s). Operating System Error: (%s).
CAUSE: The program failed during user authentication, checking the external file.
ACTION: Check your server log for more details.
PARAMS: The number of the initialization procedure that failed.

ERROR: [DM_SESSION_E_INVALID_GROUP_NAME]

SEVERITY: ERROR
DESCRIPTION: S Invalid group name (%s).
CAUSE: The specified group is not valid in the target docbase.
ACTION: Specify a valid group name.
PARAMS: The parameter is the speified group name.

ERROR: [DM_SESSION_E_CANT_FIND_VERSION_STAMP_TABLE]

SEVERITY: ERROR
DESCRIPTION: S Cannot find version stamp table for document base %s.
CAUSE: A failure occurred during database startup that prevented the system from reading internal database tables.
ACTION: Retired message.
PARAMS: The name of the document base.

ERROR: [DM_SESSION_E_ATTEMPT_TO_SAVE_TYPE]

SEVERITY: ERROR
DESCRIPTION: Attempt to save object of type dm_type.
CAUSE: The program client attempted to save an object of type dm_type.
ACTION: Use alter type or create type instead.
PARAMS: None.

ERROR: [DM_SESSION_E_INVALID_SESSION_ID]

SEVERITY: ERROR
DESCRIPTION: S The session referred to by ID %s does not exist.
CAUSE: An invalid session ID was used. The session does not exist.
ACTION: The caller (most likely a client) was in error. Report and continue.
PARAMS:

ERROR: [DM_SESSION_E_UNEXPECTED_EXTERNAL]

SEVERITY: ERROR
DESCRIPTION: SIS The external password validation program (%s) returned an unexpected value: (%d). Error details: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_E_TICKET_EXPIRED]

SEVERITY: ERROR
DESCRIPTION: SS The %s (%s) has expired.
CAUSE: The ticket/token has expired.
ACTION: Create a new ticket/token to use.
PARAMS: The first parameter tells whether this is a ticket/token while the second one is the ticket/token.

ERROR: [DM_SESSION_E_INVALID_VENGEANCE]

SEVERITY: ERROR
DESCRIPTION: S The vengeance level %s is invalid. Valid vengeance levels are: nice, after current request, and unsafe.
CAUSE: An invalid vengeance level was given.
ACTION: The caller (most likely a client) was in error. Report and continue.
PARAMS:

ERROR: [DM_SESSION_E_LDAP_INIT]

SEVERITY: ERROR
DESCRIPTION: The initialization of the ldap library failed.
CAUSE: Unknown.
ACTION: Inform your System Administrator.
PARAMS:

ERROR: [DM_SESSION_E_LDAP_AUTH_EXPRESSION_SEARCHDN]

SEVERITY: ERROR
DESCRIPTION: S Expression is not allowed when bind type is (%s).
CAUSE: When expression is set, bind type is bind_by_dn, not bind_search_dn.
ACTION: set the bind type to bind_search_dn.
PARAMS:

ERROR: [DM_SESSION_E_DECODE_KEY_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Decoding failed while importing login ticket key from docbase (%s).
CAUSE: Running out of memory.
ACTION: Be sure the system is not overloaded.
PARAMS: the name of the docbase.

ERROR: [DM_SESSION_E_ENCRYPT_KEY_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Encryption failed while exporting login ticket key from docbase (%s).
CAUSE: Running out of memory.
ACTION: Be sure the system is not overloaded.
PARAMS: the name of the docbase.

ERROR: [DM_SESSION_E_INVALID_APPLICATION_ID]

SEVERITY: ERROR
DESCRIPTION: SS Application id (%s) does not match application access control token (%s).
CAUSE: The given application id does not match the one used in creating the access control token.
ACTION: Make sure correct application id is used.
PARAMS: The first parameter is the application id while the second one is the access control token.

ERROR: [DM_SESSION_E_LAUNCH_VALIDATION]

SEVERITY: ERROR
DESCRIPTION: SS Unable to launch the external user validation program: %s. Operating System Error: %s
CAUSE: The external program was not accessible
ACTION: Check for the existence and accesibility of the program
PARAMS:

ERROR: [DM_SESSION_E_CANT_SET_SESSION_STAMP]

SEVERITY: ERROR
DESCRIPTION: Failure to set version stamp after creating session types.
CAUSE: The program failed during database startup, because the session initialization code did not complete successfully.
ACTION: Check that the database system has been properly installed.
PARAMS: None.

ERROR: [DM_SESSION_W_MATCH_TYPE_FAILURE]

SEVERITY: WARNING
DESCRIPTION: S Match of type %s failed because type could not be found.
CAUSE: Program executed a SEARCH procedure (which searches for objects of a given type that have a set of matching attributes), passing a type name that doest not exist in the database.
ACTION: No action. Search ignored.
PARAMS: The type name.

ERROR: [DM_SESSION_W_ENUMERATE_OF_NULL]

SEVERITY: WARNING
DESCRIPTION: Attempt to enumerate objects of NULL type.
CAUSE: Program executed an ENUMERATE procedure (which enumerates objects of a given type), passing a NULL type name.
ACTION: No action. Enumerate ignored.
PARAMS: None.

ERROR: [DM_SESSION_W_FETCH_FAILED]

SEVERITY: WARNING
DESCRIPTION: SS Fetch of object with handle %s and type %s failed.
CAUSE: A fetch of an object failed. Most likely, either the type could not be found or the object did not exist.
ACTION: No action.
PARAMS: The handle of the object and the type of the object.

ERROR: [DM_SESSION_W_SAVE_OF_NONEXISTENT_OBJECT]

SEVERITY: WARNING
DESCRIPTION: S Save of object with handle %s failed because object does not exist.
CAUSE: A request was made to save an object that does not already exist in the database.
ACTION: No action. The save is ignored.
PARAMS: The handle of the object.

ERROR: [DM_SESSION_W_GENTICKET_FAIL]

SEVERITY: WARNING
DESCRIPTION: S Failed to generate login ticket for user %s.
CAUSE: Generating login ticket fails.
ACTION: Make sure unused login tickets are cleaned-up.
PARAMS: The user name and docbase base.

ERROR: [DM_SESSION_W_RESTART_AGENT_EXEC]

SEVERITY: WARNING
DESCRIPTION: The agent exec program has stopped running. It will be restarted.
CAUSE: The agent exec program has stopped running.
ACTION: Check the agent exec log file to look for error messages.
PARAMS:

ERROR: [DM_SESSION_W_LAUNCH_AGENT_EXEC]

SEVERITY: WARNING
DESCRIPTION: S Unable to launch the agent exec process due to the error: %s.
CAUSE: Server could not run the agent exec method.
ACTION: Report the error to user sysadmin.
PARAMS:

ERROR: [DM_SESSION_W_DB_PASSWORD_FILE_OWNER]

SEVERITY: WARNING
DESCRIPTION: S The database password file, (%s), is readable by other users.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_W_SAVE_COMMIT_FAILED]

SEVERITY: WARNING
DESCRIPTION: SS Save failed for object %s because transaction could not be committed.nDatabase system error message was: %s
CAUSE: A save of an object failed because the database transaction could not be successfully committed after the objects attributes were updated.
ACTION: Retry the save.
PARAMS: The handle of the object.

ERROR: [DM_SESSION_W_SAVE_OF_NULL_OBJECT]

SEVERITY: WARNING
DESCRIPTION: Save of NULL object attempted.
CAUSE: A request to save an empty object.
ACTION: No action. The save is ignored.
PARAMS: None.

ERROR: [DM_SESSION_W_LAUNCH_CHANGE_CHECK]

SEVERITY: WARNING
DESCRIPTION: S Unable to launch the change check thread. Operating system error: %s.
CAUSE: Server could not run the change check process/thread.
ACTION: Check for possible resource exhaustion or other operating system problems.
PARAMS:

ERROR: [DM_SESSION_W_AUTH_PLUGIN_DUPL_CODE]

SEVERITY: WARNING
DESCRIPTION: SS Failed to load Authentication Plugin because it attempted to register with duplicate identifier %s (%s).
CAUSE: The identifier returned by the authentication plugin is already used by another plugin.
ACTION: Make sure that each authentication plugin registers with a unique identifier.
PARAMS: The identifier and file path of the authentication plugin.

ERROR: [DM_SESSION_W_CANT_MAKE_OBJECT_MANAGER]

SEVERITY: WARNING
DESCRIPTION: SS Cannot make an object manager for user %s in document base %s.
CAUSE: A failure occurred during session creation that prevented reading the basic object tables from the database.
ACTION: Ensure that the database version is consistent with the version of the system being run. Ensure that the user is valid for the database.
PARAMS: The name of the user and the name of the document base.

ERROR: [DM_SESSION_W_CANT_RESUME_SESSION]

SEVERITY: WARNING
DESCRIPTION: SS Cannot resume session %s for user %s.
CAUSE: A request was made to resume a session that had not been previously paused.
ACTION: No action.
PARAMS: The handle of the session and the name of the user.

ERROR: [DM_SESSION_W_AGENT_EXEC_FAILURE_EXCEED]

SEVERITY: WARNING
DESCRIPTION: The failure limit of the agent exec program has exceeded. It will not be restarted again. Please correct the problem and restart the server.
CAUSE: The agent exec program fails to launch after several successive attempts.
ACTION: Report the error to user sysadmin. Please restart the server to reactive agent exec.
PARAMS:

ERROR: [DM_SESSION_W_CANT_BEGIN_TRANSACTION]

SEVERITY: WARNING
DESCRIPTION: D Cannot begin a transaction since there is an active transaction for session %s.
CAUSE: Most likely a transaction is already open. It is also possible that other problems with database will not permit the system to begin a transaction.
ACTION: close the current open transaction before beginning the next one. If a database problem has caused this problem, then solve that problem before attempting to begin another transaction.
PARAMS:

ERROR: [DM_SESSION_W_LAUNCH_DEFER_UPDATE]

SEVERITY: WARNING
DESCRIPTION: S Unable to launch process to perform deferred updates to objects due to the error: %s The updates will be performed later.
CAUSE: Unable to fork a process. May be running out of resources on the host.
ACTION: Take necessary steps to fix problems reported from OS.
PARAMS:

ERROR: [DM_SESSION_W_OBJECT_UPDATE_FAILED]

SEVERITY: WARNING
DESCRIPTION: S Save of object of type %s failed because attribute update to new values failed.
CAUSE: A request to save an object failed because the objects attributes could not be successfully updated.
ACTION: This is an internal failure and should be reported to Documentum technical support.
PARAMS: The type of the object that was attempted to be saved.

ERROR: [DM_SESSION_W_ENUMERATE_TYPE_FAILURE]

SEVERITY: WARNING
DESCRIPTION: S Enumeration of type %s failed because type could not be found.
CAUSE: Program executed an ENUMERATE procedure (which enumerates objects of a given type), passing a type name that does not exist in the database.
ACTION: No action. Enumerate ignored.
PARAMS: The name of the type that was to be enumerated.

ERROR: [DM_SESSION_W_TRANSACTION_FAILURE]

SEVERITY: WARNING
DESCRIPTION: SS Transaction commit failed for session %s database error is: %s
CAUSE: Program executed a CommitTransaction, but the transaction could not be committed. Any pending updates were rolled back.
ACTION: Retry the transaction. If the failure persists, check the error message from the database system and take whatever action it suggests.
PARAMS: The handle for the session and the internal error string from the database system.

ERROR: [DM_SESSION_W_DESTROY_ABORTED]

SEVERITY: WARNING
DESCRIPTION: S Destroy of object %s failed because transaction could not be committed.
CAUSE: Program executed an DESTROY procedure that failed because the database transaction did not successfully commit.
ACTION: The destroy had no effect retry.
PARAMS: The handle of the object that was being destroyed. Session error codes.

ERROR: [DM_SESSION_W_CHANGE_CHECK_ALIVE]

SEVERITY: WARNING
DESCRIPTION: Change check processing was not initiated. The previously launched Change Check execution is still running. Check your server log for additional messages.
CAUSE: The thread/process that was started at the previous change check time is still running
ACTION: Check for errors, such as network timeouts, in your server log
PARAMS:

ERROR: [DM_SESSION_W_LIB_LOAD]

SEVERITY: WARNING
DESCRIPTION: SS The server failed to load the shared library %s. Operating System error: %s.
CAUSE: : Cannot find the named shared library, or library corrupted.
ACTION: Copy the shared library to the $DM_HOME/bin directory.
PARAMS:

ERROR: [DM_SESSION_W_ROLLBACK_FAILURE]

SEVERITY: WARNING
DESCRIPTION: SS Transaction rollback failed for session %s database error is: %s
CAUSE: Program executed a RollbackTransaction, but the transaction could not be rolled back because of a database system error.
ACTION: Database systems rarely have rollback failures. Report the error message from the database system to your database system administrator.
PARAMS: The handle for the session and the internal error string from the database system.

ERROR: [DM_SESSION_W_SET_LDAP_OPT_PROTOCOL_VERSION_FAILED]

SEVERITY: WARNING
DESCRIPTION: Failed to set LDAP protocol version to Version-3. Proceeding with default V2 protocol version.
CAUSE: Unable to make a connection to the LDAP server using LDAP V3 protocol.
ACTION: Make sure that the remote LDAP Server is configured for LDAP V3.
PARAMS:

ERROR: [DM_SESSION_W_CANT_MAKE_TYPE_MANAGER]

SEVERITY: WARNING
DESCRIPTION: SS Cannot make a type manager for user %s in document base %s.
CAUSE: A failure occurred during session creation that prevented reading the basic type tables from the database.
ACTION: Check that the database version is consistent with the version of the system being run. Check that the user is valid for the database.
PARAMS: The name of the user.

ERROR: [DM_SESSION_W_MATCH_TYPE_NULL]

SEVERITY: WARNING
DESCRIPTION: Attempt to match objects of NULL type.
CAUSE: Program executed a SEARCH procedure (which searches for objects of a given type that have a set of matching attributes), passing a NULL type name.
ACTION: No action. Search ignored.
PARAMS: None.

ERROR: [DM_SESSION_W_ZOMBIE_HOT_SESSION_FOUND]

SEVERITY: WARNING
DESCRIPTION: L The session record for process/thread %ld was marked active, but had not been used within the server timeout interval. The session was moved to the inactive list.
CAUSE: The session was not moved from the active list.
ACTION: None needed at this point.
PARAMS:

ERROR: [DM_SESSION_W_NO_CONNECTION]

SEVERITY: WARNING
DESCRIPTION: The connection with the server has been dropped.
CAUSE: The connection with the server was dropped.
ACTION: If the retry flag is set for the session, then the operation that caused the dropped connection to be noticed will be retried if a new session can be established. Otherwise, a new session must be opened before further operations can be performed.
PARAMS: None.

ERROR: [DM_SESSION_W_DESTROY_FAILED]

SEVERITY: WARNING
DESCRIPTION: S Destroy of object %s failed.
CAUSE: Program executed an DESTROY procedure that failed the object did not exist or an internal error caused the object not to be removed from the database.
ACTION: Check that the object did exist.
PARAMS: The handle of the object that was to be destroyd.

ERROR: [DM_SESSION_W_PASSWORD_STALE]

SEVERITY: WARNING
DESCRIPTION: SS The password for user (%s) with user OS name (%s) is stale
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_W_LDAP_NOCONFIG]

SEVERITY: WARNING
DESCRIPTION: The server cannot be set up for ldap services because the ldap config object does not exist.
CAUSE: : Cannot find the ldap config object indicated by the ldap_config_id field of the server config.
ACTION: Check that the server config and ldap configuration objects were properly created. In the meantime, the server will be functional but will not support any ldap services.
PARAMS:

ERROR: [DM_SESSION_W_MATCH_ATTRIBUTE_ERROR]

SEVERITY: WARNING
DESCRIPTION: IS Match failed because attribute %d in type %s is invalid.
CAUSE: Program executed a SEARCH procedure (which searches for objects of a given type that have a set of matching attributes), passing a set of attribute values to match that have types inconsistent with the values of the attributes in the database.
ACTION: No action. Search ignored.
PARAMS: The number and type of the mismatched attributes.

ERROR: [DM_SESSION_W_CANT_SET_CONVERSION_IDENTIFIER]

SEVERITY: WARNING
DESCRIPTION: S Failed to set the vtsamp identifier for docbase %s.
CAUSE: Tried to create set a vstamp for ACL converson, but failed.
ACTION: Need to set the identifier in order to do ACL conversion.
PARAMS:

ERROR: [DM_SESSION_W_EXEC_POOL_FULL]

SEVERITY: WARNING
DESCRIPTION: Unable to launch process to perform deferred updates to objects, because the execution context pool is currently full. The updates will be performed later.
CAUSE: Fail to lauch process because of full execution context pool.
ACTION: If thiss been happening a lot, increase concurrent_session in the server.ini.
PARAMS:

ERROR: [DM_SESSION_T_TYPE_REFRESH]

SEVERITY: TRACE
DESCRIPTION: II Checking for type changes (inline) server count=%d db count=%d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_T_TYPE_DETACH]

SEVERITY: TRACE
DESCRIPTION: SS Detaching type from cache ID=%s, name=%s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_T_TYPE_DBLOAD]

SEVERITY: TRACE
DESCRIPTION: SSI Loaded type from database ID=%s, name=%s type_cache_vstamp=%d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_T_TYPE_DROP]

SEVERITY: TRACE
DESCRIPTION: SS Dropping type from cache ID=%s, name=%s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_T_TYPE_DBLOAD_ATTEMPT]

SEVERITY: TRACE
DESCRIPTION: S Attempting type load from database name=%s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_T_TYPE_REFRESH_CHANGECHECK]

SEVERITY: TRACE
DESCRIPTION: II Checking for changes (global) server count=%d db count=%d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_I_SESSION_PAUSE]

SEVERITY: INFORMATION
DESCRIPTION: S Session %s paused.
CAUSE: This is an informational message generated at session pause.
ACTION: None. Informational message only.
PARAMS: The id of the session and the current time

ERROR: [DM_SESSION_I_CURRENT_DYNAMIC_GROUP_ENTRIES]

SEVERITY: INFORMATION
DESCRIPTION: SSS %s dynamic groups for session [%s] : [%s]
CAUSE: this is an internal trace message.
ACTION: None.
PARAMS:

ERROR: [DM_SESSION_I_AUTH_PLUGIN_LOAD_INIT]

SEVERITY: INFORMATION
DESCRIPTION: SSS Authentication plugin ( %s ) was %s. %s
CAUSE: The specified Authentication Plugin was loaded but not initialized because of the initialization file(s) are corrupt or initialization file(s) are not present at specified location.
ACTION: Find the corrupt initialization filename in the authentication plugin log and replace it with proper one.
PARAMS:

ERROR: [DM_SESSION_I_TRANSACTION_ABORT]

SEVERITY: INFORMATION
DESCRIPTION: Transaction aborted because of client timeout
CAUSE: The transaction begun by the client was aborted because of a timeout.
ACTION: None.
PARAMS:

ERROR: [DM_SESSION_I_PUSHING_OBJ_BY_CHUNKS]

SEVERITY: INFORMATION
DESCRIPTION: SD Operation %s is pushing the object %s by chunks now.
CAUSE: This is an informational message generated if operation logging has been turned on
ACTION: None. Informational message only.
PARAMS: The name of the operation which is pusing the object by chunks.

ERROR: [DM_SESSION_I_OPERATION_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: S Operation %s started.
CAUSE: This is an informational message generated if operation logging has been turned on
ACTION: None. Informational message only.
PARAMS: The name of the operation completed

ERROR: [DM_SESSION_I_SESSION_START]

SEVERITY: INFORMATION
DESCRIPTION: SS Session %s started for user %s.
CAUSE: This is an informational message generated at session startup.
ACTION: None. Informational message only.
PARAMS: The id of the session and the client node name of the user

ERROR: [DM_SESSION_I_RETRYING_DATABASE_CONNECTION]

SEVERITY: INFORMATION
DESCRIPTION: SII The following error was encountered trying to get a database connection: %s nThe server will retry %d more time(s) (every %d seconds).
CAUSE: This is an informational message generated if rdbms_connect_retry_timeout is > 0 and a connection attempt failed.
ACTION: None. Informational message only.
PARAMS:

ERROR: [DM_SESSION_I_GENERIC_TRACE3]

SEVERITY: INFORMATION
DESCRIPTION: SSS %s %s %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_I_KILL_SESSION]

SEVERITY: INFORMATION
DESCRIPTION: SS User %s is attempting to kill session %s.
CAUSE: There was an attempt to kill the session.
ACTION: None. Informational message only.
PARAMS:

ERROR: [DM_SESSION_I_OPERATION_ARGUMENTS]

SEVERITY: INFORMATION
DESCRIPTION: S %s
CAUSE: This is an informational message generated if operation logging has been turned on
ACTION: None. Informational message only.
PARAMS: The arguments for the current operation.

ERROR: [DM_SESSION_I_DEADLOCK_INFO]

SEVERITY: INFORMATION
DESCRIPTION: A database deadlock occurred.
CAUSE: A database deadlock occurred in the operation.
ACTION: No action is needed if the deadlock occurs inside a docserver method because DMCL will retry the same query automatically. However, if the deadlock occurs within a user transaction, i.e., started with a begintran, then user has to rerun the transaction because all the DBMS operation so far have been rolled back after it is chosen as a deadlock victim.
PARAMS:

ERROR: [DM_SESSION_I_DEADLOCK_RETRY]

SEVERITY: INFORMATION
DESCRIPTION: Retrying server operation following a DBMS Deadlock Error. Deadlock errors returned from the server are retried by the DMCL when the operation is not part of a larger multi-operation transaction. The hope is that the second attempt at the operation will succeed. When deadlock retry is successfull, the operation will return ok but will have left deadlock error messages in the error stream. This informational message indicates that those messages do not indicate a true failure.
CAUSE: A database deadlock occurred in the operation.
ACTION: If the retry succeeds, no action is necessary.
PARAMS:

ERROR: [DM_SESSION_I_INIT_BEGIN]

SEVERITY: INFORMATION
DESCRIPTION: S Initialize %s.
CAUSE: This is an informational message generated when the document base is initializing each type.
ACTION: None.
PARAMS:

ERROR: [DM_SESSION_I_ASSUME_USER]

SEVERITY: INFORMATION
DESCRIPTION: SS Session %s is owned by user %s now.
CAUSE: Informational message when a session assumed by a different user.
ACTION: None. Informational only.
PARAMS: session id and user name

ERROR: [DM_SESSION_I_FIX_OBJ_INCONSISTENCIES_TRACE]

SEVERITY: INFORMATION
DESCRIPTION: S %s
CAUSE: Informational message for the fix object table inconsistencies procedure.
ACTION: None. Informational message only.
PARAMS: The trace statement generated by the server.

ERROR: [DM_SESSION_I_AUTH_PLUGIN_LOADED]

SEVERITY: INFORMATION
DESCRIPTION: SS Loaded Authentication Plugin with code %s (%s).
CAUSE: Informational message when an authentication plugin is loaded.
ACTION: None. Informational only.
PARAMS: The code and file path of the Authentication Plugin.

ERROR: [DM_SESSION_I_INIT_END]

SEVERITY: INFORMATION
DESCRIPTION: S Initialized %s.
CAUSE: This is an informational message generated when the document base is initializing each type.
ACTION: None.
PARAMS:

ERROR: [DM_SESSION_I_OPERATION_ENDED]

SEVERITY: INFORMATION
DESCRIPTION: S Operation %s completed.
CAUSE: This is an informational message generated if operation logging has been turned on
ACTION: None. Informational message only.
PARAMS: The name of the operation completed.

ERROR: [DM_SESSION_I_FIRST_ATTEMPT_FAIL]

SEVERITY: INFORMATION
DESCRIPTION: SS Attempt to make a %s connection failed, trying to create a %s connection instead.
CAUSE: Informational message displayed if the first attempt fails when connect command argument secure_flag is specified as either try_secure_first or try_native_first.
ACTION: None. Informational only.
PARAMS: Two strings: secure and native

ERROR: [DM_SESSION_I_OPERATION_RESULTS]

SEVERITY: INFORMATION
DESCRIPTION: S %s
CAUSE: This is an informational message generated if operation logging has been turned on
ACTION: None. Informational message only.
PARAMS: The result of the current operation.

ERROR: [DM_SESSION_I_GENERIC_TRACE1]

SEVERITY: INFORMATION
DESCRIPTION: S %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SESSION_I_CONNECTED_TO_DATABASE]

SEVERITY: INFORMATION
DESCRIPTION: SS Successfully connected to database %s on %s
CAUSE: Informational message when a session establishes a database connection.
ACTION: None. Informational only.
PARAMS: Parameter 1 is the database name. Parameter 2 is the name of the server or machine on which the database resides.

ERROR: [DM_SESSION_I_SESSION_QUIT]

SEVERITY: INFORMATION
DESCRIPTION: S Session %s quit.
CAUSE: This is an informational message generated at session close.
ACTION: None. Informational message only.
PARAMS: The id of the session and the current time

ERROR: [DM_SESSION_I_INITIALIZE_DB]

SEVERITY: INFORMATION
DESCRIPTION: S Initializing document base %s
CAUSE: This is an informational message generated when the document base is first initialized
ACTION: None: Informational message only.
PARAMS: The name of the document base.

ERROR: [DM_SESSION_I_SESSION_AUTHENTICATED]

SEVERITY: INFORMATION
DESCRIPTION: SS Session %s started and authenticated for user (%s).
CAUSE: This is an informational message generated at session startup.
ACTION: None. Informational message only.
PARAMS: The id of the session and the client node name of the user

ERROR: [DM_SESSION_I_TRACE_ENABLED]

SEVERITY: INFORMATION
DESCRIPTION: IISSI Trace enabled for client process %d (thread %d) on machine %s. Trace facility is %s, level %d.
CAUSE: Informational message when a session enables tracing at level >= 10.
ACTION: None. Informational only.
PARAMS: Client session info (process_id, thread_id, machine_name) The trace facility

ERROR: [DM_SESSION_I_NEW_CONN]

SEVERITY: INFORMATION
DESCRIPTION: S Established new connection.nNew session identifier is %s
CAUSE: The connection with the server was dropped and has been reestablished.
ACTION: None. The new connection is now ready for use.
PARAMS: The handle of the new session.

ERROR: [DM_SESSION_I_DYNAMIC_ROLE_OPERATION]

SEVERITY: INFORMATION
DESCRIPTION: SSSSSS Session %s %s dynamic role %s. Mode is %s. RPC name is %s, result of the operation is %s
CAUSE: this is an internal trace message.
ACTION: none.
PARAMS:

ERROR: [DM_SESSION_I_GENERIC_TRACE2]

SEVERITY: INFORMATION
DESCRIPTION: SS %s %s
CAUSE:
ACTION:
PARAMS:

nahoru

DM_SIGN

ERROR: [DM_SIGN_E_MUST_MATCH_LOGIN_NAME]

SEVERITY: ERROR
DESCRIPTION: SS The login name (%s) passed in does not match with users user_login_name (%s).
CAUSE: The passed in login name must match the name given in user_login_name attribute of the current user.
ACTION: Please supply the correct login name of the current user. $Id: dmevent.e,v 5.8 2003/01/20 19:45:19 ghwang Exp $ dmInbox class errors
PARAMS:

ERROR: [DM_SIGN_E_INVALID_USER]

SEVERITY: ERROR
DESCRIPTION: S User (%s), has failed to pass the signature validation check.
CAUSE: The program failed to establish a session for the user.
ACTION: Check to see that the user is valid to the operating system. Check to see that the passwords supplied are correct.
PARAMS:

ERROR: [DM_SIGN_E_ACCOUNT_LOCKED]

SEVERITY: ERROR
DESCRIPTION: S The Operating System account for user (%s) has been locked.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SIGN_E_NON_EXIST_OBJ]

SEVERITY: ERROR
DESCRIPTION: D The object identified by %s does not exist.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SIGN_E_ACCOUNT_EXPIRED]

SEVERITY: ERROR
DESCRIPTION: S The Operating System account for user (%s) has expired.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SIGN_E_ACCOUNT_DROPPED]

SEVERITY: ERROR
DESCRIPTION: S The Operating System account for user (%s) has been dropped.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SIGN_E_PASSWORD_CHECK_GETPWNAM]

SEVERITY: ERROR
DESCRIPTION: SSSD Operating System Failure during user %s validation. (User OS name = %s, Domain = %s, and session id = %s)
CAUSE: The program failed during electronic signature validation, checking the external file.
ACTION: Check your server log for more details.
PARAMS:

ERROR: [DM_SIGN_E_UNEXPECTED_CHK_RES]

SEVERITY: ERROR
DESCRIPTION: SI The return value from the external signature validation program (%s) returned an unexpected value: (%d)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SIGN_E_PASSWORD_EXPIRED]

SEVERITY: ERROR
DESCRIPTION: S The Operating System password for user (%s) has expired.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SIGN_E_DOMAIN_IS_NOT_ACCEPTABLE]

SEVERITY: ERROR
DESCRIPTION: S The passed in domain %s is not an acceptable domain to perform sign-off.
CAUSE: The user objects user_login_domain is not set up to accept this domain.
ACTION: Please see your system administrator to correct it.
PARAMS:

ERROR: [DM_SIGN_E_CHK_PASS_OS_ERROR]

SEVERITY: ERROR
DESCRIPTION: There was an unexpected error during validation of your electronic signature. Please see your system administrator or check the server log
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SIGN_E_VERSION_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: DL Signoff on the document (%s) failed because of version mismatch: old version was %d.
CAUSE: Signoff failed because the version stamp in the object was inconsistent with the version stamp currently stored in the database.
ACTION: Refetch the object, issue signoff again.
PARAMS: D – Object ID. L – Version stamp.

ERROR: [DM_SIGN_E_MUST_MATCH_OS_NAME_ATTR]

SEVERITY: ERROR
DESCRIPTION: SS The OS name %s passed in is not the current users OS name %s.
CAUSE: The passed in OS name must match the name given in user_os_name attribute of the current user.
ACTION: Please supply the correct OS name of the current user.
PARAMS:

ERROR: [DM_SIGN_W_PASSWORD_STALE]

SEVERITY: WARNING
DESCRIPTION: S The password for user (%s) is stale —————————————————————–
CAUSE:
ACTION:
PARAMS:

nahoru

DM_STORAGE

ERROR: [DM_STORAGE_F_UNABLE_TO_COMPUTE_DATE_EPOCH]

SEVERITY: FATAL
DESCRIPTION: S Unable to get epoch for the date %s
CAUSE: Unable to compute the epoch (seconds elapsed since 1/1/1970) for the date specified. This would happen if the date is less than 1/1/1970 or greater than 1/1/2038
ACTION: ??
PARAMS:

ERROR: [DM_STORAGE_F_VERSION_STAMPING]

SEVERITY: FATAL
DESCRIPTION: I Failed to version stamp dm_store object to %d.
CAUSE: Type conversion failed.
ACTION: Report the problem.
PARAMS:

ERROR: [DM_STORAGE_F_NO_CONTENT_STORAGE_OR_ARCHIVE_SERVICE_LICENSE]

SEVERITY: FATAL
DESCRIPTION: A Content Storage or Archive Services license is required to configure a storage object for compression and content duplication prevention
CAUSE: User specified a non-zero value for compression_mode or content_dupl_pref attribute while creating a storage object, but there is no valid CSS or AS license configured for the respository.
ACTION: Contact EMC Technical support to purchase a CSS or AS license.
PARAMS:

ERROR: [DM_STORAGE_F_MEMORY_ALLOCATION_FAILED]

SEVERITY: FATAL
DESCRIPTION: S Unable to allocate memory for %s object
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_F_NO_CONTENT_STORAGE_SERVICE_LICENSE_FOR_PM]

SEVERITY: FATAL
DESCRIPTION: A Content Storage Services license is required set the PARALLEL_DEGREE parameter for the CONTENT_MIGRATION method to a value greater than zero.
CAUSE: User attempted to do parallel migration using the CONTENT_MIGRATION method, but there is no valid CSS license configured for the respository.
ACTION: Contact EMC Technical support to purchase a CSS license.
PARAMS:

ERROR: [DM_STORAGE_F_NO_CONTENT_STORAGE_OR_HIGH_VOLUME_LICENSE]

SEVERITY: FATAL
DESCRIPTION: A Content Storage or High-Volume Server license is required to configure a storage object for compression and content duplication prevention
CAUSE: User specified a non-zero value for compression_mode or content_dupl_pref attribute while creating a storage object, but there is no valid CSS or HVS license configured for the respository.
ACTION: Contact EMC Technical support to purchase a CSS or HVS license.
PARAMS:

ERROR: [DM_STORAGE_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_store to version %d.
CAUSE: Type conversion failed.
ACTION: Report the problem.
PARAMS:

ERROR: [DM_STORAGE_F_NO_CONTENT_STORAGE_SERVICE_LICENSE]

SEVERITY: FATAL
DESCRIPTION: A Content Storage Services license is required to configure a storage object for content hash generation
CAUSE: User specified a non-zero value for content_hash_mode attribute while creating a storage object, but there is no valid CSS license configured for the respository.
ACTION: Contact EMC Technical support to purchase a CSS license.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_SETCONTENTATTRS_NOT_CALLED]

SEVERITY: ERROR
DESCRIPTION: S setcontentattrs API must be called prior to saving the object. You must specify a DATE value for %s using setcontentattrs API first.
CAUSE: This error occurs when user executes a save command for an object whose content is configured to be saved in a dm_ca_store storage and the underlying storage object has been configured to accept a retention value.
ACTION: Call setcontentattrs API with a DATE value for the specified name and then call save API.
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_PLUGIN]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid shared library
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_BAD_DEFAULT_STORE]

SEVERITY: ERROR
DESCRIPTION: SS The default store (%s) for type %s does not exist.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_REPLICA_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Error fetching replica record: %s.
CAUSE: Replica record with specified id could not be fetched from database.
ACTION: Check error log for other messages that should give more detailed information on the error.
PARAMS: %1 – Object id of dmi_replica_record object

ERROR: [DM_STORAGE_E_INVALID_LOCATION_NAME]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid location object name
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NO_ROOT]

SEVERITY: ERROR
DESCRIPTION: Attempt to create filestore without specifying root location
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_MOUNT_NOT_EXECUTED]

SEVERITY: ERROR
DESCRIPTION: S You must execute mount for %s before retrieving content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_PLATFORM_INDICATOR]

SEVERITY: ERROR
DESCRIPTION: I Invalid value for a_platform attribute : %d. Should be between 1 and 5
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_GET_REPLICA_FAILED]

SEVERITY: ERROR
DESCRIPTION: D Failed to get the replica record of content %s during computing its other file size in distributed store.
CAUSE: : Getting replica record of content failed. -1 will be returned as computed other file size.
ACTION: : Check error log to figure out the failure reason of getting replica record.
PARAMS:

ERROR: [DM_STORAGE_E_CURSOR_EXEC_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Database error occured while executing a cursor. Error from database was %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_UNABLE_TO_OBTAIN_CONTENT_ADDRESS]

SEVERITY: ERROR
DESCRIPTION: S Unable to obtain content address for content object %s
CAUSE: This error occurs during save of an object with content stored in a dm_ca_store type object. The generated content address token could not be obtained by the client from server for the pushed and saved content.
ACTION: This error probably occured because of a previous error from dm_ca_store Plugin library. Check other messages. If there is no other error message, re-issue the save command on the parent object.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_UNABLE_TO_VERIFY_TRIGGER]

SEVERITY: ERROR
DESCRIPTION: SIS Unable to verify if the clip %s is triggered or not. Error Code : %d, Error message : %s
CAUSE: Error occurred while trying to see if the clip was triggered with conditional retainer or not.
ACTION: Look at the server log for details on the error message.
PARAMS:

ERROR: [DM_STORAGE_E_TAR_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SI Tar step failed during %s operation — OS error was %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_SECURITY_PRIVATE]

SEVERITY: ERROR
DESCRIPTION: SS Unable to change file system security on file %s. Operating System error: %s
CAUSE: Operating system unable to complete requested operation
ACTION: Check the permissions on the specified file. Check the effective user of the running server process.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_SETCONTENTATTRS_FAILED]

SEVERITY: ERROR
DESCRIPTION: Invalid storage to process content attributes
CAUSE: This error occurs when client (DMCL) finds that the storage for an object is invalid. This can occur when an application destroys a CA store object and recreates one with the same name and uses the newly created CA store object to store content of an object.
ACTION: Shutdown and restart the server and the client application.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_FEATURE_NOT_ENABLED]

SEVERITY: ERROR
DESCRIPTION: Content Addressable Storage Services feature is not enabled for the server installation. Contact Documentum Technical Support.
CAUSE: User attempted to create a CA store object in a server installation for which Content addressable Storage services feature is not enabled.
ACTION: Contact Documentum Technical Support to know how to enable the feature.
PARAMS:

ERROR: [DM_STORAGE_E_CANT_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS Cant change %s attribute for storage object %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CASTORE_INVALID_ATTR_VALUE]

SEVERITY: ERROR
DESCRIPTION: SSS %s is not a valid value for %s as its a value for %s attribute
CAUSE: Value specified for a_retention_attr_name is also specified for a_content_attr_name or vice versa. Value for a_retention_attr_name cannot appear in the list of values for a_content_attr_name.
ACTION: Either remove the value from the list of values for a_content_attr_name or specify a different value for a_retention_attr_name
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_NO_VALUE_FOR_ATTR]

SEVERITY: ERROR
DESCRIPTION: S Value not specified for %s attribute.
CAUSE: This error appears when no value was specified for an attribute for which a value is required, while creating a dm_ca_store type object.
ACTION: Specify an appropriate value for the specified attribute.
PARAMS:

ERROR: [DM_STORAGE_E_EXEC_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Command execution failure: %s. os_error: %s.
CAUSE: Unable to execute the command successfully
ACTION: See your system administrator.
PARAMS:

ERROR: [DM_STORAGE_E_NO_FULLTEXT_PARENT]

SEVERITY: ERROR
DESCRIPTION: SS Cant mark content %s for indexing, because parent %s is not an index_parent
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_RESET_FILE]

SEVERITY: ERROR
DESCRIPTION: SS An unexpected failure occurred while attempting to set file security on file %s. Operating System error: %s
CAUSE: Operating system unable to complete requested operation
ACTION: Check the permissions on the specified file. Check the effective user of the running server process.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_EBR_NOT_ENABLED]

SEVERITY: ERROR
DESCRIPTION: S Unable to enable EBR for the clip, Error : %s
CAUSE: Error occurred while trying to enable the clip for Event Based Retention.
ACTION: See the server log for the detail of the error.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_CALLBACK_INVALID_POSITION]

SEVERITY: ERROR
DESCRIPTION: S Incorrect argument value for position, for attribute %s
CAUSE: A dm_ca_store plugin library called the server callback function with an incorrect value for postion argument.
ACTION: While calling the callback to obtain a value for a single attribute the position argument value must be 0 and to obtain a value for repeating attribute, the position should be 0 or more.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_DELETE_NOT_ALLOWED_BY_STORAGE]

SEVERITY: ERROR
DESCRIPTION: SSS Content object %s cannot be destroyed because storage %s does not allow deletes. Content Address is %s
CAUSE: This error occurs when running the DESTROY_CONTENT apply method for a content object whose content is in a CA store and the underlying storage system does not allow delete operation.
ACTION: There is no action required. Content object cannot be destroyed if the underlying storage does not allow deletion of content.
PARAMS:

ERROR: [DM_STORAGE_E_SIZE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SS Files sizes disagree when doing import — expected %s bytes, but file had %s bytes
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CONTENT_ACCESSOR_MISSING]

SEVERITY: ERROR
DESCRIPTION: S No Accessor defined for Store %s.
CAUSE: There is no accessor defined for the store.
ACTION: Check the setting of native_access and java_access on the store. To use the ACS content accessor the value of native_access must be NONE and java_access set to a java module providing direct access to the store.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_CONTENT_ADDRESS_SIZE_EXCEEDS_MAXIMUM]

SEVERITY: ERROR
DESCRIPTION: SII dm_casplugin_write_close() method in plugin %s returned -1 because it requires %d bytes for content address. The maximum is %d.
CAUSE: dm_casplugin_write_close() method returned -1 to Content Server indicating that size of the buffer passed to that function is not enough to return the content address.
ACTION: The maximum size of the content address that could be returned by a dm_ca_store Plugin is 2000 bytes. The plugin implementation should not exceed that limit. Address the problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_CLIP_DELETE_NOT_ALLOWED_AS_UNDER_EBR]

SEVERITY: ERROR
DESCRIPTION: S The clip %s is under Event Based Retention and cannot be deleted.
CAUSE: Delete operation is not allowed when the clip is under Event Based Retention.
ACTION: Not Supported.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_DUMP_WITH_CONTENT_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: Dump with content is not supported for objects using dm_ca_store type object for storing content.
CAUSE: dump with content is not supported for objects that use a storage area of dm_ca_store type.
ACTION: Either perform a dump without content or exclude objects that use dm_ca_store storage from the dump.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PUSH_CONTENT_ATTRS_FAILED]

SEVERITY: ERROR
DESCRIPTION: S PUSH_CONTENT_ATTRS failed because %s
CAUSE: An error occured while executing the PUSH_CONTENT_ATTRS apply method.
ACTION: Incorrect/invalid arguments specified for the apply method. see the second part of the error message for more information.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_WRITE_ERROR]

SEVERITY: ERROR
DESCRIPTION: SII dm_casplugin_write function in plugin %s returned incorrect number of bytes written. Expected: %d, Returned: %d
CAUSE: dm_casplugin_write() method failed to write all the data. The function is expected to return the number of bytes written and the value returned by the function is not equal to the size of data to be written supplied by Content Server.
ACTION: This is a plugin specific error. Check other messages and address the problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: SS Cannot destroy storage object %s because %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_UNABLE_TO_PROCESS_RH]

SEVERITY: ERROR
DESCRIPTION: S %s.
CAUSE: : Error occured while try to propagating retention holds to CA Store.
ACTION: : Error is plugin specific, Address problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_INVALID_CONTENT_ADDRESS]

SEVERITY: ERROR
DESCRIPTION: Content address is either empty or NULL
CAUSE: This error occurs when Content Server attempts to read content in a dm_ca_store and the specified content address is either empty or NULL. This can happen if the content address stored in the dmr_content object is modified directly in the database or if the content object was created using a 4.2.x client (dmcl).
ACTION: Verify that the i_contents attribute of the content object for the sysobject for which getfile or getcontent was executed. If you had created the sysobject with 4.x dmcl, content address is lost and the object is unusable.
PARAMS:

ERROR: [DM_STORAGE_E_NO_TEMP_LOCATION]

SEVERITY: ERROR
DESCRIPTION: No temp location specified in server config
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_SECURITY_PUBLIC]

SEVERITY: ERROR
DESCRIPTION: SS Unable to change file system security on file %s. Operating System error: %s
CAUSE: Operating system unable to complete requested operation
ACTION: Check the permissions on the specified file. Check the effective user of the running server process.
PARAMS:

ERROR: [DM_STORAGE_E_CANT_INITIALIZE_LOCALAREA]

SEVERITY: ERROR
DESCRIPTION: Unable to initialize localarea for plugin content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_ERROR_DURING_WRITE]

SEVERITY: ERROR
DESCRIPTION: S Error while attempting to write content to dm_ca_store object : %s
CAUSE: A transient error has occured while attempting to save content in a dm_ca_store storage.
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CHANGE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s is not allowed to be changed after the storage object is created.
CAUSE: User tried to change some attribute (e.g. media_type) after the storage object is created.
ACTION: Due to security reason, some attribute like media_type is not allowed to be changed after the storage object is created.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_STORE_MISSING_RETENTION_FIELD]

SEVERITY: ERROR
DESCRIPTION: S Field value (%s) specified for a_retention_attr_name is missing in a_content_attr_name
CAUSE: While creating a dm_ca_store object, value specified for a_retention _attr_name was not specified as one of the values for a_content_attr_name repeating attribute.
ACTION: Specify the a_retention_attr_name value as one of the values for a_content_attr_name attribute.
PARAMS:

ERROR: [DM_STORAGE_E_COMPONENT_CHANGE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: SS The attribute %s is not allowed to be changed on a component store %s.
CAUSE: The user has attempted to change an attribute on a component store which must be kept synchronized with the corresponding attribute on the distributed store.
ACTION: The store has to be removed from the distributed store before the attribute can be changed.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_DELETE_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SSISS An error occured while attempting to destroy content through plugin %s, for storage %s: Error Code: %d. Error Message: %s. Content Address is %s.
CAUSE: An error occured while destroying content stored in a CAS Store. The dm_casplugin_delete() plugin library returned an error code.
ACTION: Check the content retention settings at the storage level. Check connectivity errors. Take action based on the error code in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_READONLY]

SEVERITY: ERROR
DESCRIPTION: S Could not write to storage object %s. Storage is marked Read-Only
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_LAUNCH_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to launch the command: %s. os_error: %s.
CAUSE: Unable to lauch command successfully.
ACTION: You may run out of processes or see your system administrator.
PARAMS:

ERROR: [DM_STORAGE_E_FORCE_DELETE_NOT_SUPER_USER]

SEVERITY: ERROR
DESCRIPTION: You must be a super user or a retention manager to perform force delete operation
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_ENABLE_EBR_WITH_PERIOD_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Unable to save teh subcontent object with address %s
CAUSE: Error in saving the subcontent object to the database after the clip was successfully enabled for EBR.
ACTION: Look for database errors in the server log and take appropiate action.
PARAMS:

ERROR: [DM_STORAGE_E_INSUFFICIENT_BUFFER_SIZE]

SEVERITY: ERROR
DESCRIPTION: II Turbo content retrieval requires a minimum buffer size of %d. Supplied buffer size is %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_STORE_TYPE_FOR_COMPRESSION]

SEVERITY: ERROR
DESCRIPTION: compression_mode can be set only for dm_filestore and dm_ca_store storage types.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_OFFLINE]

SEVERITY: ERROR
DESCRIPTION: S Could not read from storage object %s. Storage is offline
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_BLOB_SAVE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Attempt to save content in blob store %s failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_REPLICATE_BAD_TYPE]

SEVERITY: ERROR
DESCRIPTION: S The type specified for replication (%s) is not a sysobject subtype
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_BLOB_INDEX_CREATE]

SEVERITY: ERROR
DESCRIPTION: SS Could not create the index for blob store %s. %s.
CAUSE: An error occurred during the creation of a blobstore. The error occurred attempting to create an index on the blobstore table. When the user creates a blobstore storage area, an RDBMS table is created to hold the content data. The table is named the same as the storage area and an index is created (_i) on the ticket column. The error occurred trying to create this index.
ACTION: Check the error log for other errors. Check the RDBMS error message included with this message. Check for available space in the RDBMS. ARGUMENTS: %s – the name of the storage area %s – the RDBMS error message
PARAMS:

ERROR: [DM_STORAGE_E_FEATURE_NOT_SUPPORTED_FOR_STORAGE_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS The %s feature is not supported for %s storage type
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_REPLICA_UPDATE]

SEVERITY: ERROR
DESCRIPTION: D Error updating replica record: %s.
CAUSE: Replica record with specified id could not be updated in database.
ACTION: Check error log for other messages that should give more detailed information on the error.
PARAMS: %1 – Object id of dmi_replica_record object

ERROR: [DM_STORAGE_E_NOT_ONLINE]

SEVERITY: ERROR
DESCRIPTION: S Could not update storage object %s. Storage is not online
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_FAR_STORE_WRITE]

SEVERITY: ERROR
DESCRIPTION: S Cannot write directly to far store %s. This storage area is not accessible by the current server.
CAUSE: An validation check on a referenced storage area showed that the location is not currently accessible by the server. This could be due to the disk being temporarily unmounted or could be because the storage area is remote to the current documentum server.
ACTION: Check the error log for other errors. Check whether the objects and storage areas referenced should be accessible by your current site. You may need to issue the requested operation on a different server where the storage area is not listed as a Far Store. ARGUMENTS: %s – the name of the storage area
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_CLIP_CLOSE]

SEVERITY: ERROR
DESCRIPTION: SIS Error during closing the clip %s, Error code %d, Error message %s
CAUSE: Error occurred becuase clip could not be closed.
ACTION: Look at the server log for appropiate error message.
PARAMS:

ERROR: [DM_STORAGE_E_EXTERNAL_STORE_OTHERFILE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: Resource fork files cannot be saved in an External Store
CAUSE: This error occurs while attempting to save the mac resource fork file into an External Storage.
ACTION: None. External Store cannot be used to save content that have mac resource fork files associated with it.
PARAMS:

ERROR: [DM_STORAGE_E_LINK_LOCATION_UNDEFINED]

SEVERITY: ERROR
DESCRIPTION: S Link location name %s is not location object name
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CASTORE_UNABLE_TO_UPDATE_VERSION_STAMP]

SEVERITY: ERROR
DESCRIPTION: I Unable to update the version stamp of ca_store_version to %d
CAUSE: A database error occured while attempting to update the version stamp of CA store type.
ACTION: See the action for the accompanying database errors.
PARAMS:

ERROR: [DM_STORAGE_E_INCORRECT_PLUGIN_VERSION]

SEVERITY: ERROR
DESCRIPTION: IIS Plugin protocol version %d.%d is not supported. Plugin path :%s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_WRITE]

SEVERITY: ERROR
DESCRIPTION: SSI Plugin ID: %s returned error: %s, error code:%d
CAUSE: The dm_ca_store store plugin returned an error while performing a write content operation.
ACTION: the error code returned is plugin specific. Address the problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_CANT_FETCH_PLUGIN]

SEVERITY: ERROR
DESCRIPTION: SS %s failed for plugin object %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_MISSING_RETENTION_FIELD_VALUE]

SEVERITY: ERROR
DESCRIPTION: S No value was specified for attribute %s. Value for this attribute is required because its value defines the retention period of the content
CAUSE: While saving an object, user did not specify value for the attribute as indicated in the error message. Value for the indicated attribute is required because its value is used by the dm_ca_store plugin to set the retention period on the content.
ACTION: Specify a value for the indicated attribute and reattempt save.
PARAMS:

ERROR: [DM_STORAGE_E_DIGITAL_SHREDDING_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SSS The file %s in store %s could not be shredded. OS/Other error: %s.
CAUSE: This error may occur if the file does not exist, the file format is not supported, the file cannot be opened for write access or there was an error writing to the file.
ACTION: If the file exists it should be shredded and removed by an alternate mechanism.
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_VALUE]

SEVERITY: ERROR
DESCRIPTION: IS Invalid value (%d) specified for %s attribute
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_CALLBACK_ATTR_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S Requested attribute %s not found in the dm_ca_store type.
CAUSE: A dm_ca_store plugin library called the server callback function to obtain an storage object attribute value, for an attribute not found for the dm_ca_store type.
ACTION: Check if the attribute has been spelt right in the plugin while calling the callback function. Attribute names are case sensitive. Refer to the Object Reference manual for dm_store and dm_ca_store attribute information.
PARAMS:

ERROR: [DM_STORAGE_E_COULD_NOT_OPEN_FILE_FOR_WRITE]

SEVERITY: ERROR
DESCRIPTION: S The file- %s could not be opened for writing
CAUSE: The directory to write the file probably does not exist.
ACTION: Make sure that the directory to write the file exists.
PARAMS:

ERROR: [DM_STORAGE_E_NOT_A_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: SSS argument (%s) specified for mount for (%s) is not a valid directory on %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_MOUNT_FAILED]

SEVERITY: ERROR
DESCRIPTION: SSI mount failed for %s because %s %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NO_PLUGIN_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S There is no content for plugin object %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_MOUNT_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S mount cannot be executed for %s because it is not a dm_extern_file object
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_GFSMP_OTHER_TICKET_PATH]

SEVERITY: ERROR
DESCRIPTION: S Cannot allocate other ticket and path for filestore %s.
CAUSE: The system was unable to create a other ticket and path for the specified filestore.
ACTION: Restart your server
PARAMS:

ERROR: [DM_STORAGE_E_LINK_SAVE_FAIL]

SEVERITY: ERROR
DESCRIPTION: IS Cant save link record while fetching ticket %d from storage object %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NOT_A_FILE]

SEVERITY: ERROR
DESCRIPTION: S File %s could not be opened for reading
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CANT_GET_CONTENT_TOKEN]

SEVERITY: ERROR
DESCRIPTION: S Could not obtain content token for %s object
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_ACS_INTERNAL_ERROR]

SEVERITY: ERROR
DESCRIPTION: S ACS Content Transfer Connector failed %s.
CAUSE: This is an internal error.
ACTION: Attempt to reproduce the problem with acs_connector_trace tracing enabled, and provide the repository log file to EMC Technical support.
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_URL]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid URL
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_COPY_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Copy of file %s to file %s failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CANT_OPEN_PLUGIN]

SEVERITY: ERROR
DESCRIPTION: SSI Could not open shared library %s for external store object %s, error : %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NO_PROTOCOL]

SEVERITY: ERROR
DESCRIPTION: Attempt to store other file using invalid protocol specification
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_UNABLE_TO_GET_EBR]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: Error occurred while trying to get the retention period set by conditional retainer.
ACTION: See the server log for further details of the operation.
PARAMS:

ERROR: [DM_STORAGE_E_CANT_MAKE_OTHER_FILE]

SEVERITY: ERROR
DESCRIPTION: S Cant create file %s for other content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_EBR_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: Event Based Retention is not supported on the centera cluster.
CAUSE: Error occurred becuase Event Based Retention is not supported or enabled on the Centera Cluster.
ACTION: Contact centera support if this feature is required.
PARAMS:

ERROR: [DM_STORAGE_E_EXTSTORE_PLUGIN_ERROR]

SEVERITY: ERROR
DESCRIPTION: SSS Session: %s, Store: %s, message: %s
CAUSE: : Error occured in the external store plugin
ACTION: : Error is plugin specific, address problem based on error message
PARAMS:

ERROR: [DM_STORAGE_E_RESTORE_NO_FILE]

SEVERITY: ERROR
DESCRIPTION: The RESTORE method must include a file_path argument from which to restore the document content.
CAUSE: The RESTORE method was invoked without the required file_path argument.
ACTION: Check syntax of command.
PARAMS:

ERROR: [DM_STORAGE_E_BAD_COMPONENT]

SEVERITY: ERROR
DESCRIPTION: SS The store %s cannot be used in as a component in a %s store
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_BLOB_READ_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Database error %s occured when reading blob from blob store %s
CAUSE: A database error occured when attempting to read the blob data from a dm_blobstore
ACTION: Refer to the database error.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_CALLBACK_INVALID_STORE_ID]

SEVERITY: ERROR
DESCRIPTION: S Invalid storage object id %s
CAUSE: A dm_ca_store plugin passed in an incorrect storage object id to the callback function
ACTION: The storage object id passed to the callback function should be the same that was supplied during a call to dm_casplugin_prepare_for_write() or dm_casplugin_prepare_for_read() functions in the plugin. Verify that you are passing the same storage id.
PARAMS:

ERROR: [DM_STORAGE_E_NO_PATH]

SEVERITY: ERROR
DESCRIPTION: SS The location %s for filestore %s is not defined in the server configuration
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_FULLTEXT_INDEX_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: Fulltext indexing not supported for content in external storage
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_INCORRECT_ATTR_COUNT]

SEVERITY: ERROR
DESCRIPTION: SS Attribute count for %s and %s should be equal
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CANT_INITIALIZE_PLUGIN]

SEVERITY: ERROR
DESCRIPTION: SSS Could not initialize plugin ID: %s, Path: %s, Reason : %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NEED_LOCATION]

SEVERITY: ERROR
DESCRIPTION: SS Cant use temp location %s, oserror: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NO_FULLTEXT_INDEX]

SEVERITY: ERROR
DESCRIPTION: SS No fulltext index exists for storage %s — cant mark content %s for indexing
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_RESTORE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Content restore failed because %s.
CAUSE: PURGE_CONTENT operation failed. There should usually be a previous error message giving more detail on the reason of failure.
ACTION: Check the error log for other errors.
PARAMS:

ERROR: [DM_STORAGE_E_UNABLE_TO_LOCK]

SEVERITY: ERROR
DESCRIPTION: SSSS Unable to lock storage object (%s) for ticket allocation, object id is %s, Lock statement: %s, Error from database: %s
CAUSE: A database error occured when attempting to lock a storage object during ticket allocation. Internal programming error.
ACTION: Contact tech support with exact error message.
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_COMPONENT]

SEVERITY: ERROR
DESCRIPTION: SS Store %s is an invalid component for distributed store %s
CAUSE: This error occurs when user specified a dm_ca_store object as a component while creating a distributed store object.
ACTION: dm_ca_store objects cannot be specified as a component of a distributed distributed store. Do not specify dm_ca_store object as a component of a distributed store.
PARAMS:

ERROR: [DM_STORAGE_E_GET_STORAGE_INFO_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS Unable to get the storage info for [%s]: %s
CAUSE: This error is returned by GetStorageInfo apply call when it encounters an operating system or storage system error
ACTION: Refer to the second part of the error message and take corrective action.
PARAMS:

ERROR: [DM_STORAGE_E_EXTERNAL_STORE_TYPE_UPGRADE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to upgrade %s type, %s attribute failed for %s
CAUSE: This error occurs when Content Server fails to upgrade one of the external store types. Most likely a database error is the cause.
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_READ]

SEVERITY: ERROR
DESCRIPTION: SSI Plugin ID: %s returned error: %s, error code:%d
CAUSE: The CAS store plugin returned an error while performing a read content operation.
ACTION: the error code returned is plugin specific. Address the problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_NOT_SYS_ADMIN]

SEVERITY: ERROR
DESCRIPTION: S You must have sys admin privileges to perform a %s operation
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NOT_ACCESSIBLE]

SEVERITY: ERROR
DESCRIPTION: SS Storage area %s is not currently accessible. Reason: %s.
CAUSE: An validation check on a referenced storage area showed that the location is not currently accessible by the server. This could be due to the disk being temporarily unmounted or could be because the storage area is remote to the current documentum server.
ACTION: Check the error log for other errors. Check whether the objects and storage areas referenced should be accessible by your current site. You may need to issue the requested operation on a different server. ARGUMENTS: %s – the name of the storage area %s – the operating system message from the attempted access
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_UNABLE_TO_VERIFY_RH]

SEVERITY: ERROR
DESCRIPTION: SIS Unable to verify Retention Hold for content address %s, Error Code: %d, Error message: %s.
CAUSE: Error occurred trying to verify if clip is under retention hold or not.
ACTION: See if Retention Hold is supported or check the plugin error and address the problem in the environment.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_INCORRECT_CLIENT_VERSION]

SEVERITY: ERROR
DESCRIPTION: S Incorrect client version (%s) to store content in a dm_ca_store object.
CAUSE: An older version of dmcl is being used to push content to a dm_ca_store which is not supported.
ACTION: Use dmcl thats same or later version as the Content Server.
PARAMS:

ERROR: [DM_STORAGE_E_BAD_TICKET]

SEVERITY: ERROR
DESCRIPTION: SSI Use of invalid ticket for storage object with name %s storage may be improperly configured.nTicket was %s. Data Ticket was %i.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CURSOR_FETCH_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Database error occured while fetching sub content object(s). Error from database was %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NOT_COMPONENT]

SEVERITY: ERROR
DESCRIPTION: SS Store %s is not a component of the distributed store %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_BLOB_INSERT_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Could not insert data in blob store %s. %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_OBJECT_ID]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid external store object id
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NO_ACS]

SEVERITY: ERROR
DESCRIPTION: SS ACS Content Transfer Connector cannot find ACS for server %s to %s content.
CAUSE: No dm_acs_config object was found in the docbase for the server of the connection.
ACTION: Check if the dm_acs_config object exists and that srv_config_id contains the ID of the dm_server_config object.
PARAMS:

ERROR: [DM_STORAGE_E_REPLICATE_NOACCESS]

SEVERITY: ERROR
DESCRIPTION: S Cannot replicate to storage area %s as it is not directly accessible by this server.
CAUSE: An validation check on a referenced storage area showed that the location is not currently accessible by the server. This could be due to the disk being temporarily unmounted or could be because the storage area is remote to the current documentum server.
ACTION: Check the error log for other errors. Check whether the objects and storage areas referenced should be accessible by your current site. You may need to issue the requested operation on a different server. ARGUMENTS: %s – the name of the storage area
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_RETENTION_FIELD_TYPE_INCORRECT]

SEVERITY: ERROR
DESCRIPTION: S Type of value field %s is not correct. Beause this field defines the retention period, it should be of DATE type.
CAUSE: This error occurs while saving an object that uses dm_ca_store type object for storage. The error indicates that the value for the a_retention_attr_name in the storage object is not of type DATE. Because the retention attribute value is used to set retention period on the content stored in the storage area, type of the attribute name specified for a_retention_attr_name should be of type DATE.
ACTION: The Administrator should set the value for a_retention_attr_name value for the underlying storage object to a right attribute name.
PARAMS:

ERROR: [DM_STORAGE_E_WRONG_THUMB_KEY]

SEVERITY: ERROR
DESCRIPTION: D Either the thumbnail key file is missing or the key length is less than 24 bytes for store (%s) that requires ticket.
CAUSE: Either the thumbnail key file, thumbserver.key, is missing or the length of the key is less than 24 while the store requires the thumbnail URL to be encripted (i.e., its require_ticket flag is set to true).
ACTION: Talk to your sysadmin to either create a thumbnail key file under $DM_HOME/bin or turn the require_ticket flag off on that store.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_UNABLE_TO_TRIGGER_EBR]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: Error occurred when trying to trigger the clip with Event Based Retention. ACtion: Look at the error message and take appropiate action.
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_MAKE_SOURCE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Could not create source object while attempting to decrypt shared library – %s.
CAUSE: The path pointing to the encrypted shared library is probably not correct.
ACTION: Make sure that the shared library exists at the path specified.
PARAMS:

ERROR: [DM_STORAGE_E_NO_CLOSE_REPLICA]

SEVERITY: ERROR
DESCRIPTION: IS Could not find close replica fetching ticket %d from storage object %s. n Fetch or copy failed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_WRONG_PROTOCOL]

SEVERITY: ERROR
DESCRIPTION: SSI Protocol for server does not match stored protocol for storage object with name%s.nTicket was %s. Data Ticket was %i.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NO_MORE_MEMORY]

SEVERITY: ERROR
DESCRIPTION: No more memory to perform an operation
CAUSE: The system has run out of memory to perform an operation.
ACTION: Make sure you have enough system resources to perform the operation.
PARAMS:

ERROR: [DM_STORAGE_E_SYMBOL_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SS Could not find API %s in %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_UNABLE_TO_GET_RETENTION_PERIOD]

SEVERITY: ERROR
DESCRIPTION: SSIS Unable to obtain retention period for content address %s through plugin %s. Error code from dm_casplugin_get_retention_period is %d. Storage id is %s.
CAUSE: The function dm_casplugin_get_retention_period in the specified plugin for the dm_ca_store object returned an error code.
ACTION: This error is specific to the plugin and storage object. Address the problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_COMPONENT_ALREADY_EXISTS]

SEVERITY: ERROR
DESCRIPTION: SS The component %s already exists in store %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_FILE_LINK]

SEVERITY: ERROR
DESCRIPTION: SSS An unexpected failure occurred while attempting to link file %s to file %s. Operating System error: %s
CAUSE: Operating system unable to complete requested operation
ACTION: Check the permissions on the specified file. Check the effective user of the running server process.
PARAMS:

ERROR: [DM_STORAGE_E_BAD_LINK_STORE]

SEVERITY: ERROR
DESCRIPTION: S Linked storage object %s has no component.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_PREPARE_FOR_RH]

SEVERITY: ERROR
DESCRIPTION: SIS Plugin Id: %s, Error code: %d , Error message %s
CAUSE: : Error occured in dm_casplugin_prepare_for_rh_utils while performing Retention Hold related operation.
ACTION: : Error is plugin specific, Address problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_UNABLE_TO_GET_CONTENT_ATTRS]

SEVERITY: ERROR
DESCRIPTION: S Unable to collect content attributes from content object %s during load.
CAUSE: This error occurs when the content server is unable to obtain content attribute values whose values are to be pushed to the storage, during the load operation of a content object.
ACTION: See other messages
PARAMS:

ERROR: [DM_STORAGE_E_SERVER_PLATFORM_INDICATOR]

SEVERITY: ERROR
DESCRIPTION: Unable to obtain server platform indicator
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_UNABLE_TO_FETCH_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SS Unable to fetch content for content address %s in storage %s
CAUSE: This error occurs while Content Server attempts to fetch the content for the specified content address. Content Server is attempting to fetch content for full-text indexing or to create a rendition for full-text indexing. This error is reported after the plugin for the specified storage object failed to retrieve the content from the storage area.
ACTION: Look at other error messages for the plugin specific error that occured while fetching the content. Address the problem reported by the plugin. Because of this failure the full index batch would have failed and sysobjects will need to be marked for indexing again.
PARAMS:

ERROR: [DM_STORAGE_E_RESTORE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: LL The file specified in the RESTORE request has a size of %d bytes which does not match the recorded content size (%d bytes).
CAUSE: The file given in a RESTORE operation had a size which was different than the original size of the document as recorded in the dmr_content object. A document can only be restored from a file if the file looks like it matches existing content meta-data.
ACTION: The document cannot be restored using the specified content file. This check can be overridden by first zeroing out the data_ticket field of the dmr_content object being restored. ARGUMENTS: The size of the external file data (in bytes). The size recorded in the dmr_content object (in bytes).
PARAMS:

ERROR: [DM_STORAGE_E_MAX_BLOB_SIZE_EXCEEDED]

SEVERITY: ERROR
DESCRIPTION: S Attempt to store into blob failed — size (%s) must be less than 65535 bytes
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_PLUGIN_OBJECT_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS Plugin objects should be of dm_plugin type. %s is of type %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_PREPARE_FOR_WRITE]

SEVERITY: ERROR
DESCRIPTION: SSI Plugin ID: %s returned error: %s, error code:%d
CAUSE: The dm_ca_storestore plugin returned an error while performing prepare for write operation.
ACTION: the error code returned is plugin specific. Address the problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_NO_ACS_BASE_URL]

SEVERITY: ERROR
DESCRIPTION: SS ACS Content Transfer Connector cannot find URL for ACS %s using %s protocol.
CAUSE: No reference to the given protocol was found on acs_supported_protocol of the dm_acs_config object.
ACTION: Add the given protocol to acs_supported_protocol and specify the corresponding URL on acs_base_url.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_PREPARE_FOR_EBR]

SEVERITY: ERROR
DESCRIPTION: SIS Plugin Id: %s, Error code: %d , Error message %s
CAUSE: Error occurred in dm_casplugin_prepare_for_ebr_utils while performing EBR related operation.
ACTION: Error is plugin specific , Address problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_EXTERNAL_STORE_CANT_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS Cannot update %s because %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_GFSMP_DATA_TICKET_PATH]

SEVERITY: ERROR
DESCRIPTION: S Cannot allocate data ticket and path for filestore %s.
CAUSE: The system was unable to create a data ticket and path for the specified filestore.
ACTION: Restart your server.
PARAMS:

ERROR: [DM_STORAGE_E_NO_PLUGIN_FOUND]

SEVERITY: ERROR
DESCRIPTION: SS No plugin found for external store object %s for %s execution mode
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_FAR_STORE_READ]

SEVERITY: ERROR
DESCRIPTION: S Attempt to read from far store %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NO_STORE_FOR_NAME]

SEVERITY: ERROR
DESCRIPTION: S There is no storage object with name %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_UNABLE_TO_SAVE_LOCATION_OBJECT]

SEVERITY: ERROR
DESCRIPTION: S Unable to save %s dm_location object.
CAUSE: This error occurs when Content Server attempts to save the specifed dm_location object and that save had failed. Content Server creates the specified dm_location object which is used as temporary storage when content in a dm_ca_store needs to be retrieved for full-text indexing or to create a rendition of the content for full-text indexing if the primary format of the content is not full-text indexable.
ACTION: Look at the other error messages and take appropriate action.
PARAMS:

ERROR: [DM_STORAGE_E_NOT_FILESTORE]

SEVERITY: ERROR
DESCRIPTION: S The store %s is not a file store
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_WRITE_CLOSE]

SEVERITY: ERROR
DESCRIPTION: SSI Plugin ID: %s returned error: %s, error code:%d
CAUSE: The dm_ca_storestore plugin returned an error while performing a write close operation.
ACTION: the error code returned is plugin specific. Address the problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_FILE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SS Error accessing file (%s) while migrating the content to CA store. Operating System error is %s
CAUSE: File not found at the path specified
ACTION: refer to the Operating system error and take appropriate action.
PARAMS:

ERROR: [DM_STORAGE_E_NOT_DISTRIBUTED]

SEVERITY: ERROR
DESCRIPTION: S The store %s is not a distributed store
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_COMPONENT_PREFERENCE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SSS Setting of attribute %s on store %s does not match distributed store %s.
CAUSE: This error occurs when the user attempts to add a component store whose deduping preference does not match the distributed store.
ACTION: If the distributed store has the deduping preference enabled you may only add component stores which have enabled deduping.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_DUPLICATE_VALUE]

SEVERITY: ERROR
DESCRIPTION: SS Value %s for attribute %s is specified more than once.
CAUSE: This error appears while saving a new dm_ca_store object or while saving an existing dm_ca_store object after changes and same value has been specified more than once for a repeating attribute.
ACTION: Clear the one of the duplicate values for the specified repeating attribute and save.
PARAMS:

ERROR: [DM_STORAGE_E_NO_LOCAL_STORE]

SEVERITY: ERROR
DESCRIPTION: S No local storage exists for distributed store %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CANT_OPEN_CA_STORE_PLUGIN]

SEVERITY: ERROR
DESCRIPTION: SSIS Could not open plugin library %s for content addressable store object %s, error : %d. Plugin ID: %s
CAUSE: An error occured while attempting to read content from a content addressable store (dm_ca_store object). Common cause for this error is a corrupt plugin library.
ACTION: check the content for plugin id specified, at page 0. Test the plugin library outside of Documentum server environment to check if it loads successfully.
PARAMS:

ERROR: [DM_STORAGE_E_BLOB_COLUMN_ALLOCATE]

SEVERITY: ERROR
DESCRIPTION: SS Could not allocate columns in blob store %s. %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CANT_CREATE_PLUGIN_READER]

SEVERITY: ERROR
DESCRIPTION: SS Could not open plugin reader %s to read %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_DUPLICATE_NAME]

SEVERITY: ERROR
DESCRIPTION: S Attempt to make storage object with name %s — name already used
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_TRIGGER_EBR_WITH_PERIOD_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Unable to save the subcontent object with address %s
CAUSE: Error in saving the subcontent object to the database after the clip was successfully triggered.
ACTION: Look for Database related errors in the server log and take appropiate action.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_PREPARE_FOR_READ]

SEVERITY: ERROR
DESCRIPTION: SSI Plugin ID: %s returned error: %s, error code:%d
CAUSE: The dm_ca_store plugin returned an error while performing prepare for read operation.
ACTION: the error code returned is plugin specific. Address the problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_CONTENT_NOT_NEW]

SEVERITY: ERROR
DESCRIPTION: IS Page %d of object %s is not new.
CAUSE: User executed setcontentattrs api for an object and the content object identified by the specified arguments is not new.
ACTION: setcontattrs API can be executed only for new content objects. If content attributes are to be updated for an existing content, use SET_CONTENT_ATTRS Apply method.
PARAMS:

ERROR: [DM_STORAGE_E_CANT_GET_PLUGIN_PATH]

SEVERITY: ERROR
DESCRIPTION: S Could not obtain path of the plugin for %s object
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_SYNC_REP_RECORDS]

SEVERITY: ERROR
DESCRIPTION: Error performing SYNC_REPLICA_RECORDS operation.
CAUSE: Could not execute the SYNC_REPLICA_RECORDS operation.
ACTION: Check error log for other messages that should give more detailed information on the error.
PARAMS:

ERROR: [DM_STORAGE_E_ACS_HTTP_POST_FAILURE]

SEVERITY: ERROR
DESCRIPTION: I ACS Content Transfer Connector failed to post the HTTP request to the ACS with status %d.
CAUSE: The ACS may not be functioning correctly.
ACTION: Check that the ACS is functioning. Attempt to reproduce the problem with acs_connector_trace tracing enabled, and provide the ACS and content repositor log files to EMC Technical support.
PARAMS:

ERROR: [DM_STORAGE_E_MKDIR_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Cannot create storage directory %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_PLUGIN_OBJECT_ID]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid object id value for a_plugin_id attribute. Object does not exist in docbase
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_WAIT_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to wait for the command: %s. os_error: %s.
CAUSE: Unable to wait for command to finish successfully.
ACTION: See your system administrator.
PARAMS:

ERROR: [DM_STORAGE_E_GFSMP_INVALID_STORE_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS Store %s has storage type %s not supported by GET_FILESTORE_METADATA_AND_PATH
CAUSE: Storage supplied to GET_FILESTORE_METADATA_AND_PATH must be dm_filestore or dm_distributedstore.
ACTION: Refer to the server documentation for the required parameters.
PARAMS:

ERROR: [DM_STORAGE_E_CANT_MAKE_LOCALDIR]

SEVERITY: ERROR
DESCRIPTION: Unable to make directory for downloading plugin content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CANT_DOWNLOAD_PLUGIN_CONTENT]

SEVERITY: ERROR
DESCRIPTION: Unable to download plugin library content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_OBSOLETE_CMD]

SEVERITY: ERROR
DESCRIPTION: S Apply method %s has been obsolete.
CAUSE: User tries to run an obsolete apply method.
ACTION: Dont do this. PARAMETER: Name of the apply method.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_FETCH_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SSSS An Operating System error occured while attempting to write content to %s : %s. Content Address is %s, storage is %s
CAUSE: This error occurs when the Content Server attempts to fetch content for the specified content address in the specified storage. Content Server fetches the content to a temporary location for full-text indexing or to create a rendition for full-text indexing.
ACTION: Look at the operating system specific error message. This could be a permission problem or not enough disk space to create/write to the temporary file.
PARAMS: S Name of the temporary file. S Operating system error message S Content Address for which Content Server attempts to fetch the content S Storage object name

ERROR: [DM_STORAGE_E_CANT_USE_EXTERNAL_STORE]

SEVERITY: ERROR
DESCRIPTION: S Object %s cannot be used as a plugin because it uses external storage
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_OBJECT_NAME]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid external store object name
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_BAD_TYPE]

SEVERITY: ERROR
DESCRIPTION: I Cant make storage for type %d — type not registered
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_SET_METADATA]

SEVERITY: ERROR
DESCRIPTION: SSI Plugin ID: %s returned error: %s, error code:%d
CAUSE: The dm_ca_store plugin returned an error while performing a set metadata operation.
ACTION: the error code returned is plugin specific. Address the problem in your environment.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_MISSING_ENTRY_POINT]

SEVERITY: ERROR
DESCRIPTION: DSS Incorrect version of CA store Plugin with id %s, path %s , missing entry point %s
CAUSE: Incorrect version of CA store plugin.
ACTION: Make sure the the content of the dm_plugin object reported in the error message is the same as the one under $DM_HOME/bin. The name of the plugin library is emcplugin.dll (windows), libemcplugin.so (Solaris, Linux, AIX) and libemcplugin.sl (HP-UX). Fetch the dm_plugin object reported in the error message, set the page 0 content of the object to the CA store plugin library as described above (depending on the Operating system), save the dm_plugin object. Or, copy the CA store plugin to the plugin path reported in the error message directly as the install owner/administrator.
PARAMS:

ERROR: [DM_STORAGE_E_BAD_NAME]

SEVERITY: ERROR
DESCRIPTION: SS Illegal name %s for storage object of type %s
CAUSE: Storage object names are limited to alphanumeric characters and the underscore character (_). Also the name of blobstore objects are limited by the maximum length tablename for the underlying database for Oracle and Sybase, this length is 30 characters, for Informix, it is 18 characters.
ACTION: Chose a different name and try to save the object again
PARAMS:

ERROR: [DM_STORAGE_E_FILE_WRITE_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Error writing to content file %s. File size %s bytes.
CAUSE: An error was returned during an attempt to store a new content file.
ACTION: Check for available diskspace to create the new file with the indicated size.
PARAMS:

ERROR: [DM_STORAGE_E_NO_STORE_FOR_ID]

SEVERITY: ERROR
DESCRIPTION: S There is no storage object with id %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_PLUGIN_INIT_FAILED]

SEVERITY: ERROR
DESCRIPTION: SSI %s API in %s returned a failure code of %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NO_NAME]

SEVERITY: ERROR
DESCRIPTION: Attempt to create new storage object without giving it a name
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_NO_REPLICA]

SEVERITY: ERROR
DESCRIPTION: S No replica exists in the component store %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CANT_OBTAIN_PLUGIN_VERSION]

SEVERITY: ERROR
DESCRIPTION: S Unable to obtain plugin protocol version. Plugin path: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CASTORE_DUMP_CLIP]

SEVERITY: ERROR
DESCRIPTION: S CASTORE_DUMP_CLIP error: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_LOCATION_NOT_FOUND_FOR_FETCH]

SEVERITY: ERROR
DESCRIPTION: SSS A dm_location object with name %s not found while attempting to fetch content for content address %s in storage %s
CAUSE: This error occurs when the Content Server attempts to fetch the content for the specified content address from the storage area specified. Content Server creates a dm_location object with the reported name during server initialization and the location is used as temporary storage for content fetched from dm_ca_store storage objects. The temporary storage is necessary for full text indexing of the content or creating renditions for full-text indexing.
ACTION: Verify that a dm_location object with the reported name exists in the docbase and that its valid. If its not valid, destroy the specified dm_location object, stop the server and restart. Content Server would check for the existence of the specified dm_location object and create if it does not exist in the docbase.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_UNABLE_TO_CHECK_CAN_DELETE]

SEVERITY: ERROR
DESCRIPTION: SSI Unable to check if storage %s allows deletes because dm_casplugin_can_delete() in plugin %s returned error code %d
CAUSE: Content Server failed to check if the dm_ca_storage object allows deleting of content.
ACTION: Check the error code returned by the plugin as part of the message and take corrective action in the plugin implementation.
PARAMS:

ERROR: [DM_STORAGE_E_INVALID_ARGUMENTS]

SEVERITY: ERROR
DESCRIPTION: S Invalid arguments passed to %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_BLOB_TABLE_CREATE]

SEVERITY: ERROR
DESCRIPTION: SS Could not create the table for blob store %s. %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CASTORE_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S Content Addressable Storage type is not supported on %s architecture EMC Centera 32 Bit SDK is NOT available on HPUX IA64 Platform
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CASTORE_UNABLE_TO_WIDEN_ATTR]

SEVERITY: ERROR
DESCRIPTION: S A database failure occured while widening the length of attribute %s
CAUSE: A database error occured while attempting to widen a CA store type attribute.
ACTION: See the action for the accompanying database errors.
PARAMS:

ERROR: [DM_STORAGE_E_GETFILE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S getfile not allowed for sysobject %s, because the storagetype for the object has not plugin configured
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_TURBO_SAVE_FAILED]

SEVERITY: ERROR
DESCRIPTION: Database and/or network error occured while saving turbo content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_OTHERFILE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: Resource fork files cannot be saved in a CA Store
CAUSE: This error occurs while attempting to save the mac resource fork file into a CA Storage.
ACTION: None. CA Store cannot be used to save content that have mac resource fork files associated with it.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_REMOVE_CONTENT_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: Removing content from a dm_ca_store type storage is not supported. Contact Documentum Technical Support.
CAUSE: User attempted to destroy a sysobject whose content resides in a dm_ca_store type storage.
ACTION: We do not currently support removing content from a dm_ca_store type storage area. This will be supported in future.
PARAMS:

ERROR: [DM_STORAGE_E_CREATE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Cannot create storage file %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_RH_NOT_ENABLED]

SEVERITY: ERROR
DESCRIPTION: Retention Hold is not supported on the centera cluster.
CAUSE: Error occurred becuase Retention Hold is not supported or enabled on the Centera Cluster.
ACTION: Contact centera support if this feature is required.
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_PLUGIN_UNABLE_TO_VERIFY_EBR]

SEVERITY: ERROR
DESCRIPTION: S Unable to verify Event Based Retention. Error : %s
CAUSE: Error occurred trying to verify if EBR is set or not.
ACTION: See if EBR is supported or check the plugin error and address the problem in the environment.
PARAMS:

ERROR: [DM_STORAGE_E_RENAME_EXT_SEARCH]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to rename a file matching (%s) to (%s). Operating System error: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_RENAME_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to rename a file (%s) to (%s). Operating System error: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_DUMP_WITH_CONTENT_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: Dump with content is not supported for objects that use external storage
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_FORCE_DELETE_NOT_ALLOWED_IN_EXTERNAL_TRANSACTION]

SEVERITY: ERROR
DESCRIPTION: You cannot perform force delete after having initiated an explicit transaction
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_GFSMP_MISSING_PARAMETERS]

SEVERITY: ERROR
DESCRIPTION: S Required parameters %s are missing from GET_FILESTORE_METADATA_AND_PATH
CAUSE: Required parameters were not supplied to the GET_FILESTORE_METADATA_AND_PATH server api call.
ACTION: Refer to the server documentation for the required parameters.
PARAMS:

ERROR: [DM_STORAGE_E_DELETEREP_NOACCESS]

SEVERITY: ERROR
DESCRIPTION: S Cannot delete replica from storage area %s as it is not directly accessible by this server.
CAUSE: An validation check on a referenced storage area showed that the location is not currently accessible by the server. This could be due to the disk being temporarily unmounted or could be because the storage area is remote to the current documentum server.
ACTION: Check the error log for other errors. Check whether the objects and storage areas referenced should be accessible by your current site. You may need to issue the requested operation on a different server. ARGUMENTS: %s – the name of the storage area
PARAMS:

ERROR: [DM_STORAGE_E_DUPLICATE_PLATFORM_INDICATOR]

SEVERITY: ERROR
DESCRIPTION: I Cannot specify duplicate platform indicator values for a_platform attribute: %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CANT_LINK]

SEVERITY: ERROR
DESCRIPTION: SS Could not make link between %s and %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_BLOB_MEMORY]

SEVERITY: ERROR
DESCRIPTION: S Out of memory for blob store %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CHECK_RETENTION_EXPIRED]

SEVERITY: ERROR
DESCRIPTION: S Reason: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_DUPLICATE_LOCATIONS]

SEVERITY: ERROR
DESCRIPTION: SS Storage object %s already using location %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_SYNTAX_ERROR]

SEVERITY: ERROR
DESCRIPTION: Incorrect syntax for mount command
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_TEMP_CONNECTION_NOT_VALID]

SEVERITY: ERROR
DESCRIPTION: Could not obtain TEMP_CONNECTION from the database
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_FORCE_DELETE_FAILED]

SEVERITY: ERROR
DESCRIPTION: ISS Error %d (%s) occured during force delete. Content Address %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_E_CA_STORE_CONTENT_CANNOT_BE_DESTROYED]

SEVERITY: ERROR
DESCRIPTION: SSS Content object %s cannot be destroyed because the retention period has not expired. Content Address is %s. Storage area name is %s.
CAUSE: A retention period has been set on the content residing in a dm_ca_store type storage, that prevents destroying of the dmr_content object.
ACTION: None. Content object with a retention period set to a future date cannot be destroyed.
PARAMS:

ERROR: [DM_STORAGE_E_LAST_REPLICA]

SEVERITY: ERROR
DESCRIPTION: S Cant delete last replica in storage %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_T_FILESTORE_TRACE]

SEVERITY: TRACE
DESCRIPTION: S %s $Id: dmsysobj.e,v 5.45 2003/04/24 22:49:48 yasoja Exp $ dmSysObject class errors
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_T_EXTSTORE_TRACE]

SEVERITY: TRACE
DESCRIPTION: SSS Session: %s, Store: %s, message: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_T_FILESTORE_DUPLICATE_CONTENT_TRACE]

SEVERITY: TRACE
DESCRIPTION: S %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_W_CA_STORE_ORPHAN_CONTENT_ADDRESS]

SEVERITY: WARNING
DESCRIPTION: S Content Address %s is orphaned because of transaction rollback
CAUSE: This error appears when the content for an object is stored successfully in a dm_ca_store storage area, but the sysobject and content objects are not saved in the docbase due to transaction rollback. The transaction is being rolled back due to some other error.
ACTION: This is an informational message to indicate that there is no content object in the docbase that refers to this content address. if there is no retention period set on the reported content address user can destroy the content represented by the content address using native storage system tools. Otherwise, user needs to wait until the retention period expires to be able to destroy the content.
PARAMS:

ERROR: [DM_STORAGE_W_LINKSTORE_CLEANUP]

SEVERITY: WARNING
DESCRIPTION: Cleanup of Linked Storage areas being skipped due to errors. Could not complete cleanup of links created by old getfile operations.
CAUSE: A failure looking for, validating, or removing old links.
ACTION: Check the error log for earlier error messages indicating the the cause of the error.
PARAMS:

ERROR: [DM_STORAGE_W_ACL_DOMAIN_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: SS Your program may be unable to open the file because it will attempt the open as the domain who is logged onto your computer (%s), but file security is granted to the domain connected to the docbase (%s).
CAUSE: The security of the underlying file system grants permission to specific users in specific domains the documentum system grants permission to thed user logged into the system. If those credentials dont match the security of the system will prevent access
ACTION: Login to the workstation or computer as the same user you are logging into Documentum
PARAMS:

ERROR: [DM_STORAGE_W_RENAME_MULTIPLE]

SEVERITY: WARNING
DESCRIPTION: SI During the scan for files matching the pattern (%s) (%d) files were found. This is unexpected and should be investigated.
CAUSE: Access to a file in a filestore determined that the requested file needed to be renamed to match the dos_extension attribute specified in the corresponding format. However, multiple files matched which is unexpected. This could be caused by someone directly manipulating files in a filestore.
ACTION: Look at all the files in the filestore matching the one named in the error message.
PARAMS:

ERROR: [DM_STORAGE_W_CHECK_PERMISSIONS]

SEVERITY: WARNING
DESCRIPTION: SSS The directory %s exists (for filestore %s). All files should be %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_W_CANT_FETCH_FORMAT]

SEVERITY: WARNING
DESCRIPTION: I Unable to fetch format object with id %d
CAUSE: The format object does not exist in the docbase – possibly deleted
ACTION: Locate the content objects that refer to this format id and reset the format
PARAMS:

ERROR: [DM_STORAGE_W_CA_STORE_UNABLE_TO_READ_FULL_CONTENT]

SEVERITY: WARNING
DESCRIPTION: SSS Unable to read full content for content address %s. Size in the docbase is %s bytes. Bytes read from the store is %s
CAUSE: This warning message appears when the Content Server is unable to read the full content from a storage area represented by a dm_ca_store object.
ACTION: Check other error messages from the storage object. Verify that any thirdparty libraries required for the operation of the dm_ca_store object is the right version.
PARAMS:

ERROR: [DM_STORAGE_W_BLOB_INDEX_DB2_RULE]

SEVERITY: WARNING
DESCRIPTION: S On DB2 platforms, blobstore names must be unique within the first 16 characters. The index creation failure could have occurred because an index with the same name already exists, created for a different blobstore with a name similar to %s.
CAUSE: This error is given whenever an error is encountered during the create index step of blobstore creation. It alerts the user that the index creation will fail if another blobstore exists with a similar store name.
ACTION: Check to see if the blobstore being created has a unique name. Also check the database error given by the previous error message for more information on the create-index failure.
PARAMS:

ERROR: [DM_STORAGE_W_ACL_USER_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: SS Your program may be unable to open the file because it will attempt the open as the user who is logged onto your computer (%s), whereas file permissions are granted to the user connected to the docbase (%s).
CAUSE: The security of the underlying file system grants permission to specific users in specific domains the documentum system grants permission to thed user logged into the system. If those credentials dont match the security of the system will prevent access
ACTION: Login to the workstation or computer as the same user you are logging into Documentum
PARAMS:

ERROR: [DM_STORAGE_W_NO_PATH_FOR_FAR_STORE]

SEVERITY: WARNING
DESCRIPTION: SS No path defined for location %s for far filestore %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_W_CA_STORE_TIME_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: SIIS Local time in UTC and Storage time in UTC do not match. Storage Address: %s, Local time in UTC: %d, Storage time in UTC: %d, Storage Object id: %s
CAUSE: This warning is reported when the time settings on the Content server host and the Storage system differ by more than 5 minutes. This warning is reported only if the storage object is retention enabled, since the difference in time settings will result miscalculation of retention expiration.
ACTION: Synchronize the time settings between the Content Server host and Storage system.
PARAMS:

ERROR: [DM_STORAGE_W_CA_STORE_CONTENT_METADATA_FIELD_NOT_FOUND]

SEVERITY: WARNING
DESCRIPTION: SS Field %s not found for object %s.
CAUSE: this error occurs when one of the values specified for a_content_attr_name in the underlying dm_ca_store object is not set using the setcontentattrs API before saving the parent object. This is a client side error reported when saving an object with its storage set to a dm_ca_store object.
ACTION: This is just a warning message. Content would still be saved without the attributes value being set as a tag value in the storage system. Have the Docbase Administrator check the values specified for a_content_attr_name attribute for the dm_ca_store object.
PARAMS:

ERROR: [DM_STORAGE_W_REMOVE_FILES]

SEVERITY: WARNING
DESCRIPTION: SS Filestore %s deleted. Files in %s can be removed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_W_NO_SYSOBJECT_DEFAULT]

SEVERITY: WARNING
DESCRIPTION: No default storage was set for type dm_sysobject
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_W_CANT_CHANGE]

SEVERITY: WARNING
DESCRIPTION: SS Cant change %s attribute for storage object %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_W_REPLICA_EXISTS]

SEVERITY: WARNING
DESCRIPTION: S A replica already exists in the store %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_W_CANT_FETCH_FORMAT2]

SEVERITY: WARNING
DESCRIPTION: D Unable to fetch format object with id %s.
CAUSE: The format object does not exist in the docbase – possibly deleted
ACTION: Locate the content objects that refer to this format id and reset the format
PARAMS:

ERROR: [DM_STORAGE_W_NOT_SUPPORTED]

SEVERITY: WARNING
DESCRIPTION: SS The %s storage type is not supported on this platform (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_W_SUBCONTENT_SAVE_FAILED]

SEVERITY: WARNING
DESCRIPTION: Failed to save the turbostore content as subcontent object.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_W_SIZE_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: II Actual content size of %d is different from record content size of %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_I_OTHERFILE_NOT_ALLOWED]

SEVERITY: INFORMATION
DESCRIPTION: S otherfile disallowed for %s, because it uses external storage
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_I_CANT_USE_EXTERNAL_STORE]

SEVERITY: INFORMATION
DESCRIPTION: Cannot use an external store for addrendition
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_I_STORAGE_NAME_REQUIRED]

SEVERITY: INFORMATION
DESCRIPTION: S A valid storage name is required since %s uses external storage
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_I_SETCONTENT_NOT_ALLOWED]

SEVERITY: INFORMATION
DESCRIPTION: S setcontent disallowed for %s, because it uses external storage
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_I_CANT_CHECKOUT]

SEVERITY: INFORMATION
DESCRIPTION: S cant checkout %s, because it uses external storage
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_I_INSERTCONTENT_NOT_ALLOWED]

SEVERITY: INFORMATION
DESCRIPTION: S insertcontent disallowed for %s, because it uses external storage
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_STORAGE_I_DM_STORAGE_E_CHANGE_NOT_ALLOWED_CRYPTO_MODE]

SEVERITY: INFORMATION
DESCRIPTION: Changing crypto-mode attribute is not allowed.
CAUSE: An attempt was made to update the crypto_mode attribute..
ACTION: Do not attempt to modify the crypto_mode attribute.
PARAMS:

ERROR: [DM_STORAGE_I_APPENDCONTENT_NOT_ALLOWED]

SEVERITY: INFORMATION
DESCRIPTION: S appendcontent disallowed for %s, because it uses external storage
CAUSE:
ACTION:
PARAMS:

nahoru

DM_SYSOBJECT

ERROR: [DM_SYSOBJECT_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dm_sysobject type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_SYSOBJECT_F_LIGHTWEIGHT_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_lightweight object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_SYSOBJECT_F_INIT6]

SEVERITY: FATAL
DESCRIPTION: The conversion vstamp object is missing.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_sysobject object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_SYSOBJECT_F_INT1]

SEVERITY: FATAL
DESCRIPTION: S The following database query %s could not be executed.
CAUSE: Inconsistency between the server and the sysobject type.
ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_SYSOBJECT_F_INIT7]

SEVERITY: FATAL
DESCRIPTION: The default security mode is unknown. Verify that the parameter -security is specified in the server command line with a value of acl or none.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dm_sysobject type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_SYSOBJECT_F_INIT4]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error converting the dm_sysobject type.
CAUSE: Unknown.
ACTION: Look at the error message logged by the type manager. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_SYSOBJECT_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_sysobject to version %d.
CAUSE: Type conversion failed.
ACTION: Report the problem.
PARAMS:

ERROR: [DM_SYSOBJECT_F_ATTR_NOT_FOUND]

SEVERITY: FATAL
DESCRIPTION: SS Could not find attribute %s on type %s
CAUSE: Inconsistency between the server and the type definition.
ACTION: Report the problem. Upgrade Manager Facility errors ** Documentum e-Content Server ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1991-2000 ** All rights reserved. **
PARAMS:

ERROR: [DM_SYSOBJECT_F_INIT5]

SEVERITY: FATAL
DESCRIPTION: Failed to set the security version stamps.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANNOT_CHANGE_FT_ATTRS_WHEN_SHARED]

SEVERITY: ERROR
DESCRIPTION: S Cannot change any ftindex attribute of %s since it is shared by some lightweight object and its allow_propagating_changes flag is false.
CAUSE: User has tried to change some ftindex attribute of an object which is shared by some lightweight object and its allow_parent_ftchange flag is false.
ACTION: User should avoid changing any ftindex attribute on the parent object when it is shared by lots of children object. However, if it is not the case, then user can set the allow_parent_ftchange flag to true so that the operation can succeed.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_FETCH_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a sysobject – Invalid object ID %s
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ATTACH_NON_RET_MANAGER_OWNED_RETAINER]

SEVERITY: ERROR
DESCRIPTION: D The retainer object %s needs to be owned by retention managers in order to attach to a sysobject.
CAUSE: A user tried to attach a retainer object that is not owned by retention managers to a sysobject.
ACTION: A retainer not owned by retention managers can never be attached to a sysobject.
PARAMS:

ERROR: [DM_SYSOBJECT_E_UPDATE_RETAIN_UNTIL_UNABLE_TO_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Unable to save %s after updating i_retain_until attribute value
CAUSE: Unable to save sysobject after updating the i_retain_until attribute. Action: Refer to the action of other error messages.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ATTACH_REPLICA_POLICY]

SEVERITY: ERROR
DESCRIPTION: D Attach of replica policy %s is not supported.
CAUSE: The client attempted to attach a replica policy to a sysobject.
ACTION: Choose a local policy.
PARAMS: The first parameter is the policy id of the replica policy.

ERROR: [DM_SYSOBJECT_E_CANT_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Cannot save %s sysobject.
CAUSE: One or more operations has failed during this save. Consult the following error message(s) for more help.
ACTION: Try again after fixing previous problems.
PARAMS:

ERROR: [DM_SYSOBJECT_E_REVERT_ACL]

SEVERITY: ERROR
DESCRIPTION: SSSS Failed to revert the ACL %s in domain %s during reversion of %s %s.
CAUSE: Failed to revert the associated ACL during sysobject reversion.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_UNKNOWN_PERMIT]

SEVERITY: ERROR
DESCRIPTION: S The permit of the sysobject %s is unknown.
CAUSE: The method needs to know the permit to complete, but the permit is unknown.
ACTION: The method is either not used appropriately or something goes wrong.
PARAMS:

ERROR: [DM_SYSOBJECT_E_PERMIT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S The permit requested should have been granted for sysobject %s.
CAUSE: The server doesnt know why the requested permit was not granted.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_NEED_RELATE_OR_RET_MANAGER]

SEVERITY: ERROR
DESCRIPTION: SSS The session user %s needs to have relate permit on the sysobject %s or a retention manager in order to call %s.
CAUSE: A user wants to perform some operation (e.g., removeretention) which requires the user to be either a retention manager or have relate permit on the sysobject.
ACTION: Make sure the user has enough privilege.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_RELATE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S No relate access sysobject named %s. CAUSE:You do not have sufficient permission to relate this sysobject. This could be because of insufficient permission on the sysobject itself, or on the sysobjects primary cabinet.
CAUSE:
ACTION: First determine if it is the sysobject, or its cabinet, that you do not have relate access to. Then, see your System Administrator or the owner of the sysobject or cabinet.
PARAMS:

ERROR: [DM_SYSOBJECT_E_SETSTORAGE_INVALID_STORAGE]

SEVERITY: ERROR
DESCRIPTION: S The storage name specified %s is invalid.
CAUSE: Storage name specified for the setstorage api is invalid.
ACTION: specify a valid storage area name.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_OBJECT_UNSIGNED]

SEVERITY: ERROR
DESCRIPTION: D The object %s is unsigned.
CAUSE: No dm_addesignature audit records were found for this sysobject. Deleting these audit records will make the sysobject appear unsigned.
ACTION: Verify that dm_addesignature audit records are not being deleted.
PARAMS: The first parameter is the id of the sysobject which is being signed or verified.

ERROR: [DM_SYSOBJECT_E_CHANGE_STATE_PERM_2]

SEVERITY: ERROR
DESCRIPTION: SSD It requires the CHANGE_STATE permit to perform %s on the object %s(%s).
CAUSE: The user does not have the CHANGE_STATE extended permission (maybe WRITE permit) on the sysobject while attempting to perform the said operation.
ACTION: Grant the user CHANGE_STATE and WRITE permits on the object.
PARAMS:

ERROR: [DM_SYSOBJECT_E_BAD_RESUME_STATE]

SEVERITY: ERROR
DESCRIPTION: ID Resume failed since the resume state %d is not a valid state of the associated policy %s.
CAUSE: The state may have been removed.
ACTION: Reattach the sysobject to an INSTALLED policy.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_FORCE_DELETE]

SEVERITY: ERROR
DESCRIPTION: SSS Cant force delete object (%s) because storage (%s) does not allow the operation, for the specified authorization parameters (%s)
CAUSE: This error occurs when attempting to forcedelete a sysobject and its content, where the storage area does not allow the force delete operation for the specified the authroization parameters.
ACTION: Consult your system administrator to create a proper authorization file to be used as a value for the forcedelete API.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ATTACH_RETAINER_TO_DIST_COPY]

SEVERITY: ERROR
DESCRIPTION: DS You cannot attach the retainer object %s to sysobject %s which is either a reference or replica object.
CAUSE: A user tried to attach a retainer object to an object which is either a reference or replica object.
ACTION: A retainer can never be attached to any distributed object.
PARAMS:

ERROR: [DM_SYSOBJECT_E_BAD_CUR_STATE_2]

SEVERITY: ERROR
DESCRIPTION: SSDID %s on the object %s(%s) failed since the current state %d is not a valid state of the associated policy %s.
CAUSE: The state may have been removed.
ACTION: Reattach the sysobject to an INSTALLED policy.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DELETE_UNDER_RETENTION]

SEVERITY: ERROR
DESCRIPTION: S Object %s is under retention and cannot be deleted.
CAUSE: You do not have the necessary permit to delete this sysobject as it is managed under retention rules.
ACTION: Object cannot be deleted without contacting the System Administrator.
PARAMS:

ERROR: [DM_SYSOBJECT_E_BINDFILE_SOURCE]

SEVERITY: ERROR
DESCRIPTION: Failed to bind file due to missing source sysobject object.
CAUSE: The source sysobject for bindfile command is missing.
ACTION: Please make sure the id of the source sysobject is correct. If this still happens, there can be an internal problem.
PARAMS:

ERROR: [DM_SYSOBJECT_E_FOLDER_DEF_ACL]

SEVERITY: ERROR
DESCRIPTION: S ACL inheritance failed, due to missing ACL in the folder %s.
CAUSE: The folder to inherit the ACL doesnt have an ACL defined.
ACTION: Associated an ACL with the folder.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S Cannot access file (%s)
CAUSE: File or pointer could not be read. Most likely invalid path or pointer is specified for content.
ACTION: Specify a correct path or pointer and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_INVALID_AUDIT_RECORD]

SEVERITY: ERROR
DESCRIPTION: D Audit record %s for the existing electronic signature is invalid.
CAUSE: Verification of the audit record failed.
ACTION: Verify the status of the dm_addesignature audit record.
PARAMS: The first parameter is the id of the audit record which is being verified.

ERROR: [DM_SYSOBJECT_E_CANT_CHANGE_CONTENT_UNDER_RETENTION]

SEVERITY: ERROR
DESCRIPTION: S You can not change/add any primary content to sysobject %s when it is under retention unless you are a retention manager.
CAUSE: A user who is not a retention manager tried to add a new primary content or change an existing one when the object is under retention.
ACTION: You can only add/change any primary content when the object is not under retention if you are not a retention manager.
PARAMS:

ERROR: [DM_SYSOBJECT_E_FORCE_DELETE_CANT_EXPUNGE_CONTENT_OBJECT]

SEVERITY: ERROR
DESCRIPTION: DD force delete failed because an error occured during deletion of content object %s. Sysobject is %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_GET_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SLS Cannot get %s format for %d content of %s sysobject.
CAUSE: Could not retrieve the specified content, most likely format or page specified does not exist, or conversion for the specified format was not successful.
ACTION: Check other error messages on the message queue to find out what the specific problem was. Take the action appropriate to those more specific messages (such as, specify valid page number or format and try again).
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: S Cannot destroy %s sysobject.
CAUSE: Could not destroy this sysobject. Most likely, there are versions of this sysobject checked out by others, or the content of this sysobject could not be destroyd.
ACTION: Make sure that all versions of this sysobject are checked in and storage area for the content object is valid.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NEED_RET_MANAGER]

SEVERITY: ERROR
DESCRIPTION: SSD The session user %s needs to be a retention manager in order to call %s on the sysobject with ID %s.
CAUSE: A user wants to perform some operation (e.g., removeretention) which requires the user to be a retention manager on the sysobject because the sysobject is under retention.
ACTION: Make sure the user is a retention manager or the sysobject is not under retention.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_INVALID_HASH_FORMAT_AUDIT]

SEVERITY: ERROR
DESCRIPTION: SD The format of hash attribute value %s in audit record %s is invalid.
CAUSE: The server supports a fixed set of hash values. Initially only the format SHA-1 is supported.
ACTION: Verify the hash format in the specified audit record.
PARAMS: The first parameter is the hash format. The second parameter is the audit record ID.

ERROR: [DM_SYSOBJECT_E_NEW_ACL]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to get the associated ACL object (%s, %s) for the sysobject %s.
CAUSE: Failed to create a dmACL object.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DROP_LABEL]

SEVERITY: ERROR
DESCRIPTION: S Cannot drop %s label.
CAUSE: Tried to drop a label that is in use for a composite. As long as a label is used for composite containment, the label cannot be dropped.
ACTION: Try again after removing the component containment that relies on this label.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DELETE_LOCKED]

SEVERITY: ERROR
DESCRIPTION: SS Cannot delete sysobject %s since its locked by user %s.
CAUSE: Cannot delete a locked sysobject.
ACTION: Have the user who holds the lock unlock the given sysobject, and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_SIGNATURE_METHOD_NOT_RUN]

SEVERITY: ERROR
DESCRIPTION: S The signature method %s did not execute.
CAUSE: The signature page method could not be found.
ACTION: Verify the existence of the signature page method file.
PARAMS: The first parameter is the name of the signature page method..

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_HASH_PRIMARY_CONTENT]

SEVERITY: ERROR
DESCRIPTION: D The primary content for object %s could not be hashed.
CAUSE: The sysobjects content could not be hashed prior to signing.
ACTION: Verify that the sysobject has content in the signature format.
PARAMS: The first parameter is the object ID of the sysobject that is being signed.

ERROR: [DM_SYSOBJECT_E_BP_SCHD_SAME_TIME]

SEVERITY: ERROR
DESCRIPTION: SS Scheduled %s failed since there exists other event scheduled at the same time %s.
CAUSE: Another BP event has been scheduled at the same time already.
ACTION: Choose a different time to schedule the event.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_STORAGE]

SEVERITY: ERROR
DESCRIPTION: S The specified storage (%s) is invalid.
CAUSE: The specified storage does not match a valid storage from the docbase.
ACTION: Consult the dm_store for valid storage specifications.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DESTROYC]

SEVERITY: ERROR
DESCRIPTION: S Cannot destroy root of the %s version tree.
CAUSE: Tried to delete the root of a version tree.
ACTION: Delete the dependent versions before the root.
PARAMS:

ERROR: [DM_SYSOBJECT_E_BP_ON_OPENTRAN]

SEVERITY: ERROR
DESCRIPTION: S A BP event %s failed because this session has an open transaction.
CAUSE: User tried to issue a BP event (i.e., attach, promote, demote, suspend, and resume) within an open transaction.
ACTION: Commit the transaction and re-run the BP event again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_LINK_ADJUST]

SEVERITY: ERROR
DESCRIPTION: DS Failed to adjust the link count of the sysobject %s. The database error message was: %s
CAUSE: Failed to deferred update the sysobjects r_link_cnt.
ACTION: Fix the database problem according to the reported error message.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DEREF_ACL]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to de-reference the ACL %s in domain %s for sysobject %s.
CAUSE: Failed to deref.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S The operation %s is not supported.
CAUSE: The operation is not supported.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_MAT_OPTION_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: D Failed to materialize object %s due to the materialization option mismatch
CAUSE: A user tried to materialize an object which is against the types materialization option.
ACTION: If the materialization option of the lightweight type is not AUTO MATERIALIZATION, you need to provide a shared parent ID while creating a lightweight instance. This error is most likely caused by a DQL CREATE statement. Please revise the DQL CREATE statement to provide a shared parent ID for each newly-created lightweight object.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_VERIFY_AUDIT_RECORD]

SEVERITY: ERROR
DESCRIPTION: D Audit record %s for the previous electronic signature cannot be verified.
CAUSE: dmVerifyAuditRecord failed to return a result collection.
ACTION: Verify the status of the dm_addesignature audit record.
PARAMS: The first parameter is the id of the audit record which is being verified.

ERROR: [DM_SYSOBJECT_E_MUST_OWNED_BY_RET_MANAGER]

SEVERITY: ERROR
DESCRIPTION: S The owner %s needs to be a retention manager.
CAUSE: Only a retention manager can own a dm_retainer object.
ACTION: The owner needs to be a member, direct or indirect, of the dm_retention_managers group.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_TYPE_FOR_OPERATION]

SEVERITY: ERROR
DESCRIPTION: SSS Cannot perform %s operation on %s since it is of type %s.
CAUSE: The specified operation not supported on this type of sysobject.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CHANGE_PERMITS]

SEVERITY: ERROR
DESCRIPTION: S Only the %s sysobject owner, superuser, and anyone with the change_permit permit can change permits.
CAUSE: A user, other than a superuser or sysobject owner, tried to change security permits In ACL security mode, anyone with the CHANGE_PERMIT permit are allowed to change security permits.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CREATE]

SEVERITY: ERROR
DESCRIPTION: Cannot create a new sysobject
CAUSE: Could not successfully create a new sysobject. Either network connection or database connection could not be established, or bad docbase.
ACTION: See your System Administrator.
PARAMS:

ERROR: [DM_SYSOBJECT_E_MISSING_REQUIRED_PARA]

SEVERITY: ERROR
DESCRIPTION: S Some required parameter is missing in the %s call.
CAUSE: A required parameter is missing from the apply call.
ACTION: Check the syntax to make sure that all required parameters are supplied.
PARAMS:

ERROR: [DM_SYSOBJECT_E_OPEN_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SS The file %s cannot be opened because it is in use by another application. (Operating System error: %s).
CAUSE: The file is in use by another process.
ACTION: Close any applications using the particular file and try again
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOCOMPS_TO_FREEZE]

SEVERITY: ERROR
DESCRIPTION: S The %s sysobject has no assembled components to be frozen.
CAUSE: The current sysobject has no assembled components to freeze.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_SIGNATURE_NUMBER_MISSING]

SEVERITY: ERROR
DESCRIPTION: ID Missing electronic signature number %d for object %s. Signature numbers must be consecutive and increase beginning with 1.
CAUSE: All previous dm_addesignature audit records must be present.
ACTION: Verify that one or more audit records were deleted. Objects in this state can no longer be signed.
PARAMS: The first parameter is the number electronic signature number. The second parameter is the object ID of the sysobject that is being signed.

ERROR: [DM_SYSOBJECT_E_ESIGN_CONTENT_HASH_FAILED]

SEVERITY: ERROR
DESCRIPTION: DSS Could not generate a hash value for object %s in format %s with hashing algorithm %s.
CAUSE: Hashing of the content data failed. A hash is made both before and after the signature page is added.
ACTION: Check the content error for more specific information about the failure.
PARAMS: The first parameter is the id of the sysobject which is being signed. The second parameter is the format of the content object being hashed. The third parameter is the hashing algorithm requested.

ERROR: [DM_SYSOBJECT_E_NAME_NOT_UNIQUE]

SEVERITY: ERROR
DESCRIPTION: SS The object_name of %s must be unique for %s type.
CAUSE: object_name of specified system defined subtype of sysobject must be unique.
ACTION: Specify a unique name.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_UNFREEZE]

SEVERITY: ERROR
DESCRIPTION: S The %s sysobject can not be unfrozen.
CAUSE: The current sysobject can not unfrozen. It may participate in frozen assemblies or be an older version of the current version tree.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_SCHED_PASSED]

SEVERITY: ERROR
DESCRIPTION: SSDS The date %s scheduled to %s the object %s is smaller than the current time %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_NEED_ACTIVE_RETAINER_OBJ]

SEVERITY: ERROR
DESCRIPTION: SD The operation %s applied to a sysobject requires the retainer %s to be non-inactive.
CAUSE: A user tried to execute a retainer-specific operation on a retainer which is inactive.
ACTION: Make sure that the object is either an active or locked retainer.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_RELATE_ACCESS2]

SEVERITY: ERROR
DESCRIPTION: SSS No relate access to sysobject %s, since %s %s is protected. CAUSE:You do not have sufficient permission to relate this sysobject. This could be because of insufficient permission on the sysobject itself, or on the sysobjects primary cabinet.
CAUSE:
ACTION: Fix the permit of the specified object.
PARAMS:

ERROR: [DM_SYSOBJECT_E_IS_DELETED]

SEVERITY: ERROR
DESCRIPTION: S The sysobject %s has been deleted and can not be updated/deleted.
CAUSE: User tried to update/delete a deleted object.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ACL_REVISE_GROUP]

SEVERITY: ERROR
DESCRIPTION: SSSS Failed to revise group name of the ACL %s in domain %s of %s %s.
CAUSE: Failed to revise the group name in the associated ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_FIND_LABEL]

SEVERITY: ERROR
DESCRIPTION: SS Cannot find %s version label for %s sysobject.
CAUSE: Cannot find the specified version label in this sysobjects the version hierarchy.
ACTION: Specify a valid label.
PARAMS:

ERROR: [DM_SYSOBJECT_E_SETTIME_MODIFY_FAIL]

SEVERITY: ERROR
DESCRIPTION: S A failure occurred while trying to update set_time of content object: database error message was %s
CAUSE: Database system failure.
ACTION: The database system error message may indicate how to repair the error.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CONTENTS_SHARED]

SEVERITY: ERROR
DESCRIPTION: S Can not change the content of %s sysobject since it is shared.
CAUSE: User tried to modify the a_content_type of a sysobjec where the content is being shared by multiple sysobject.
ACTION: Try a setfile instead.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_PARTS]

SEVERITY: ERROR
DESCRIPTION: S No parts exists for %s sysobjects.
CAUSE: User tried to perform a compound document operation such as removepart, where none exists.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_ACL_SOURCE]

SEVERITY: ERROR
DESCRIPTION: The destinated ACL source is invalid.
CAUSE: The server is told an invalid source to inherit ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_FIXED_ILABELS]

SEVERITY: ERROR
DESCRIPTION: S Version label %s is internal and cannot be changed.
CAUSE: An internal version label is used during the checkin operation.
ACTION: Try again with a different version label.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_UNLINKCOMPOSITE]

SEVERITY: ERROR
DESCRIPTION: DLS Cannot unlink composite with ID %s at position %d from %s sysobject.
CAUSE: Could not unlink the composite at the specified position number, since the composite id does not exist at the specified position number.
ACTION: Try again with a valid composite id and position number.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NEED_READ_OR_RET_USER_MANAGER]

SEVERITY: ERROR
DESCRIPTION: SSS The session user %s needs to have READ permit on the sysobject %s or a retention user/manager in order to call %s.
CAUSE: A user wants to perform some operation (e.g., addretention) which requires the user to either have READ permit on the object or be a retention user/manager of the sysobject.
ACTION: Make sure the user has enough privilege.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NEW_SAVENEW]

SEVERITY: ERROR
DESCRIPTION: Cannot execute saveasnew operation on an object which has never been saved to the docbase.
CAUSE: The source object of the saveasnew operation is not a persistent object in the docbase. The object must first be saved to the docbase before it can be used in a saveasnew request.
ACTION: Check the application logic. If the action performed is on a newly created object, perhaps a simple save is appropriate.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_METHOD_TIMED_OUT]

SEVERITY: ERROR
DESCRIPTION: S eSignature Method Timed Out Please increase the timeout_max and timeout_default values for (%s) method
CAUSE: When a huge size file (50mb) is submitted for eSign, fusion.exe takes 40 mins to eSign. Workaround is to increase timeout parameters for eSign Method.
ACTION: Ask your Documentum Administrator to correct it.
PARAMS:

ERROR: [DM_SYSOBJECT_E_UPDATE_RETAIN_UNTIL_INVALID_OBJECT]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid sysobject
CAUSE: An invalid object id was specified for UPDATE_RETAIN_UNTIL_DATE apply method
ACTION: Supply a valid sysobject id.
PARAMS:

ERROR: [DM_SYSOBJECT_E_FAILED_CHECK_FOR_PARKED_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SD Failed to check if any content object for the sysobject %s , ID : %s is parked.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_OBJECT_NOT_CHECKED_IN]

SEVERITY: ERROR
DESCRIPTION: D Object %s is checked out. Objects must be checked in to be signed.
CAUSE: A signature cannot be added to a checked-out sysobject..
ACTION: Check-in the sysobject that is to be signed..
PARAMS: The first parameter is the object ID of the sysobject that is being signed..

ERROR: [DM_SYSOBJECT_E_CANT_VERSION_LOCKED]

SEVERITY: ERROR
DESCRIPTION: SS Cannot create a new version of sysobject %s since its locked by user %s.
CAUSE: Cannot create a new version of a locked sysobject.
ACTION: Coordinate your change with the user who holds the lock.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_READ_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S Cannot access content for (%s) sysobject
CAUSE: Content for the specified sysobject cannot be read.
ACTION: Look at the following errors on the error message queue for more detail.
PARAMS:

ERROR: [DM_SYSOBJECT_E_SETSTORAGE_UNABLE_TO_VALIDATE_STORAGE]

SEVERITY: ERROR
DESCRIPTION: S Unable to validate the specified storage area name %s
CAUSE: A communication error occured while attempting to validate the storage area name specified, with the content server.
ACTION: Check the server log for any errors.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_FROZEN]

SEVERITY: ERROR
DESCRIPTION: S The %s sysobject is not frozen.
CAUSE: User tried to unfreeze a non-frozen sysobject.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CHANGE_RETAINER_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Cant change the value of aging_method attribute of an existing retainer object (%s).
CAUSE: : This error occurs when attempting to change the aging_method of a dm_retainer object.
ACTION: Cannot change the aging_method attribute value of an existing dm_retainer object. Create a new dm_retainer and attach it to object(s).
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_REGISTER]

SEVERITY: ERROR
DESCRIPTION: SS Could not register the specified %s event for %s sysobject.
CAUSE: The specified event could not be registered. Most likely bad event name specified.
ACTION: Correct the event name and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_FETCH_FOLDER]

SEVERITY: ERROR
DESCRIPTION: D Failed to fetch the folder %s.
CAUSE: The given folder id may be invalid.
ACTION: Specify the right folder id and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_STORE_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S Cannot store content pointed by file %s
CAUSE: The system could not store specified file as part of this sysobject, probably because of an invalid file name.
ACTION: Try again with valid file name.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_AUDIT_CREATION_FAILED]

SEVERITY: ERROR
DESCRIPTION: D An electronic signature audit record for object %s could not be created.
CAUSE: The signature process failed because an audit record could not be created.
ACTION: Verify that audit records can be created.
PARAMS: The first parameter is the object ID of the sysobject that is being signed.

ERROR: [DM_SYSOBJECT_E_DUPLICATED_JMS_SERVLET_NAME]

SEVERITY: ERROR
DESCRIPTION: S The repeating attribute servlet_name contains a duplicate for %s.
CAUSE: Failed to maintain unique servlet_name values while editing these attributes.
ACTION: Remove attribute values to make servlet_name unique.
PARAMS:

ERROR: [DM_SYSOBJECT_E_APPLY_ADHOC_ACL]

SEVERITY: ERROR
DESCRIPTION: SSIISSSS Failed to %s ACE (%s, %d, %d) to the ACL %s in name space %s for %s %s.
CAUSE: Error found while applying the add-hoc list to the ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ILLEGAL_FLOATING_NUMBER]

SEVERITY: ERROR
DESCRIPTION: S The floating number, %s, is either out of range, illegal, or specifies a zero other than 0 or 0.0.
CAUSE: The SET_CONTENT_ATTRS apply call fails to be executed due to an error in the FLOAT function. The error may be caused by an overflowed floating number or a specification of a zero value other than 0 or 0.0.
ACTION: Check the literal specified in the FLOAT function to see if there exists any illegal symbol. Note that zero is only allowed to be specified as 0 or 0.0. Correct your syntax and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DELETE_RELATION_EXISTS]

SEVERITY: ERROR
DESCRIPTION: SS Cannot delete object %s since dm_relation object(s) %s exists with integrity_kind set to 1.
CAUSE: Cannot delete an object referenced by a dm_relation object with integrity kind set to 1.
ACTION: Delete the dm_relation object that references this object, and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ACCESS_FILE]

SEVERITY: ERROR
DESCRIPTION: SS Cannot access file %s due to Operating System error: %s
CAUSE: File or pointer could not be read. Most likely invalid path or pointer is specified for content.
ACTION: Specify a correct path or pointer and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_ASSEMBLY]

SEVERITY: ERROR
DESCRIPTION: S No assembly object is attached sysobject named %s.
CAUSE: The current sysobject does not have any assembly object attached to it.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_DEMOTE_BASE]

SEVERITY: ERROR
DESCRIPTION: SD Demote failed since the current state %s is a base state of the associated policy %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_BAD_FROM_STATE]

SEVERITY: ERROR
DESCRIPTION: SDS Cannot %s the sysobject %s from the state %s.
CAUSE: User has specified an invalid from state in the operation. A state is an invalid from state in an operation either it does not exist in the associated policy object or it is not the right from state.
ACTION: Make sure the state does exist in the associated policy object and it is the right from state.
PARAMS:

ERROR: [DM_SYSOBJECT_E_LIGHTWEIGHT_CANNOT_CREATE]

SEVERITY: ERROR
DESCRIPTION: Cannot create a new lightweight sysobject
CAUSE: Could not successfully create a new lightweight sysobject. Either the network connection or database connection could not be established, or other error reported in the previous message.
ACTION: See your System Administrator.
PARAMS:

ERROR: [DM_SYSOBJECT_E_USER_DEF_ACL]

SEVERITY: ERROR
DESCRIPTION: S ACL inheritance failed, due to missing ACL in the User %s.
CAUSE: The User to inherit the ACL doesnt have an ACL defined.
ACTION: Associated an ACL with the User.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ATTACH_EXPIRED_RETENTION]

SEVERITY: ERROR
DESCRIPTION: DS You cannot attach the retainer object %s to sysobject %s because the retention is expired.
CAUSE: A user tried to attach a retainer object whose retention is already expired. This can happen when either the retention_interval is a negative value (retention_rule_type is INTERVAL) or the retention_date is older than the current date (retention_rule_type is DATE).
ACTION: You must attach a retainer object with valid retention period.
PARAMS:

ERROR: [DM_SYSOBJECT_E_TYPE_DEF_ACL]

SEVERITY: ERROR
DESCRIPTION: S ACL inheritance failed, due to missing ACL in the type %s.
CAUSE: The type to inherit the ACL doesnt have an ACL defined.
ACTION: Associated an ACL with the type.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_AUDIT_RECORD_NULL_ID]

SEVERITY: ERROR
DESCRIPTION: Couldnt read object id of audit record.
CAUSE: The audit record r_object_id attribute has an invalid value.
ACTION: Check the dm_addesignature audit records for the object that is being signed or verified.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_PRIV_TO_CHG_LOC]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) does not have enough privilege to copy/move/link/unlink %s sysobject.
CAUSE: Must have CHANGE_LOCATION privilege to copy/move/link/unlink objects.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ATTACH_RETAINER_TO_RETAINER]

SEVERITY: ERROR
DESCRIPTION: DS You cannot attach the retainer object %s to sysobject %s which is also a retainer.
CAUSE: A user tried to attach a retainer object to another retainer object.
ACTION: A retainer can never be attached to another retainer object.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CIRC_LINK]

SEVERITY: ERROR
DESCRIPTION: S %s sysobject can not be contained in itself.
CAUSE: A sysobject is contained in itself.
ACTION: Circluar links are not allowed. No action.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_SOURCE]

SEVERITY: ERROR
DESCRIPTION: SS The ACL source specified %s for the sysobject %s is invalid. The source could be either FOLDER, TYPE or USER.
CAUSE: Invalid source is given to useacl.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CHANGE_CONTENT]

SEVERITY: ERROR
DESCRIPTION: DSS Content [%s] cannot be changed for sysobject [%s]. Reason: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DELETE_SHARED_BY_LIGHTWEIGHT]

SEVERITY: ERROR
DESCRIPTION: S Cannot delete object %s because it is shared by lightweight objects.
CAUSE: You cannot delete a sysobject that is shared by one or more lightweight objects.
ACTION: Make sure that the sysobject is not referenced in the i_sharing_parent property of any unmaterialized lightweight objects.
PARAMS:

ERROR: [DM_SYSOBJECT_E_REORDERING_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Could not recompute part order numbers for sysobject named %s. (See your sysadmin)
CAUSE: During reordering of part order number, database errors have prevented the server to complete this task.
ACTION: More exact reasons are in other errors along with this message. More likely database is not available or some database limit has been reached.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_INVALID_PRE_SIGNATURE_HASH_FORMAT]

SEVERITY: ERROR
DESCRIPTION: S The format of the preSignatureHash argument %s is invalid.
CAUSE: The server supports a fixed set of hash values. Initially only the format SHA-1 is supported.
ACTION: Verify the hash format of the preSignatureHash argument passed in the call to addesignature.
PARAMS: The first parameter is the hash format.

ERROR: [DM_SYSOBJECT_E_INVALID_PERMIT]

SEVERITY: ERROR
DESCRIPTION: IS Invalid permit %d specified for %s sysobject.
CAUSE: You have specified a permit that is outside the valid range.
ACTION: Specify a valid permit number.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANNOT_CHANGE_RETENTION_ATTRS_WHEN_SHARED]

SEVERITY: ERROR
DESCRIPTION: S Cannot change any retention-related attribute of %s since it is shared by some lightweight object and its allow_propagating_changes flag is false.
CAUSE: User has tried to change some ftindex attribute of an object which is shared by some lightweight object and its allow_parent_ftchange flag is false.
ACTION: User should avoid changing any ftindex attribute on the parent object when it is shared by lots of children object. However, if it is not the case, then user can set the allow_parent_ftchange flag to true so that the operation can succeed.
PARAMS:

ERROR: [DM_SYSOBJECT_E_LINK_PERMIT]

SEVERITY: ERROR
DESCRIPTION: S Linking or unlinking to the folder %s failed. WRITE permit is required on the folder.
CAUSE: Require WRITE permit on the folder in order to link/unlink.
ACTION: Change the permissions of the folder and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_VERIFICATION_FAILED]

SEVERITY: ERROR
DESCRIPTION: D The electronic signature for object %s is invalid.
CAUSE: Verification of a pre-existing electronic signature failed.
ACTION: Verify the validity of the audit record hash data.
PARAMS: The first parameter is the object ID of the sysobject that is being signed.

ERROR: [DM_SYSOBJECT_E_SETSTORAGE_EXISTING_CONTENT_OBJECT]

SEVERITY: ERROR
DESCRIPTION: setstorage API cannot be executed on an existing dmr_content object.
CAUSE: cannot call setstorage on an existing dmr_content object.
ACTION: Either check out the object or wait until retention is expired.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_PAGE_NUM]

SEVERITY: ERROR
DESCRIPTION: LSL Invalid page number = %d for %s sysobject. Maximum page count is %d.
CAUSE: You have attempted to access a non-existent page in a multi-page document.
ACTION: Try a valid page number.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_XPERMIT_NAME]

SEVERITY: ERROR
DESCRIPTION: SS There exists at least one invalid extended permission name in %s for operation %s.
CAUSE: At least one of the extended permission names provided in the list is invalid. Currently, only the following names for extended permissions are supported: (1) execute_proc (2) change_location (3) change_state (4) change_permit (5) change_owner
ACTION: Only supply names in the above list.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_FIND_METHOD]

SEVERITY: ERROR
DESCRIPTION: S Cant find method %s.
CAUSE: The requested signature page method could not be found.
ACTION: Verify the existence of the signature page method.
PARAMS: The first parameter is the method name.

ERROR: [DM_SYSOBJECT_E_NONEXISTENT_LABEL]

SEVERITY: ERROR
DESCRIPTION: SS Label %s does not exist in %s sysobject.
CAUSE: Tried to drop a non-existent label.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_BAD_ORDER]

SEVERITY: ERROR
DESCRIPTION: L Invalid order number %d specified. Must be positive and non-zero.
CAUSE: You have specified a negative or zero order number during an insertcomp or removecomp operation. The order number must be positive. (The zero order number is resevered for the composite itself.)
ACTION: Specify a positive order number with the insertcomp or removecomp operation.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_SIGNATURE_METHOD_FAILED_02]

SEVERITY: ERROR
DESCRIPTION: SSL Method %s failed :: Arguments %s :: Method Returned %d
CAUSE: The esignature method has failed / aborted.
ACTION: Look in the server log for errors pertaining to this failure.
PARAMS: The first parameter is the method name. The second parameter is the argument list. The third parameter is the returned value from esign method

ERROR: [DM_SYSOBJECT_E_ACL_NEED_NAME]

SEVERITY: ERROR
DESCRIPTION: SSS Need an accessor name for operation %s of %s %s to succeed.
CAUSE: User name is missing in an operation that requires it.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_CREATE_TEMP_FILE]

SEVERITY: ERROR
DESCRIPTION: SS Unable to create temporary file %s. Error: %s.
CAUSE: A file system error occured when trying to create a temprorary file.
ACTION: Verify that the name and path to the temporary file are valid.
PARAMS: The first parameter is the temporary file name. The second parameter is the operating system error code.

ERROR: [DM_SYSOBJECT_E_ESIGN_USER_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SS The optional user name argument %s if provided must match the name of the logged in user %s.
CAUSE: The user name argument and the name of the logged in user do not match.
ACTION: Either omit the user name argument or pass in the name of the logged in user.
PARAMS: The first parameter is the user name that was passed into the function The secord parameter is the name of the user who logged in.

ERROR: [DM_SYSOBJECT_E_FAILED_TO_TRIGGER_ONE_OR_MORE_CLIPS]

SEVERITY: ERROR
DESCRIPTION: D One or more clips could not be triggered for sysobject %s.
CAUSE: Error occurred while trying to trigger clips related to a sysobject.
ACTION: See the server log for further details.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_READ_ACCESS2]

SEVERITY: ERROR
DESCRIPTION: SSS No read access to sysobject %s since %s %s is protected. CAUSE:You do not have read access to this sysobject. ACTION:See your System Administrator or the owner of the sysobject.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_UPDATE_RETAIN_UNTIL_UNABLE_TO_COMMIT_BATCH]

SEVERITY: ERROR
DESCRIPTION: I An error occured while attempting to commit changes made to %d objects
CAUSE: A database error occured while committing a batch of objects after having updated the i_retain_until attribute of those objects.
ACTION: Refer to other error messages for the session and take corrective action suggested for those errors.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_LINKCOMPOSITE]

SEVERITY: ERROR
DESCRIPTION: DSSS Cannot link composite with ID %s and version label %s, version label %s must exist in %s sysobject.
CAUSE: Could not link the composite to the sysobject, since the version label of the sysobject does not exist.
ACTION: Specify a valid version label for the given sysobject and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NEED_CONDITIONAL_RETAINER]

SEVERITY: ERROR
DESCRIPTION: SD The operation %s requires the object %s to have conditional retainers attached.
CAUSE: An operation requiring that conditional retainer was attempted on a sysobject without any conditional retainers.
ACTION: Attach conditional retainers and then retry the operation.
PARAMS:

ERROR: [DM_SYSOBJECT_E_LINK_PERMIT2]

SEVERITY: ERROR
DESCRIPTION: SD Linking or unlinking to the folder %s failed on sysobject %s. WRITE permit is required on the folder, when using folder security.
CAUSE: Require WRITE permit on the folder in order to link/unlink.
ACTION: Change the permissions of the folder and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_PRE_SIGNATURE_HASH_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: DSS Mismatch between object %s with hash string %s and preSignatureHash argument %s.
CAUSE: The preSignatureHash argument was found to be invalid.
ACTION: Verify that the client application is properly hashing the document prior to calling addesignature.
PARAMS: The first parameter is the object ID of the sysobject that is being signed. The second parameter is the hash of the sysobject. The third parameter is the hash value that was passed into addesignature.

ERROR: [DM_SYSOBJECT_E_STORAGE_TYPE_CHANGE_DISALLOWED_PARKED_STATE]

SEVERITY: ERROR
DESCRIPTION: SI Cannot change a_storage_type of %s because content for page %d is in parked state
CAUSE: User changed the a_storage_type of an object whose content is in parked state and is not directly accessible to the Content Server to process the storage type change. ACTION:Wait until the content is uploaded from parked state to actual storage destination and then change the storage type.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_AUDIT_RECORD_UNSIGNED]

SEVERITY: ERROR
DESCRIPTION: D Audit record %s for the existing electronic signature is unsigned.
CAUSE: dm_addesignature audit records must be signed. Since audit records of this type are automatically signed finding an unsigned record is unexpected.
ACTION: Verify the status of the unsigned dm_addesignature audit record.
PARAMS: The first parameter is the id of the audit record which was found to be unsigned.

ERROR: [DM_SYSOBJECT_E_NO_VRSN_ACCESS2]

SEVERITY: ERROR
DESCRIPTION: SSS No version access for sysobject %s since %s %s is protected. CAUSE:You do not have sufficient permission to version (checkout) this sysobject. This could be because of insufficient permission on the sysobject itself, or on the sysobjects primary cabinet.
CAUSE:
ACTION: First determine if it is the sysobject, or its cabinet, that you do not have version access to. Then, see your System Administrator or the owner of the sysobject or cabinet.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CREATE_VERSION_WHEN_SHARED]

SEVERITY: ERROR
DESCRIPTION: S Cannot create a new version of the sysobject named %s when it is shared.
CAUSE: You cannot version a sysobject that shares its properties with one or more lightweight objects.
ACTION: To version the sysobject, first detach it from any lightweight objects that share its properties.
PARAMS:

ERROR: [DM_SYSOBJECT_E_UPDATE_CABID]

SEVERITY: ERROR
DESCRIPTION: S Failed to update the cabinet ID of the sysobjects. This change is necessary due to the change of the primary link of the folder %s.
CAUSE: Failed to update the cabinet IDs of all the sysobjects.
ACTION: Retry the operation. If it still fails due to database problems, contact your sysadmins to fix the reported database errors and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_PREEXISTING_SIGNATURE_INVALID]

SEVERITY: ERROR
DESCRIPTION: D The previous electronic signature for object %s is invalid. New signatures may not be added.
CAUSE: An object cannot be signed if a pre-existing signature is invalid.
ACTION: Verify the validity of any existing electronic signatures.
PARAMS: The first parameter is the object ID of the sysobject that is being signed.

ERROR: [DM_SYSOBJECT_E_CAUSE]

SEVERITY: ERROR
DESCRIPTION: : A user tried to change an existing rendition or delete one when the object is under retention where at least one retainer has the rendition_rule set to ALL (i.e., 0).
CAUSE:
ACTION: You can only change/delete rendition when the object is not under retention or all of its associated retainers have the rendition_rule set to PRIMARY (i.e., 1).
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_ALLOW_DEMOTE]

SEVERITY: ERROR
DESCRIPTION: SD Demote failed since the sysobjects current state %s of policy %s is not allowed to demote.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ADD_NOTE]

SEVERITY: ERROR
DESCRIPTION: S Cannot add note sysobject named %s
CAUSE: Reserved for future use.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_WRITE_TO_TEMP_FILE]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to write content to temporary file %s at position %s. Error: %s.
CAUSE: An error occurred while writing a content file to a temporary file.
ACTION: Verify the validity of the content for the sysobject that is being signed.
PARAMS: The first parameter is the temporary file path. The second parameter is the file position where the error occurred. The third parameter is the OS error number..

ERROR: [DM_SYSOBJECT_E_NOT_INSTALLED]

SEVERITY: ERROR
DESCRIPTION: SD %s failed because the associated policy %s is not INSTALLED.
CAUSE: The policy object is not in INSTALLED state.
ACTION: You must install the policy object before the sysobject can be promoted to the target state.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_WRITE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S No write access sysobject named %s. CAUSE:You do not have sufficient permission to write this sysobject. This could be because of insufficient permission on the sysobject itself, or on the sysobjects primary cabinet.
CAUSE:
ACTION: First determine if it is the sysobject, or its cabinet, that you do not have write access to. Then, see your System Administrator or the owner of the sysobject or cabinet.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_NEW_ATOMIC]

SEVERITY: ERROR
DESCRIPTION: SS %s operation in atomic mode can not apply to a new sysobject named %s.
CAUSE: The operation in atomic mode can only apply to an existing sysobject.
ACTION: Save the sysobject first and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_FORCE_DELETE_CANT_EXPUNGE_SUBCONTENT_OBJECT]

SEVERITY: ERROR
DESCRIPTION: DDD force delete failed because an error occured during deletion of a subcontent object (%s), content object is %s, Sysobject is %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_A_CONTROLLING_APP_VALUE]

SEVERITY: ERROR
DESCRIPTION: S The a_controlling_app value of %s is invalid. Application codes can only contain alphanumeric characters or _.
CAUSE: a_controlling_app values can only contain alphanumeric values or _. No whitespace or other characters are allowed. Also, the application code value of dm_all_applications is not not allowed.
ACTION: Correct the value of a_controlling_app
PARAMS: The first parameter is the value that was entered for a_controlling_app

ERROR: [DM_SYSOBJECT_E_CANT_VERSION_A_RETAINER]

SEVERITY: ERROR
DESCRIPTION: S Cannot version %s since it is a retainer object.
CAUSE: User has tried to create a new version of a retainer object.
ACTION: Retainer objects are not allowed to be versioned.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ONLY_ATTACH_ACTIVE_RETAINER]

SEVERITY: ERROR
DESCRIPTION: DS You cannot attach a locked or inactive retainer object %s to sysobject %s.
CAUSE: A user tried to attach a locked or inactive retainer object to a sysobject.
ACTION: A locked or inactive retainer can never be attached to another retainer object.
PARAMS:

ERROR: [DM_SYSOBJECT_E_OBJECT_NOT_CHECKEDOUT]

SEVERITY: ERROR
DESCRIPTION: SS Object %s has not been checked out prior to calling %s API
CAUSE: This error occurs when an application calls setfile or setcontent API to set the content of an existing page of an existing sysobject thats using a retention enabled CA Store. To alter the content page of a sysobject that is using a retention enabled CA store, the object must be checked out first.
ACTION: checkout the sysobject and retry changing the content.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CHANGE_CONTAINMENT_UNDER_RETENTION]

SEVERITY: ERROR
DESCRIPTION: S You can not change/add/remove any containment to sysobject %s when it is under retention unless you are a retention manager.
CAUSE: A user who is not a retention manager tried to change/add/remove a containment when the parent object is under retention.
ACTION: You can only change/add/remove any containment when the parent object is not under retention or you need to be a retention manager.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_ATTACHABLE_TYPE]

SEVERITY: ERROR
DESCRIPTION: SD The object type %s is not an acceptable type to policy %s.
CAUSE: The type of the object you tried to attach the policy is not a subtype of the primary type, or is not an acceptable subtype as listed in included_type[] repeating attribute.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_GET_VERIFY_AUDIT_RESULTS]

SEVERITY: ERROR
DESCRIPTION: D Audit record %s for the previous electronic signature has no verification results.
CAUSE: dmVerifyAuditRecord failed returned an empty result collection.
ACTION: Verify the status of the dm_addesignature audit record.
PARAMS: The first parameter is the id of the audit record which is being verified.

ERROR: [DM_SYSOBJECT_E_CANT_FIND_USER]

SEVERITY: ERROR
DESCRIPTION: S The user %s specified does not exist.
CAUSE: non-exist user is found.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_FROZEN]

SEVERITY: ERROR
DESCRIPTION: S The %s sysobject is frozen.
CAUSE: User tried to update/delete a frozen sysobject.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_SIGNATURE_SOURCE_ALREADY_EXISTS]

SEVERITY: ERROR
DESCRIPTION: DD Object %s appears unsigned but a signature source content object %s already exists for it.
CAUSE: Unsigned objects will not be signed if a rendition with the page modifier dm_sig_source already exists. This prevents the re-signing of sysobjects if there dm_addesignature audit records were all deleted.
ACTION: Verify that sysobject was already signed. Determine what happened to the audit records.
PARAMS: The first parameter is the object ID of the sysobject that is being signed. The second parameter is the dm_sig_source object ID.

ERROR: [DM_SYSOBJECT_E_ESIGN_CURSOR_ERROR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the creation of a cursor needed for reading addesignature audit trail records (%s).
CAUSE: A SQL statement that queries the Documentum schema has failed. This error message indicates that a failure occurred during the parsing of the generated SQL statement by the underlying RDBMS.
ACTION: The error message from the RDBMS is shown in the message. Use that error message to figure out what has happened.
PARAMS: The first parameter is the database error number.

ERROR: [DM_SYSOBJECT_E_TRIGGER_COND_RET_DISALLOWED_PARKED_STATE]

SEVERITY: ERROR
DESCRIPTION: SD Cannot trigger Conditional Retainer of sysobject %s because one of the contents with ID %s is in Parked State.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_SAVE_ORIGINAL]

SEVERITY: ERROR
DESCRIPTION: The original content could not be saved.
CAUSE: The original content could not be saved with the page modifier dm_sig_source.
ACTION: Verify the status of the sysobject content in the signature format.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_FIND_GROUP]

SEVERITY: ERROR
DESCRIPTION: S The group %s specified does not exist.
CAUSE: non-exist group found
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANNOT_BRANCH_ON_HOLD]

SEVERITY: ERROR
DESCRIPTION: S Cannot branch sysobject %s because this sysobject is under retention hold.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_FIND_CHRONICLE]

SEVERITY: ERROR
DESCRIPTION: D %s chronicle identifier does not exist.
CAUSE: a non-existant chroncile id is specified.
ACTION: Specify an existing chroncile id.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_WRITE_ACCESS2]

SEVERITY: ERROR
DESCRIPTION: SSS No write access for sysobject %s since %s %s is protected. CAUSE:You do not have sufficient permission to write this sysobject. This could be because of insufficient permission on the sysobject itself, or on the sysobjects primary cabinet.
CAUSE:
ACTION: First determine if it is the sysobject, or its cabinet, that you do not have write access to. Then, see your System Administrator or the owner of the sysobject or cabinet.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_LOCK]

SEVERITY: ERROR
DESCRIPTION: SS Cannot lock %s sysobject, locked by %s.
CAUSE: Could not lock this sysobject since it is already is locked by another user.
ACTION: Ask the other party to unlock or checkin the sysobject.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_REPLACEP]

SEVERITY: ERROR
DESCRIPTION: S Cannot replace the self reference containment object for %s sysobject.
CAUSE: User tried to replace the self reference containment object.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_STORAGE_TYPE_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SSSSS Storage type for object %s cannot be changed from %s to %s, because %s is a retention enabled store and %s is not
CAUSE: This error occurs when a_storage_type attribute of an existing sysobject is changed from a retention enabled CA store to a non-retention enabled CA store. A CA store is retention enabled if it is configured to require a retention period or is configured to use a default retention date.
ACTION: You cannot initiate an implicit migration of content from a retention enabled CA store to non-retention enabled CA store. Specify a retention enabled store object name if you want to change the storage type and retry the operation.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_PRIMARY_FOLDER]

SEVERITY: ERROR
DESCRIPTION: Failed to derive ACL from the primary folder, since cabinets have no primary folders.
CAUSE: Try to derive ACL from primary folder which cabinets do not have.
ACTION: Derive ACL from other resources than primary folder.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_PRUNEI]

SEVERITY: ERROR
DESCRIPTION: DS Cannot prune %s sysobject: %s
CAUSE: One or more previous database operations were erroneous. ACION: Examine the previous error messages for more detail.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_INSERTP]

SEVERITY: ERROR
DESCRIPTION: S Cannot insert part before the self reference containment object for %s sysobject.
CAUSE: User tried to insert a part before the self reference containment object.
ACTION: Try again with a valid insertpart.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_UNSUPPORTED_HASH_ALGORITHM]

SEVERITY: ERROR
DESCRIPTION: S hash_algorithm %s is not supported
CAUSE: addeignature gets an unsupported Hash Algorithm parameter from dmcl
ACTION: SHA-1 is the only Supported Algorthm. Return error to the caller.
PARAMS: The first parameter is the unsupported Hash Algorithm supplied the dmcl/client

ERROR: [DM_SYSOBJECT_E_CANT_CHANGE_OWNER]

SEVERITY: ERROR
DESCRIPTION: S Must be a superuser/owner or anyone with change_owner permit to change the owner_name to %s.
CAUSE: Only a superuser can change the owner_name attribute of a sysobject. In ACL mode, we allow anyone with the change_owner permit to change the owner of the object.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INCONSISTENT_JMS_SERVLET_ATTRS]

SEVERITY: ERROR
DESCRIPTION: The number of jms servlet attributes (servlet_name, base_uri) is not consistent.
CAUSE: Failed to maintain same value count while editing these attributes.
ACTION: Add or remove attribute values to make them consistent.
PARAMS:

ERROR: [DM_SYSOBJECT_E_BAD_SCHED]

SEVERITY: ERROR
DESCRIPTION: SD The date %s scheduled to promote the object %s is a bad date.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CONTENT_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: DSS Could not retrieve content for the object %s in format %s with page modifier %s.
CAUSE: A rendition in the signature format for the sysobject could not be found.
ACTION: Make sure that the a sysobject has a rendition or primary content in the signature format. If this is not the first signature then a rendition with page modifier dm_sig_source must also exits.
PARAMS: The first parameter is the id of the sysobject which is being signed. The second parameter is the format of the content that could not be retrieved. A blank format indicates that the primary content was requested. The third parameter is the page modifier.

ERROR: [DM_SYSOBJECT_E_ESIGN_SIGNATURE_NUMBER_ERROR]

SEVERITY: ERROR
DESCRIPTION: D Invalid electronic signature number for object %s. Signature numbers must be consecutive and increase beginning with 1.
CAUSE: All previous dm_addesignature audit records must be present.
ACTION: Verify that one or more audit records were altered. Objects in this state can no longer be signed.
PARAMS: The first parameter is the object ID of the sysobject that is being signed.

ERROR: [DM_SYSOBJECT_E_CANT_BINDFILE]

SEVERITY: ERROR
DESCRIPTION: LSLS Cannot bind page %d of %s sysobject to page %d of %s sysobject.
CAUSE: Either invalid page number for src or dst in invalid object.
ACTION: Consult the other error messages for this operation for more help.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INCONSISTENT_JMS_SERVLET_ATTRS2]

SEVERITY: ERROR
DESCRIPTION: The number of repeating attributes (servlet_name, base_uri, and supported_protocol) is not consistent.
CAUSE: Failed to maintain same value count while editing these attributes.
ACTION: Add or remove attribute values to make them consistent.
PARAMS:

ERROR: [DM_SYSOBJECT_E_LIGHTWEIGHT_CANNOT_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Cannot save a lightweight sysobject (%s)
CAUSE: Could not successfully create a new lightweight sysobject. Either the network connection or database connection could not be established, or other error reported in the previous message.
ACTION: See your System Administrator.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ILLEGAL_PARAMETER_VALUE]

SEVERITY: ERROR
DESCRIPTION: SSSS You have specified a wrong value (%s) for parameter (%s) in the apply method (%s). The legal values are (%s)
CAUSE: An illegal value was used for the specified parameter in the apply method.
ACTION: Use one of the legal values as listed in the error message.
PARAMS:

ERROR: [DM_SYSOBJECT_E_DISALLOWED_OP_FOR_UNMATERIALIZED_OBJ]

SEVERITY: ERROR
DESCRIPTION: SD The operation %s performed on object %s is disallowed because the lightweight object is not materialized
CAUSE: The specified operation, most likely a setter, was performed on an unmaterialized lightweight object which is not allowed on server side. If it happened on DFC and the lightweight type allows auto materialization, DFC should materialized the lightweight object before sending the request to server.
ACTION: Materialize the lightweight object and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_MUST_BE_OWNER]

SEVERITY: ERROR
DESCRIPTION: S You must be the owner (or superuser) to perform %s operation.
CAUSE: To do attach, you must be the owner or have superuser privilege.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_UPDATE_RETAIN_UNTIL_INVALID_ARGUMENTS]

SEVERITY: ERROR
DESCRIPTION: Invalid arguments specified for UPDATE_RETAIN_UNTIL_DATE apply method
CAUSE: UPDATE_RETAIN_UNTIL_DATE apply method was executed with invalid arguments.
ACTION: Refer to the Content Server Administrator guide for valid arguments.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOCOMPS_TO_THAW]

SEVERITY: ERROR
DESCRIPTION: S The %s sysobject has no assembled components to be thawed.
CAUSE: The current sysobject has no assembled components to thaw.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_DECRYPT_PASSWORD]

SEVERITY: ERROR
DESCRIPTION: I Password decryption failed with error code %d.
CAUSE: The passed in password could not be successfully decrypted.
ACTION: Check the password format..
PARAMS: The first parameter is the error code .

ERROR: [DM_SYSOBJECT_E_ESIGN_FAILED_AUDIT_CREATION_FAILED]

SEVERITY: ERROR
DESCRIPTION: D An esignature audit record for object %s could not be created for the failed addesignature API Call
CAUSE: The signature process failed when trying to create dm_addesignature_failed audit.
ACTION: Verify that audit records can be created.
PARAMS: The first parameter is the object ID of the sysobject that is being signed.

ERROR: [DM_SYSOBJECT_E_LIGHTWEIGHT_UTILITIES_FAILED]

SEVERITY: ERROR
DESCRIPTION: S The server RPC LIGHTWEIGHT_UTILITIES failed for one or more Shared Parents in dm_job_request.The EXECUTION_MODE was %s.
CAUSE: Look at the server log for detailed error messages.
ACTION: Look in the dm_job_request type for entries with request_completed to true and job_name dm_Lightweight_Utilities and run LIGHTWEIGHT_UTILITIES RPC manually in recovery mode by passing RECOVERY_MODE,B,T as one of the arguments. If the errors persist report them with appropiate error messages in the logs.
PARAMS:

ERROR: [DM_SYSOBJECT_E_RETAINERS_NOT_COMPATIBLE]

SEVERITY: ERROR
DESCRIPTION: SDD The operation %s applied to a sysobject requires the two retainer objects %s and %s to be compatible.
CAUSE: A user tried to swap two incompatible retainers on an object.
ACTION: Make sure that the two retainer objects are compatible. Two retainers are compatible if and only if the following attributes are identical: . owner_name . acl_domain . acl_name . retainer_strategy . r_retention_status . retention_rule_type . rendition_rule . enforcement_rule . immutability_rule . aging_method
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CREATE_JOB_REQUEST_FOR_SHARED_PARENT]

SEVERITY: ERROR
DESCRIPTION: D Cant Create Job Request for Shared Parent %s after retention was pushed successfully.
CAUSE: This error occurs after the retention is pushed for the shared parent and we try and create a job request to propagate the retention changes for all its lightweight children.
ACTION: Look at the server log for error messages.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_FETCH_ACL]

SEVERITY: ERROR
DESCRIPTION: SSSSS Failed to fetch the ACL %s in domain %s for %s %s. [%s]
CAUSE: Failed to fetch ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_SAVEASNEW_KEEP_STORAGE_INVALID_STORAGE_ON_TARGET]

SEVERITY: ERROR
DESCRIPTION: SS Storage (%s) does not exist in (%s) respository
CAUSE: User executed saveasnew api with keepOriginalStorages flag set to TRUE, to copy an object from one repository to another. But a storage area that exists in the source repository does not exist in the target repository.
ACTION: You cannot specify TRUE for keepOriginalStorages in the saveasnew Api because there is a storage incompatibility between the source and target repositories. Either create identically named storages and of the same storage type on both the repositories or specify FALSE for the keepOriginalStorages.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_DELETE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S No delete permit on %s sysobject.
CAUSE: You do not have the necessary permit to delete this sysobject. ACTION:See your System Administrator or the owner of the sysobject.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_NEED_TRIGGERED_CONDITIONAL_RETAINER]

SEVERITY: ERROR
DESCRIPTION: D The Object %s doesn not have any triggered conditional retainers attached.
CAUSE: Operation TRIGGER_CONDITIONAL_RETAINER failed because none of the retainers attached to the sysobject was triggered.
ACTION: Trigger all the conditional retainers attached to a sysobject and then retry the operation.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_REMOVE_RENDITION]

SEVERITY: ERROR
DESCRIPTION: LSS Cannot remove rendition number %d identified by %s format from %s sysobject.
CAUSE: Most likely this rendition does not exist.
ACTION: Try a valid rendition.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_REMOVE_RENDITION2]

SEVERITY: ERROR
DESCRIPTION: IS Rendition page %d is not removed for %s because retention period has not expired
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_FILE_AND_VERSION_MAPPING]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to find the sysobject r_object_id corresponding to the path %s and version %s due to database errors. The message from the database is: %s
CAUSE: Failed to execute the query that gets the object id with the given path to the sysobject and version number
ACTION: Fix the database problem as reported in the error message and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_UNLOCK]

SEVERITY: ERROR
DESCRIPTION: S Unsuccessful in removing the lock on %s sysobject.
CAUSE: The server was unable to remove the lock, most likely version mismatch or database problems.
ACTION: Correct the version mismatch or database problem first and try again. If there were database problems, there should be additional messages with this operation that explain the reasons.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_UNREGISTER]

SEVERITY: ERROR
DESCRIPTION: SS Could not unregister the specified %s event for %s sysobject.
CAUSE: The specified event could not be unregistered. Most likely bad event name specified.
ACTION: Correct the event name and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_CHECKEDOUT]

SEVERITY: ERROR
DESCRIPTION: S The specified %s sysobject is not checked out.
CAUSE: User tried to checkin a sysobject that is not checkout.
ACTION: Checkout the sysobject before checkin.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_STATE]

SEVERITY: ERROR
DESCRIPTION: SSD %s failed because the state %s is not in policy %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOLABELS]

SEVERITY: ERROR
DESCRIPTION: S Need one or more symbolic labels to mark/unmark %s sysobject.
CAUSE: Mark commands require one or more supplied symbolic labels.
ACTION: Specify one or more symbolic labels and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANNOT_MATERIALIZE]

SEVERITY: ERROR
DESCRIPTION: D Cannot materialize the lightweight object (%s)
CAUSE: System failed to materialize the specified lightweight object. The following are some possible reasons: a) There is no memory for creating a materialized object. b) The old parent can not either be found or cloned.
ACTION: Make sure there is enough memory and the old parent still exists.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NEED_NAME]

SEVERITY: ERROR
DESCRIPTION: S The %s objects must have an object_name.
CAUSE: The specified object type must have object_name.
ACTION: Specify a name.
PARAMS:

ERROR: [DM_SYSOBJECT_E_LENGTH_WIDEN_FAILED]

SEVERITY: ERROR
DESCRIPTION: The upgrade failed on widening sysobjects attribute lengths.
CAUSE: The database server may have problems widening the column length, or the attribute length may already be widen.
ACTION: Check database server log or use sql script(under dba) to upgrade.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ACL_CACHE]

SEVERITY: ERROR
DESCRIPTION: SS Error reported by the ACL cache of the sysobject %s. The message is: %s.
CAUSE: The ACL cache reports error.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_HASH_RENDITION_CONTENT]

SEVERITY: ERROR
DESCRIPTION: D The rendition to be signed for object %s could not be hashed.
CAUSE: The sysobjects content could not be hashed prior to signing.
ACTION: Verify that the sysobject has content in the signature format.
PARAMS: The first parameter is the object ID of the sysobject that is being signed.

ERROR: [DM_SYSOBJECT_E_BAD_CABINET]

SEVERITY: ERROR
DESCRIPTION: SD The sysobject %s has a bad primary cabinet ID %s.
CAUSE: Bad primary cabinet id.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_SYSOBJECT_E_SET_ATTR_SYNTAX_ERROR]

SEVERITY: ERROR
DESCRIPTION: S The parameters, %s, specified in the SET_CONTENT_ATTRS call contains syntax error.
CAUSE: The SET_CONTENT_ATTRS apply call fails to be executed due to a syntax error in the argument, parameters.
ACTION: The syntax in the argument, parameters, needs to be in the format of ={, =}. Correct your syntax and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_KEEP_RELATIONS]

SEVERITY: ERROR
DESCRIPTION: S Can not keep user/system defined relations for %s sysobject.
CAUSE: Previous errors have forced the server to abort the copying user/system defined relations.
ACTION: See previous error messages.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_PROXVAL_IN_JMSCONFIG]

SEVERITY: ERROR
DESCRIPTION: I Invalid projection_proximity_value value %d.
CAUSE: projection_proximity_value is invalid.
ACTION: Make sure projection_proximity_value is greater than 0.
PARAMS:

ERROR: [DM_SYSOBJECT_E_FAIL_ENTRY]

SEVERITY: ERROR
DESCRIPTION: SDDSD %s failed because the document %s does not satisfy the entry criteria (%s) of state %s in policy %s.
CAUSE: The document does not satisfy the criteria specified in the entry criteria object.
ACTION: Check the entry criteria object and the values of involved attributes.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_READ_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S No read access sysobject named %s. CAUSE:You do not have read access to this sysobject. ACTION:See your System Administrator or the owner of the sysobject.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_TOOMANY_INSERTP]

SEVERITY: ERROR
DESCRIPTION: SS You have inserted too many parts before %s child for sysobject called %s, please save or checkin now to reorder parts.
CAUSE: You have inserted too many components before a part.
ACTION: Perform a save or checkin will recompute orders and should should be able to continue compound doc changes.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_CREATE_TEMP_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: S Cant create the temporary directory %s.
CAUSE: An error occurred while creating the directory used by the addesignature temporary files.
ACTION: Verify that the path doesnt already exist.
PARAMS: The first parameter is the path to the temporary directory.

ERROR: [DM_SYSOBJECT_E_INVALID_FORMAT]

SEVERITY: ERROR
DESCRIPTION: S The specified format (%s) is invalid.
CAUSE: The specified format does not match a valid format from the docbase.
ACTION: Consult the dm_format type for valid format specifications.
PARAMS:

ERROR: [DM_SYSOBJECT_E_RESUME_NOT_NORM]

SEVERITY: ERROR
DESCRIPTION: SD Cannot resume to state %s which is not a normal state of policy %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANNOT_SAVECONTATTRS_ON_HOLD]

SEVERITY: ERROR
DESCRIPTION: S Cannot apply SAVE_CONT_ATTRS on sysobject %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_WRITE_CONTENT_TO_FILE]

SEVERITY: ERROR
DESCRIPTION: D Cant write content object %s to file %s.
CAUSE: The content could not be written.
ACTION: Check for the existence of a pre-existing file.
PARAMS: The first parameter is the object ID of the content object The secord parameter is the file name of the temporary file.

ERROR: [DM_SYSOBJECT_E_CANT_SET_FORK_ON_EXISTING_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S You cannot set the resource fork for the sysobject (%s) after the content has been saved.
CAUSE: The client attempted to set the resource fork on a page of the sysobject after its content has been saved.
ACTION:
PARAMS: The first parameter is the name of the sysobject.

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_DELETE_TEMPORARY_FILE]

SEVERITY: ERROR
DESCRIPTION: S Cant delete the temporary file %s.
CAUSE: A temporary file could not be cleaned up.
ACTION: Check the temporary file for open handles.
PARAMS: The first parameter is the temporary file name.

ERROR: [DM_SYSOBJECT_E_BAD_CUR_STATE]

SEVERITY: ERROR
DESCRIPTION: SID %s failed since the current state %d is not a valid state of the associated policy %s.
CAUSE: The state may have been removed.
ACTION: Reattach the sysobject to an INSTALLED policy.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_FT_INDEX]

SEVERITY: ERROR
DESCRIPTION: S The specified format (%s) cannot be indexed by the full text engine.
CAUSE: The format specified during setfile/getfile… operation cannot be indexed by the full text engine.
ACTION: Look into dm_format type for a list of all indexable formats.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ALREADY_LINKED]

SEVERITY: ERROR
DESCRIPTION: SD Sysobject named %s is already linked to %s folder
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_ALLOW_BP_SCHD]

SEVERITY: ERROR
DESCRIPTION: SSD Scheduled %s failed since the current state %s of policy %s is not schedulable.
CAUSE: The current state is not allowed to be scheduled.
ACTION: Before scheduling a BP event, move current state to a state whose allow_schedule value is true.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_MULTI_PAGE]

SEVERITY: ERROR
DESCRIPTION: SS Cannot perform %s operation since %s sysobject is not a multi-page sysobject.
CAUSE: Tried to perform a multi-page operation on a simple document.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_PART]

SEVERITY: ERROR
DESCRIPTION: S Invalid part definition for %s sysobject.
CAUSE: User has specified invalid part.
ACTION: Examine the previous error messages for more info.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_SAVE_IMMUTABLE]

SEVERITY: ERROR
DESCRIPTION: S Cannot save %s since it is immutable.
CAUSE: User has tried to save an older version of a sysobject.
ACTION: Older versions of a sysobject can only be versioned. Use checkin rather than save.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_LINKED]

SEVERITY: ERROR
DESCRIPTION: SD Sysobject %s not linked to folder %s.
CAUSE: This sysobject is not linked to this folder, or the id value specified for the folder is invalid.
ACTION: Try with a valid id.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NAME_MAPPING]

SEVERITY: ERROR
DESCRIPTION: SS Failed to the given name %s to the objects handle due to database errors. The message from the database is: %s
CAUSE: Failed to execute the query that gets the object id with the given unique object name.
ACTION: Fixed the database problem as reported in the error message and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_A_SYSOBJECT]

SEVERITY: ERROR
DESCRIPTION: D %s is not a sysobject which is required for lifecycle operation.
CAUSE: The specified object is not a type or subtype of sysobject.
ACTION: Make sure that the object for lifecycle operation is of dmsysobject type or its subtype.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_TARGET_BP_SCHD]

SEVERITY: ERROR
DESCRIPTION: S Scheduled %s failed since no check state is specified.
CAUSE: A check state is needed for a scheduled business policy event.
ACTION: Choose a check state whose allow_schedule value is true.
PARAMS:

ERROR: [DM_SYSOBJECT_E_SQL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to execute the statement: %s. The error message from the database was: %s
CAUSE: Failed to execute the query due to some database errors.
ACTION: Try the operation again. If it still fails, contact your sysadmins to fix the database problem. Adjust database configuration parameters, if necessary.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANNOT_CHECKOUT_IMMUTABLE_HOLD]

SEVERITY: ERROR
DESCRIPTION: S Cannot checkout sysobject %s because it is under an immutable retention hold.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_LOCKED]

SEVERITY: ERROR
DESCRIPTION: SS The operation on %s sysobject was unsuccessful because it is locked by user %s.
CAUSE: The requested operation cannot be done on a locked sysobject.
ACTION: Coordinate with the user holding the lock, or create a branch.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_SINGLE_PAGE]

SEVERITY: ERROR
DESCRIPTION: S Cannot perform this operation since %s sysobject is not a single-page sysobject.
CAUSE: Tried to perform a single-page operation on a multi-page document.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ACTIVATE_RETAINER]

SEVERITY: ERROR
DESCRIPTION: D You cannot activate the retainer object %s when it is inactive.
CAUSE: A user tried to activate a retainer object when it is inactive.
ACTION: An inactive retainer can never be re-activated.
PARAMS:

ERROR: [DM_SYSOBJECT_E_UPDATE_VTREE]

SEVERITY: ERROR
DESCRIPTION: S Failed to update the attributes used to maintain the version tree. The message from the database is: %s
CAUSE: Failed to update the attributes.
ACTION: Fix the database problem as reported and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_FILE_PERMISSION]

SEVERITY: ERROR
DESCRIPTION: SS The file %s cannot be opened because the current user does not have sufficient permissions. (Operating System error: %s).
CAUSE: The current user does not have the necessary permissions to access the file or the file is in use.
ACTION: Check the on-disk file permissions. Change if necessary.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_PRUNE_LOCKED]

SEVERITY: ERROR
DESCRIPTION: S Cannot prune sysobject %s version tree since one or more of its versions are locked.
CAUSE: Cannot prune a locked version tree.
ACTION: Unlock all versions on this version tree and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_DM_PROCESS_OBJECT_COPY]

SEVERITY: ERROR
DESCRIPTION: S Failed to copy %s because copying workflow templates from one docbase to another is not supported.
CAUSE: The client attempted to copy a process definition object also known as a workflow template, which is not allowed between docbases.
ACTION: Please use the SaveAs feature in WorkFlowManager or create a new workflow template manually with similar attributes.
PARAMS: The first parameter is the name of the workflow template.

ERROR: [DM_SYSOBJECT_E_CANT_SAVE_ACL]

SEVERITY: ERROR
DESCRIPTION: SSSS Failed to save the ACL %s in domain %s for the %s %s.
CAUSE: Failed to save ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CHANGE_RENDITION_UNDER_RETENTION]

SEVERITY: ERROR
DESCRIPTION: S You can not change/delete any rendition from sysobject %s when it is under retention.
CAUSE: A user tried to change an existing rendition or delete one when the object is under retention where at least one retainer has the rendition_rule set to ALL (i.e., 0).
ACTION: You can only change/delete rendition when the object is not under retention or all of its associated retainers have the rendition_rule set to PRIMARY (i.e., 1).
PARAMS:

ERROR: [DM_SYSOBJECT_E_JMS_HOST_PORT_ALREADY_USED]

SEVERITY: ERROR
DESCRIPTION: An existing dm_jms_config object is already configured to use the same host name and port.
CAUSE: Attempting to create a duplicate dm_jms_config object using hostname and port.
ACTION: Make sure all dm_jms_config objects in docbase use unique hostname and port.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_AUDIT_HASH_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: DSDS Mismatch between object %s with hash string %s and audit record %s with hash string %s.
CAUSE: The sysobject signature is invalid. The hash of the signed object does not match the one stored in the audit record.
ACTION: Check the sysobject to see if it has been altered since the signature was made.
PARAMS: The first parameter is the object ID of the sysobject that is being signed. The second parameter is the hash value for the sysobject. The third parameter is the ID of the audit record being used for verification. The fourth parameter is the hash value from the audit record.

ERROR: [DM_SYSOBJECT_E_INCONSISTENT_PROJECTION_ATTRS_IN_JMSCONFIG]

SEVERITY: ERROR
DESCRIPTION: The number of repeating attributes (server_config_id, projection_enable, projection_proximity_value, projection_targets, and projection_ports) is not consistent.
CAUSE: Failed to maintain same value count while editing these attributes.
ACTION: Add or remove attribute values to make them consistent.
PARAMS:

ERROR: [DM_SYSOBJECT_E_OVERRIDE_ENTRY]

SEVERITY: ERROR
DESCRIPTION: S Cannot override an entry criteria. User %s must be the owner of the policy or a superuser.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_BAD_TARGET_STATE]

SEVERITY: ERROR
DESCRIPTION: SDS Cannot %s the sysobject %s to the state %s.
CAUSE: User has specified an invalid state in the operation. A state is an invalid target state in an operation either it does not exist in the associated policy object or it is not the right target state.
ACTION: Make sure the state does exist in the associated policy object and it is the right target state.
PARAMS:

ERROR: [DM_SYSOBJECT_E_EXPUNGE_REPLICA]

SEVERITY: ERROR
DESCRIPTION: Cannot destroy a versioned replica or prune subset of its version tree. For replica, only deletion of all versions is allowed. (Reference prune command with objects chronicle_id and keepSLabel=F)
CAUSE: Destroying a single versioned replica could cause consistency issues on version tree during replication.
ACTION: Do not destroy a versioned replica. If space consumption is the concern, remove contents from replica or simply prune the whole version tree.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_ACL_DOMAIN]

SEVERITY: ERROR
DESCRIPTION: SSS The %s %s is given an invalid ACL domain %s.
CAUSE: Invalid ACL domain is given.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_NOTIFY]

SEVERITY: ERROR
DESCRIPTION: SS Could not send notification for %s event for %s sysobject.
CAUSE: The notification for the specified event could not be sent. Most likely bad event name specified, or failed database operation.
ACTION: Check the event name, and any other error messages for this operation.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DESTROYU]

SEVERITY: ERROR
DESCRIPTION: S Cannot destroy sysobject named: %s since it is referenced by another compound document or an assembly object.
CAUSE: Tried to destroy a sysobject that is in use in a compound document.
ACTION: Delete the compound doucments before the deleting this sysobject.
PARAMS:

ERROR: [DM_SYSOBJECT_E_VERSION_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: L save of object failed because of version mismatch: old version was %d
CAUSE: The save of an object failed because the version stamp in the object was inconsistent with the version stamp currently stored in the database.
ACTION: Refetch the object, make the necessary changes and save it again.
PARAMS: The identifier of the object, the type of the object and the old value of the version stamp.

ERROR: [DM_SYSOBJECT_E_LIGHTWEIGHT_ILLEGAL_PARENT_ID]

SEVERITY: ERROR
DESCRIPTION: D The parent id (%s) is illegal
CAUSE: The parent ID is illegal for one of the following reasons: a) It is a null ID. b) It points to a non-existent object. c) It is not an instance of a shareable type. d) The parent type is not declared as the parent type of the lightweight type. e) The parent is not the CURRENT version or has been versioned.
ACTION: Reset the parent id to a legal id.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANNOT_SAVE_ON_HOLD]

SEVERITY: ERROR
DESCRIPTION: S Cannot save modifications on sysobject %s because it was under retention hold.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DO_ASSEMBLY_CHANGES]

SEVERITY: ERROR
DESCRIPTION: S Both the thaw and freeze flags are turned on for %s sysobject.
CAUSE: Server detected the freeze and thaw assembly flags turned on at the same time.
ACTION: Report this to Documentum.
PARAMS:

ERROR: [DM_SYSOBJECT_E_SAVEASNEW_KEEP_STORAGE_INCOMPATIBLE_STORAGE_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSSSS Storage area (%s) on source repository (%s) is of type (%s) and on target repository (%s) its of type (%s)
CAUSE: User executed saveasnew api with keepOriginalStorages flag set to TRUE, to copy an object from one repository to another. But a storage area that exists on both repositories is of different type.
ACTION: You cannot specify TRUE for keepOriginalStorages in the saveasnew Api because there is a storage incompatibility between the source and target repositories. Either create identically named storages and of the same storage type on both the repositories or specify FALSE for the keepOriginalStorages.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_READ_DATA_SOURCE]

SEVERITY: ERROR
DESCRIPTION: D Failed to read the data from content object %s.
CAUSE: The content object could not be read.
ACTION: Verify the validity of the sysobject that is being signed.
PARAMS: The first parameter is the object ID of the content object that is being signed.

ERROR: [DM_SYSOBJECT_E_NO_CONTENT_TYPE]

SEVERITY: ERROR
DESCRIPTION: S No content type specified for %s sysobject.
CAUSE: Content type must be specified before adding any contents.
ACTION: Try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_DESTROY_ACL]

SEVERITY: ERROR
DESCRIPTION: SSSS Failed to destroy the ACL %s in the domain %s for %s %s.
CAUSE: Failed to destroy the ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_MIGRATE]

SEVERITY: ERROR
DESCRIPTION: SS Can not migrate %s sysobject to %s storage area.
CAUSE: Previous errors (os/db) prevented the server to migrate the sysobject to the destrination storage.
ACTION: See the previous error msgs.
PARAMS:

ERROR: [DM_SYSOBJECT_E_UPDATE_RETAIN_UNTIL_UNABLE_TO_EXECUTE_QUERY]

SEVERITY: ERROR
DESCRIPTION: S An error occured while executing a DQL statement to fetch objects to update the i_retain_until attribute: Query: %s
CAUSE: The WHERE_CLAUSE specified for the UPDATE_RETAIN_UNTIL_UPDATE apply method had syntax errors.
ACTION: Refer to other error messages for the session and take corrective action to fix those problems and reexecute the apply method.
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_TYPE]

SEVERITY: ERROR
DESCRIPTION: SDS The %s object identified by %s is not a subtype of %s.
CAUSE: User tried to perform an operation not supported for this object.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NOT_IN_RESTRICTED_FOLDERS]

SEVERITY: ERROR
DESCRIPTION: D The sysobject (%s) is not in any folder (or subfolder of the folder) specified in the users restricted_folder_ids.
CAUSE: If restricted_folder_ids is specified, every sysobject fetched/saved must reside in at least one folder specified in the restricted_folder_ids or a subfolder of any folder in the list. The ID you have specified may be a valid object ID, but it does not reside in a folder (or subfolder) specified in the users restricted_folder_ids.
ACTION: Fetch another object or link the object to one of the restricted folders or their subfolders.
PARAMS: The first ID value is the sysobject id and the second one is the offending folder id.

ERROR: [DM_SYSOBJECT_E_CANT_SET_FORK_WITHOUT_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S You cannot set the resource fork for the sysobject (%s) before setting its content.
CAUSE: The client attempted to set the resource fork on a page of the sysobject before setting its content.
ACTION: Use the API to set the content on the same page first. Then, try again.
PARAMS: The first parameter is the name of the sysobject.

ERROR: [DM_SYSOBJECT_E_ESIGN_PRIMARY_CONTENT_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: D Could not retrieve the primary content for the object %s.
CAUSE: The primary content for the sysobject could not be found.
ACTION: Make sure that the a sysobject has a rendition or primary content in the signature format.
PARAMS: The first parameter is the id of the sysobject which is being signed.

ERROR: [DM_SYSOBJECT_E_DISALLOWED_OP_FOR_NONSHAREABLE_TYPE]

SEVERITY: ERROR
DESCRIPTION: SDS The operation %s performed on object %s is disallowed because its type %s is not shareable
CAUSE: The specified operation was performed on an object whose type is not shareable.
ACTION: Make sure that the object is an instance of a shareable type before performing the operation.
PARAMS:

ERROR: [DM_SYSOBJECT_E_RENDITION_FMT_SAMEAS]

SEVERITY: ERROR
DESCRIPTION: SSS Rendition format %s must be different than the original format %s for %s sysobject unless the page modifier is specified.
CAUSE: User tried to
ACTION: Look at the error messages following this one for more help.
PARAMS:

ERROR: [DM_SYSOBJECT_E_EXIST_CHECK_BP_SCHD]

SEVERITY: ERROR
DESCRIPTION: SSD Scheduled %s failed since check state %s does not exist in policy %s.
CAUSE: A check state is needed for a scheduled business policy event.
ACTION: Supply a check state (i.e. a target state for Promote and Demote, and a source state for Suspend and Resume).
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CHANGE_XPERMITS]

SEVERITY: ERROR
DESCRIPTION: S Only the %s sysobject owner and superuser can change extended permits.
CAUSE: A user, other than a superuser or sysobject owner, tried to change extended security permits
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ALREADY_LOCKED]

SEVERITY: ERROR
DESCRIPTION: S You already have document %s checked out.
CAUSE: Attempt to checkout document already checked out by the current user.
ACTION: None necessary.
PARAMS:

ERROR: [DM_SYSOBJECT_E_FLABEL_INUSE]

SEVERITY: ERROR
DESCRIPTION: S Cannot redefine an internal label %s since it is in use.
CAUSE: Tried to redefine an implicit label that is used for composite containment. If implicit version label of a sysobject is in use by composite then it cannot be reassigned.
ACTION: None.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANNOT_ATTACH_CONDITIONAL_RETAINER]

SEVERITY: ERROR
DESCRIPTION: D Cannot attach conditional retainer to sysobject %s because it has triggered conditional retainers attached to it.
CAUSE: Cannot attach conditional retainer after the clip has been triggered for EBR.
ACTION: Not Supported.
PARAMS:

ERROR: [DM_SYSOBJECT_E_BAD_ADHOC_OP]

SEVERITY: ERROR
DESCRIPTION: ISS The operation (%d) for an ad-hoc ACE of %s %s is neither grant (1) nor revoke (-1).
CAUSE: Found a bogus operation in the ad-hoc operation.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_BROWSE_ACCESS2]

SEVERITY: ERROR
DESCRIPTION: SSS No browse access to sysobject %s since %s %s is protected.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_SAVE_NO_LINK]

SEVERITY: ERROR
DESCRIPTION: S Cannot save %s sysobject without any link.
CAUSE: All sysobjects must have a parent folder.
ACTION: Link this sysobject to a folder and try again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_BROWSE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S No browse access sysobject named %s. CAUSE:You do not have browse access to this sysobject. ACTION:See your System Administrator or the owner of the sysobject.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CHECKOUTNEW]

SEVERITY: ERROR
DESCRIPTION: S Cannot checkout %s sysobject, since it is not in the docbase.
CAUSE: The referenced sysobject has not been saved.
ACTION: Save the sysobject, before checking out.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_DELETE_RETAINER]

SEVERITY: ERROR
DESCRIPTION: S Cannot delete retainer object %s since it is used by other objects.
CAUSE: Cannot delete a retainer object when it is still in use.
ACTION: Make sure that the retainer object is not referenced in the i_retainer_id of any other sysobject.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_PRUNE]

SEVERITY: ERROR
DESCRIPTION: D Cannot prune %s sysobject and its descendants.
CAUSE: One or more previous operations were erroneous. ACION: Examine the previous error messages for more detail.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_POLICY]

SEVERITY: ERROR
DESCRIPTION: SD %s failed because the policy %s does not exist.
CAUSE: The policy object may have been destroyed.
ACTION: You must attach the sysobject to some valid policy object.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CHANGE_STATE_PERM]

SEVERITY: ERROR
DESCRIPTION: SD It requires the CHANGE_STATE and WRITE permits to perform %s operation on object %s.
CAUSE: The user does not have the CHANGE_STATE extended permission (maybe WRITE permit) on the sysobject while attempting to perform the said operation.
ACTION: Grant the user CHANGE_STATE and WRITE permits on the object.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_DEFAULT_POLICY]

SEVERITY: ERROR
DESCRIPTION: SDS %s failed because the default policy %s for type %s does not exist.
CAUSE: The policy object may have been destroyed.
ACTION: You must attach the sysobject to some valid policy object.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_FORCE_DELETE_UNDER_HOLD]

SEVERITY: ERROR
DESCRIPTION: S Cant force delete object (%s) because it is under retention hold.
CAUSE: : This error occurs when attempting to force-delete a sysobject which is under retention hold(s).
ACTION: Remove the retention hold(s) applied on the sysobject and then try deleting it again.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_CREATE_VERSION]

SEVERITY: ERROR
DESCRIPTION: S Cannot create new version of sysobject named %s.
CAUSE: Could not create a new versioned sysobject. Either the sysobject is locked by another person or current user does not have version permit or version label can not be assigned.
ACTION: See the previous error msgs
PARAMS:

ERROR: [DM_SYSOBJECT_E_ACTION]

SEVERITY: ERROR
DESCRIPTION: : Cannot modify SysObject until the retention hold is removed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_VERSION_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S No version access sysobject named %s. CAUSE:You do not have sufficient permission to version (checkout) this sysobject. This could be because of insufficient permission on the sysobject itself, or on the sysobjects primary cabinet.
CAUSE:
ACTION: First determine if it is the sysobject, or its cabinet, that you do not have version access to. Then, see your System Administrator or the owner of the sysobject or cabinet.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_FETCH_RENDITION]

SEVERITY: ERROR
DESCRIPTION: LS Can not fetch prestored rendition for page %d of %s sysobject.
CAUSE: Conditions prior to this operation have caused failure of this operation.
ACTION: Consult the other error message report with this error or previous error messages for the actual reason.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_MOVE_SYMBOLIC]

SEVERITY: ERROR
DESCRIPTION: SS Cannot move symbolic label %s from %s sysobject.
CAUSE: Cannot move the specified symbolic label. Most likely the original sysobject is locked by another user and, until it is unlocked, that object cannot be changed.
ACTION: Either checkin with a different label or coordinate your changes with the user that has the document locked.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ASSEMBLE]

SEVERITY: ERROR
DESCRIPTION: S Cannot build the assembly for %s sysobject.
CAUSE: The user tried to specify invalid options to assemble a compound document, or the book specified has no components to assemble, or the assembled into document is also a compound document.
ACTION: Review the dql predicate or the assemble parameters.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ADD_RENDITION]

SEVERITY: ERROR
DESCRIPTION: LSSS Cannot add rendition number %d identified by %s file, %s format sysobject named %s.
CAUSE: Adding this new rendition was not successful. Either invalid file name or format specification, or rendition number out of sequence.
ACTION: Look at the error messages following this one for more help.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_SIGNATURE_METHOD_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Method %s failed. Arguments: %s.
CAUSE: The signature page method .
ACTION: Look in the server log for errors pertaining to this failure.
PARAMS: The first parameter is the method name. The second parameter is the argument list.

ERROR: [DM_SYSOBJECT_E_NO_PROM_TERMINAL]

SEVERITY: ERROR
DESCRIPTION: ID Promote failed since the sysobjects current state %d is a terminal state of the associated policy %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_INVALID_SERVER_CONFIG_ID_IN_JMSCONFIG]

SEVERITY: ERROR
DESCRIPTION: S %s is not a valid server_config id.
CAUSE: The r_object_id value does not belong to a valid dm_server_config object.
ACTION: Assign a correct r_object_id value which belongs to a dm_server_config object, to server_config_id attribute.
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANNOT_SHARE_PARENT_WITH_DIFF_LIGHTWEIGHT_TYPES]

SEVERITY: ERROR
DESCRIPTION: DSS Cannot share object %s with an instance of type %s because it is already shared by instances of type %s
CAUSE: User has tried to share an object which is already shared by instances of a different lightweight type which the type of the new sharing child is not a subtype of.
ACTION: User should only share the parent with either the same sharing type (recorded in i_sharing_type) or any of its subtypes.
PARAMS:

ERROR: [DM_SYSOBJECT_E_SAVE_FAILED_UNAVAILABLE_SUBTYPE]

SEVERITY: ERROR
DESCRIPTION: S Your client is older than your server, and you have attempted to create an object of a type (%s) that is not available to your clients version.
CAUSE: A sysobject subtype that is available in your docbase was created by an e-Content Server that is newer than the Documentum Client Library (dmcl) of the client you are using. You cannot create an object of that type unless the dmcl matches. You would not get a correct ID, nor proper save semantics if this were allowed.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_PROM_TERMINAL_2]

SEVERITY: ERROR
DESCRIPTION: SDI Promote failed since the object, %s(%s), is in the terminal state %d.
CAUSE: The object is already it the terminal state.
ACTION: Promote is not allowed. Check the associated lifecycle.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_UPDATE_CONTENT]

SEVERITY: ERROR
DESCRIPTION: D Cant update the content for object %s.
CAUSE: The content object could not be saved.
ACTION: Verify the status of the sysobject that is being signed..
PARAMS: The first parameter is the object ID of the sysobject that is being signed.

ERROR: [DM_SYSOBJECT_E_LIGHTWEIGHT_CANNOT_FETCH_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch the lightweight sysobject the object ID %s is invalid
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_SYSOBJECT_E_FAILED_TO_CHECK_IF_CONTENT_TRIGGERED]

SEVERITY: ERROR
DESCRIPTION: D Failed to check if the content objects for sysobject %s were triggered.
CAUSE: The content list for the sysobject was invalid.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_INSUFFICIENT_PRIVILEGE_FOR_PLUGIN]

SEVERITY: ERROR
DESCRIPTION: You must be a system administrator to create or destroy objects of dm_plugin type.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_CONTENT_TO_PRINT]

SEVERITY: ERROR
DESCRIPTION: S Sysobject %s has no content to print. CAUSE:This document has no content/pages to print. ACTION:None.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_CANT_ASSEMBLE_WITH_OPEN_TRAN]

SEVERITY: ERROR
DESCRIPTION: DI Cannot build the assembly for %s sysobject with frequency (%d) greater than zero when there is an open transaction.
CAUSE: The user tried to assemble a compound document with a specified transaction commit frequency when there is already an open transaction.
ACTION: Either close the transaction or reset the frequency to -1 before assemblying a compound document.
PARAMS:

ERROR: [DM_SYSOBJECT_E_ESIGN_CANT_AUTHENTICATE_USER]

SEVERITY: ERROR
DESCRIPTION: S User %s could not be authenticated.
CAUSE: The password argument did not properly authenticate the user..
ACTION: Verify the users login name and password.
PARAMS: The first parameter is the user name.

ERROR: [DM_SYSOBJECT_E_CANCEL_NO_JOB]

SEVERITY: ERROR
DESCRIPTION: SSD The job %s scheduled at %s for object %s does not exist.
CAUSE: The specified job does not exist in the docbase.
ACTION: Either the job has already been destroyed or the specified time is not correct.
PARAMS:

ERROR: [DM_SYSOBJECT_E_NEED_RETAINER_OBJ]

SEVERITY: ERROR
DESCRIPTION: SD The operation %s applied to a sysobject requires the object %s to be a retainer object.
CAUSE: A user tried to execute a retainer-specific operation on a non-retainer object.
ACTION: Make sure that the object is a retainer.
PARAMS:

ERROR: [DM_SYSOBJECT_E_LIGHTWEIGHT_NO_BROWSE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S No Browse access to the lightweight sysobject named %s. CAUSE:You do not have Browse access to this lightweight sysobject. ACTION:Ask a System Administrator or the owner of the lightweight sysobject to give you the access.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_E_NO_DELETE_ACCESS2]

SEVERITY: ERROR
DESCRIPTION: SSS No delete permit on sysobject %s since %s %s is protected.
CAUSE: You do not have the necessary permit to delete this sysobject. ACTION:See your System Administrator or the owner of the sysobject.
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_W_MERGE_PARENT_FETCH]

SEVERITY: WARNING
DESCRIPTION: DD Unable to fetch parent link %s for folder %s. The load operation is unable to determine what to do with the link and will leave it in its current state.
CAUSE: An error was encountered in a load operation while attempting to merge the folder links of an incoming sysobject with an existing object. The error was encountered while processing links of the existing object that were not found in the incoming object from the dumpfile. Replication rules state that the links should be retained if they are links to folders outside the current replication target folder, and removed otherwise. The load operation was unable to fetch the folder to make this determination and so retained the link by default.
ACTION: Check that the source and target docbases are both running the same version of the eContent Server. This warning could be the result of incompatible rules for dumping and loading folder objects. The object referenced in this error message should be checked at the end of the replication run to see if it is properly linked into its parent folders.
PARAMS:

ERROR: [DM_SYSOBJECT_W_ATTRS_NOT_ALTERED_FTINDEX]

SEVERITY: WARNING
DESCRIPTION: S String-valued attributes have not been marked for fulltext indexing because index objects of type %s already exist in the docbase. Please run the method dm_UpgradeFTSysObjAttrs.
CAUSE: An attempt was made to mark string-valued attributes for indexing after index objects of the type already exist.
ACTION: Run the method dm_UpgradeFTSysObjAttrs which will first reset the indexes and then mark the attributes for indexing. See the Documentum Server Administration Guide for more details.
PARAMS: The type name.

ERROR: [DM_SYSOBJECT_W_NOT_PRUNED]

SEVERITY: WARNING
DESCRIPTION: DS The object %s was not pruned. The reason was %s.
CAUSE: The object wasnt pruned due to the reason reported.
ACTION: No action is required unless you want the object to be pruned as well. The reason might be one of the following: 1) The keep symbolic label flag in the prune API was true and the object did have some symbolic label. If this was the reason, then re-issue the prune API with the flag set to false. 2) The object was referenced by some virtual document. If this was the reason, then you need to delete the referencing object (the parent) first.
PARAMS:

ERROR: [DM_SYSOBJECT_W_RECURSIVE_DELETE]

SEVERITY: WARNING
DESCRIPTION: SD Recursive attempt to delete the sysobject %s (ID: %s)
CAUSE: Server internal error.
ACTION: Report the problem to technical support.
PARAMS:

ERROR: [DM_SYSOBJECT_W_NOT_CASCADE_DELETED_UNDER_RETENTION]

SEVERITY: WARNING
DESCRIPTION: S Sysobject %s is not cascade deleted because it is under retention.
CAUSE: The sysobject was related to another sysobject that was to be deleted. Because the way the relation was set up, a cascade delete on the object was performed. Since the object is under retention, we dont delete the object for cascade delete. Note that the original object as well as the relation object would be deleted.
ACTION: If you need to delete the sysobject, you need to delete it directly.
PARAMS:

ERROR: [DM_SYSOBJECT_W_FOLDER_DEFACL]

SEVERITY: WARNING
DESCRIPTION: SS Failed to inherit ACL for %s %s, since it does not have a primary folder.
CAUSE: The sysobject doesnt have a primary folder.
ACTION: Set the ACL or permissions for the sysobject.
PARAMS:

ERROR: [DM_SYSOBJECT_W_RETAINER_NOT_ATTACHED]

SEVERITY: WARNING
DESCRIPTION: SD Sysobject %s is not attached to retainer %s.
CAUSE: A user tried to remove a retainer object from a sysobject which is not attached to the retainer.
ACTION: Make sure that you only remove the retainer object attached to the sysobject.
PARAMS:

ERROR: [DM_SYSOBJECT_W_ASSUMING_ACL_SECURITY_MODE]

SEVERITY: WARNING
DESCRIPTION: The server has dedected an unsupported security mode. ACL security is being assumed.
CAUSE: The server has dedected a security_mode other than ACL or NONE. The server will assume ACL security mode. Typically this will occur if the server finds the i_security_mode vstamp to be set to a value other than ACL or NONE. The server will automatically correct this.
ACTION: None needed.
PARAMS:

ERROR: [DM_SYSOBJECT_W_RENDITION_NOT_REMOVED]

SEVERITY: WARNING
DESCRIPTION: IS Rendition page %d is not removed for %s because keep_flag is set to TRUE
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_W_CANNOT_MODIFY_CONTROLLED_SYSOBJECT]

SEVERITY: WARNING
DESCRIPTION: SSS An unauthorized application (User: %s) has attempted to modify the Controlled SysObject with id %s. Only applications with an application_code of %s can modify this SysObject.
CAUSE: An attempt has been made to modify a Controlled SysObject from an unauthorized application. Controlled Sysobjects can only be modified by owning applications. The applications application_code value in the sessionconfig object must match the a_controlling_app value of the SysObject.
ACTION: Ensure that you are using the appropriate application to modify this SysObject. If this message appears in the server log, it can typically be ignored and there is no cause for alarm. The warning just indicates that specified user attempted to modify a controlled sysobject from an unauthorized application.
PARAMS: The first parameter is the user. The second parameter is the object id of the SysObject. The third parameter is the a_controlling_app of the SysObject.

ERROR: [DM_SYSOBJECT_W_RETAINER_ALREADY_ATTACHED]

SEVERITY: WARNING
DESCRIPTION: SD Sysobject named %s is already attached to %s retainer object
CAUSE: A user tried to attach a retainer object to a sysobject twice.
ACTION: Make sure that every retainer object is attached to a sysobject at most once.
PARAMS:

ERROR: [DM_SYSOBJECT_W_CANT_FETCH_ACL]

SEVERITY: WARNING
DESCRIPTION: D Cannot fetch the ACL associated with sysobject %s.
CAUSE: Check the previous error messages.
ACTION: Verify that this sysobject has a valid acl_name and acl_domain
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_SIGNATURE_NUMBER]

SEVERITY: TRACE
DESCRIPTION: I AddESignature: This is signature number %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_MERGE_3]

SEVERITY: TRACE
DESCRIPTION: S Removing local folder: folder_path=%s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_SYSOBJ_SAVE_FAILED]

SEVERITY: TRACE
DESCRIPTION: DSI Save of sysobject (id = %s, name = %s) failed during Phase %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_OBJECT_ID]

SEVERITY: TRACE
DESCRIPTION: D AddESignature: Called for object %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_SAVE_AUDIT]

SEVERITY: TRACE
DESCRIPTION: AddESignature: Saving dm_addesignature audit record.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_OPERATION_SUCCEEDED]

SEVERITY: TRACE
DESCRIPTION: D AddESignature: Operation succeeded. New audit record ID is %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_CHECK_PERMISSIONS]

SEVERITY: TRACE
DESCRIPTION: AddESignature: Checking user permissions.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_CHECK_TCS_ENABLED]

SEVERITY: TRACE
DESCRIPTION: AddESignature: Verifying that Trusted Content Services are enabled.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_MERGE_1]

SEVERITY: TRACE
DESCRIPTION: SSS Checking local folder path for sysobject ID=%s, folder_path=%s, tgt_path=%s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_VERIFY_NOT_CHECKED_OUT]

SEVERITY: TRACE
DESCRIPTION: AddESignature: Verifying that the object is not checked out.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_READ_USER_OS_NAME]

SEVERITY: TRACE
DESCRIPTION: S AddESignature: Get user login name %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_UPDATE_RETAIN_UNTIL_DATE]

SEVERITY: TRACE
DESCRIPTION: S %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_VERIFY_PREVIOUS_SIGNATURES]

SEVERITY: TRACE
DESCRIPTION: AddESignature: Verifying any previously existing signatures.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_FAILED_SAVE_AUDIT]

SEVERITY: TRACE
DESCRIPTION: AddESignature: Saving dm_addesignature_failed audit record.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_AUTHENTICATE_USER]

SEVERITY: TRACE
DESCRIPTION: S AddESignature: Authenticating user %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_CHECK_PRE_SIGNATURE_HASH]

SEVERITY: TRACE
DESCRIPTION: AddESignature: Verifying pre-signature hash.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_SAVE_ORIGINAL_CONTENT]

SEVERITY: TRACE
DESCRIPTION: AddESignature: Saving original (unsigned) content object with page modifier dm_sig_source.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_CREATE_TEMP_FILE]

SEVERITY: TRACE
DESCRIPTION: S AddESignature: Creating temporary file %s with content to be signed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_NEW_CONTENT]

SEVERITY: TRACE
DESCRIPTION: D AddESignature: Creating new content object %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_FULL_FETCH]

SEVERITY: TRACE
DESCRIPTION: DI Full Fetch of SysObj id=%s cache_vstamp=%d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_CALL_METHOD]

SEVERITY: TRACE
DESCRIPTION: SS AddESignature: Calling method %s with arguments %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_ESIGN_ARGUMENT_VALUE]

SEVERITY: TRACE
DESCRIPTION: SS AddESignature: Method argument %s has value %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_SYSOBJECT_T_MERGE_2]

SEVERITY: TRACE
DESCRIPTION: S Appending folder: folder_path=%s
CAUSE:
ACTION:
PARAMS:

nahoru

DM_TYPE_MGR

ERROR: [DM_TYPE_MGR_E_LOAD_TYPINFO_FIX]

SEVERITY: ERROR
DESCRIPTION: S An Error occurred applying updates to the dmi_type_info object for new type %s during the second phase of load processing. During load operations, when we we create a new type, we bring over the data dictionary information from the source docbases type info record. This error indicates that a failure was encountered during an attempt to apply that update.
CAUSE: Internal error in load processing
ACTION: Check for other errors which may give more detail on the problem. If the error appears transient, the load can be retried by simply fetching the same dm_load_record and issueing a new save on it. If the load cannot be retried, it should be reverted by fetching the dm_load_record and applying the revert api.
PARAMS: %1 – the name of the type being processed.

ERROR: [DM_TYPE_MGR_E_GET_ASPECT_INFO_TYPE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: There is no dmc_aspect_type in the repository
CAUSE: There is no dmc_aspect_type type defined/created in the repository for GET_ASPECT_USE_INFO apply method to use.
ACTION: Refer to the installation guide and resolve installation/upgrade errors.
PARAMS:

ERROR: [DM_TYPE_MGR_E_UNABLE_TO_POPULATE_TABLE]

SEVERITY: ERROR
DESCRIPTION: SSS Type Manager was unable to populate the table %s for type %s: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The first parameter is the name of the table being populated. The second parameter is the name of the type. The third parameter is the error string from the database system.

ERROR: [DM_TYPE_MGR_E_SAVE_INSERT_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Failure to save new type %s in object table: error from database system was %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The name of the type and the database system error string.

ERROR: [DM_TYPE_MGR_E_CANT_CREATE_TABLE]

SEVERITY: ERROR
DESCRIPTION: SSS Failure to create attribute table %s for type %s: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The names of the table being created and the type being stored and the error string from the database system.

ERROR: [DM_TYPE_MGR_E_INDEX_WITHOUT_TYPE_TABLE]

SEVERITY: ERROR
DESCRIPTION: DS The dmi_index object with id %s on type %s, refers to an attribute in a table that no longer exists in the database. The type manager will drop the dmi_index object and clean up.
CAUSE: The dmi_index object refers to an attribute(s) that no longer exists because one of the corresponding types tables in the database does not exist. This is most likely due to the r_table of a type being dropped since there are no more repeating attributes, but the corresponding indices were not dropped.
ACTION: Check the dmi_index object and make sure it is removed. Also, if the index was on the r_object_id or i_position columns, make sure that the dm_type object no longer refers to the dmi_index object.
PARAMS: The first parameter is the object id of the dmi_index object. The second parameter is the name of the type that is indexed.

ERROR: [DM_TYPE_MGR_E_CANT_SAVE_ACL]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to save ACL %s in name space %s for type %s.
CAUSE: Failed to save the ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_TYPE_MGR_E_CANT_REMOVE_TYPE_ON_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Failure to remove type named %s before saving new type.
CAUSE: Internal system error.
ACTION: Report this error and its parameters to your Documentum site representative.
PARAMS: The name of the type being saved.

ERROR: [DM_TYPE_MGR_E_LOAD_SYNONYM_CHECK]

SEVERITY: ERROR
DESCRIPTION: S An Error occurred looking for a synonym for the type %s during load processing of the dmi_type_info object. During load operations, when we encounter dm_type or dmi_type_info objects we check for an existing type of the same name in the docbase to determine what action to take. This error occured during an attempt to determine if the named type was already existing or was created during the current load. If this error occurs while checking an existing type, it will not cause any bad effects, assuming there are no other errors in the load. However, if this error occurs while checking a newly created type, it will likely cause the operation to bypass any new data dictionary information that should have been created along with the type.
CAUSE: Internal error in load processing
ACTION: Check for other errors which may give more detail on the problem. Check that new types were created as expected, including the data dictionary information (indicated by the type_override field of the dmi_type_info entry). If the load was not successfull it can be reverted and retried by fetching the dm_load_record and applying the revert,c,l command and then the save,c,l command.
PARAMS: %1 – the name of the type being processed.

ERROR: [DM_TYPE_MGR_E_CURSOR_ERROR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the creation of a cursor (%s).
CAUSE: A SQL statement that queries the Documentum schema has failed. This error message indicates that a failure occurred during the parsing of the generated SQL statement by the underlying RDBMS.
ACTION: The error message from the RDBMS is shown in the message. Use that error message to figure out what has happened.
PARAMS:

ERROR: [DM_TYPE_MGR_E_TYPE_HAS_OBJECTS]

SEVERITY: ERROR
DESCRIPTION: S Attempt to remove type %s, which still has objects.
CAUSE: Program attempted to remove a type for which objects still exists.
ACTION: Destroy the objects in the type before removing it.
PARAMS: The name of the type.

ERROR: [DM_TYPE_MGR_E_INDEX_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SSS Failure to create index named %s for type %s: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The name of the index, the name of the type for which it was being created, and the error string from the database.

ERROR: [DM_TYPE_MGR_E_INDEX_ALREADY_EXISTS]

SEVERITY: ERROR
DESCRIPTION: SD The index being created on type %s already exists. The existing index is represented by dmi_index object with id %s.
CAUSE: Duplicate indices cannot be created. An index on the desired attributes and type already exists.
ACTION: Check the dmi_index object specified in the error and verify that it is on the same attributes.
PARAMS: The first parameter is the object id of the dmi_index object. The second parameter is the name of the type that is indexed.

ERROR: [DM_TYPE_MGR_E_ADD_UPDATE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failure to update type table adding attributes for type %s: error from database system is %s
CAUSE: Internal error.
ACTION: Check the error message from the database system. The The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The name of the type and the database error string.

ERROR: [DM_TYPE_MGR_E_ADD_UPDATE_FRESH_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failure to batch update type table adding attributes for type %s: error from database system is %s
CAUSE: Internal error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The name of the type and the database error string.

ERROR: [DM_TYPE_MGR_E_CANT_ADD_COLUMN]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to add column %s from table %s: error from database system is %s
CAUSE: Internal error.
ACTION: Check the error message from the database system. The The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The name of the column, the name of the table to which it is being added, and the error string from the database.

ERROR: [DM_TYPE_MGR_E_VERSION_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: Version of type manager code not consistent with database contents.
CAUSE: The database version stamp for the type manager is inconsistent with the version stamp in the system being run.
ACTION: Check to see that the document base being opened was built with the same version of the Documentum system.
PARAMS: None.

ERROR: [DM_TYPE_MGR_E_DATABASE_INTERNAL_ERROR]

SEVERITY: ERROR
DESCRIPTION: S An database error occured in while making object table. The database internal error is %s
CAUSE: Internal database system error.
ACTION: Report this error and its prarmeters to your Documentum site representative.
PARAMS: The database internal error.

ERROR: [DM_TYPE_MGR_E_CANT_BUILD_NAME_INDEX]

SEVERITY: ERROR
DESCRIPTION: S Failure to construct name index on type table: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The error string from the database system.

ERROR: [DM_TYPE_MGR_E_CANT_CREATE_INDEX]

SEVERITY: ERROR
DESCRIPTION: SSS Failure to create index for table %s as part of creation of type %s: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The names of the table and the type being indexed and the error string from the database system.

ERROR: [DM_TYPE_MGR_E_EXISTING_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Cannot create type %s because a type by that name already exists in the database and the server preserve_existing_types flag is enabled. To complete this operation the type must be manually dropped or the server flag disabled. This error message is given if during type initialization at server startup the server finds that a type it needs to create conflicts with another type by the same name already in the database. By default the server will simply drop the type and re-create it. But if the server startup parameter preserve_existing_types is present then this error is given instead.
CAUSE: Type already exists in the docbase
ACTION: Ensure that it is ok to remove the existing type and then manually drop it. Alternatively the preserve_existing_types flag can be removed from the server startup options and the server restarted.
PARAMS: %s – the type name

ERROR: [DM_TYPE_MGR_E_EXISTING_TABLE]

SEVERITY: ERROR
DESCRIPTION: SS Cannot create type %s because the table %s unexpectedly already exists in the database and the server preserve_existing_types flag is enabled. To complete this operation the table must first be manually dropped or the server flag disabled. This error message is given if during type creation the server finds that a table it needs to create already exists in the database. By default the server will simply drop the table and re-create it. But if the server startup parameter -preserve_existing_types is present then this error is given instead.
CAUSE: Table already exists in the docbase
ACTION: Ensure that it is ok to remove the existing table and then manually drop it. Alternatively the preserve_existing_types flag can be removed from the server startup options and the server restarted.
PARAMS: %s – the type name %s – the table name

ERROR: [DM_TYPE_MGR_E_INITIAL_COMMIT_FAILED]

SEVERITY: ERROR
DESCRIPTION: Failure to commit version stamp change on initialization.
CAUSE: Internal system error.
ACTION: Report this error and its parameters to your Documentum site representative.
PARAMS: None.

ERROR: [DM_TYPE_MGR_E_CANT_FETCH_ACL]

SEVERITY: ERROR
DESCRIPTION: SSSS Failed to fetch the ACL %s in name space %s for the type %s. [%s]
CAUSE: Failed to fetch the given ACL.
ACTION: Try a valid ACL.
PARAMS:

ERROR: [DM_TYPE_MGR_E_OLD_VERSION]

SEVERITY: ERROR
DESCRIPTION: SII Old version of type %s — version stamp is %d database version is %d
CAUSE: An attempt to alter a type that has been modified since it was fetched
ACTION: Quit the session, start a new session and try again
PARAMS: The name of the type, the version stamp in the cached copy and the database version stamp

ERROR: [DM_TYPE_MGR_E_CANT_ADD_ISREPLICA]

SEVERITY: ERROR
DESCRIPTION: S Attempt to add (internal) i_is_replica attribute to type %s before saving failed.
CAUSE: Internal system error.
ACTION: Report this error and its parameters to your Documentum site representative.
PARAMS: The name of the type.

ERROR: [DM_TYPE_MGR_E_CANT_DEREF_ACL]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to de-reference ACL %s in name space %s for type %s.
CAUSE: Failed to deref the ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_TYPE_MGR_E_UNABLE_TO_ADJUST_INDEX_POSITIONS]

SEVERITY: ERROR
DESCRIPTION: SS The type manager was unable to modify the attribute positions in the dmi_index objects for the type %s as a result of attribute changes to one or more of its supertypes. The following database error occurred: %s
CAUSE: Whenever attributes are added or removed from a type, the attribute positions of its subtypes changes. As a result, we need to adjust the dmi_index objects of any of the types subtypes because the dmi_index object uses attribute positions to determine which attributes are indexed. If this error occurs, it means there was a failure in the type managers attempt to adjust the dmi_index objects.
ACTION: This really should only occur due to a database or query error. Check database errors or any additional errors that may have been reported and contact your Documentum Administrator.
PARAMS: The first parameter is the name of the type the index was created on.

ERROR: [DM_TYPE_MGR_E_QUERY_EXECUTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS The Type Manager encountered an error while trying to execute the following query: %s. Database error was %s.
CAUSE: Query execution failed.
ACTION: Check the error message from the database in order to determine the cause of the query failure.
PARAMS: The first parameter is the query that was being executed. The second parameter is the resulting error from the database.

ERROR: [DM_TYPE_MGR_E_CANT_FIND_TABLE]

SEVERITY: ERROR
DESCRIPTION: SSS Failure to find table %s as part of fetch of type %s: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The name of the table that should exist and the type of which it is a component and the error string from the database system.

ERROR: [DM_TYPE_MGR_E_CANT_DROP_COLUMN]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to drop column %s from table %s: error from database system is %s
CAUSE: Internal error.
ACTION: Check the error message from the database system. The The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The name of the column, the name of the table from which it is being dropped, and the error string from the database.

ERROR: [DM_TYPE_MGR_E_DROP_UPDATE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failure to update type table dropping attributes for type %s: error from database system is %s
CAUSE: Internal error.
ACTION: Check the error message from the database system. The The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The name of the type and the database error string.

ERROR: [DM_TYPE_MGR_E_LOAD_TYPINFO_UPD]

SEVERITY: ERROR
DESCRIPTION: S An Error occurred applying updates to the dmi_type_info object for new type %s during load processing. During load operations, when we we create a new type, we bring over the data dictionary information from the source docbases type info record. This error indicates that a failure was encountered during an attempt to apply that update.
CAUSE: Internal error in load processing
ACTION: Check for other errors which may give more detail on the problem. If the error appears transient, the load can be retried by simply fetching the same dm_load_record and issueing a new save on it. If the load cannot be retried, it should be reverted by fetching the dm_load_record and applying the revert api.
PARAMS: %1 – the name of the type being processed.

ERROR: [DM_TYPE_MGR_E_CANT_FIND_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Failure to find type %s in type table
CAUSE: Internal system error.
ACTION: Report this error and its parameters to your Documentum site representative.
PARAMS: The type name.

ERROR: [DM_TYPE_MGR_E_CANNOT_ADD_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to add attribute (%s) to type (%s) before saving failed.
CAUSE: Internal system error.
ACTION: Report this error and its parameters to your Documentum site representative.
PARAMS: The respective names of the attribute and the type.

ERROR: [DM_TYPE_MGR_E_CANT_FIND_TYPE_HANDLE]

SEVERITY: ERROR
DESCRIPTION: S Failure to find type with handle %s in type table
CAUSE: Internal system error.
ACTION: Report this error and its parameters to your Documentum site representative.
PARAMS: The id of the type.

ERROR: [DM_TYPE_MGR_E_REMOVE_COMMIT_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Failure to commit changes to type tables when removing type %s
CAUSE: Internal system error.
ACTION: Repeat the execution of the program if the problem persists, report to Documentum technical support.
PARAMS:

ERROR: [DM_TYPE_MGR_E_GET_ASPECT_INFO_UNABLE_TO_VERIFY]

SEVERITY: ERROR
DESCRIPTION: SS A database error occured while checking if aspect %s has attributes defined (OR) if objects that have the aspect attached has attributes defined by the aspect. Database error is %s
CAUSE: A database error occured while executing the GET_ASPECT_USE_INFO apply method.
ACTION: Refer to the accompanying database error.
PARAMS:

ERROR: [DM_TYPE_MGR_E_UNABLE_TO_CREATE_SEQUENCE_OBJECT]

SEVERITY: ERROR
DESCRIPTION: SS The type manager was unable to create a sequence object for the type %s as a result of attribute changes to one or more of its supertypes. The following database error occurred: %s
CAUSE: A failure occurred while issuing a CREATE SEQUENCE statement.
ACTION: Refer to the reason and take the corrective action.
PARAMS: The first parameter is the name of the type the sequence object was created on. Query Facility errors ** Documentum DocuServer ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1991-1999 ** All rights reserved. **

ERROR: [DM_TYPE_MGR_E_CANT_BUILD_OBJ_TABLE]

SEVERITY: ERROR
DESCRIPTION: S Failure to construct new object table while constructing new database: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The error string from the database system.

ERROR: [DM_TYPE_MGR_E_CANT_ADD_VERSION_STAMP]

SEVERITY: ERROR
DESCRIPTION: S Attempt to add (internal) version stamp attribute to type %s before saving failed.
CAUSE: Internal system error.
ACTION: Report this error and its parameters to your Documentum site representative.
PARAMS: The name of the type.

ERROR: [DM_TYPE_MGR_E_CANT_DROP_TABLE]

SEVERITY: ERROR
DESCRIPTION: SSS Failure to drop table %s as part of creation or modification of type %s: error from database system is %s
CAUSE: Internal system error.
ACTION: Report this error and its parameters to your Documentum site representative.
PARAMS: The names of the table being dropped and the type being stored and the error string from the database system.

ERROR: [DM_TYPE_MGR_E_SAVE_SAME_NAME]

SEVERITY: ERROR
DESCRIPTION: S Attempt to save type %s while type with this name already exists.
CAUSE: Program attempted to save a type that has the same name as one this already exists in the database.
ACTION: Remove the old type from the database first.
PARAMS: The name of the type.

ERROR: [DM_TYPE_MGR_E_GET_ASPECT_INFO_INVALID_ASPECT_NAME]

SEVERITY: ERROR
DESCRIPTION: S There is no aspect in the repository with the name %s OR the argument specified is either NULL or empty
CAUSE: ASPECT_NAME argument specified for GET_ASPECT_USE_INFO apply method is invalid.
ACTION: Specify a valid value for the ASPECT_NAME argument.
PARAMS:

ERROR: [DM_TYPE_MGR_E_NO_OLD_OBJ_TABLE]

SEVERITY: ERROR
DESCRIPTION: S Unable to either find or construct old style object table: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative. The old style object table is necessary to protect the docbase from inadvertant connection by an older server.
PARAMS: The error string from the database system.

ERROR: [DM_TYPE_MGR_E_ATTR_CHECK_FAILED]

SEVERITY: ERROR
DESCRIPTION: S A database query to check upgrade status failed. Message: %s.
CAUSE: While checking if an upgrade occurred, a query failed.
ACTION: Call Documentum tech support.
PARAMS:

ERROR: [DM_TYPE_MGR_E_CONNECTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: Cannot initialize type manager because of connection failure.
CAUSE: An attempt to make an internal database connection failed, causing the type manager to fail during initialization.
ACTION: Check to see that the database system is still running retry the operation.
PARAMS: None

ERROR: [DM_TYPE_MGR_E_CANNOT_REMOVE_DEFAULT_ASPECT]

SEVERITY: ERROR
DESCRIPTION: SS Cannot remove default aspect %s from type %s because the aspect is not found in the types type info.
CAUSE: The specified aspect name in the DQL ALTER TYPE REMOVE DEFAULT ASPECTS statement does not exist in the types type info.
ACTION: Check default_aspects in the type info object to make sure that the default aspect is specified there before issuing the DQL statement. It is possible that the specified default aspect was removed by another user already.
PARAMS:

ERROR: [DM_TYPE_MGR_E_INIT_DBMS_ERR]

SEVERITY: ERROR
DESCRIPTION: S Error from DBMS during initialization of the type manager. Error was: %s. This error message is given if an error is obtained during type initializtion at server startup which prevents the server from determining if a server type exists or not in the underlying database.
CAUSE: Error from DBMS during server startup.
ACTION: Resolve DBMS condition leading to error
PARAMS: – the dbms error message

ERROR: [DM_TYPE_MGR_E_SAVE_COMMIT_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Failure to commit transaction when saving type %s
CAUSE: Internal system error.
ACTION: Repeat the execution of the program if the problem persists, report to your Documentum site representative.
PARAMS: None.

ERROR: [DM_TYPE_MGR_E_TOO_MANY_ATTRIBUTES]

SEVERITY: ERROR
DESCRIPTION: SI Cannot add attributes since %s would have more than the maximum number of attributes (%d)
CAUSE: Attempted to add attributes to a type such that the type would have more than the maximum number of attributes allowed.
ACTION: None.
PARAMS: The first parameter is the name of the type. The second parameter is the maximum number of attributes allowed.

ERROR: [DM_TYPE_MGR_E_GET_ASPECT_INFO_INCORRECT_ASPECT_TYPE]

SEVERITY: ERROR
DESCRIPTION: dmc_aspect_type does not have the i_attr_def attribute
CAUSE: dmc_aspect_type type in the repository does not have i_attr_def attribute.
ACTION: Refer to the installation guide and resolve any installation/upgrade errors
PARAMS:

ERROR: [DM_TYPE_MGR_E_CANT_BUILD_OBJ_INDEX]

SEVERITY: ERROR
DESCRIPTION: S Failure to construct type index on object table: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The error string from the database system.

ERROR: [DM_TYPE_MGR_E_ACL_REVISE_GROUP]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to revise the group name of the ACL %s in domain %s for type %s.
CAUSE: Failed to revise the group name of the associated ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_TYPE_MGR_E_TYPE_INFO_UPGRADE_FAILED]

SEVERITY: ERROR
DESCRIPTION: The type_info upgrade failed.
CAUSE: The type_info object upgrade failed.
ACTION: Call Documentum tech support.
PARAMS:

ERROR: [DM_TYPE_MGR_E_CANT_SAVE_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSS Failure to insert row for type %s in table %s: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The names of the type and the table that was being updated and the error string from the database system.

ERROR: [DM_TYPE_MGR_E_CHECK_FTINDEX_FAIL]

SEVERITY: ERROR
DESCRIPTION: S While checking for whether types already indexed, the following database query %s could not be executed.
CAUSE: Unknown
ACTION: Report this error and its parameters to your Documentum site representative.
PARAMS: The failed database query command.

ERROR: [DM_TYPE_MGR_E_CANT_CREATE_VIEW]

SEVERITY: ERROR
DESCRIPTION: SSS Failure to create view table %s as part of creation of type %s: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The names of the view and the type being created and the error string from the database system.

ERROR: [DM_TYPE_MGR_E_ZERO_PERMIT]

SEVERITY: ERROR
DESCRIPTION: SIII Failed to save ACL for type %s because permits for owner, group and world, (%d,%d,%d), need to be either all NULLs or not NULLs.
CAUSE: The OGW-permits under ACL security mode need to be either all zeros or all none-zeros.
ACTION: Reset the OGW-permits.
PARAMS:

ERROR: [DM_TYPE_MGR_E_MAKE_INDEX_FAILED]

SEVERITY: ERROR
DESCRIPTION: S MAKE_INDEX failed to create the requested index. Reason: %s
CAUSE: A failure occured while processing the MAKE_INDEX apply method.
ACTION: Refer to the reason and take the corrective action.
PARAMS:

ERROR: [DM_TYPE_MGR_E_ATTRIBUTE_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: SS The length of the %s attribute of the type %s is too long
CAUSE: The length of a string valued attribute exceeds the database limit
ACTION: Reduce the length and retry the type creation or alteration
PARAMS:

ERROR: [DM_TYPE_MGR_E_UNABLE_TO_LOCK_TYPE_CHAIN]

SEVERITY: ERROR
DESCRIPTION: The Type Manager was unable to lock the type chain for type %s.
CAUSE: The Type Manager encountered an error while trying to lock the type chain through the dm_dd_root_types table. The type chain is typically locked during a ALTER/CREATE/DROP or Data Dictionary publish operation.
ACTION: Refer to additional error messages to determine the cause of the failure.
PARAMS: The first parameter is the name of the type.

ERROR: [DM_TYPE_MGR_E_BAD_INDEX_SPACE]

SEVERITY: ERROR
DESCRIPTION: S The index space %s does not exist
CAUSE: An invalid index space name passed to create index or move index
ACTION: Determine the proper index space name
PARAMS: The name of the index space

ERROR: [DM_TYPE_MGR_E_BAD_VSTAMP]

SEVERITY: ERROR
DESCRIPTION: IS Unexpected version stamp (%d) is found for type %s.
CAUSE: The dm_vstamp object found for this type contains an unexpected version number. The dm_vstamp object could be corrupted. The type may have been changed unexpectedly.
ACTION: Call Documentum tech support.
PARAMS: The vstamp value and the type name.

ERROR: [DM_TYPE_MGR_E_ALTER_BAD_ARGS]

SEVERITY: ERROR
DESCRIPTION: SSS Operation %s failed on type %s because %s
CAUSE: User error attempting to add/drop attributes from type
ACTION: Correct the error and retry the operation
PARAMS: The name of the operation (add, drop), the name of the type and the reason for the failure.

ERROR: [DM_TYPE_MGR_E_OBJECT_REMOVE_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Failure to remove objects of type %s from object table before removing type: error from database system was %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The name of the type and the database error string.

ERROR: [DM_TYPE_MGR_E_ALTER_DATABASE_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to modify type %s failed — database error message was: %s
CAUSE: There was a database failure while modifying a type
ACTION: Correct the error and retry the operation
PARAMS: The name of the type and the error message from the database syste

ERROR: [DM_TYPE_MGR_E_INDEX_DROP_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SSS Failure to drop index named %s for type %s: error from database system is %s
CAUSE: Internal system error.
ACTION: Check the error message from the database system. The problem may be resolvable in the database system. If not, report this error and the error from the database system, and any other error messages on the error message queue to your Documentum site representative.
PARAMS: The name of the index, the name of the type for which it was being created, and the error string from the database.

ERROR: [DM_TYPE_MGR_E_CANNOT_CREATE_ROOT_TYPES_TABLE]

SEVERITY: ERROR
DESCRIPTION: The Type Manager was unable to create the dm_dd_root_types table. More specific error messages should accompany this error.
CAUSE: The Type Manager encountered an error during the creation of the dm_dd_root_types table.
ACTION: It is necessary to check additional error messages for details on why this failure occurred.
PARAMS: None

ERROR: [DM_TYPE_MGR_W_SAVE_SUPER_FIRST]

SEVERITY: WARNING
DESCRIPTION: SS Before saving type %s must save its supertype %s.
CAUSE: Program attempted to save a type for which the supertype has not yet been saved.
ACTION: Save the supertype first, and then save the type.
PARAMS: The names of the type and its supertype.

ERROR: [DM_TYPE_MGR_W_UNABLE_TO_MOVE_INDEX]

SEVERITY: WARNING
DESCRIPTION: DSI The type manager was unable to move the index with id %s, for type %s, at position %d because the position is invalid. The database index has been dropped. The dmi_index object should be corrected manually and the MOVE_INDEX apply method should be used to recreate the database index.
CAUSE: There is a known problem for customers who have upgraded their documentum server that was caused by the fact that attribute indices are determined by using the attribute position. The server was not previously adjusting these positions as types were modified which now makes them potentially invalid. In the case that this warning is issued, the attribute position is no longer a valid attribute of the type. Since we do not know what attribute the index should be on, the server simply drops the index and request customers to correcting the attribute position in dmi_index object and using the MOVE_INDEX apply method to properly adjust the index.
ACTION: The customer should determine which attribute the index should be on, and then manually correct the dmi_index object in the database. They should then use the MOVE_INDEX apply method to recreate the index in the database.
PARAMS: The first parameter is the object id of the dmi_index object. The second parameter is the name of the type the index was created on. The third parameter is the attribute position of the index.

ERROR: [DM_TYPE_MGR_W_UNABLE_TO_REMOVE_COMPOSITE_TYPE]

SEVERITY: WARNING
DESCRIPTION: The type manager was unable to remove the dm_composite type.
CAUSE: The type manager was unable to remove the composite type. As part of Piper, the type manager attempts to remove the composite type since it is no longer supported. If the type manager was unable to remove the type, it most likely suggests that the version stamp is bad.
ACTION: This should not affect the server at all. The composite removal is simply for convenience and to remove unnecessary tables from the database. No action is required.
PARAMS: None.

ERROR: [DM_TYPE_MGR_W_UNABLE_TO_CLEANUP_INDEX]

SEVERITY: WARNING
DESCRIPTION: DS The type manager was unable to remove the dmi_index object with id %s on type %s. This index needs to be removed since it references a table that no longer exists. Remove the dmi_index object and any references to it in the types dm_type table.
CAUSE: The dmi_index object refers to an attribute(s) that no longer exists because one of the corresponding types tables in the database does not exist. This is most likely due to the r_table of a type being dropped since there are no more repeating attributes, but the corresponding indices were not dropped.
ACTION: Check the dmi_index object and make sure it is removed. Also, if the index was on the r_object_id or i_position columns, make sure that the dm_type object no longer refers to the dmi_index object.
PARAMS: The first parameter is the object id of the dmi_index object. The second parameter is the name of the type that is indexed.

ERROR: [DM_TYPE_MGR_W_INDEX_WITHOUT_TYPE_TABLE]

SEVERITY: WARNING
DESCRIPTION: DS The dmi_index object with id %s on type %s, refers to an attribute in a table that no longer exists in the database. The type manager will drop the dmi_index object and clean up.
CAUSE: The dmi_index object refers to an attribute(s) that no longer exists because one of the corresponding types tables in the database does not exist. This is most likely due to the r_table of a type being dropped since there are no more repeating attributes, but the corresponding indices were not dropped.
ACTION: Check the dmi_index object and make sure it is removed. Also, if the index was on the r_object_id or i_position columns, make sure that the dm_type object no longer refers to the dmi_index object.
PARAMS: The first parameter is the object id of the dmi_index object. The second parameter is the name of the type that is indexed.

ERROR: [DM_TYPE_MGR_W_SAVE_SAME_NAME]

SEVERITY: WARNING
DESCRIPTION: S Attempt to save type %s while type with this name already exists.
CAUSE: Program attempted to save a type that has the same name as one this already exists in the database.
ACTION: Remove the old type from the database first.
PARAMS: The name of the type.

ERROR: [DM_TYPE_MGR_W_UNABLE_TO_REMOVE_COMPOSITE_SNAPSHOT_TABLE]

SEVERITY: WARNING
DESCRIPTION: The type manager was unable to remove the dmi_composite_snapshot table.
CAUSE: There was an error in removing the dmi_composite_snapshot table from the database. This is part of the Piper composite removal.
ACTION: The table can be dropped from the database manually, but it is not necessary.
PARAMS: None.

ERROR: [DM_TYPE_MGR_W_BAD_INDEX_ATTRIBUTE]

SEVERITY: WARNING
DESCRIPTION: SI Attempt to create index on type %s using illegal attribute %d
CAUSE: Program attempted to create an index with an invalid attribute specification (the attribute does not exist or has an undefined type).
ACTION: None.
PARAMS: The name of the type and the position of the erroneous attribute in the type.

ERROR: [DM_TYPE_MGR_W_MIXED_INDEX]

SEVERITY: WARNING
DESCRIPTION: S Attempt to create index on type %s with both repeating and single valued attributes.
CAUSE: Program attempted to create an index with a specification that includes both single- and multi-valued attributes.
ACTION: Use separate indices for the single-valued attributes and the multi-valued attributes.
PARAMS: The name of the type.

ERROR: [DM_TYPE_MGR_W_TYPE_HAS_OBJECTS]

SEVERITY: WARNING
DESCRIPTION: S Attempt to remove type %s, which still has objects.
CAUSE: Program attempted to remove a type for which objects still exists.
ACTION: Destroy the objects in the type before removing it.
PARAMS: The name of the type.

ERROR: [DM_TYPE_MGR_W_UNABLE_TO_PURGE_PENDING_PUBLISHES_FOR_TYPE]

SEVERITY: WARNING
DESCRIPTION: S There was an error while trying to remove data dictionary entries relating to the %s type. The type will still be dropped.
CAUSE: The server was trying to remove entries pertaining to the type being dropped from the dd_publish_log, but could not.
ACTION: Normal server operation should continue, although there may be a problem with the dd_publish_log table that entries could not be removed. Check to see if any rows in the table are locked, or if the rows pertaining to the type exist.
PARAMS: The first parameter of the error is the name of the type being dropped.

ERROR: [DM_TYPE_MGR_W_BAD_TYPE_INDEX]

SEVERITY: WARNING
DESCRIPTION: S Attempt to create an index for non-persistent type %s.
CAUSE: Program attempted to create an index on attributes of a type that is not in the database.
ACTION: None: internal programming error. No index is created.
PARAMS: The name of the type.

ERROR: [DM_TYPE_MGR_W_NULL_TYPE_INDEX]

SEVERITY: WARNING
DESCRIPTION: Attempt to create an index on attributes of the NULL type.
CAUSE: Program attempted to create an index on the NULL type.
ACTION: None.
PARAMS: None.

ERROR: [DM_TYPE_MGR_W_ALTER_NOT_FOUND]

SEVERITY: WARNING
DESCRIPTION: S the attributes being dropped for type %s do not exist
CAUSE: The user specified a set of non-existent attributes to be dropped from a type.
ACTION: None.
PARAMS: The name of the type

ERROR: [DM_TYPE_MGR_W_DROP_FAILURE]

SEVERITY: WARNING
DESCRIPTION: SSS Cannot remove table %s for type %s: error from database system is %s
CAUSE: Program could not drop one of the internal attribute tables while either removing a type from the database or dropping the last single- or multi-valued attribute of a type.
ACTION: None: internal programming error.
PARAMS: The names of the table that could not be removed and the type being removed and the error string from the database system.

ERROR: [DM_TYPE_MGR_W_REMOVE_SUBTYPES]

SEVERITY: WARNING
DESCRIPTION: S Attempt to remove type %s, which has subtypes.
CAUSE: Program attempted to remove a type that has subtypes.
ACTION: Remove the subtypes first, then remove the type.
PARAMS: The name of the type.

ERROR: [DM_TYPE_MGR_W_NAME_TOO_LONG]

SEVERITY: WARNING
DESCRIPTION: SS attempt to save type %s failed because attribute or type name %s is too long
CAUSE: The maximum length of persistent type and attribute names is 27 characters.
ACTION: Shorten the names and redo the save.
PARAMS: The name of the type and the name that was too long

nahoru

DM_UPGRADE_MGR

ERROR: [DM_UPGRADE_MGR_F_INTERNAL_ERROR]

SEVERITY: FATAL
DESCRIPTION: S The Upgrade Manager has encountered an internal error: %s.
CAUSE: An internal error has occurred in the Upgrade Manager
ACTION: Report this error to your Documentum Tech Support Representative.
PARAMS: Details of the internal error Id: dmuser.e,v 4.1 1996/11/22 12:19:28 roger Exp $ DmUser and dmGroup classes errors // // Documentum DocuServer // Confidential Property of Documentum, Inc. // (c) Copyright Documentum, Inc., 1992 – 1995 // All rights reserved.

ERROR: [DM_UPGRADE_MGR_F_INTERNAL_INDEX_VALIDATION_FAILURE]

SEVERITY: FATAL
DESCRIPTION: D Unable to validate dmi_index object with ID %s due to an internal error.
CAUSE: This is an internal error. The only reason we should ever get this is that our internal hard coded list of indices that we use to validate against is out of synch. Check the hard coded list in dmconv.cxx, dmUpgrade40 class.
ACTION: Report this error to a Documentum Adminstrator.
PARAMS: The first parameter is the object id of the dmi_index object that was being validated.

ERROR: [DM_UPGRADE_MGR_E_INDEXED_ATTRIBUTE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SSD The attribute %s of type %s, indexed by dmi_index object with ID %s does not exist.
CAUSE: The indexed attribute does not exist in the docbase.
ACTION: Verify that the attribute referenced by the dmi_index object exists. If it does not exist, remove the index and restart upgrade.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type. The third parameter is the id of the dmi_index object.

ERROR: [DM_UPGRADE_MGR_E_QUERY_EXECUTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS The Upgrade Manager failed to execute the following query: %s. The database error is %s.
CAUSE: Query execution failed.
ACTION: Check the error message from the database in order to determine the cause of the query failure.
PARAMS: The first parameter is the query that was being executed. The second parameter is the resulting error from the database.

ERROR: [DM_UPGRADE_MGR_E_UNABLE_TO_VALIDATE_INDEX]

SEVERITY: ERROR
DESCRIPTION: D Unable to validate dmi_index object with ID %s. The index either could not be validated or does not exist.
CAUSE: The upgrade code attempts to validate all Documentum indices due to a potential error during previous upgrades in which the dmi_index object was inconsistent with the actual indexed attribute. If this error occurs, either the index could not be properly validated, or it does not exist.
ACTION: Contact a Documentum Administrator with the information given in the error
PARAMS: The first parameter is the object id of the dmi_index object that was being validated.

ERROR: [DM_UPGRADE_MGR_E_UNABLE_TO_CREATE_INDEX]

SEVERITY: ERROR
DESCRIPTION: SS The Upgrade Manager failed to create an index on table %s. The error from the database was: %s
CAUSE: Index creation on a table failed. A database error has occurred.
ACTION: Contact a Documentum Administrator with the supplied database error.
PARAMS: The table the index was being created on. The error from the database.

ERROR: [DM_UPGRADE_MGR_W_UNABLE_TO_VALIDATE_USER_INDEX]

SEVERITY: WARNING
DESCRIPTION: DS Unable to validate the dmi_index object with ID %s. The index name is %s. Verify that the index refers to the correct attribute(s).
CAUSE: The upgrade code tried to validate all indices due to a potential error during previous upgrades in which the attribute field in dmi_index was not updated properly. As a result, some indices may point to the wrong attribute(s).
ACTION: Users should drop this index using the DROP_INDEX apply method and then recreate the index using the MAKE_INDEX apply method.
PARAMS: The first parameter is the object id of the dmi_index object. The second parameter is the index name of the dmi_index object.

ERROR: [DM_UPGRADE_MGR_I_SYBASE_ROW_LOCKING_COMPLETED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has completed verifying that row level locking is enabled for all tables.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_PREVENTING_PRE_40_SERVER_FROM_STARTING]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has now reached a point where it cannot revert the docbase back to a pre-4.0 server.
CAUSE: This is an informational message generated at the point when the server cannot be reverted back to a pre-4.0 server.
ACTION: None
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_DOCBASE_UPGRADE_COMPLETE]

SEVERITY: INFORMATION
DESCRIPTION: S The Upgrade Manager has successfully upgraded the docbase to version %s.
CAUSE: This is an informational message generated at the beginning of upgrade.
ACTION: None.
PARAMS: The version we are trying to upgrade to.

ERROR: [DM_UPGRADE_MGR_I_INDEX_VALIDATION_COMPLETED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has successfully completed validating Documentum indices.
CAUSE: This is an informational message generated at the completion of indice validation.
ACTION: None
PARAMS: None

ERROR: [DM_UPGRADE_MGR_I_INDEX_VALIDATION_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has started to validate Documentum indices. The Upgrade Manager will attempt to correct any incorrect indices
CAUSE: This is an informational message generated at the beginning of indice validation.
ACTION: None
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_VALIDATING_INDEX]

SEVERITY: INFORMATION
DESCRIPTION: D The Upgrade Manager is validating index with ID %s.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: The object id of the index object being validated.

ERROR: [DM_UPGRADE_MGR_I_DROPPING_INDEX_ON_DMI_OBJECT_TYPE]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager is dropping the index on the dmi_object_type table for enhanced upgrade performance
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_RECREATING_INDEX_ON_DMI_OBJECT_TYPE]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager is re-creating the index on dmi_object_type table.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_OBJECT_TABLE_CONVERSION_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has started the object table conversion.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_DOCBASE_UPGRADE_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: S The Upgrade Manager has started to upgrade the docbase to version %s.
CAUSE: This is an informational message generated at the start of upgrade.
ACTION: None.
PARAMS: The version we are trying to upgrade to.

ERROR: [DM_UPGRADE_MGR_I_INDEX_CREATION_FOR_UPGRADE_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has started to create the necessary indices for upgrade. This may take some time.
CAUSE: This is an informational message generated at the beginning of indices creation
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_DOCBASE_UPGRADE_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: S The Upgrade Manager was unable to upgrade the docbase to version %s. Customers are encouraged to turn on sql tracing as well as upgrade tracing and restart the upgrade. The additional tracing information will be helpful in determining the cause of upgrade failure.
CAUSE: The server upgrade process failed due to one or more errors. More detailed information regarding the error should have been reported earlier in the log.
ACTION: Gather up error information from the server log and determine the cause of the failure. If the cause can be fixed, the upgrade should be re-runnable.
PARAMS: The version we are trying to upgrade to.

ERROR: [DM_UPGRADE_MGR_I_UPGRADE_INFO]

SEVERITY: INFORMATION
DESCRIPTION: S %s.
CAUSE: This is an informational message generated when the document base is upgrading.
ACTION: None.
PARAMS:

ERROR: [DM_UPGRADE_MGR_I_INDEX_CREATION_FOR_UPGRADE_COMPLETED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has created the necessary indices for upgrade.
CAUSE: This is an informational message generated at the completion of indices creation
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_SYBASE_ROW_LOCKING_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has started verifying that row level locking is enabled for all tables.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_INDEX_CREATION_FOR_UPGRADE_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager was unable to create the necessary indices for upgrade.
CAUSE: This is an informational message generated upon failure of index creation. More detailed error messages should have been reported earlier.
ACTION: Look at the server log for additional error messages which may indicate the nature of the problem.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_OBJECT_TABLE_CONVERSION_COMPLETED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has completed the object table conversion.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_SYBASE_ROW_LOCKING_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has failed to set row locking on existing tables.
CAUSE: This is an informational message generated upon failure to set row level locking. More detailed error messages should have been reported earlier.
ACTION: Look at the server log for additional error messages which may indicate the nature of the problem.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_OBJECT_TABLE_CONVERSION_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has encountered a failure during object table conversion.
CAUSE: This is an informational message generated upon failure of object table conversion. More detailed error messages should have been reported earlier.
ACTION: Look at the server log for additional error messages which may indicate the nature of the problem.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_INDEX_VALIDATION_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager failed to validate Documentum indices.
CAUSE: This is an informational message generated upon failure of index validation. More detailed error messages should have been reported earlier.
ACTION: Look at the server log for additional error messages which may indicate the nature of the problem.
PARAMS: None.

nahoru

DM_USER

ERROR: [DM_USER_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dm_user type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum Site Representive.
PARAMS:

ERROR: [DM_USER_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_user object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report this message and any parameters to your Documentum Site Representive.
PARAMS:

ERROR: [DM_USER_F_INT1]

SEVERITY: FATAL
DESCRIPTION: S The following database query could not be executed: %s.
CAUSE: Inconsistency between the server and the user type.
ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_USER_F_CVT1]

SEVERITY: FATAL
DESCRIPTION: S Could not update the new user_db_name attribute. Database error was: %s
CAUSE: In the current release a new attribute has been added to the dm_user type: user_db_name. Formerly, this name, the users database login name, was equivalent to the user_name. They can now differ, and the conversion to the current release attempted to initialize the user_db_name values to the user_name values. This step has failed.
ACTION: Only users who are going to register database tables for use within DocuServer need to have a user_db_name. For all other users, the user_db_name attribute is optional. If the conversion failed, you can either 1) run an SQL query to set the user_db_name to the user_name, or 2) leave most of the user_db_name values empty, and only set those that are actually needed. The docbase owners user_db_name must be set.
PARAMS:

ERROR: [DM_USER_F_UNKNOWN_AUTH_PROTOCOL]

SEVERITY: FATAL
DESCRIPTION: The docbase auth_protocol is not of any value known to server.
CAUSE: Unknown.
ACTION: Ask the DBA to fix the corrupted data and then restart the server.
PARAMS:

ERROR: [DM_USER_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dm_user type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum Site Representive.
PARAMS:

ERROR: [DM_USER_F_INIT4]

SEVERITY: FATAL
DESCRIPTION: S Cannot create or retrieve the superuser %s dmUser object during initialization.
CAUSE: Possible problems with underlying database. ACTION:Look at the error logged by the type manager. Report this message and any parameters to your Documentum Site Representive.
ACTION:
PARAMS:

ERROR: [DM_USER_F_CVT2]

SEVERITY: FATAL
DESCRIPTION: Could not convert the dm_user type.
CAUSE: In the current release two new attributes have been added to the dm_user type: user_db_name and description. The conversion failed during the addition of these attributes to the dm_user type.
ACTION: Report this message to your Documentum Site representative.
PARAMS:

ERROR: [DM_USER_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert the dm_user to version %d.
CAUSE: Type conversion failed.
ACTION: Report this message to your Documentum Site representative.
PARAMS:

ERROR: [DM_USER_E_CANT_FETCH_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a user – Invalid object ID %s
CAUSE: Cannot fetch the user with the given object id.
ACTION: Try again with the correct id.
PARAMS:

ERROR: [DM_USER_E_CANT_SET_SUPER_USER_STATE]

SEVERITY: ERROR
DESCRIPTION: A super users state can not be set by any one other than a super user
CAUSE: A non-super user tried to set a super users user_state
ACTION: dont try to change a super users user_state if you are not a super user.
PARAMS:

ERROR: [DM_USER_E_MUST_HAVE_LOGINNAME]

SEVERITY: ERROR
DESCRIPTION: S A new %s user object must have a login name
CAUSE: All user definition must have a user_name, user_login_name and e-mail address before save.
ACTION: Set all required attributes and try again.
PARAMS:

ERROR: [DM_USER_E_INVALID_XPRIVILEGES]

SEVERITY: ERROR
DESCRIPTION: IS Specified privileges %d are invalid, supported values are %s and their ord values.
CAUSE: Tried to set an invalid privilege code.
ACTION: Try again with valid privilege code.
PARAMS:

ERROR: [DM_USER_E_INVALID_XPRIVILEGE_VALUES]

SEVERITY: ERROR
DESCRIPTION: IIII Specified privileges %d are invalid, supported values are %d, %d, %d and their ord values.
CAUSE: Tried to set an invalid privilege code.
ACTION: Try again with valid privilege code.
PARAMS:

ERROR: [DM_USER_E_NEED_SU_OR_SYS_PRIV]

SEVERITY: ERROR
DESCRIPTION: S The current user (%s) needs to have superuser or sysadmin privilege.
CAUSE: Must have Superuser or SysAdmin privilege to perform this operation.
ACTION: Consult your Documentum Administrator.
PARAMS:

ERROR: [DM_USER_E_CANT_CREATE_EXISTING_USER]

SEVERITY: ERROR
DESCRIPTION: S Cannot create user %s since it already exists
CAUSE: Tried to create a user that already exists. All user names must be unique.
ACTION: Try again with a different user_name.
PARAMS:

ERROR: [DM_USER_E_NEED_SYS_OR_USER_ADMIN_OR_OWNER]

SEVERITY: ERROR
DESCRIPTION: SS The user (%s) needs to have at least sysadmin privilege or be the users user admin or owner to change the %s user object.
CAUSE: Must have at least SysAdmin privilege or the users user admin to save user objects.
ACTION: Consult your Documentum Administrator.
PARAMS:

ERROR: [DM_USER_E_ILLEGAL_DIR_NAME]

SEVERITY: ERROR
DESCRIPTION: SS Cannot save a directory user %s because its user_login_domain (%s) is not a legal LDAP config name
CAUSE: For directory users, the user_login_domain must be a legal directory config name.
ACTION: Make sure to provide a legal directory config name for the user.
PARAMS:

ERROR: [DM_USER_E_PASSWORD_ENCRYPTION_FAIL]

SEVERITY: ERROR
DESCRIPTION: Server failed to encrypt user password.
CAUSE: An internal error occured while encrypting user password.
ACTION: A previous error message may contain some native error code. Please contact Documentum Tech Support with a trace of all error messages.
PARAMS:

ERROR: [DM_USER_E_LOGON_DOM_NO_MATCH_USR]

SEVERITY: ERROR
DESCRIPTION: S You cannot authenticate against %s domain.
CAUSE: You have not specified a logon domain, or you have specified a domain different from the one used to create your docbase user account.
ACTION: Logon again using the domain name which was used to create your docbase user account. See you dmadmin if you do not know the correct domain name.
PARAMS:

ERROR: [DM_USER_E_PASSWORD_DECRYPTION_FAIL]

SEVERITY: ERROR
DESCRIPTION: Server failed to decrypt user password.
CAUSE: An internal error occured while encrypting user password.
ACTION: A previous error message may contain some native error code. Please contact Documentum Tech Support with a trace of all error messages.
PARAMS:

ERROR: [DM_USER_E_CANT_SAVE_ACL]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to save ACL %s in name space %s for user object %s.
CAUSE: Failed to save the default ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_USER_E_SPECIFY_ALTERNATE]

SEVERITY: ERROR
DESCRIPTION: A valid alternate performer for workflows must be specified, if workflow_disabled is set.
CAUSE: The attribute workflow_disabled was set to True, but an alternate performer was not specified, or an invalid performer name was given.
ACTION: Either enter a valid performer in the user_delegation, or set workflow_disabled to False.
PARAMS:

ERROR: [DM_USER_E_MUST_HAVE_OSNAME]

SEVERITY: ERROR
DESCRIPTION: S A new %s user object must have an OS user name
CAUSE: All user definition must have a user_name, user_os_name and e-mail address before save.
ACTION: Set all required attributes and try again.
PARAMS:

ERROR: [DM_USER_E_NOT_DOCUMENTUM_USER]

SEVERITY: ERROR
DESCRIPTION: S User %s does not exist in the docbase
CAUSE: The user attempting to open a session does not exist.
ACTION: Try again with the correct name.
PARAMS:

ERROR: [DM_USER_E_DOCUMENTUM_USER_LOCKED]

SEVERITY: ERROR
DESCRIPTION: S User %s is locked in the repository — session closed.
CAUSE: A locked user tried to login to the repository.
ACTION: Ask the Documentum Administrator to unlock the account.
PARAMS:

ERROR: [DM_USER_E_ENCRYPTION_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: II The internal gernerated encrypted password is too long (%d). It cannot exceed the size of %d.
CAUSE: An internal error caused the size to be too large.
ACTION: A previous error message may contain some native error code. Please contact Documentum Tech Support with a trace of all error messages.
PARAMS: I – Actual string size of the encrypted password. I – Allowed string size.

ERROR: [DM_USER_E_INVALID_ACL_DOMAIN]

SEVERITY: ERROR
DESCRIPTION: SS The user %s is given an invalid ACL domain %s.
CAUSE: Invalid ACL domain is given.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_USER_E_NEED_SU_OR_SYS_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser or sysadmin privilege to save or destroy %s user object.
CAUSE: Must have Superuser or SysAdmin privilege to save user objects.
ACTION: Consult your Documentum Administrator.
PARAMS:

ERROR: [DM_USER_E_ACL_REVISE_GROUP]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to revise the group name of the ACL %s in domain %s for user %s.
CAUSE: Failed to revise the group name of the associated ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_USER_E_MUST_HAVE_EMAIL]

SEVERITY: ERROR
DESCRIPTION: S A new %s user object must have a EMail address
CAUSE: All user definition must have a user_name, user_os_name and e-mail address before save.
ACTION: Set all required attributes and try again.
PARAMS:

ERROR: [DM_USER_E_STATE_WORKFLOW_CONFLICT]

SEVERITY: ERROR
DESCRIPTION: You can not set user_state to inactive and workflow_ready to ready concurently
CAUSE: try to set user_state to inactive and workflow_ready to ready.
ACTION: set user_state to inactive or workflow_ready to ready, but not both.
PARAMS:

ERROR: [DM_USER_E_MUST_HAVE_LOGON_DOMAIN]

SEVERITY: ERROR
DESCRIPTION: You must specify the OS/LDAP domain to successfully logon to the docbase
CAUSE: The docbase is running in domain_required mode. All users must specify the OS domain to authenticate against when logon. Starting from 5.3, server supports multiple LDAP services. As a result, each LDAP user is required to include the LDAP object name in
ACTION: Specify the domain name and try again.
PARAMS:

ERROR: [DM_USER_E_NEED_SUPER_USER_PRIV]

SEVERITY: ERROR
DESCRIPTION: S The current user (%s) needs to have superuser privilege to save the object.
CAUSE: Must have superuser privilege to save the object. The user tried to do the following without superuser privileges: . add or remove superuser/sysadmin/audit privileges from the user object. . user_db_name. . user_xprivileges (checked in ValidateXSecurity). . first_failed_auth_utc_time. . last_login_utc_time. . deactivated_utc_time. . deactivated_ip_addr. . user_ldap_dn.
ACTION: Consult your Documentum superuser.
PARAMS:

ERROR: [DM_USER_E_EXISTING_USER_OSNAME]

SEVERITY: ERROR
DESCRIPTION: S Cannot create user %s since its user_os_name already exists
CAUSE: Tried to create a user that its user_os_name exists. All user names must be unique.
ACTION: Try again with a different user_os_name.
PARAMS:

ERROR: [DM_USER_E_LOAD_OSNAME_CONFLICT]

SEVERITY: ERROR
DESCRIPTION: SSS A dm_user object with user name %s was encountered which has a user_os_name (%s) which conflicts with an existing dm_user object. The user_os_name of the object being loaded has been changed to %s.
CAUSE: The Docbase cannot support two different users with the same user_os_name, but a dm_user object was found in the dumpfile with a user_os_name that conflicts with an existing user.
ACTION: If the System Administrator takes no action, the docbase and objects will still be usable, but it will not be possible for the user identified above to actually log into the docbase. If it is intended for the new dm_user to be a valid user of the docbase, then the new and old users must be differentiated by changing one of their os names. The System Administrator should change the system os names to be different and then also change the user_os_name value of the appropriate dm_user object. If it was intended that the two conflicting users were actually the same user – but the user_name values of the dm_user objects were inadvertantly slightly different, then it is possible to find all of the newly loaded objects owned by the new dm_user and change their ownership to the local user. The new invalid user object can then be removed.
PARAMS: %1s – the user_name of the load object %2s – the conflicting user_os_name %3s – the new user_os_name of the load object

ERROR: [DM_USER_E_INVALID_PRIVILEGE_VALUES]

SEVERITY: ERROR
DESCRIPTION: III Specified privileges %d are invalid, supported range is %d:%d
CAUSE: Tried to set an invalid privilege code.
ACTION: Try again with valid privilege code.
PARAMS:

ERROR: [DM_USER_E_CANT_SAVE_A_USER]

SEVERITY: ERROR
DESCRIPTION: S Cannot save user %s.
CAUSE: Couldnt save the user object.
ACTION: Most likely the current in memory user object is out of date.
PARAMS:

ERROR: [DM_USER_E_INVALID_PERMIT]

SEVERITY: ERROR
DESCRIPTION: IS Invalid permit %d specified for user %s.
CAUSE: User has specified a permit that is outside the valid range.
ACTION: Specify a valid permit number.
PARAMS:

ERROR: [DM_USER_E_DIR_MAPPED_ATTR_CHANGED]

SEVERITY: ERROR
DESCRIPTION: SS Cannot save the directory user %s because at least one directory-mapped attribute (%s) has been changed
CAUSE: For directory users, non-superuser is not allowed to change any directory-mapped attribute.
ACTION: Do not change any directory-mapped attributes. You need to either reset or revert the object in order to save other changes.
PARAMS:

ERROR: [DM_USER_E_CANT_GRANT_PRIV_TO_SELF]

SEVERITY: ERROR
DESCRIPTION: IS You cant grant the specified privilege %d to yourself (%s).
CAUSE: You can not grant PURGE AUDIT and CHANGE AUDIT privilege to yourself.
ACTION: Consult your Documentum Administrator.
PARAMS:

ERROR: [DM_USER_E_RESERVED_NAME]

SEVERITY: ERROR
DESCRIPTION: S The user name %s is reserved.
CAUSE: The user name provided is a reserved name.
ACTION: Pick a different user name. Currently, the following names are reserved: . dm_owner . dm_group . dm_world
PARAMS:

ERROR: [DM_USER_E_EXISTING_USER_LOGINNAME]

SEVERITY: ERROR
DESCRIPTION: S Cannot create user %s since its user_login_name already exists
CAUSE: Tried to create a user that its user_login_name exists. All user login names must be unique.
ACTION: Try again with a different user_login_name.
PARAMS:

ERROR: [DM_USER_E_CANT_DROP_USER_FROM_GROUP]

SEVERITY: ERROR
DESCRIPTION: SS Cannot drop user %s from group %s.
CAUSE: Couldnt drop the specified user from a group.
ACTION: Examine the following errors on your error queue for more help. Either invalid user or group name.
PARAMS:

ERROR: [DM_USER_E_CANT_FETCH_ACL]

SEVERITY: ERROR
DESCRIPTION: SSSS Failed to fetch the default ACL %s in name space %s of user %s. [%s]
CAUSE: Failed to fetch the default ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_USER_E_CANT_DESTROY_A_USER]

SEVERITY: ERROR
DESCRIPTION: S Cannot destroy user %s.
CAUSE: User documents could not be unlocked or its a user for group object.
ACTION: If is_group is set then do not delete it. otherwise see previous messages on why documents could not be unlocked.
PARAMS:

ERROR: [DM_USER_E_MUST_HAVE_LOGINDOMAIN]

SEVERITY: ERROR
DESCRIPTION: S A new user object (%s) must have a login domain name
CAUSE: All user definition must have a user_name, user_login_name, user_login_domain (when domain_required mode is on), and e-mail address before save.
ACTION: Set all required attributes and try again.
PARAMS:

ERROR: [DM_USER_E_NOT_IN_RESTRICTED_FOLDERS]

SEVERITY: ERROR
DESCRIPTION: SS The folder (%s) is not in the users (%s) restricted_folder_ids list.
CAUSE: If restricted_folder_ids is specified, its default folder must reside in a folder specified in the restricted_folder_ids or a subfolder of any folder in the list. The ID you have specified may be a valid object ID, but it does not reside in a folder (or subfolder) specified in the users restricted_folder_ids.
ACTION: Make sure the supplied folder is in one of the restricted folders or their subfolders.
PARAMS: The first value is the offending folder id and the second value is the name of the user.

ERROR: [DM_USER_E_MUST_HAVE_OSDOMAIN]

SEVERITY: ERROR
DESCRIPTION: S A new %s user object must have an OS domain name
CAUSE: All user definition must have a user_name, user_os_name, user_os_domain (when domain_required mode is on), and e-mail address before save.
ACTION: Set all required attributes and try again.
PARAMS:

ERROR: [DM_USER_E_NEED_SYS_OR_USER_ADMIN_PRIV]

SEVERITY: ERROR
DESCRIPTION: SS The user (%s) needs to have at least sysadmin privilege or be the users user admin to change the %s user object.
CAUSE: Must have at least SysAdmin privilege or the users user admin to save user objects.
ACTION: Consult your Documentum Administrator.
PARAMS:

ERROR: [DM_USER_E_CANT_FIND_USER]

SEVERITY: ERROR
DESCRIPTION: S Cannot find user %s.
CAUSE: Cannot find the group with the given name.
ACTION: Try again with the correct name.
PARAMS:

ERROR: [DM_USER_E_CANT_DEREF_ACL]

SEVERITY: ERROR
DESCRIPTION: SSS Failed to fetch the default ACL %s in name space %s of user %s.
CAUSE: Failed to fetch the default ACL.
ACTION: Report the bug.
PARAMS:

ERROR: [DM_USER_E_NOT_DOCBASE_DOMAIN_USR]

SEVERITY: ERROR
DESCRIPTION: SS User %s from domain %s does not exist in the docbase — session closed.
CAUSE: The domain user attempting to open a session does not exist.
ACTION: Try again with the correct user name and domain name.
PARAMS:

ERROR: [DM_USER_E_DOCUMENTUM_USER_INACTIVE]

SEVERITY: ERROR
DESCRIPTION: S User %s is not activated in the docbase — session closed.
CAUSE: An inactive user tried to login to the docbase.
ACTION: Ask the Documentum Administrator to activate the account.
PARAMS:

ERROR: [DM_USER_E_CANT_UNREGISTER]

SEVERITY: ERROR
DESCRIPTION: SS Could not unregister the specified %s event for %s object.
CAUSE: The specified event could not be unregistered. Most likely bad event name specified.
ACTION: Correct the event name and try again.
PARAMS:

ERROR: [DM_USER_E_INVALID_STATE_VALUE]

SEVERITY: ERROR
DESCRIPTION: I Specified state %d is invalid, supported values are 0/1/2/3
CAUSE: Tried to set an invalid state. Only the following values are supported: . 0 — Active state. . 1 — Inactive state. . 2 — Locked state. . 3 — Locked and inactive state.
ACTION: Try again with a valid state.
PARAMS:

ERROR: [DM_USER_E_CANT_REVOKE_PRIV_FROM_SELF]

SEVERITY: ERROR
DESCRIPTION: IS You cant revoke the specified privilege %d from yourself (%s).
CAUSE: You can not revoke PURGE AUDIT and CHANGE AUDIT privilege from yourself.
ACTION: Consult your Documentum Administrator.
PARAMS:

ERROR: [DM_USER_E_MUST_HAVE_NAME]

SEVERITY: ERROR
DESCRIPTION: A user object must have a name
CAUSE: All user definitions must have a user_name, user_os_name and e-mail address before save.
ACTION: Set all required attributes and try again.
PARAMS:

ERROR: [DM_USER_E_LOGON_DOM_NO_MATCH_SVR]

SEVERITY: ERROR
DESCRIPTION: S You cannot authenticate against %s domain.
CAUSE: You have specified a logon domain which is different from the server default.
ACTION: Logon again using the server default domain.
PARAMS:

ERROR: [DM_USER_E_USER_LOCKED_AND_INACTIVE]

SEVERITY: ERROR
DESCRIPTION: S User %s is locked and inactive in the repository — session closed.
CAUSE: A locked and inactive user tried to login to the repository.
ACTION: Ask the Documentum Administrator to unlock and activate the account.
PARAMS:

ERROR: [DM_USER_E_LOAD_LOGINNAME_CONFLICT]

SEVERITY: ERROR
DESCRIPTION: SSS A dm_user object with user name %s was encountered which has a user_login_name (%s) which conflicts with an existing dm_user object. The user_login_name of the object being loaded has been changed to %s.
CAUSE: While loading users into the repository, a user was encountered whose user_login_name (or user_os_name) conflicts with the login name of an existing user in the repository. In order to proceed, server changed the login name to a dummy name like @DCTM Unknown User@.
ACTION: If the System Administrator takes no action, the docbase and objects will still be usable, but it will not be possible for the user identified above to actually log into the docbase. If it is intended for the new dm_user to be a valid user of the docbase, then the new and old users must be differentiated by changing one of their login/os names. The System Administrator should change the system os names to be different and then also change the user_login_name (and user_os_name) value of the appropriate dm_user object. If it was intended that the two conflicting users were actually the same user – but the user_name values of the dm_user objects were inadvertantly slightly different, then it is possible to find all of the newly loaded objects owned by the new dm_user and change their ownership to the local user. The new invalid user object can then be removed.
PARAMS: %1s – the user_name of the load object %2s – the conflicting user_login_name %3s – the new dummy user_login_name of the load object

ERROR: [DM_USER_E_EXISTING_USER_NAME]

SEVERITY: ERROR
DESCRIPTION: S Cannot create user %s since its user_name already exists
CAUSE: Tried to create a user that its user_name exists. All user names must be unique.
ACTION: Try again with a different user_name.
PARAMS:

nahoru

DM_VERITY_COLL

ERROR: [DM_VERITY_COLL_F_STYLE_CURSOR_PROBLEM]

SEVERITY: FATAL
DESCRIPTION: SS Problem reading collection style cursor. Database: error %s. Query: %s
CAUSE: RDBMS error.
ACTION: Look for messages from RDBMS or OS.
PARAMS: %s – The RDBMS error message.

ERROR: [DM_VERITY_COLL_F_CANT_CREATE_DUMMY_FILE]

SEVERITY: FATAL
DESCRIPTION: S Cant create the dummy file for updating non-indexable or no-content sysobjects (update phase I). Filename %s.
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages. Partition Facility errors ** Documentum Content Server ** Confidential Property of EMC Corporation ** (c) Copyright Documentum, Inc., 2007 – 2010 ** All rights reserved. **
PARAMS:

ERROR: [DM_VERITY_COLL_F_CANT_FIND_UPDATE_WORKDIR]

SEVERITY: FATAL
DESCRIPTION: S Cant find an update work directory. Filename %s.
CAUSE: Internal error. Probably filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_F_CANT_CREATE_PHASE1_LOCKFILE]

SEVERITY: FATAL
DESCRIPTION: S Cant create the lock file for update phase I. Filename %s.
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_F_UPDATE_SESSION_PROBLEM]

SEVERITY: FATAL
DESCRIPTION: Cant open vdk sessions or collections for this fulltext index.
CAUSE: Verity failed to establish a session or open all collections for this index, or the index has invalid references.
ACTION: See other accompanying error messages, and retry the operation in a new session.
PARAMS:

ERROR: [DM_VERITY_COLL_F_CANT_LAUNCH_UPDATE_PHASE2]

SEVERITY: FATAL
DESCRIPTION: Update phase 2 launch failed.
CAUSE: Probable OS resource problem: out of memory, disk space, etc.
ACTION: Look for OS error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_F_CANT_CREATE_UPDATE_WORKDIR]

SEVERITY: FATAL
DESCRIPTION: S Cant create an update work directory. Filename %s.
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_F_CANT_RENAME_BATCH_PREP_FILE]

SEVERITY: FATAL
DESCRIPTION: SI Rename of file %s failed after %d tries. OS error: %s
CAUSE: Internal error. Probably filesystem or disk problem.
ACTION: Retry indexing with a larger batch size.
PARAMS:

ERROR: [DM_VERITY_COLL_F_DOC_CURSOR_PROBLEM]

SEVERITY: FATAL
DESCRIPTION: S Problem reading document cursor. Database: error %s.
CAUSE: RDBMS error.
ACTION: Look for messages from RDBMS or OS
PARAMS: %s – The RDBMS error message.

ERROR: [DM_VERITY_COLL_F_CANT_ACQUIRE_PHASE1_LOCK]

SEVERITY: FATAL
DESCRIPTION: S Cant acquire file lock for update phase I. Filename %s.
CAUSE: Internal error. Another server may be holding the lock.
ACTION: Verify that there is only one server running an update, then try again.
PARAMS:

ERROR: [DM_VERITY_COLL_E_COMMIT_FAILED]

SEVERITY: ERROR
DESCRIPTION: The fulltext update operation failed to commit the changes made to the database.
CAUSE: Database error
ACTION: Examine the database logs. Once error is resolved, rerun the fulltext operation.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_MAKE_FILES]

SEVERITY: ERROR
DESCRIPTION: S Could not initialize Verity files for partition %s
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_E_FTINDEX_BAD_STATUS]

SEVERITY: ERROR
DESCRIPTION: The fulltext index object is in a bad status. Check for errors in the server and session logs.
CAUSE: An set, revert, or save operation turned the status of the object bad.
ACTION: Examine logs for error messages. Once error is resolved, rerun the operation.
PARAMS:

ERROR: [DM_VERITY_COLL_E_DOC_INDEX_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to index new Verity doc set %s failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_VDB_OPEN]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to open Verity VDB %s failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_NO_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S Attempt to index content with non-existent id %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_OPEN_SESSION]

SEVERITY: ERROR
DESCRIPTION: I Cant open Vdk Session: Error code = %d.
CAUSE: Verity internal error.
ACTION: Report this error to your Documentum site representative.
PARAMS: %d – Verity error code

ERROR: [DM_VERITY_COLL_E_BAD_LOAD_HEADER]

SEVERITY: ERROR
DESCRIPTION: The verity_dump_header file had the wrong format — load failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANNOT_MARK_CONTENT_BAD]

SEVERITY: ERROR
DESCRIPTION: SSI Content %s with parent %s failed to save after setting the update_count attr to %d.
CAUSE: The save operation on the content failed most likely due to database error.
ACTION: Examine the database logs for any errors and inspect the content object. PARAMETERS:Content id, parent id, update_count
PARAMS:

ERROR: [DM_VERITY_COLL_E_UPDATE_DIR_BAD]

SEVERITY: ERROR
DESCRIPTION: S The update batch file is unreadable or missing. Name: %s.
CAUSE: Disk failure or bad mount.
ACTION: Check the disk and directory.
PARAMS:

ERROR: [DM_VERITY_COLL_E_TAR_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SI Tar step failed during %s operation — OS error was %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_EXEC_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Command execution failure: %s. Operating system error: %s.
CAUSE: Unable to execute the command successfully
ACTION: See your system administrator.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_OPEN_COLLECTION_DIR]

SEVERITY: ERROR
DESCRIPTION: SI Cant open collection in directory %s: Error code = %d.
CAUSE: Internal error. Possible disk corruption or failure.
ACTION: None may be necessary, we will attempt recovery.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_CHANGE_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: S Failure in attempt to set working directory to %s
CAUSE: Unable to change working directory before reading Verity index
ACTION: See your system administrator
PARAMS:

ERROR: [DM_VERITY_COLL_E_LOST_PHASE2_FILE]

SEVERITY: ERROR
DESCRIPTION: S Update file %s has disappeared.
CAUSE: Internal error. Possible disk corruption or failure.
ACTION: None may be necessary, we will attempt recovery.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_SUBMIT_ADMIN_OPT]

SEVERITY: ERROR
DESCRIPTION: II Cant submit admin optimization on %d-th collection: Error code = %d.
CAUSE: Verity administrative error. Cant cleanup collection.
ACTION: Check the status file for other messages.
PARAMS: %d – the collection number %d – the verity error return code

ERROR: [DM_VERITY_COLL_E_DOC_SET_CREATE]

SEVERITY: ERROR
DESCRIPTION: S Attempt to create new Verity doc set failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_STAT_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SSI Content object %s identified by %s path could not be accessed OS Error is %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_MERGE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to merge partitions %s and %s failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_CONVERT]

SEVERITY: ERROR
DESCRIPTION: SS Cant convert content %s to format %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_BAD_DESC_FILE]

SEVERITY: ERROR
DESCRIPTION: S Bad update descriptor file. Cant read %s.
CAUSE: Internal error. An indexing descriptor file was written with an unreadable section.
ACTION: Report this error to your Documentum site representative.
PARAMS: %s – the name of the unreadable section.

ERROR: [DM_VERITY_COLL_E_DEST_STYLE_FILE_OPEN_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Could not open file %s for write
CAUSE: Check that the directory exists, and has permission to write
ACTION: Contact Documentum support if directory does not exist. PARAMETERS:File name
PARAMS:

ERROR: [DM_VERITY_COLL_E_NO_VERITY_DIR]

SEVERITY: ERROR
DESCRIPTION: Verity location directory not defined in server configuration
CAUSE: Server configuration must have a Verity location.
ACTION: Install Verity if necessary, create a location object pointing to it, and put this location object in the server config.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_DESTROY_PHASE1_FILE]

SEVERITY: ERROR
DESCRIPTION: SS In update phase1, when attempting to erase file %s, got os error:%s
CAUSE: OS error.
ACTION: Examine OS error string and react accordingly
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_ACCESS_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SSS The content identified by id (%s) which references the file named (%s) cannot be accessed. Operating System error: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_SET_PARSE_HANDLE]

SEVERITY: ERROR
DESCRIPTION: S Cant set the Verity document parser for style %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_TRANSACTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS Could not %s transaction for %s operation
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_PATH_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: S The directory path %s is too long to be used by Verity
CAUSE: The path chosen for the index is too long for the Verity API
ACTION: Chose a different location with a shorter file path and retry the index creation
PARAMS:

ERROR: [DM_VERITY_COLL_E_BAD_BATCH]

SEVERITY: ERROR
DESCRIPTION: S Failure attempting to index batch with format %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_ACQUIRE_PHASE2_LOCK]

SEVERITY: ERROR
DESCRIPTION: S Cant acquire file lock for update phase II. Filename %s.
CAUSE: Internal error. Another server may be holding the lock.
ACTION: Verify that there is only one server running an update, then try again.
PARAMS:

ERROR: [DM_VERITY_COLL_E_LAUNCH_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to launch the command: %s. Operating system error: %s.
CAUSE: Unable to lauch command successfully.
ACTION: You may run out of processes or see your system administrator.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_DESTROY_LAST_STATUS_OPT_FILE]

SEVERITY: ERROR
DESCRIPTION: SS During cleaning, when attempting to erase file %s, got os error:s%
CAUSE: OS Error
ACTION: Examine OS error string and reach accordingly
PARAMS:

ERROR: [DM_VERITY_COLL_E_VDB_WRITE]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to write Verity VDB %s failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_PART_UPDATE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSSS Attempt to update partition index %s failed trying to %s partitions %s and %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_DESTROY_PHASE2_FILE]

SEVERITY: ERROR
DESCRIPTION: SS In update phase2, when attempting to erase file %s, got os error:%s
CAUSE: OS error.
ACTION: Examine OS error string and react accordingly
PARAMS:

ERROR: [DM_VERITY_COLL_E_PHASE2_TIMED_OUT]

SEVERITY: ERROR
DESCRIPTION: I Phase 2 timed out after %d seconds. Killing it.
CAUSE: Indexing filter has looped.
ACTION: Look for Verity error messages and documents marked bad and retry.
PARAMS:

ERROR: [DM_VERITY_COLL_E_NO_FILTER]

SEVERITY: ERROR
DESCRIPTION: S No Verity filter for format %s
CAUSE: No verity_filter defined for this format.
ACTION: Modify the format, adding a verity_filter.
PARAMS:

ERROR: [DM_VERITY_COLL_E_VERITY_DELETE_ERROR]

SEVERITY: ERROR
DESCRIPTION: I Verity index delete request returned error. Code = %d.
CAUSE: Verity indexing error during delete request. Document may already have been deleted.
ACTION: Check the status file for other messages.
PARAMS: %d – the verity error return code

ERROR: [DM_VERITY_COLL_E_BAD_PHASE2_FILENAME]

SEVERITY: ERROR
DESCRIPTION: S Found badly formatted update file. Filename %s.
CAUSE: Internal error. Possible disk corruption or failure.
ACTION: None may be necessary, we will attempt recovery.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_CREATE_UPDATE_STATUS_FILE]

SEVERITY: ERROR
DESCRIPTION: S Cant create an update status file. Filename %s.
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_E_MKVDK_FAILURE]

SEVERITY: ERROR
DESCRIPTION: I mkvdk failed — OS error was %d. Please check status.last file (for fulltext update operation) or status_optimize.last file (for fulltext clean operation) for more messages.
CAUSE: OS Error.
ACTION: Examine OS error number and react accordingly
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_OPEN_COLLECTION]

SEVERITY: ERROR
DESCRIPTION: SI Cant open collection for style %s: Error code = %d.
CAUSE: Possible filesystem offline or corrupted.
ACTION: Look for operating system error messages.
PARAMS: %s – collection subtype %d – Verity error code

ERROR: [DM_VERITY_COLL_E_WAIT_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to wait for the command: %s. Operating system error: %s.
CAUSE: Unable to wait for command to finish successfully.
ACTION: See your system administrator.
PARAMS:

ERROR: [DM_VERITY_COLL_E_BAD_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S Attempt to index content with id %s failed — Verity filter rejected content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_ATTRIBUTE_QUERY_FAILED]

SEVERITY: ERROR
DESCRIPTION: SI The query %s to fetch indexed attribute values with batch size %d failed. Check the server and database logs for any db errors.
CAUSE: The query returned a NULL collection.
ACTION: Check the server and database logs for further errors. PARAMETERS:query string and number of contents to batch in one fetch to client
PARAMS:

ERROR: [DM_VERITY_COLL_E_NO_STATUS_FILES_DURING_UPDATE]

SEVERITY: ERROR
DESCRIPTION: An update seems to be in progress but there are no status files (either current or old).
CAUSE: Unknown error.
ACTION: Try again. If indexing problems occur, contact your Documentum site representative.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_SUBMIT_BULK]

SEVERITY: ERROR
DESCRIPTION: SSI Cant submit bulk update on %s for %s: Error code = %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_VDB_COMMIT]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to commit changes to Verity VDB %s failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_FETCH_PARENT]

SEVERITY: ERROR
DESCRIPTION: SS Error fetching dm_sysobject parent (%s) of dmr_content object %s will contine to look for another valid parent.
CAUSE: A content being indexed contains a reference to a sysobject parent that could not be fetched. The index code needed to fetch the parent object in order to index the content but could not. This may be the result of a parent_id value or index_parent value which points to a deleted sysobject. As long as another parent_id value can be found which points to a valid sysobject this error will not affect processing.
ACTION: Check for any other recent errors in the error log which may indicate the problem. Check the content object for consistent data.
PARAMS: %s – the object id of the sysobject which could not be fetched %s – the object id of the content object being indexed

ERROR: [DM_VERITY_COLL_E_PART2_UPDATE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSS Attempt to update partition index %s failed trying to %s partition %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_FETCH_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S Error: cant fetch dmr_content object %s during fulltext index administration.
CAUSE: During full-text index processing, a failure occured fetching a content object to use in building the index. This content object will not be indexed.
ACTION: Check for any other recent errors in the error log which may indicate the problem.
PARAMS: %s – the object id of the content object being indexed

ERROR: [DM_VERITY_COLL_E_CANT_FIND_TYPE_INFO]

SEVERITY: ERROR
DESCRIPTION: S Cant determine ftindex attributes because internal type info not found for type: %s.
CAUSE: Internal error. Probable memory corruption.
ACTION: Report this error to your Documentum site representative.
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_SET_COLLECTION]

SEVERITY: ERROR
DESCRIPTION: SSI Cant set collection for style %s on %s: Error code = %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_ADD_STYLE]

SEVERITY: ERROR
DESCRIPTION: SS Cant add style files to collection due to database error: %s. SQL statement: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_SET_DOC_HANDLE]

SEVERITY: ERROR
DESCRIPTION: S Cant set the Verity document description for style %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_USE_FULL_PATHNAME]

SEVERITY: ERROR
DESCRIPTION: S The dump file (%s) must be specified by a full path name
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_ACTION]

SEVERITY: ERROR
DESCRIPTION: Check permission of file.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_TIMEOUT]

SEVERITY: ERROR
DESCRIPTION: LLS Timeout after %ld minutes attempting to index batch of size %ld of format %s
CAUSE: The indexing step took too long and was terminated. The batch will be marked as having failed.
ACTION: Attempt to retry the batch by doing a mark_for_retry and another update. If the problem is a looping or crashing filter, the subsequent update will generate another timeout.
PARAMS:

ERROR: [DM_VERITY_COLL_E_SOURCE_STYLE_FILE_OPEN_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Could not open file %s for read
CAUSE: Check that the file exists.
ACTION: Contact Documentum support if file does not exist. PARAMETERS:File name
PARAMS:

ERROR: [DM_VERITY_COLL_E_DOC_NOT_INDEXED]

SEVERITY: ERROR
DESCRIPTION: SS Verity indexing failed for content %s (key %s).
CAUSE: The content may be bad, or may have caused the filter to crash or loop. Or, there may be nothing wrong with this content, just that it was indexed in a batch along with a bad content.
ACTION: Check the status file for other messages. mark_for_retry then rerun indexing with a smaller batch size.
PARAMS: %s – the object id of the content which failed %s – the verity key generated for that content

ERROR: [DM_VERITY_COLL_E_CAUSE]

SEVERITY: ERROR
DESCRIPTION: The process was unable to access the file identified by the file name.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_API_HANDLE_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Attempt to build Verity API handle failed. Verity bin directory was %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_BAD_LOAD_FILE]

SEVERITY: ERROR
DESCRIPTION: S Load failed because file %s not found in index dump
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_CREATE_PHASE2_LOCKFILE]

SEVERITY: ERROR
DESCRIPTION: S Cant create the lock file for update phase II. Filename %s.
CAUSE: Out of space on disk, read-only filesystem or filesystem off-line, or other filesystem or disk problem.
ACTION: Look for operating system error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_E_VDB_UPDATE]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to update Verity VDB %s failed while updating partition %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_EMPTY_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SS Content object %s has empty file identified by %s path.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_FTINDEX_DEADLOCK]

SEVERITY: ERROR
DESCRIPTION: The database is in the deadlock state, so no fulltext operations will be performed. Check for errors in the server and session logs.
CAUSE: Database error, deadlock state caused by external factors
ACTION: Examine database logs. Once error is resolved, rerun the fulltext operation.
PARAMS:

ERROR: [DM_VERITY_COLL_E_UPDATE_VERITY_INDEX_ERROR]

SEVERITY: ERROR
DESCRIPTION: I Verity indexing returned error. Code = %d.
CAUSE: Verity indexing error. Possible bad content or filter problem.
ACTION: Check the status file for other messages.
PARAMS: %d – the verity error return code

ERROR: [DM_VERITY_COLL_E_STYLE_FILE_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS The line %s missing in %s file
CAUSE: The line is missing in file
ACTION: Contact Documentum support. PARAMETERS:line, File name
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_MAKE_ROOT]

SEVERITY: ERROR
DESCRIPTION: Cant build root partition copy
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CANT_MAKE_EMPTY_PARTITION]

SEVERITY: ERROR
DESCRIPTION: S Cant build empty Verity partition with name %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_COPY_ENC_STYLE_ARG_INVALID]

SEVERITY: ERROR
DESCRIPTION: Null arguments passed to function that adds decryption filters to style.uni file.
CAUSE: Internal error
ACTION: Contact Documentum support.
PARAMS:

ERROR: [DM_VERITY_COLL_E_NO_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: S Directory %s doesnt exist
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_E_CLEAR_PENDING_CANT_ACQUIRE_LOCK]

SEVERITY: ERROR
DESCRIPTION: S The clear pending method cant acquire the file lock for modifiying the index. Filename %s. Try again later.
CAUSE: Other fulltext activity, such as an update.
ACTION: Try again later.
PARAMS:

ERROR: [DM_VERITY_COLL_W_CANT_CONVERT]

SEVERITY: WARNING
DESCRIPTION: SS Cant convert content %s to format %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_W_NO_UPDATE_WORKDIR]

SEVERITY: WARNING
DESCRIPTION: S Directory %s does not exist. The fulltext index has probably never been updated before or does not exist.
CAUSE: The fulltext index has probably never been updated before or does not exist.
ACTION: Update the index to create a work directory.
PARAMS:

ERROR: [DM_VERITY_COLL_W_VERITY]

SEVERITY: WARNING
DESCRIPTION: S verity error/warning. message is: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_W_NO_TYPE]

SEVERITY: WARNING
DESCRIPTION: S Cant process tdk collection because type %s was not found.
CAUSE: The type probably does not exist anymore. An orphaned content object that refers to a non-existing type may still exist.
ACTION: Run the DmClean job to remove all orphaned content objects.
PARAMS:

ERROR: [DM_VERITY_COLL_W_BAD_CONTENT]

SEVERITY: WARNING
DESCRIPTION: S Attempt to index content with id %s failed — Verity filter rejected content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_W_NO_CONTENT]

SEVERITY: WARNING
DESCRIPTION: S Attempt to index content with non-existent id %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_W_CONTENT_OFFLINE]

SEVERITY: WARNING
DESCRIPTION: S Attempt to index offline content with id %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_W_CANNOT_PURGE_DIR]

SEVERITY: WARNING
DESCRIPTION: S During crash recovery phase, attempt to purge %s directory failed.
CAUSE: This is most likely caused by another process or resource holding possession on the directory or possibly an OS error.
ACTION: Look for OS error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_W_NO_VERITY_FILE]

SEVERITY: WARNING
DESCRIPTION: No Verity Full-Text Engine messages will be logged in the status file.
CAUSE: Either the launch of the Verity Full-Text Engine (mkvdk) failed due to a probable OS resource problem, or the launch failed to create an output file containing Verity messages.
ACTION: Look for OS error messages.
PARAMS:

ERROR: [DM_VERITY_COLL_W_CANT_FIND_PHASE1_LOCKFILE]

SEVERITY: WARNING
DESCRIPTION: S Cant find the lock file for update phase I. Filename %s.
CAUSE: Unknown.
ACTION: Probably none necessary.
PARAMS:

ERROR: [DM_VERITY_COLL_W_NO_CURRENT_STATUS_FILE_DURING_UPDATE]

SEVERITY: WARNING
DESCRIPTION: An update is in progress but there is no current status file. The previous status file is returned.
CAUSE: The update may have terminated during the execution of the check_ftindex.
ACTION: Try again.
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEIII_END]

SEVERITY: TRACE
DESCRIPTION: II End phase 3 (verification only) fulltext index update. Total successful docs: %d, total failed: %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_VERITY_INDEX_START]

SEVERITY: TRACE
DESCRIPTION: Begin Verity indexing. Verity messages (if any) begin here.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_BATCH_START]

SEVERITY: TRACE
DESCRIPTION: II Begin Verity indexing: epoch %d batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_RECOVERY_NORMAL]

SEVERITY: TRACE
DESCRIPTION: No evidence of previous crash found.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_MAKE_BATCH_FILE_START]

SEVERITY: TRACE
DESCRIPTION: I Begin making batch file for batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_DESC_FILE]

SEVERITY: TRACE
DESCRIPTION: Contents of descriptor file follow this message:
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_GET_CONTENT_END]

SEVERITY: TRACE
DESCRIPTION: End executing sql cursor to get pending content objects.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEI_END]

SEVERITY: TRACE
DESCRIPTION: II End phase 1 fulltext index update. total good: %d total bad: %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_BATCH_START]

SEVERITY: TRACE
DESCRIPTION: II Being processing crashed batch file: epoch %d batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_GET_CONTENT_START]

SEVERITY: TRACE
DESCRIPTION: Begin executing sql cursor to get pending content objects.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_DIR_SEARCH_START]

SEVERITY: TRACE
DESCRIPTION: Searching work directory.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_GET_BATCH_START]

SEVERITY: TRACE
DESCRIPTION: I Begin processing batch %d of pending contents.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_COLLECTION_END]

SEVERITY: TRACE
DESCRIPTION: SI End processing collection with object type %s at position %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_BATCH_END]

SEVERITY: TRACE
DESCRIPTION: II End processing crashed batch file: epoch %d batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEI_START]

SEVERITY: TRACE
DESCRIPTION: Begin phase 1 fulltext index update.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_BATCH_DESC]

SEVERITY: TRACE
DESCRIPTION: SI Batch collection dir %s, size %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_VERITY_BATCH_FILE]

SEVERITY: TRACE
DESCRIPTION: Contents of Verity batch file follow this message:
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_VERITY_INDEX_END]

SEVERITY: TRACE
DESCRIPTION: S End Verity indexing. Return value: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_GET_BATCH_END]

SEVERITY: TRACE
DESCRIPTION: I End processing batch %d of pending contents.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEII_END]

SEVERITY: TRACE
DESCRIPTION: II End phase 2 fulltext index update. Total successful docs: %d, total failed: %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_RECOVERY_START]

SEVERITY: TRACE
DESCRIPTION: Begin update crash recovery phase.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_MAKE_BATCH_FILE_END]

SEVERITY: TRACE
DESCRIPTION: I End making batch file for batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_FOUND_RUNNING_BATCH]

SEVERITY: TRACE
DESCRIPTION: IISI The UPDATE_FTINDEX method has found a running batch file (epoch=%d batch=%d) from a previous update run on fulltext index %s and will examine if a previous failure occured. Please refer to the most recent status file in the fulltext working directory to see if any objects failed indexing from the previous run. If failed objects are reported and you wish to reindex these objects, use the MARK_FOR_RETRY method with update_count=%d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_VERIFY_DOCS_START]

SEVERITY: TRACE
DESCRIPTION: I Begin verifying contents in batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_COLLECTION_START]

SEVERITY: TRACE
DESCRIPTION: SI Begin processing collection with object type %s at position %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_VERIFY_DOCS_END]

SEVERITY: TRACE
DESCRIPTION: I End verifying contents in batch %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEII_START]

SEVERITY: TRACE
DESCRIPTION: Begin phase 2 fulltext index update.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CRASH_RECOVERY_END]

SEVERITY: TRACE
DESCRIPTION: End update crash recovery phase.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_BATCH_END]

SEVERITY: TRACE
DESCRIPTION: II End Verity indexing: successful docs: %d, failed: %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_CANT_RENAME_BATCH_FILE]

SEVERITY: TRACE
DESCRIPTION: SSI The UPDATE_FTINDEX method was unable to rename batch file %s for fulltext index %s. All contents in this batch will not be indexed and are marked as failed. Please refer to the most recent status file in the fulltext working directory to see the failed objects. If failed objects are reported and you wish to reindex these objects, use the MARK_FOR_RETRY method with update_count=%d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_T_UPDATE_PHASEIII_START]

SEVERITY: TRACE
DESCRIPTION: Begin phase 3 (verification only) fulltext index update.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERITY_COLL_I_FTINDEX_IN_PROGRESS]

SEVERITY: INFORMATION
DESCRIPTION: I Another fulltext operation is currently in progress on this fulltext index with epoch %d.
CAUSE:
ACTION:
PARAMS:

nahoru

DM_VERSION

ERROR: [DM_VERSION_E_MAJOR_SCALE_BOUNDS_EXCEEDED]

SEVERITY: ERROR
DESCRIPTION: II The maximum bounds for a Major revision has been exceeded. Major =%d, Maximum =%d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERSION_E_PATCH_SCALE_BOUNDS_EXCEEDED]

SEVERITY: ERROR
DESCRIPTION: II The maximum bounds for a Patch revision has been exceeded. Patch =%d, Maximum =%d $Id: dmwflow.e,v 1.35 2002/09/06 19:58:19 xtang Exp $ Workflow errors
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERSION_E_PARSE_NO_HEADER]

SEVERITY: ERROR
DESCRIPTION: S Format string is not parsable: expecting numeric value for version. Format string: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERSION_E_MINOR_SCALE_BOUNDS_EXCEEDED]

SEVERITY: ERROR
DESCRIPTION: II The maximum bounds for a Minor revision has been exceeded. Minor =%d, Maximum =%d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERSION_E_MAINT_SCALE_BOUNDS_EXCEEDED]

SEVERITY: ERROR
DESCRIPTION: II The maximum bounds for a Maintenence revision has been exceeded. Maintenence =%d, Maximum =%d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_VERSION_E_MEMORY_EXHAUSTED]

SEVERITY: ERROR
DESCRIPTION: I Memory allocation of %d bytes failed
CAUSE:
ACTION:
PARAMS:

nahoru

DM_WORKFLOW

ERROR: [DM_WORKFLOW_E_CANT_REMOVE_ATTACHMENT]

SEVERITY: ERROR
DESCRIPTION: DD Cannot remove the attachment %s because this attachment is not attached to workflow %s.
CAUSE: This attachment object is not attached to the specified workflow. You may have specified an incorrect workflow or incorrect attachment.
ACTION: If the workflow is incorrect, examine the r_workflow_id attribute of the attachment object to determine the correct workflow. If the attachment is incorrect, use the following query to find all attachments for the the workflow: select r_object_id from dmi_wf_audittrail where r_workflow_id = . After correcting the error, retry the operation.
PARAMS: D – attachment ID D – workflow ID

ERROR: [DM_WORKFLOW_E_NO_TRANSITION_METHOD]

SEVERITY: ERROR
DESCRIPTION: S Cannot find the method %s, which is needed to evaluate the automatic transition condition.
CAUSE: The method is not present or is not in the correct location.
ACTION: Rerun the dm_bpm_install.ebs script to reinstall the method. The script is in %DM_HOME%/install/install/admin.
PARAMS: S – Name of the method used to evaluate automatic transition

ERROR: [DM_WORKFLOW_E_CANT_SAVE]

SEVERITY: ERROR
DESCRIPTION: D Saving the object, %s, is not allowed.
CAUSE: Users are not allowed to modify this object.
ACTION: Use an alternate API to modify the attributes.
PARAMS: D – object id

ERROR: [DM_WORKFLOW_E_SETSUPERVISOR_WORKFLOW]

SEVERITY: ERROR
DESCRIPTION: SD The workflow %s (%s) can not be changed supervisor, unless it is in DORMANT, RUNNING or HALTED state.
CAUSE: Tried to set supervisor on a workflow that is either terminated or finished.
ACTION: Do not execute such operation on terminated or finished workflow.
PARAMS: S – workflow name D – workflow ID

ERROR: [DM_WORKFLOW_E_PACKAGE_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: SS Package %s is required for performer resolution, but is not defined on an input port of activity %s.
CAUSE: Performer resolution is to be derived from an input package, and the package name has been identified. However, the package is not defined on an input port of this activity.
ACTION: Add the package to an input port, or disable performer resolution from this package name.
PARAMS: S – package name s – activity name

ERROR: [DM_WORKFLOW_E_NO_RELATE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: D The operation requires at least RELATE permit on object(%s) or can be performed by a user with SYSADMIN or SUPERUSER privileges.
CAUSE: The user does not have enough object level permission or privileges.
ACTION: Retry the operation, after required permissions or privileges are granted.
PARAMS: D – object id

ERROR: [DM_WORKFLOW_E_DUPLICATE_ROUTE_ID]

SEVERITY: ERROR
DESCRIPTION: S The route case identifier, %s, already exists.
CAUSE: The route case identifier has been added already.
ACTION: Specify a different route case identifier.
PARAMS: s – route case identifier

ERROR: [DM_WORKFLOW_E_OPERATION_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: D The activity object %s cannot be saved because the package definitions cannot be correctly saved.
CAUSE: The package definitions of the activity contain some pre-existing non-default values in the r_package_flag attribute. Client applications built on a pre-5.3 client library do not recognize the r_package_flag attribute, and consequently, if the attribute contains non-default values, its values cannot be saved to the repository by a pre-5.3 client library.
ACTION: Use a 5.3 or above client application to modify package definition of the activity.
PARAMS: D – activity ID

ERROR: [DM_WORKFLOW_E_CANT_REACH]

SEVERITY: ERROR
DESCRIPTION: S Activity %s can not be reached from any start activity.
CAUSE: There is no link path from any start activity to this activity.
ACTION: Add a link path from a start activity to this one.
PARAMS: S – activity name

ERROR: [DM_WORKFLOW_E_REFERENCING_PROCESS]

SEVERITY: ERROR
DESCRIPTION: This operation is not allowed where there is referencing validated process.
CAUSE: There is a validated referencing process for this activity.
ACTION: Transition all referencing process to DRAFT state.
PARAMS:

ERROR: [DM_WORKFLOW_E_NO_START_END_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: There is no start or end activity.
CAUSE: The process definition does not have a start or an end activity.
ACTION: Add a start or an end activity to the process definition.
PARAMS:

ERROR: [DM_WORKFLOW_E_DESTROY_STATE]

SEVERITY: ERROR
DESCRIPTION: Can not destroy an installed process definition.
CAUSE: the process definition is in installed state
ACTION: uninstall the process first
PARAMS:

ERROR: [DM_WORKFLOW_E_UNIQUE_PORT_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: SSS The package definition by the name %s has duplicated entries in port %s of activity %s.
CAUSE: A package definition has duplicated entries with a port.
ACTION: Remove the duplicated entry and retry the operation.
PARAMS: S – package name S – port name S – activity name

ERROR: [DM_WORKFLOW_E_ITEM_NEED_SIGNOFF]

SEVERITY: ERROR
DESCRIPTION: D It is required to sign off workitem %s before complete.
CAUSE: In the activity definition, sign_off_required attribute has been set to TRUE. This will require the preformer to eletronically sign it off before the workitem can be marked as complete.
ACTION: Use signoff API to sign it off. Then redo the complete.
PARAMS: D – workitem id

ERROR: [DM_WORKFLOW_E_TRANS_MAX_OUTPUT_CNT_EXCEEDED]

SEVERITY: ERROR
DESCRIPTION: I A maximum of %d output ports can be selected. (The maximum is defined in the activitys transition_max_output_cnt attribute.)
CAUSE: The number of output ports selected exceeded the maximum number allowed.
ACTION: Select fewer output ports than the number defined in the transition_max_output_cnt attribute of the dm_activity object.
PARAMS: I – the maximum number of output ports that can be selected.

ERROR: [DM_WORKFLOW_E_EMPTY_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: D The package (%s) contains no bound component.
CAUSE: The package has no bound component.
ACTION: Ask workflow supervisor to replace this package with one that has proper component(s).
PARAMS: D – the problematic package ID

ERROR: [DM_WORKFLOW_E_INVOKE_FAULT_HANDLER]

SEVERITY: ERROR
DESCRIPTION: SID Failed to invoke fault-handler for activity %s (%d) of workflow (%s).
CAUSE: Errors occurred while invoking fault-handler for an activity.
ACTION: Examine the additional error message that accompanied this error message and take the action recommended for that error.
PARAMS: S – activity name I – activity sequence number D – workflow ID

ERROR: [DM_WORKFLOW_E_ACTIVITY_RUNTIME]

SEVERITY: ERROR
DESCRIPTION: I The sequence number of an activity run-time instance has an invalid value %d.
CAUSE: The object refers to an activity run-time instance that does not exist.
ACTION: Retry the operation. If the problem persists, try with a new connection.
PARAMS: I: sequence number of an activity run-time instance

ERROR: [DM_WORKFLOW_E_CANT_RESUME]

SEVERITY: ERROR
DESCRIPTION: SD The workflow %s can only resume, when its referenced process (%s) is installed.
CAUSE: The referenced process has not been installed.
ACTION: Install the referenced process and retry the operation.
PARAMS: S – workflow name D – the referenced process ID

ERROR: [DM_WORKFLOW_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: D Can not destroy process definition due to being referenced by workflow (%s).
CAUSE: the process definition is in use by a workflow
ACTION: abort the workflow first
PARAMS: D – workflow id

ERROR: [DM_WORKFLOW_E_INTERNAL_STATE]

SEVERITY: ERROR
DESCRIPTION: SD The %s object (%s) is in a bad state.
CAUSE: The object is marked bad by the e-Content Server.
ACTION: First, retry the operation. If the problem persists, try with a new connection.
PARAMS: S: type name D: object ID

ERROR: [DM_WORKFLOW_E_INVALID_PORT]

SEVERITY: ERROR
DESCRIPTION: SS The port name %s is not defined on activity %s. PARAMTERS: s – port name. S – activity name.
CAUSE: The port name specified does not exist in the activity definition.
ACTION: Specify an existing port name.
PARAMS:

ERROR: [DM_WORKFLOW_E_SD_REPORT]

SEVERITY: ERROR
DESCRIPTION: SSID Failed to generate a report for the SD element %s at activity %s (%d) of workflow (%s).
CAUSE: Errors occurred while reporting on an SD element for an activity.
ACTION: Examine the additional error message that accompanied this error message and take the action recommended for that error.
PARAMS: S – The structured data element name S – The activity name I – The activity sequence number D – The workflow object ID

ERROR: [DM_WORKFLOW_E_NO_NOTE]

SEVERITY: ERROR
DESCRIPTION: D The specified note, %s, has not been added to the package.
CAUSE: The note has not been attached to the package.
ACTION: Specify a note attached to the package.
PARAMS: D – the note id.

ERROR: [DM_WORKFLOW_E_NOT_PERFORMER]

SEVERITY: ERROR
DESCRIPTION: The current user is not the activity performer.
CAUSE: Only the activity performer can perform this operation.
ACTION: Ask the activity performer to perform this operation.
PARAMS:

ERROR: [DM_WORKFLOW_E_CHANGE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: DS Workflow (%s) can only be modified by its creator %s or users with SUPERUSER privilege.
CAUSE: Unauthorized users attempt to modify a workflow.
ACTION: Please ask the creator or superusers to make the chaneges.
PARAMS: D – workflow ID S – creator name

ERROR: [DM_WORKFLOW_E_PORT_INCOMPAT_TYPE]

SEVERITY: ERROR
DESCRIPTION: ISSSS Type incompatibility occurs between the %dth packages of the source activity %s port %s and destination activity %s port %s
CAUSE: package type of source port is a super type of package type of destination port
ACTION: change the type specification
PARAMS: I – the position of packages within the ports S – source activity S – source port S – destination activity S – destination port

ERROR: [DM_WORKFLOW_E_CURSOR]

SEVERITY: ERROR
DESCRIPTION: SS The cursor %s fails. The error message from the database server is: %s.
CAUSE: An internal cursor failure occurrs.
ACTION: Re-try the operation. If the problem persists, please see your local system administrative.
PARAMS: S – the query S – the database error message

ERROR: [DM_WORKFLOW_E_SRC_LINK_END_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: SS End activity %s has an outgoing link %s.
CAUSE: there is an outgoing link out of an end activity
ACTION: remove the outgoing link
PARAMS: s – activity name s – link name

ERROR: [DM_WORKFLOW_E_END_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: More than one end activities are specified.
CAUSE: there are more than one end activity in the process definition
ACTION: change process definition to have only one end activity
PARAMS:

ERROR: [DM_WORKFLOW_E_PORT_INCOMPAT_PKGCNT]

SEVERITY: ERROR
DESCRIPTION: SSSS Source activity %s source port %s has different package count than destination activity %s destination port %s.
CAUSE: input and output ports have different number of packages
ACTION: change input or output port definition
PARAMS: s – source activity s – source port s – destination activity s – destination port

ERROR: [DM_WORKFLOW_E_CONFLICT_PACKAGE_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSSS The package definition by the name %s has conflicting types: %s and %s on activity %s.
CAUSE: A package is declared by more than one types.
ACTION: Check all the package definitions of a package and make sure they are declared under one single type.
PARAMS: S – package name SS – conflicting package types S – activity name

ERROR: [DM_WORKFLOW_E_BAD_PARAM]

SEVERITY: ERROR
DESCRIPTION: S The parameter %s specified is invalid.
CAUSE: the parameter is invalid.
ACTION: specify a valid value for the parameter.
PARAMS: s – the invalid parameter

ERROR: [DM_WORKFLOW_E_CANT_REPEAT]

SEVERITY: ERROR
DESCRIPTION: SD The referenced activity %s (%s) does not allow extension.
CAUSE: The referenced activitys performer_flag attribute is not set to allow extension
ACTION: If this workitem should be extended, modify the referenced activity to allow extension
PARAMS: S – Activity name D – the referenced activity ID

ERROR: [DM_WORKFLOW_E_INVALID_PACKAGE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S The package type, %s, is not valid.
CAUSE: The package type specified is not an existing type.
ACTION: Specify an existing persistent type.
PARAMS: S – package type

ERROR: [DM_WORKFLOW_E_PORT_EXIST]

SEVERITY: ERROR
DESCRIPTION: S The specified port %s already exists.
CAUSE: There is already a port with the same name.
ACTION: Use a different port name and re-try the operation.
PARAMS: S – port name

ERROR: [DM_WORKFLOW_E_CHECK_EVENT]

SEVERITY: ERROR
DESCRIPTION: SD The workflow engine fails to check for event %s for workflow (%s).
CAUSE: Errors occurred during checking an event.
ACTION: Report this problem to your local sysadmin to investigate.
PARAMS: S – event name D – workflow ID

ERROR: [DM_WORKFLOW_E_NO_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: There is no package in the activity definition.
CAUSE: The activity definition does not have any package.
ACTION: Add a package to the activity definition.
PARAMS:

ERROR: [DM_WORKFLOW_E_LENGTH_WIDEN_FAILED]

SEVERITY: ERROR
DESCRIPTION: S The upgrade failed on widening attribute lengths for type %s. PARAMTERS: S – type name
CAUSE: For an unknown reason, type conversion failed.
ACTION: Check if there are any database errors or problems. Report the problem to Documentum Support.
PARAMS:

ERROR: [DM_WORKFLOW_E_DELIVER_PACKAGES]

SEVERITY: ERROR
DESCRIPTION: SSSS The activity run-time %s fails to deliver packages from the source port %s to the destination port %s of activity %s.
CAUSE: Errors occurred while packages were delivered to the destination activities.
ACTION: Ask the workflow supervisor to investigate the reported problem and restart the current activity.
PARAMS: S – source activity name S – source port name S – destination port name S – destinartion activity name

ERROR: [DM_WORKFLOW_E_ACTION_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: SSS This operation is not allowed when the state is %s for %s %s.
CAUSE: An illegal operation is attempted, when the target object is at the indicated state.
ACTION: Do not execute such operation.
PARAMS: S – state name S – object type. e.g. activity, workflow, process, or activity instance S – object name

ERROR: [DM_WORKFLOW_E_AUTO_TASK]

SEVERITY: ERROR
DESCRIPTION: S Launch of %s failed: the method was launched successfully but the method did not acquire/complete the workitem.
CAUSE: Method script was not written correctly.
ACTION: Modify the method and make sure it would exit with a non-zero value if the workitem is not acquired/completed.
PARAMS: S – workitem ID

ERROR: [DM_WORKFLOW_E_COMPUTE_TRANS_COND]

SEVERITY: ERROR
DESCRIPTION: SID Failed to compute transition condition for activity %s (%d) of workflow (%s).
CAUSE: Unable to compute the transition condition due to errors.
ACTION: Ask the workflow supervisor to investigate the problem or restart the problematic activity.
PARAMS: S – activity name I – sequence number of activity run-time D – ID of the containing worklfow

ERROR: [DM_WORKFLOW_E_INCOMING_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: IISD The number of packages (%d) does not match what is expected (%d) as defined in port %s of the activity definition (%s).
CAUSE: There are either under- or over-supplied incoming packages.
ACTION: Ask workflow supervisor or your local sysadmin to check the set of packages against the port definition of the associated activity.
PARAMS: I – the number of available packages I – the expected number of packages as defined in the port definition S – the port name D – ID of the associated activity definition object

ERROR: [DM_WORKFLOW_E_NAME_NOT_EXIST]

SEVERITY: ERROR
DESCRIPTION: SSS The %s object by the name %s specified in attribute %s does not exist.
CAUSE: Could not fetch an object with the given name.
ACTION: Provide a valid name and retry the operation.
PARAMS: S – type name S – object name S – attribute name

ERROR: [DM_WORKFLOW_E_VALUE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: SSS The value set to the attribute %s of %s %s is illegal.
CAUSE: An illegal value is set to an attribute.
ACTION: Use a legal value for such an attribute. Refer to the reference manual, if necessary.
PARAMS: S – attribute name S – object type, e.g. activity, process, etc S – object name

ERROR: [DM_WORKFLOW_E_CANT_CREATE]

SEVERITY: ERROR
DESCRIPTION: S Cannot create a %s object.
CAUSE: Could not create a new object.
ACTION: Report this error to Documentum sysadmins.
PARAMS: S: type name

ERROR: [DM_WORKFLOW_E_CONFLICT_PORT_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS The port of name %s is used in multiple port types on activity %s.
CAUSE: A port is declared as multiple port types.
ACTION: Examine port names and types and fix the problematic values. Re-try the previous operation.
PARAMS: S – port name S – activity name

ERROR: [DM_WORKFLOW_E_SRC_LINK_EXCEPTION_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: SS EXCEPTION activity %s can not have an outgoing link %s.
CAUSE: An outgoing link was defined for the specified EXCEPTION activity. However, an EXCEPTION activity may not have outgoing links.
ACTION: Remove the outgoing link from the activity.
PARAMS: s – activity name s – link name

ERROR: [DM_WORKFLOW_E_MISSING_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: SS A package %s is missing, but is required to satisfy definition of output port %s.
CAUSE: A package does not exist, yet is required by the output port.
ACTION: Ask the workflow supervisor to add such a package and retstart such an activity.
PARAMS: S – package name S – output port name

ERROR: [DM_WORKFLOW_E_NO_CONDITION]

SEVERITY: ERROR
DESCRIPTION: D The activity definition, %s, does not have any route case.
CAUSE: The activity has automatic transition but without any route case.
ACTION: Use addroutecase to create route cases.
PARAMS: D – activity id

ERROR: [DM_WORKFLOW_E_PACKAGE_TYPE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SD The type %s of the package %s does not exist.
CAUSE: Failed to examine the type of an incoming package.
ACTION: Verify existance of the type. If it does not exist, report the problem to your local sysadmin.
PARAMS: S – the problematic package type D – ID of the incoming package

ERROR: [DM_WORKFLOW_E_PROCESS_AUTO_TASK]

SEVERITY: ERROR
DESCRIPTION: DDSS Workflow Agent failed to process task %s of workflow %s. The task is using method %s. %s.
CAUSE: Examine the reported error.
ACTION: Examine and fix the reported problems, and retry the operation.
PARAMS: D – ID of the failed automatic task D – ID of the workflow S – Name of the method S – cause of the failure

ERROR: [DM_WORKFLOW_E_SEND_WF_EVENT]

SEVERITY: ERROR
DESCRIPTION: SD The workflow engine fails to send an event %s for workflow (%s).
CAUSE: Errors occurred while recording a workflow event.
ACTION: Report to your local sysadmin to fix the reported problems.
PARAMS: S – event name D – workflow ID

ERROR: [DM_WORKFLOW_E_DEST_LINK_DUPLICATE]

SEVERITY: ERROR
DESCRIPTION: SS Destination activity %s port %s has two incoming links.
CAUSE: two link has the same destination port
ACTION: change the link destination port specification
PARAMS: S – destination activity S – destination port

ERROR: [DM_WORKFLOW_E_CLEAN_NOTE]

SEVERITY: ERROR
DESCRIPTION: D Failed to clean up old notes attached to a package (%s).
CAUSE: The workflow engine fails to remove reference entries from the set of annotation attributes.
ACTION: Ask the workflow supervisor to manually remove old notes from such a package.
PARAMS: D – package ID

ERROR: [DM_WORKFLOW_E_LINK_ATTR_COUNT]

SEVERITY: ERROR
DESCRIPTION: No of elements in link_src_activity/link_src_port/link_dest_activity/link_dest_port does not match that of link_name.
CAUSE: Did not use addlink/removelink commands.
ACTION: Make the number of elements in link_src_activity/link_src_port/link_dest_activity/link_dest_port/link_name match.
PARAMS:

ERROR: [DM_WORKFLOW_E_COLLECT_SD_ELEMENTS]

SEVERITY: ERROR
DESCRIPTION: D The workflow (%s) fails to collect instances of Structured Data Elements.
CAUSE: The database cursor used to collect instances of SD elements failed due to an error.
ACTION: Report the problem to your local sysadmins to eliminate the cause of the database error.
PARAMS: D – workflow ID

ERROR: [DM_WORKFLOW_E_NO_PACKAGE_COMPONENT]

SEVERITY: ERROR
DESCRIPTION: SS The package, %s, for the activity, %s, does not have a component. PARAMTERS: S – package name S – activity name
CAUSE: The specified package does not have any component.
ACTION: Restart the workflow and use addpackage to specify a component.
PARAMS:

ERROR: [DM_WORKFLOW_E_ENGINE_PROCESSING_ERROR]

SEVERITY: ERROR
DESCRIPTION: D Internal error during processing of workflow, %s.
CAUSE: Refer to previous error message for cause.
ACTION: Retry the operation. Inform the workflow supervisor if it fails again.
PARAMS: D – workflow id

ERROR: [DM_WORKFLOW_E_DUPLICATE_REPEAT]

SEVERITY: ERROR
DESCRIPTION: D Workitem %s is a repeated workitem it cannot be further repeated.
CAUSE: This workitem is a product of a repeat. Repeating it further is not allowed.
ACTION: Do not repeat this workitem.
PARAMS: D – workitem object ID

ERROR: [DM_WORKFLOW_E_TRANSITION_PRIVILEGE]

SEVERITY: ERROR
DESCRIPTION: S The operation can only be performed by the workflow supervisor %s or users with SYSADMIN privilege.
CAUSE: An operation is attempted by an unauthorized users.
ACTION: Do not execute such operation or request required privileges to be granted.
PARAMS: S – workflow supervisor name

ERROR: [DM_WORKFLOW_E_SRC_LINK_DUPLICATE]

SEVERITY: ERROR
DESCRIPTION: SS Source activity %s port %s has two outgoing links.
CAUSE: two link has the same source port
ACTION: change the link source port specification
PARAMS: S – source activity S – source port

ERROR: [DM_WORKFLOW_E_MISSING_VALUE]

SEVERITY: ERROR
DESCRIPTION: SSSD The attribute %s of %s %s (%s) has to be set for this operation to succeed.
CAUSE: The attribute value has to be provided.
ACTION: Please set the attribute and retry the operation.
PARAMS: S – attribute name S – object type. e.g. activity, workflow or package S – object name D – object ID

ERROR: [DM_WORKFLOW_E_WORKITEM_TRANSITION]

SEVERITY: ERROR
DESCRIPTION: D Workitem (%s) fails to make the state transition.
CAUSE: Transition failed due to some errors.
ACTION: Report problems to workflow supervisor or your local sysadmin.
PARAMS: D – workitem ID

ERROR: [DM_WORKFLOW_E_PACKAGE_CONSOLIDATION]

SEVERITY: ERROR
DESCRIPTION: SID Package consolidation fails on activity %s (%d) of the workflow (%s).
CAUSE: Errors occurr during package consolidation.
ACTION: If the problem were caused by database errors and seems to persist, report to your local sysadmin. If the problem were caused by a bogus package, ask the workflow supervisor to fix it. Replacing such a package may be necessary.
PARAMS: S – the activity name I – activity sequence number D – ID of the containing workflow

ERROR: [DM_WORKFLOW_E_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: SD The %s object (%s) does not exist.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS: S: type name D: object ID

ERROR: [DM_WORKFLOW_E_INCOMING_PORT]

SEVERITY: ERROR
DESCRIPTION: S The given port name %s is neither an input nor a revert port.
CAUSE: Packages arrive at a port that is neither an input nor a revert port.
ACTION: Report to the process designer and ask to check any incoming links connect to a port of non-incoming type such as output port.
PARAMS: S – the problematic port name

ERROR: [DM_WORKFLOW_E_LINK_DUPLICATE]

SEVERITY: ERROR
DESCRIPTION: S Link name %s is a duplicate.
CAUSE: there is another link of the same name in the process.
ACTION: use a different link name.
PARAMS: s – link name

ERROR: [DM_WORKFLOW_E_WORKFLOW_NOT_RUNNING]

SEVERITY: ERROR
DESCRIPTION: This operation is not allowed when the workflow is halted. PARAMTERS:
CAUSE: The workflow is not in running state.
ACTION: Consult workflow supervisor or system adminitrator to bring the workflow back to running state.
PARAMS:

ERROR: [DM_WORKFLOW_E_ACTIVITY_TYPE]

SEVERITY: ERROR
DESCRIPTION: D The specified object (%s) is not an activity definition object.
CAUSE: the object specified by the ID is not an activity definition object
ACTION: Replace the with ID of an activity definition object..
PARAMS: D – the activity definition object ID

ERROR: [DM_WORKFLOW_E_NO_ACCESS]

SEVERITY: ERROR
DESCRIPTION: D This user does not have the permission to perform the current operation on object, %s.
CAUSE: The user does not have permission required for this operation.
ACTION: Consult the docbase administrator or the workflow supervisor.
PARAMS: D – object id

ERROR: [DM_WORKFLOW_E_PORT_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS An input (or output) activity %s port %s is specified as source (or destination) port in a link. PARAMTERS: s – activity name s – port name
CAUSE: incorrect type of port specified in a link
ACTION: use the right type of port
PARAMS:

ERROR: [DM_WORKFLOW_E_ATTACHMENT_SAVE_DESTROY]

SEVERITY: ERROR
DESCRIPTION: You cannot use save or destroy methods to create or destroy a workflow attachment object. You must use addAttachment or removeAttachment methods (in IDfWorkflow and IDfWorkitem interfaces) to create or destroy a workflow attachment object.
CAUSE: Cannot use save or destroy methods to create or destroy a dmi_wf_attachment object.
ACTION: Use addAttachment or removeAttachment methods to create or destory a dmi_wf_attachment object.
PARAMS:

ERROR: [DM_WORKFLOW_E_CLEANUP_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: D Fails to clean up activity run-time list of workflow (%s).
CAUSE: Errors occurred while cleaning up finished activities from the list.
ACTION: Ask workflow supervisor to examine and fix the problem, if possible.
PARAMS: D – workflow ID

ERROR: [DM_WORKFLOW_E_DESTROY_WORKFLOW]

SEVERITY: ERROR
DESCRIPTION: SD The workflow %s (%s) can not be destroyed, unless it is in DORMANT, FINISHED or TERMINATED state.
CAUSE: Tried to destroy a workflow that is either running or temporarily halted.
ACTION: Either finish or terminate the workflow prior to destroying it.
PARAMS: S – workflow name D – workflow ID

ERROR: [DM_WORKFLOW_E_NO_RUNTIME_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: SS The package, %s, does not exist for the activity, %s. PARAMTERS: S – package name S – activity name
CAUSE: The specified package has not been added or manufactured for the activity.
ACTION: Use addpackage method to add the package to the workflow.
PARAMS:

ERROR: [DM_WORKFLOW_E_CREATE_ACTIVITY_RUNTIME]

SEVERITY: ERROR
DESCRIPTION: S Fails to instantiate a new activity run-time for %s.
CAUSE: Errors occurred during creation of an activity run-time instance.
ACTION: Ask workflow supervisor to restart the current activity.
PARAMS: S – activity name

ERROR: [DM_WORKFLOW_E_TRANSITION_TIMEOUT]

SEVERITY: ERROR
DESCRIPTION: SI The transition evaluation method %s timed out. The method timeout is currently set to %d.
CAUSE: This error occured when the automatic transition evaluation takes longer time to finish. If the time exceeds the method timeout length, this error will occur.
ACTION: Set the timeout_default attribute of the method to a greater value. If timeout_default is set to more than 5 minutes, you may need to set client_session_timeout in server.ini accordingly.
PARAMS: S – Name of the method used to evaluate automatic transition I – The method timeout value

ERROR: [DM_WORKFLOW_E_INVALID_PACKAGE_INPUT_PORT]

SEVERITY: ERROR
DESCRIPTION: SSS The package %s is not in the specified input port %s of activity %s. PARAMTERS: s – package name s – port name s – activity name
CAUSE: The package does not exit in the specified input port.
ACTION: Specify the input port where the package exists.
PARAMS:

ERROR: [DM_WORKFLOW_E_SAVE_ONCE]

SEVERITY: ERROR
DESCRIPTION: D The workflow, %s, can be saved only once.
CAUSE: Dm_workflow object can be saved only once.
ACTION: Consult the workflow supervisor.
PARAMS: D – object id

ERROR: [DM_WORKFLOW_E_SELFLINK_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: SII Activity %s has a link to itself. This is not allowed for activities with performer_type %d and transition_type %d.
CAUSE: A sequential activity with prescribed transition should not have a link to itself.
ACTION: Remove the link, or change performer_type or transition_type of the activity
PARAMS: S – activity name I – activity performer_type I – activity transition_type

ERROR: [DM_WORKFLOW_E_INVALID_ACTIVITY_STATE]

SEVERITY: ERROR
DESCRIPTION: S The activity, %s, is not in dormant state.
CAUSE: The activity needs to be in dormant state for this operation to succeed.
ACTION: addpackage or removepackage is not allowed once the activity has been started.
PARAMS: S – activity name

ERROR: [DM_WORKFLOW_E_NO_SUPERVISOR_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SD The supervisor %s, designated in workflow %s, does not have at least RELATE permit on the referenced process.
CAUSE: The supervisor designated for this workflow does not have RELATE permissions on the process object
ACTION: Designate a new supervisor with sufficient privileges, or change the permissions on the referenced process
PARAMS: S – supervisor name D – the referenced process ID

ERROR: [DM_WORKFLOW_E_PACKAGE_EXISTS]

SEVERITY: ERROR
DESCRIPTION: The package already exists.
CAUSE: A package of the same name already exist for the activity of the workflow.
ACTION: Specify a package that has not been added to the activity.
PARAMS:

ERROR: [DM_WORKFLOW_E_OUTPUT_PORT]

SEVERITY: ERROR
DESCRIPTION: SD The specified output port %s does not exist in the activity definition (%s).
CAUSE: The given output port name is not defined.
ACTION: Provide a legal output port and retry the operation.
PARAMS: S – output port name D – ID of the referred dm_activity object

ERROR: [DM_WORKFLOW_E_OUT_OF_RANGE]

SEVERITY: ERROR
DESCRIPTION: SIISS The value of the attribute %s should be between %d and %d for %s %s.
CAUSE: The attribue value is out of range.
ACTION: Set the attribute to a value as suggested and retry the operation.
PARAMS: S – attribute name I – the lower bound I – the upper bound S – the object type, e.g. activity, process, etc S – the object name

ERROR: [DM_WORKFLOW_E_PACKAGE_EXIST]

SEVERITY: ERROR
DESCRIPTION: SS The given package name %s already exists in port %s.
CAUSE: A package definition by the same name exists in such port.
ACTION: Provide a proper package or port name and retry the operation.
PARAMS: S – package name S – port name

ERROR: [DM_WORKFLOW_E_WFLOW_AGENT_STATE]

SEVERITY: ERROR
DESCRIPTION: SS Workflow agent is unable to %s. Workflow agent is currently %s .
CAUSE: Cannot perform the requested action on the workflow agent because of the current state of the workflow agent.
ACTION: Please try the same action when the workflow agent is in proper state. Transformation Facility errors
PARAMS: S – Action user is trying to perform on the workflow agent. S – The current state of workflow agent.

ERROR: [DM_WORKFLOW_E_INSTALL_PROCESS_HANDLE_WORKFLOW]

SEVERITY: ERROR
DESCRIPTION: SD Failed to resume or abort the workflows when installing process %s (%s). If the process has been installed, un-install the process, fix the problem, then re-install the process.
CAUSE: Errors occur during process installation. Refer to previous error message for cause. Note that some workflow instances may have been resumed or aborted by the failed operation.
ACTION: If the process has been installed by the failed operation, un-install the process, fix the reported problem, and retry the operation. Inform the workflow supervisor if it fails again.
PARAMS: S – Name of the process definition D – ID of the process definition

ERROR: [DM_WORKFLOW_E_ACT_STATE_TRANS]

SEVERITY: ERROR
DESCRIPTION: SID The workflow engine fails to make necessary state transition for activity %s (%d) within the workflow (%s).
CAUSE: State transition fails for an activity run-time.
ACTION: Report the problem to your local sysadmim. Examine the server log and see whether this is a problem specific to a workflow or accross the board.
PARAMS: S – activity name I – sequence number of the activity run-time D – ID of the containing workflow

ERROR: [DM_WORKFLOW_E_MISSING_PARAMETERS]

SEVERITY: ERROR
DESCRIPTION: S The API command %s has missing parameters.
CAUSE: There are missing parameters for the API command.
ACTION: Please refer to the reference manual and provide the required parameters.
PARAMS: S – command name

ERROR: [DM_WORKFLOW_E_FROZEN_ATTR]

SEVERITY: ERROR
DESCRIPTION: SSI The attribute %s can not be changed, when the %s object is at state (%d).
CAUSE: Changes to the indicated attribute is not allowed, when the object is at such state.
ACTION: Do not attempt such a change or change the objects state prior to changing this attribute.
PARAMS: S – attribute name S – type name I – state (an integer)

ERROR: [DM_WORKFLOW_E_SET_PRIORITY_AUTO_TASK_EXECUTING]

SEVERITY: ERROR
DESCRIPTION: D Setpriority failed on automatic workitem %s because this workitem is being executed by workflow agent.
CAUSE: This workitem is of automatic activity and is being executed by workflow agent.
ACTION: There is no need to setpriority on an automatic workitem if it is being processed by workflow agent.
PARAMS: D – workitem ID

ERROR: [DM_WORKFLOW_E_INVALID_ROUTE_ID]

SEVERITY: ERROR
DESCRIPTION: S The route case identifier, %s, specified does not exist.
CAUSE: The route case identifier does not exist in the activity definition.
ACTION: Specify an existing route case identifier.
PARAMS: s – route case identifier

ERROR: [DM_WORKFLOW_E_INVALID_ACTIVITY_NAME]

SEVERITY: ERROR
DESCRIPTION: S The activity name, %s, is invalid.
CAUSE: The package name specified does not exist in the activity.
ACTION: Specify an existing package name.
PARAMS: s – package name

ERROR: [DM_WORKFLOW_E_CONTEXT_INIT]

SEVERITY: ERROR
DESCRIPTION: Initializing %s of workflow agent execution context failed.
CAUSE: This may happen because swap space (page file on Windos) is not large enough.
ACTION: Configure more swap space or page file.
PARAMS: A character string contains event or mutex name.

ERROR: [DM_WORKFLOW_E_INSTALL_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: One of the paramter provided to install an activity definition is invalid.
CAUSE: an invalid value was specified for parameter install activity
ACTION: specify [T]rue/[F]alse
PARAMS:

ERROR: [DM_WORKFLOW_E_PORT_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S The specified port %s does not exist.
CAUSE: The given port name does not exist in the attribute for port names.
ACTION: Verify the given port name exists and re-try the operation.
PARAMS: S – the specified port name

ERROR: [DM_WORKFLOW_E_ACTIVITY_NOT_ACTIVE]

SEVERITY: ERROR
DESCRIPTION: SD The activity, %s, of workflow, %s, is not active.
CAUSE: This operation can not be performed while the activity is not active.
ACTION: Consult the workflow supervisor for the appropriate action.
PARAMS: S – activity name, D – workflow id.

ERROR: [DM_WORKFLOW_E_DESTROY_PRIVILEGE]

SEVERITY: ERROR
DESCRIPTION: SS The operation can only be performed by the workflow creator %s, the supervisor %s or users with SYSADMIN privilege.
CAUSE: An operation is attempted by an unauthorized users.
ACTION: Do not execute such operation or request required privileges to be granted.
PARAMS: S – workflow creator name S – workflow supervisor name

ERROR: [DM_WORKFLOW_E_PERFORMER_CATEGORY]

SEVERITY: ERROR
DESCRIPTION: SSD Invalid alias category for resolved performer %s of activity %s of workflow (%s): the category of the alias was not user or group
CAUSE: When resolving an alias into a performer, the alias that was found in the alias set was not of type user and/or group
ACTION: Change the alias category of the alias set to be user and/or group for this alias name
PARAMS: S – performer name or an alias S – activity name D – workflow ID

ERROR: [DM_WORKFLOW_E_SAVE_TRANSITION]

SEVERITY: ERROR
DESCRIPTION: The r_conidtion_id and r_predicate_id attributes of the activity cannot be set concurrently.
CAUSE: You attempted to set either r_condition_id or r_predicate_id when the other was already set. The attributes are mutually exclusive. Only one can be set for an activity.
ACTION: To set r_condition_id, use removeConditionRouteCase to remove the value in r_predicate_id, then use addroutecase to set r_condition_id. To set r_predicate_id, use removeroutecase to remove the value in r_condition_id, then use addConditionRouteCase to set r_predicate_id.
PARAMS:

ERROR: [DM_WORKFLOW_E_PACKAGE_ID]

SEVERITY: ERROR
DESCRIPTION: DSS The package ID (%s) given in the package definition %s is not of the declared package type %s or its sub-type.
CAUSE: The package ID is not of the declared type nor any of its sub-types.
ACTION: Provide a proper ID and retry the operation.
PARAMS: D – package ID S – package name S – package type

ERROR: [DM_WORKFLOW_E_RESTART]

SEVERITY: ERROR
DESCRIPTION: One of the paramters provided for restart is invalid.
CAUSE: an invalid value was specified for parameter restart
ACTION: specify [T]rue/[F]alse
PARAMS:

ERROR: [DM_WORKFLOW_E_PACKAGE_MERGE]

SEVERITY: ERROR
DESCRIPTION: DSDS Package merge fails, because one package (%s) is of type %s and the other (%s) is of type %s.
CAUSE: Two packages are found to have different types, which is not allowed for merge.
ACTION: Ask the workflow supervisor to make sure the two packages have the same type. Package replacement may be necessary.
PARAMS: D – the first package ID S – the first package type D – the second package ID S – the second package type

ERROR: [DM_WORKFLOW_E_COLLECT_EVENTS]

SEVERITY: ERROR
DESCRIPTION: The workflow engine fails to collect events for processing.
CAUSE: Errors occurred while the workflow engine was collecting events for processing.
ACTION: Report to your local sysadmin to fix the reported problems.
PARAMS:

ERROR: [DM_WORKFLOW_E_DESTROY_INUSE]

SEVERITY: ERROR
DESCRIPTION: SD The operation fails, because the %s object (%s) is in use.
CAUSE: The operation fails, because the specified object is being referenced by other objects.
ACTION: Make sure the object is not in use, before the operation is executed.
PARAMS: S – object type name D – object ID

ERROR: [DM_WORKFLOW_E_FEATURE_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S The feature indicated by the value in attribute %s is not currently supported.
CAUSE: The value set in the attribute refers to a feature that is not currently available.
ACTION: Use a different value and retry the operation.
PARAMS: S – attribute name

ERROR: [DM_WORKFLOW_E_LINK_NAME]

SEVERITY: ERROR
DESCRIPTION: S The link %s does not exist.
CAUSE: the link name specified does not exist.
ACTION: specify an existing link name
PARAMS: s – link name

ERROR: [DM_WORKFLOW_E_DEST_LINK_START_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: SS Start activity %s has an incoming link %s.
CAUSE: there is an incoming link into a start activity
ACTION: remove the incoming link
PARAMS: s – activity name s – link name

ERROR: [DM_WORKFLOW_E_BOGUS_EVENT]

SEVERITY: ERROR
DESCRIPTION: DD The workflow (%s) is not able to process event (%s).
CAUSE: The workflow is not able to process such an event either because the event does not exist or has bad content.
ACTION: Report this problem to your local sysadmin to fix this problem.
PARAMS: D – workflow ID D – event object ID

ERROR: [DM_WORKFLOW_E_INACTIVE_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: SID The activity run-time %s (%d) of workflow (%s) is not active.
CAUSE: The specified activity is not active.
ACTION: Retry the operation after the activity run-time becomes active.
PARAMS: S – activity name I – activity sequence number D – containing workflow ID

ERROR: [DM_WORKFLOW_E_COLLECT_OUTPORT]

SEVERITY: ERROR
DESCRIPTION: SID The activity %s (%d) of workflow (%s) fails to collect manually specified output ports for transition.
CAUSE: The cursor used to collect output ports from workitems failed due to an error.
ACTION: Report the problem to your local sysadmins to eliminate the cause of the database error.
PARAMS: S – activity name I – activity sequence number D – workflow ID

ERROR: [DM_WORKFLOW_E_MULTIPLE_PERFORMERS]

SEVERITY: ERROR
DESCRIPTION: ID Only a single performer is allowed for performer type %d in activity (%s).
CAUSE: The performer type allows only for a single value in the attribute performer_name.
ACTION: Provide only one performer, or choose a different performer type designation.
PARAMS: I – performer type D – activity ID

ERROR: [DM_WORKFLOW_E_FOREIGN_ID]

SEVERITY: ERROR
DESCRIPTION: DSS The foreign object (%s) is not allowed in the attribute %s of type %s.
CAUSE: A foreign object ID is found in an attribute, which is not expecting.
ACTION: Replace the foreign object ID with a local reference object ID that refers to the remote object. Re-try the operation.
PARAMS: D – the foreign ID S – attribute name S – type name

ERROR: [DM_WORKFLOW_E_INVALID_USER]

SEVERITY: ERROR
DESCRIPTION: S The specified user %s is not a valid user.
CAUSE: An invalid user name is provided.
ACTION: Retry the operation with a valid user name.
PARAMS: S – user name

ERROR: [DM_WORKFLOW_E_NAME_INDEX]

SEVERITY: ERROR
DESCRIPTION: SSDS The internal index for attribute %s of the %s object (%s) is corrupted for key value %s,
CAUSE: The internal index is found corrupted.
ACTION: Re-create the internal index by validate API command and re-try the previous operation.
PARAMS: S – attribute name on which an index was built S – type name D – ID of the problematic object S – attribute value

ERROR: [DM_WORKFLOW_E_MANU_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: SID Failed to manufacture packages for activity %s (%d) of workflow (%s).
CAUSE: Unable to manufacture packages for selected ports due to errors.
ACTION: Ask the workflow supervisor to investigate the problem or restart the problematic activity.
PARAMS: S – activity name I – sequence number of activity run-time D – ID of the containing worklfow

ERROR: [DM_WORKFLOW_E_CHOOSE_ATTR_COUNT]

SEVERITY: ERROR
DESCRIPTION: Number of elements in act_choose_name/act_choose_by/act_choose_for do not match.
CAUSE: The same number of repeating attribute values must appear across the three attributes.
ACTION: Make the number of elements in act_choose_name/act_choose_by/act_choose_for match.
PARAMS:

ERROR: [DM_WORKFLOW_E_COMPUTE_PERFORMER]

SEVERITY: ERROR
DESCRIPTION: SID Failed to compute performers for activity %s (%d) of the workflow (%s).
CAUSE: The operation failed due to some problems.
ACTION: Ask the workflow supervisor to restart such an activity run-time instance.
PARAMS: S – the activity name I – activity run-time sequence number D – workflow ID

ERROR: [DM_WORKFLOW_E_BINDING_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: DS Package binding failed because no object could be identified by package ID (%s) with package label %s.
CAUSE: No object with the given version label can be found within the version tree in which the given object resides.
ACTION:
PARAMS: D – package ID S – package label

ERROR: [DM_WORKFLOW_E_ACTIVITY_NOT_INSTALLED]

SEVERITY: ERROR
DESCRIPTION: D One of the referring activities (%s) has not yet been installed.
CAUSE: an activity is not in installed state when installing its process
ACTION: install the activity first
PARAMS: D – activity id

ERROR: [DM_WORKFLOW_E_ROUTE_TABLE]

SEVERITY: ERROR
DESCRIPTION: SS The following attributes should have had same number of values: %s and %s.
CAUSE: The above attributes are supposed to contain same number of values, but found otherwise.
ACTION: Ensure all these attributes have same number of values and they are properly set.
PARAMS: attribute names for condition name and port.

ERROR: [DM_WORKFLOW_E_NO_SD_ELEMENT_INSTANCE]

SEVERITY: ERROR
DESCRIPTION: SD The instance of the Structured Data Element, %s, does not exist for the workflow, %s. PARAMTERS: S – element name D – workflow ID
CAUSE: The instance of the specified Structured Data Element does not exist for the workflow. This is probably caused by starting the Workflow from a client application that does not have bpm jar files in its classpath.
ACTION: Examine the classpath of the client application, make sure bpm jar files are present in the classpath.
PARAMS:

ERROR: [DM_WORKFLOW_E_ASSIGN_TASK_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Workflow agent master failed to assign work item %s to worker threads.
CAUSE: This should not happen. It means a serious server bug if happens.
ACTION: Restart server. Report the error message to Documentum Engineering.
PARAMS: S – work item id

ERROR: [DM_WORKFLOW_E_HALT_AUTOMATIC]

SEVERITY: ERROR
DESCRIPTION: DD The workflow (%s) can not be halted, because an automatic activity (represented by a workitem (%s)) is being executed.
CAUSE: A workflow can not be halted while executing an automatic activity.
ACTION: Retry the operation after such an activity finishes.
PARAMS: D – workflow ID D – ID of the automatic workitem

ERROR: [DM_WORKFLOW_E_INVALID_ACTIVITY_TYPE]

SEVERITY: ERROR
DESCRIPTION: S The activity, %s, is not a start activity.
CAUSE: The activity is not a start activity in the process definition.
ACTION: Specify a start activity.
PARAMS: s – activity name

ERROR: [DM_WORKFLOW_E_NOT_RUNNING]

SEVERITY: ERROR
DESCRIPTION: D The workflow, %s, is not running.
CAUSE: The operation is allow only when the workflow is in running state.
ACTION: Use execute or resume to re-run the workflow.
PARAMS: D – workflow id

ERROR: [DM_WORKFLOW_E_SET_PACKAGE_SKILL_LEVEL]

SEVERITY: ERROR
DESCRIPTION: SD Attempt to set user skill level for package %s of workflow %s failed.
CAUSE: Refer to previous error message for cause.
ACTION: Retry the operation. Inform the workflow supervisor if it fails again.
PARAMS: D – workflow id

ERROR: [DM_WORKFLOW_E_METHOD_NOT_APPLICABLE]

SEVERITY: ERROR
DESCRIPTION: S The method %s is not applicable, before the object is saved.
CAUSE: An operation is attempted, when the target object has not been saved.
ACTION: Do not execute such operation, until the object is saved.
PARAMS: S – operation name

ERROR: [DM_WORKFLOW_E_WAIT_FOR_TASK_FAIL]

SEVERITY: ERROR
DESCRIPTION: Workflow agent master failed in waiting for new tasks.
CAUSE: This should not happen. It means a serious server bug if happens.
ACTION: Restart server. Report the error message to Documentum Engineering
PARAMS: None

ERROR: [DM_WORKFLOW_E_PORT_TABLE]

SEVERITY: ERROR
DESCRIPTION: SSSSSSS The following attributes should have had same number of values: %s, %s, %s, %s, %s, %s and %s.
CAUSE: The above attributes are supposed to contain same number of values, but found otherwise.
ACTION: Ensure all these attributes have same number of values and they are properly set.
PARAMS: attribute names for port names, port types, package names, package types, package operations, package IDs and package labels.

ERROR: [DM_WORKFLOW_E_ACTIVITY_NAME]

SEVERITY: ERROR
DESCRIPTION: S The activity name %s is invalid.
CAUSE: An invalid activity name was specified.
ACTION: Replace with a valid activity name.
PARAMS: S – the invalid name

ERROR: [DM_WORKFLOW_E_PACKAGE_NOT_EXISTS]

SEVERITY: ERROR
DESCRIPTION: The package does not exist.
CAUSE: The specified package does not exist.
ACTION: Specify an existing package.
PARAMS:

ERROR: [DM_WORKFLOW_E_SD_REPORT_NO_ACCESS]

SEVERITY: ERROR
DESCRIPTION: S User lacks the required privilege to access the Structured Data Report table (%s).
CAUSE: SUPERUSER privilege is required to read, write or query the reporting type of an SDT.
ACTION: Retry the operation after granting Superuser privilege to the user performing the operation.
PARAMS: S – name of the SD report table

ERROR: [DM_WORKFLOW_E_ROUTECASE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S The route case can not be found give the name %s.
CAUSE: No route case can be identified by such name.
ACTION: Provide a proper name and retry the operation.
PARAMS: S – route case name

ERROR: [DM_WORKFLOW_E_PACKAGE_TYPE_INCOMPAT]

SEVERITY: ERROR
DESCRIPTION: SDSSSD The type %s of the incoming package %s is not compatible with type %s as defined in package name %s of port %s of the activity definition (%s).
CAUSE: An incoming package is found incompatible with what is expected in the port definition.
ACTION: Ask workflow supervisor to replace the problematic package with one that has a compatible type.
PARAMS: S – type of the incoming package D – ID of the incoming package S – the expected type name S – the matching package name S – the target port name D – ID of the activity definition

ERROR: [DM_WORKFLOW_E_ACTIVITY_SEQNO]

SEVERITY: ERROR
DESCRIPTION: ID No activity run-time instance can be identified by the sequence no (%d) in workflow (%s).
CAUSE: The given activity sequence number is bogus.
ACTION: Provide a good activity sequence number and retry the operation.
PARAMS: I – activity sequence number D – workflow ID

ERROR: [DM_WORKFLOW_E_COLLECT_ACTGROUP_INSTANCES]

SEVERITY: ERROR
DESCRIPTION: DS The workflow (%s) fails to collect activity group instances with query (%s).
CAUSE: The query used to collect activity group instances failed due to an error.
ACTION: Report the problem to your local sysadmins to eliminate the cause of the database error.
PARAMS: D – workflow ID S – query

ERROR: [DM_WORKFLOW_E_CREATE_WF_CONTEXT]

SEVERITY: ERROR
DESCRIPTION: Creating Workflow agent execution context failed.
CAUSE: This may happen only after running out memory.
ACTION: Restart server. Report the error message to Documentum Engineering.
PARAMS: None

ERROR: [DM_WORKFLOW_E_PACKAGE_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS The package definition by name %s contains a non-existing type %s.
CAUSE: A non-existing type is specified as a package type.
ACTION: Replace the non-existing type with an existing one and re-try the previous operation.
PARAMS: S – package name S – package type

ERROR: [DM_WORKFLOW_E_INVALID_ROUTE_ALIASE]

SEVERITY: ERROR
DESCRIPTION: SS The route aliase %s used in activity %s is invalid.
CAUSE: The specified aliases is not package name, dm_workflow or dm_workitem.
ACTION: Specify a package name, dm_workflow or dm_workitem.
PARAMS: s – aliase s – activity name

ERROR: [DM_WORKFLOW_E_PACKAGE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SS There is no package definition by the given name %s in port %s.
CAUSE: No package definition can be identified given such port and package name.
ACTION: Provide a proper port and package name and retry the operation.
PARAMS: S – package name S – port name

ERROR: [DM_WORKFLOW_E_BAD_TYPE]

SEVERITY: ERROR
DESCRIPTION: DDS The package (%s) contains a component (%s) that is not of type %s or its sub-type.
CAUSE: The pakcage contains a component whose type is not compliant with the package type.
ACTION: Use removepackage and addpackage to replace the problematic package with a good one.
PARAMS: D: package ID D: compoent ID S: package type

ERROR: [DM_WORKFLOW_E_ACTIVITY_RUNTIME_CREATION]

SEVERITY: ERROR
DESCRIPTION: D Failed to create run-time instances for activities defined in the process definition (%s).
CAUSE: Errors occur while run-time instances were created.
ACTION: Retry the operation, if failure was due to database errors. If the problem presists, retry the operation in a new session.
PARAMS: D – ID of the referenced process defintion

ERROR: [DM_WORKFLOW_E_AGENT_LOCK_OBJ_MISSING]

SEVERITY: ERROR
DESCRIPTION: S The SysObject %s is missing from the repository.
CAUSE: The SysObject, used by the Workflow Agent Master while processing automatic activities, was not found in the repository. This object is created automatically when Content Server is started. Somehow, it was removed from the repository.
ACTION: Restart the Content Server. The server startup procedure will recreate the object.
PARAMS: S – Name of the SysObject

ERROR: [DM_WORKFLOW_E_COLLECT_PACKAGES]

SEVERITY: ERROR
DESCRIPTION: D The workflow (%s) fails to collect all available packages.
CAUSE: The cursor used to collect packages failed due to an error.
ACTION: Report the problem to your local sysadmins to eliminate the cause of the database error.
PARAMS: D – workflow ID

ERROR: [DM_WORKFLOW_E_UPDATE_TIMER]

SEVERITY: ERROR
DESCRIPTION: SDS Failed to update timer (%s) of workflow instance (%s) as %s.
CAUSE: Examine the reported error.
ACTION: Examine and fix the reported problems, and retry the operation.
PARAMS: S – Name of the timer D – ID of the workflow instance S – cause of the failure

ERROR: [DM_WORKFLOW_E_PORT_NAME]

SEVERITY: ERROR
DESCRIPTION: SS Port %s does not exist in the activity definition %s. PARAMTERS: s – port name s – activity name
CAUSE: the link port name does not exist in the activity
ACTION: specify an existing port name
PARAMS:

ERROR: [DM_WORKFLOW_E_PROCESS_EVENT]

SEVERITY: ERROR
DESCRIPTION: SSID The workflow engine fails to process %s event on behalf of activity %s (%d) of workflow (%s).
CAUSE: Errors occurred during processing an event for an activity.
ACTION: Report this problem to your local sysadmin to investigate.
PARAMS: S – event name S – activity name I – activity sequence number D – workflow ID

ERROR: [DM_WORKFLOW_E_UNABLE_TO_CREATE_INTERNAL_GROUP]

SEVERITY: ERROR
DESCRIPTION: S Unable to create internal group.
CAUSE: Internal Error
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_WORKFLOW_E_NO_EXECUTE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SD User %s has no EXECUTE permit on process (%s).
CAUSE: The user has no permission to execute a process.
ACTION: Ask your local sysadmin to grant you necessary permissions.
PARAMS: S – user name D – ID of dm_process object

ERROR: [DM_WORKFLOW_E_ATTR_COUNT]

SEVERITY: ERROR
DESCRIPTION: SSS The number of values in the %s attributes of %s %s do not match.
CAUSE: The attributes must have the same number of values. For example, if one has six values, the other must also have six values.
ACTION: Make the number of values match.
PARAMS: S – Names of the attributes, separated by / S – Type of the object, e.g. activity, process, etc S – Name of the object

ERROR: [DM_WORKFLOW_E_INPUT_BINDING]

SEVERITY: ERROR
DESCRIPTION: S Cannot add packageinfo to input port %s package ID and label binding are not allowed for input ports
CAUSE: Binding package IDs or labels is not allowed on input ports
ACTION: Binding can be done on the output port that is connected to this input port
PARAMS: S – port name

ERROR: [DM_WORKFLOW_E_EMPTY_ACTGROUP]

SEVERITY: ERROR
DESCRIPTION: SD Activity group (%s) defined on process (%s) does not contain any activity.
CAUSE: Activity group can not be empty.
ACTION: Examine and fix the reported problems, and retry the operation.
PARAMS: S – Name of the activity group D – ID of the workflow template

ERROR: [DM_WORKFLOW_E_CHECK_ACTIVITY]

SEVERITY: ERROR
DESCRIPTION: The parameter checkactivity is invalid.
CAUSE: the parameter specified is invalid.
ACTION: specifiy either [t]rue or [f]alse.
PARAMS:

ERROR: [DM_WORKFLOW_E_LAUNCH_TRANSITION]

SEVERITY: ERROR
DESCRIPTION: S Failed to launch the transition evaluation method %s.
CAUSE: Unknown
ACTION: Report to your local sysadmin to fix the reported problems. Turn on trace_launch of the method, check the server logfile and tomcat logfile.
PARAMS: S – Name of the method used to evaluate automatic transition

ERROR: [DM_WORKFLOW_E_PERFORMER_TYPE_PRIV]

SEVERITY: ERROR
DESCRIPTION: SIS The setting of %s (%d) for automatic activity %s requires SUPERUSER privileges.
CAUSE: The particular setting of the indicated attribute requires SUPERUSER privileges.
ACTION: Either use a different setting or talk to your sysadmin about your privileges.
PARAMS: S – attribute name I – attribute value S – activity name

ERROR: [DM_WORKFLOW_E_ACTIVITY_DUPLICATE]

SEVERITY: ERROR
DESCRIPTION: S Activity %s has already existed.
CAUSE: duplicate activity name in a process definition
ACTION: remove duplicate activity name
PARAMS: S – activity name

ERROR: [DM_WORKFLOW_E_UNINSTALL_PROCESS_HANDLE_WORKFLOW]

SEVERITY: ERROR
DESCRIPTION: SD Failed to halt the workflows when un-installing process %s (%s).
CAUSE: Errors occur during process un-installation. Refer to previous error message for cause. Note that some workflow instances may have been halted by the failed operation.
ACTION: Examine and fix the reported problems, and retry the operation. Inform the workflow supervisor if it fails again.
PARAMS: S – Name of the process definition D – ID of the process definition

ERROR: [DM_WORKFLOW_E_DISCONNECTED_GRAPH]

SEVERITY: ERROR
DESCRIPTION: S Activity %s does not have an incoming or outgoing link.
CAUSE: An intermediate activity does not have an incoming or outgoing link.
ACTION: Add an incoming or outgoing link to or from the activity
PARAMS: S – activity name

ERROR: [DM_WORKFLOW_E_OUTGOING_LINK]

SEVERITY: ERROR
DESCRIPTION: SS Failed to find the outgoing link from output port %s of activity %s.
CAUSE: Errors occur while looking for the outgoing connection.
ACTION: Ask the workflow supervisor to investigate the problem or restart the problematic activity.
PARAMS: S – output port name S – activity name

ERROR: [DM_WORKFLOW_E_ILLEGAL_PORT_TYPE]

SEVERITY: ERROR
DESCRIPTION: S The specified port type %s is illegal.
CAUSE: The given port type is illegal.
ACTION: Re-try the operation with one of the supported port types.
PARAMS: S – port type

ERROR: [DM_WORKFLOW_E_INVALID_NOTE]

SEVERITY: ERROR
DESCRIPTION: D The dm_note object identified as %s is not a valid object.
CAUSE: dm_note object specified is not a valid dm_note object
ACTION: specify a valid dm_note object. Null is also valid.
PARAMS: D – dm_note object id specified in addpackage API

ERROR: [DM_WORKFLOW_E_INVALID_WORKITEM_STATE]

SEVERITY: ERROR
DESCRIPTION: D The workitem, %s, is not in acquired state.
CAUSE: The workitem needs to be in acquired state for this operation to succeed.
ACTION: addpackage or removepackage is allowed only when the workitem is in acquired state.
PARAMS: D – workitem id

ERROR: [DM_WORKFLOW_E_ACTIVITY_INUSE]

SEVERITY: ERROR
DESCRIPTION: SS The activity %s is referenced by link %s.
CAUSE: Specified activity is referenced by a link.
ACTION: Remove the link and re-try the operation.
PARAMS: S – the activity in error

ERROR: [DM_WORKFLOW_E_ACCEPT_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: SSID Failed to accept packages arriving at port %s of activity %s (%d) of the workflow (%s).
CAUSE: The operation failed due to some problems.
ACTION: Ask the workflow supervisor to restart such an activity run-time instance.
PARAMS: S – the triggered port name S – name of the containing activity I – activity sequence number D – ID of the containing workflow

ERROR: [DM_WORKFLOW_E_INVALID_PACKAGE_NAME]

SEVERITY: ERROR
DESCRIPTION: S The package name, %s, is not valid.
CAUSE: The package name specified does not exist in the activity.
ACTION: Specify a package name in the activity definition.
PARAMS: S – package name

ERROR: [DM_WORKFLOW_E_PACKAGE_COMPONENT_TYPE]

SEVERITY: ERROR
DESCRIPTION: D The component, %s, is not the specified type.
CAUSE: A component is not the specified type.
ACTION: Make sure all components are of the specified type.
PARAMS: D – component ID

ERROR: [DM_WORKFLOW_E_CREATE_WORKITEM]

SEVERITY: ERROR
DESCRIPTION: SSID Failed to create a workitem for user %s within activity %s (%d) of workflow (%s).
CAUSE: Unable to create a new workitem for such user.
ACTION: Ask the workflow supervisor to investigate the problem or restart the problematic activity.
PARAMS: S – performer name S – the problematic activity name I – activity sequence number D – ID of the containing workflow

ERROR: [DM_WORKFLOW_E_SEND_WI_EVENT]

SEVERITY: ERROR
DESCRIPTION: SD The workflow engine fails to send an event %s for workitem (%s).
CAUSE: Errors occurred while recording a workitem event.
ACTION: Report to your local sysadmin to fix the reported problems.
PARAMS: S – event name D – workitem ID

ERROR: [DM_WORKFLOW_E_ACTIVITY_ATTR_COUNT]

SEVERITY: ERROR
DESCRIPTION: No of elements in activity_type/activity_priority/activity_def_id does not match that of activity_name.
CAUSE: Did not use addactivity/removeactivity commands.
ACTION: Make the number of elements in activity_name/activity_type/activity_priority/activity_def_id match.
PARAMS:

ERROR: [DM_WORKFLOW_E_NO_WRITE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: The operation requires at least WRITE permit or can be performed by a user with SYSADMIN or SUPERUSER privileges.
CAUSE: The user does not have enough object level permission or privileges.
ACTION: Retry the operation, after required permissions or privileges are granted.
PARAMS:

ERROR: [DM_WORKFLOW_E_NEED_SU_OR_SYS_PRIVS]

SEVERITY: ERROR
DESCRIPTION: S Shutdown of workflow agent failed because user (%s) does not have superuser or sys admin privileges.
CAUSE: Must have Superuser or SysAdmin privilege to perform this operation.
ACTION: Consult Documentum Administrator.
PARAMS: S – User Name

ERROR: [DM_WORKFLOW_E_INVALID_ARG]

SEVERITY: ERROR
DESCRIPTION: SSS The %s method has an invalid value (%s) for argument %s.
CAUSE: The method argument listed in the error message is invalid.
ACTION: Check the documentation to determine valid values for that argument, and then correct the argument.
PARAMS: S – Name of the method S – Value of the arguemnt S – Name of the argument

ERROR: [DM_WORKFLOW_E_CANT_END]

SEVERITY: ERROR
DESCRIPTION: S The activity %s does not reach the end activity. PARAMTERS: s – the activity
CAUSE: there is no link path from this activity to the end activity.
ACTION: create a link path to the end activity.
PARAMS:

ERROR: [DM_WORKFLOW_E_AGENT_LAUNCH]

SEVERITY: ERROR
DESCRIPTION: SS Failed to launch %s due to an operating system error: %s.
CAUSE: Launch failure was caused by an operation system error.
ACTION: Verify the operating system has enough resources.
PARAMS: S – workflow agent name S – error message from operation system

ERROR: [DM_WORKFLOW_E_SEND_WA_EVENT]

SEVERITY: ERROR
DESCRIPTION: SSID The workflow engine fails to send an event %s for activity %s (%d) of workflow (%s).
CAUSE: Errors occurred while recording an activity event.
ACTION: Report to your local sysadmin to fix the reported problems.
PARAMS: S – event name S – activity name I – activity sequence number D – workflow ID

ERROR: [DM_WORKFLOW_E_NO_VALUE]

SEVERITY: ERROR
DESCRIPTION: SSDI The attribute %s of the %s object (%s) contains no value at position %d.
CAUSE: A attribute value is missing from an expected position. This can be due to a corrupted internal index or entire object.
ACTION: Re-create the internal index by validate API command and re-try the previous operation. If such problem persists, try the failing operation on a new connection.
PARAMS: S – attribute name S – type name D – object ID I – the position where a value is missing

ERROR: [DM_WORKFLOW_E_LINK_ACTIVITY_NAME]

SEVERITY: ERROR
DESCRIPTION: S Activity %s does not exist for linking.
CAUSE: a source or destination activity name does not exist in the process definition
ACTION: specify an existing activity name
PARAMS: S – activity name

ERROR: [DM_WORKFLOW_E_UNINSTALLED_PROCESS]

SEVERITY: ERROR
DESCRIPTION: D Process definition (%s) is not installed.
CAUSE: An un-installed process defition is not ready for uses.
ACTION: Retry the operation after the process definition is installed.
PARAMS: D – process ID

ERROR: [DM_WORKFLOW_E_ADD_PORT_TABLE]

SEVERITY: ERROR
DESCRIPTION: The attributes that define a package must have the same number of values.
CAUSE: The attributes that record a package definition did not have the same number of values in each attribute. Each index position in these attributes represents one package definition. Consequently, all the attributes must have the same number of values. A missing value in one of these attributes means part of a package definition is missing.
ACTION: Ensure that all the package definition attributes are properly set and have the same number of values.
PARAMS:

ERROR: [DM_WORKFLOW_E_PERFORMER_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: SD A performer is required for activity %s (%s), or a designation of which activitys performer will choose this performer. PARAMTERS: S – activity name D – activity ID
CAUSE: An activity exists within this process that requires either a performer name or a designation that a prior activity will choose this performer. Neither has been provided.
ACTION: Either add a performer to the activity or select an activity prior to it whose performer should choose its performer.
PARAMS:

ERROR: [DM_WORKFLOW_E_WAIT_FOR_COMPLETE_TASK_FAIL]

SEVERITY: ERROR
DESCRIPTION: Workflow agent master failed in waiting for completion of currently processed task.
CAUSE: Unexpected error.
ACTION: Restart server. Report the error message to Documentum Support.
PARAMS: None

ERROR: [DM_WORKFLOW_E_CANT_START]

SEVERITY: ERROR
DESCRIPTION: SD The workflow %s can only start, when its referenced process (%s) is installed.
CAUSE: The referenced process has not been installed.
ACTION: Install the referenced process and retry the operation.
PARAMS: S – workflow name D – the referenced process ID

ERROR: [DM_WORKFLOW_E_ACTDEFID_STATE]

SEVERITY: ERROR
DESCRIPTION: D Activity definition (%s) has not been validated or installed.
CAUSE: activity definition has not been or can not be validated
ACTION: try to validate the activity definition
PARAMS: D – activity definition id

ERROR: [DM_WORKFLOW_E_PORT_NO_PACKAGE]

SEVERITY: ERROR
DESCRIPTION: SS The port %s of activity %s does not have any package.
CAUSE: Each port of an activity needs to have at least one package.
ACTION: Use addpackageinfo to add a package.
PARAMS: s – port name. s – activity name.

ERROR: [DM_WORKFLOW_F_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Failed to initialize type.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: S – type name

ERROR: [DM_WORKFLOW_F_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: SII Type %s has a bad vstamp %d. The vstamp is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS: S – type name I – the vstamp in the database I – the vstamp the server is expecting

ERROR: [DM_WORKFLOW_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type %s to version %d.
CAUSE: Type conversion failed.
ACTION: Report the problem.
PARAMS: S – type name I – the version stamp we are trying to upgrade to

ERROR: [DM_WORKFLOW_F_VIEW_INIT]

SEVERITY: FATAL
DESCRIPTION: SS Failed to create view %s: database error was: %s.
CAUSE: Failed to create a database view for port information
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_WORKFLOW_W_PEFORMER_OF_PREVIOUS_ACT]

SEVERITY: WARNING
DESCRIPTION: SS Activity %s is set to use performer(s) of activity %s. But the source activity has not been triggered or has not finished. Therefore the task is assigned to the workflow supervisor.
CAUSE: When setting up a workflow template, an activitys performer can be set to Use (Last) Performer(s) of Previous Activity. At runtime, when creating tasks for this activity, Content Server retrieves the performer(s) of the previous activity. If the previous activity is not triggered yet or has not finished, then the server returns this warning message and assigns the task to the workflow supervisor.
ACTION: Re-design the workflow template.
PARAMS: S – name of the target activity S – name of the source activity

ERROR: [DM_WORKFLOW_W_DYNAMIC_PERFORMER]

SEVERITY: WARNING
DESCRIPTION: SS Failed to resolve dynamic performer %s based on process data. %s
CAUSE: When setting up a workflow template, an activitys performer can be set to Select performer based on process data. At runtime, when creating tasks for this activity, Content Server resolves the performer(s) from the process data instances. If any error happens during the resolution, then the server returns this warning message and assigns the task to the workflow supervisor.
ACTION: Re-design the workflow template.
PARAMS: S – dynamic performer S – error happened during the performer resolution

ERROR: [DM_WORKFLOW_W_DANGLING_PORT]

SEVERITY: WARNING
DESCRIPTION: SSSD Output port %s of activity %s within process definition %s (%s) is a dangling port.
CAUSE: No outgoing connection is found for a selected output port.
ACTION: Report this message to the process designer for fix-up, if necessary.
PARAMS: S – output port name S – activity name S – name of the containing process definition D – ID of the process definition

ERROR: [DM_WORKFLOW_W_NO_DELEGATION]

SEVERITY: WARNING
DESCRIPTION: S User, %s, does not have any one to delegate to.
CAUSE: The user is not accepting new work and there is no one in the delegation list who is available.
ACTION: Make the user or people on its delegation list available or add new people to the delegation list.
PARAMS: s – user name

ERROR: [DM_WORKFLOW_W_PERFORMER_UNRESOLVED]

SEVERITY: WARNING
DESCRIPTION: SSDS A user/group could not be found for performer %s of activity %s of workflow (%s). The activity has been assigned to the workflow supervisor, %s.
CAUSE: No valid match was found for the alias provided within the alias sets associated with this workflow and with the current user.
ACTION: Make sure that an alias set accessible by the resolution scheme defines a value for the alias set.
PARAMS: S – performer name or an alias S – activity name D – workflow ID S – supervisor name

ERROR: [DM_WORKFLOW_W_BINDING_PACKAGE]

SEVERITY: WARNING
DESCRIPTION: DS Package binding failed because no object could be identified by package ID (%s) with package label %s.
CAUSE: No object with the given version label can be found within the version tree in which the given object resides.
ACTION:
PARAMS: D – package ID S – package label

ERROR: [DM_WORKFLOW_W_NO_MESSAGE_SENT]

SEVERITY: WARNING
DESCRIPTION: S An event notification could not be sent to user %s
CAUSE: The user to whom the message was designated could not be found
ACTION: Take action to remove the user from participation in the workflow
PARAMS: S – User name

ERROR: [DM_WORKFLOW_W_PERFORMER_CATEGORY]

SEVERITY: WARNING
DESCRIPTION: SSD Invalid alias category for resolved performer %s of activity %s of workflow (%s): the category of the alias was not user or group
CAUSE: When resolving an alias into a performer, the alias that was found in the alias set was not of type user and/or group
ACTION: Change the alias category of the alias set to be user and/or group for this alias name
PARAMS: S – performer name or an alias S – activity name D – workflow ID

ERROR: [DM_WORKFLOW_W_TASKSUBJECT_UNRESOLVED]

SEVERITY: WARNING
DESCRIPTION: D Resolving task subject failed for workitem (%s), task_subject attribute of its inbox item is not set.
CAUSE: Internal Error
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: D – workitem ID

ERROR: [DM_WORKFLOW_W_TASKINSTRUCTION_UNRESOLVED]

SEVERITY: WARNING
DESCRIPTION: D Resolving task instruction failed for workitem (%s), message attribute of its inbox item is not set.
CAUSE: Internal Error
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: D – workitem ID

ERROR: [DM_WORKFLOW_W_CANT_REACH]

SEVERITY: WARNING
DESCRIPTION: S Activity %s can not be reached from any start activity.
CAUSE: There is no link path from any start activity to this activity.
ACTION: Add a link path from a start activity to this one.
PARAMS: S – activity name

ERROR: [DM_WORKFLOW_W_AGENT_DIED]

SEVERITY: WARNING
DESCRIPTION: Server detected that workflow agent master has died, and is restarting it ……
CAUSE: Unknown. Server will recover automatically by re-launching the workflow agent.
ACTION:
PARAMS: None.

ERROR: [DM_WORKFLOW_W_RESOLVE_PROCESS_PARAMETER]

SEVERITY: WARNING
DESCRIPTION: SS Failed to resolve process parameter %s. %s
CAUSE: When setting up a workflow template, some activitys properties can be set to be resolved from a process parameter. e.g. the performer of an activity, or the timeout value of an automatic activity. If any error happens during the resolution at workflow runtime, then the server returns this warning message.
ACTION: Examine the error or Re-design the workflow template.
PARAMS: S – name of the process parameter S – error happened during the process parameter resolution

ERROR: [DM_WORKFLOW_W_PORT_INCOMPAT_DOWN_CASTING]

SEVERITY: WARNING
DESCRIPTION: ISSSS Down casting occurs between %dth packages from source activity %s source port %s and destination activity %s destination port %s
CAUSE: package type of source port is a super type of package type of destination port
ACTION: change the type specification
PARAMS: I – the position of packages within the ports S – source activity S – source port S – destination activity S – destination port

ERROR: [DM_WORKFLOW_W_UNABLE_TO_DELETE_INTERNAL_GROUP]

SEVERITY: WARNING
DESCRIPTION: S Unable to delete the internal group %s.
CAUSE: Internal Error
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS: S – group name

ERROR: [DM_WORKFLOW_W_EXEC_POOL_FULL]

SEVERITY: WARNING
DESCRIPTION: S Failed to launch %s due to no vacancy in the execution context pool.
CAUSE: The number of servers or agents has exceeded the supported limit.
ACTION: No actions are necessary. The server will re-launch such agent upon availability of the execution context pool.
PARAMS: S – name of workflow agent

ERROR: [DM_WORKFLOW_I_AGENT_TERMINATE]

SEVERITY: INFORMATION
DESCRIPTION: SSIS Workflow agent %s (%s : %d, session %s) has terminated sucessfully.
CAUSE: This is an informational message generated at session termination.
ACTION: None. Informational message only.
PARAMS: The first parameter indicates this is a master or worker The second parameter is pid or tid The third parameter is the process/thread id The fourth parameter is session id.

ERROR: [DM_WORKFLOW_I_SHUTDOWN_TIMEDOUT]

SEVERITY: INFORMATION
DESCRIPTION: Workflow agent shutdown has timed out. System Administrator should execute the RECOVER_AUTO_TASKS administrative method to recover the workitems.
CAUSE: This is an informational message indicating the workflow agent timed out during shutdown.
ACTION: Run the RECOVER_AUTO_TASKS adminstrative method to recover the workitems collected by this workflow agent.
PARAMS: NONE

ERROR: [DM_WORKFLOW_I_AGENT_SHUTDOWN]

SEVERITY: INFORMATION
DESCRIPTION: Workflow agent has been successfully shutdown.
CAUSE: This is an informational message indicating the workflow agent shutdown.
ACTION: None. Informational message only.
PARAMS: None

ERROR: [DM_WORKFLOW_I_AGENT_START]

SEVERITY: INFORMATION
DESCRIPTION: SSIS Workflow agent %s (%s : %d, session %s) is started sucessfully.
CAUSE: This is an informational message generated at session startup.
ACTION: None. Informational message only.
PARAMS: The first parameter indicates this is a master or worker The second parameter is pid or tid The third parameter is the process/thread id The fourth parameter is session id.

nahoru

DM_XFRM

ERROR: [DM_XFRM_E_CONVERT_TABLE]

SEVERITY: ERROR
DESCRIPTION: SSS The location defined in your server configuration for conversions, (%s), specifies a file, (%s), which cannot be accessed. The Operating System error returned was (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_XFRM_E_WAIT_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to wait for the command: %s. Operating system error: %s.
CAUSE: Unable to wait for command to finish successfully.
ACTION: See your system administrator.
PARAMS:

ERROR: [DM_XFRM_E_BAD_ATTR]

SEVERITY: ERROR
DESCRIPTION: S Bad conversion attribute: %s
CAUSE: The conversion attribute given is incorrect.
ACTION: Change the line in the convert.tbl file to a valid conversion format.
PARAMS:

ERROR: [DM_XFRM_E_CURSOR_FETCH_FAIL]

SEVERITY: ERROR
DESCRIPTION: S A failure occurred during a fetch through a cursor: database error message was %s
CAUSE: During a fetch in a database cursor, the operation failed. The operation is terminated.
ACTION: The database system error message may indicate how to repair the error.
PARAMS:

ERROR: [DM_XFRM_E_CANT_CONV]

SEVERITY: ERROR
DESCRIPTION: SSI Could not transform document %s to format %s on page %d
CAUSE: Transformation failed for some reason previously stated.
ACTION: Insure that all is well with the converter. You may need to purchase the a new converter in order to accomplish the conversion or there may not be a transformation possible to the format you have requested.
PARAMS:

ERROR: [DM_XFRM_E_NEED_LOC]

SEVERITY: ERROR
DESCRIPTION: SS Could not locate %s temp_location os_error: %s
CAUSE: Server could not open the temp_location successfully. Most likely has been removed.
ACTION: See your adminstrator.
PARAMS:

ERROR: [DM_XFRM_E_CONVERT_DIRECTORY_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SSS The location defined in your server configuration for conversions, (%s), specifies a directory, (%s), which cannot be accessed. The Operating System error returned was (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_XFRM_E_NO_BACKING_STORE2]

SEVERITY: ERROR
DESCRIPTION: No backing store to make copy of external content
CAUSE: Attempt to convert blob or turbo content without defining backing store
ACTION: See your adminstrator to correct the server_config object.
PARAMS:

ERROR: [DM_XFRM_E_NO_BACKING_STORE]

SEVERITY: ERROR
DESCRIPTION: No backing store to make copy of blob/turbo content
CAUSE: Attempt to convert blob or turbo content without defining backing store
ACTION: See your adminstrator to correct the server_config object.
PARAMS:

ERROR: [DM_XFRM_E_ATTR_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Conversion %s failed to read attributes
CAUSE: Unable to read intermediate file containing conversion results.
ACTION: Insure that there is enough space in the temporary directory and that all is well with the converter indicated.
PARAMS:

ERROR: [DM_XFRM_E_NO_ORIG]

SEVERITY: ERROR
DESCRIPTION: SI Unable to find the original for %s on page %d
CAUSE: The original format of the document no longer exists.
ACTION: Add the rendition requested. Use the setfile or addrendition command to add the original format contents to the document.
PARAMS:

ERROR: [DM_XFRM_E_NO_CVRT]

SEVERITY: ERROR
DESCRIPTION: SS Unable to find a conversion from %s to %s
CAUSE: Unable to find a conversion from the stored format to the format requested.
ACTION: Insure that all is well with the converter. You may need to purchase the a new converter in order to accomplish the conversion or there may not be a transformation possible to the format you have requested.
PARAMS:

ERROR: [DM_XFRM_E_NEED_TEMP]

SEVERITY: ERROR
DESCRIPTION: Need to define a temp_location to perform convesions.
CAUSE: Server did not sess a temp_location in your server_config object.
ACTION: Define a temp_location in your server_config object.
PARAMS:

ERROR: [DM_XFRM_E_LAUNCH_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failed to launch the command: %s. Operating system error: %s.
CAUSE: Unable to lauch command successfully.
ACTION: You may run out of processes or see your system administrator.
PARAMS:

ERROR: [DM_XFRM_E_ATTR_EXCEED]

SEVERITY: ERROR
DESCRIPTION: ISS List has > %d attributes: %s…%s
CAUSE: There are too many attributes for a conversion in the convert.tbl file.
ACTION: Reduce the number of conversion formats on the line. Break up the line into multiple conversions. If this fails return to the default convert.tbl file whose copy is named convert.bak in the convert/scripts directory.
PARAMS:

ERROR: [DM_XFRM_E_INVALID_CONV]

SEVERITY: ERROR
DESCRIPTION: S Invalid %s server_converter_location defined.
CAUSE: Invalid location is pointed by the server_config object.
ACTION: See your adminstrator to correct the server_config object.
PARAMS:

ERROR: [DM_XFRM_E_CANT_CONV_EXT]

SEVERITY: ERROR
DESCRIPTION: SSSII External converter %s could not transform document %s to format %s on page %d, status returned %d
CAUSE: Transformation failed for some reason previously stated.
ACTION: Insure that all is well with the converter. You may need to purchase the a new converter in order to accomplish the conversion or there may not be a transformation possible to the format you have requested.
PARAMS:

ERROR: [DM_XFRM_E_CANT_OPEN]

SEVERITY: ERROR
DESCRIPTION: SS Unable to open file: (%s). Operating System Error: (%s)
CAUSE: Cannot open the conversion file indicated.
ACTION: Make sure that the convert.tbl file exists in the convert/scripts directory. If necessary, copy the orginal version convert.old to convert.tbl.
PARAMS:

ERROR: [DM_XFRM_E_TOO_MANY_CVRT]

SEVERITY: ERROR
DESCRIPTION: I More than %d conversions
CAUSE: The number of lines beginning with -c has exceed the maximum.
ACTION: Eliminate unnecessary conversions. If necessary, copy the orginal version convert.old to convert.tbl.
PARAMS:

ERROR: [DM_XFRM_E_MEMORY]

SEVERITY: ERROR
DESCRIPTION: S Unable to allocate memory for file: %s
CAUSE: There is not enough memory to allocate the conversion tables.
ACTION: Restart the server and insure that there is sufficient swap space. Try reducing the size of the convert.tbl if it is very large.
PARAMS:

ERROR: [DM_XFRM_E_NO_FMT_AVAIL]

SEVERITY: ERROR
DESCRIPTION: SSI Unable to find a rendition for %s with format %s on page %d
CAUSE: No rendition exists in the database and the conversion engine has been turned off.
ACTION: Add the rendition requested. There may not be a conversion available to that format. Insure that all is well with the converter.
PARAMS:

ERROR: [DM_XFRM_E_CVRT_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Conversion %s failed for attribute %s
CAUSE: The conversion failed to convert to the format indicated.
ACTION: Insure that there is enough space in the temporary directory and that all is well with the converter indicated.
PARAMS:

ERROR: [DM_XFRM_W_NO_CONVERT_LOC_DEFINED]

SEVERITY: WARNING
DESCRIPTION: Your server configuration does not define a conversion location — no conversions can be performed.
CAUSE:
ACTION:
PARAMS:

A to je vše…

Michal Šika