DESCRIPTION: The type manager returned an error storing the dm_user type.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum Site Representive.
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.
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.
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.
DESCRIPTION: The docbase auth_protocol is not of any value known to server.
ACTION: Ask the DBA to fix the corrupted data and then restart the server.
DESCRIPTION: The dm_user type was found in the database without a version stamp.
ACTION: Report this message and any parameters to your Documentum Site Representive.
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.
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.
DESCRIPTION: I Failed to convert the dm_user to version %d.
CAUSE: Cannot fetch the user with the given object id.
ACTION: Try again with the correct id.
ACTION: dont try to change a super users user_state if you are not a super user.
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.
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.
DESCRIPTION: IIII Specified privileges %d are invalid, supported values are %d, %d, %d and their ord values.
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.
CAUSE: Tried to create a user that already exists. All user names must be unique.
ACTION: Try again with a different user_name.
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.
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.
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.
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.
DESCRIPTION: S A job request to rename user (%s) is in progress or in pipeline to be processed.
CAUSE: Rename operations are not atomic. This could leave a security hole if, say some user is renamed partially and before user object is repaired, if new user is created with same name, newly added user will have undefined rights on some of the docbase objects. Also we can’t retry/repair the last partial rename activity, because user with same name is created.
ACTION: Make sure that there is no active rename request scheduled.
PARAMS: Value is the name of the user.
DESCRIPTION: Server failed to decrypt user password.
DESCRIPTION: SSS Failed to save ACL %s in name space %s for user object %s.
CAUSE: Failed to save the default ACL.
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.
CAUSE: All user definition must have a user_name, user_os_name and e-mail address before save.
CAUSE: The user attempting to open a session does not exist.
ACTION: Try again with the correct name.
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.
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.
PARAMS: I – Actual string size of the encrypted password. I – Allowed string size.
DESCRIPTION: SS The user %s is given an invalid ACL domain %s.
CAUSE: Invalid ACL domain is given.
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.
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.
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.
ACTION: Specify the domain name and try again.
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.
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.
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.
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.
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.
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.
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.
DESCRIPTION: S The user name %s is reserved.
CAUSE: The user name provided is a reserved name.
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.
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.
CAUSE: Failed to fetch the default ACL.
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.
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.
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.
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.
DESCRIPTION: SS The user (%s) needs to have at least sysadmin privilege or be the users user admin to change the %s user object.
DESCRIPTION: S Cannot find user %s.
CAUSE: Cannot find the group with the given name.
DESCRIPTION: SSS Failed to fetch the default ACL %s in name space %s of user %s.
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.
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.
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.
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.
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.
CAUSE: All user definitions must have a user_name, user_os_name and e-mail address before save.
CAUSE: You have specified a logon domain which is different from the server default.
ACTION: Logon again using the server default domain.
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.
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.
CAUSE: Tried to create a user that its user_name exists. All user names must be unique.
DESCRIPTION: SII The upgrade failed on widening users attribute (%s) length from %d to %d.
CAUSE: The database server may have problems widening the column length (e.g., the column is indexed), or the attribute length may already be widen.
ACTION: Check database server log or use sql script(under dba) to upgrade. If the column is indexed, then drop the index, restart server and re-index the column.