DM SESSION

From DCTMWiki
Jump to: navigation, search

Contents

DM_SESSION_I_SESSION_START

"Session %s started for user %s."

CAUSE: This is an informational message generated at session startup.

ACTION: None. Informational message only.

PARAMETERS: The id of the session and the client node name of the user

DM_SESSION_I_SESSION_QUIT

"Session %s quit."

CAUSE: This is an informational message generated at session close.

ACTION: None. Informational message only.

PARAMETERS: The id of the session and the current time

DM_SESSION_I_SESSION_PAUSE

"Session %s paused."

CAUSE: This is an informational message generated at session pause.

ACTION: None. Informational message only.

PARAMETERS: The id of the session and the current time

DM_SESSION_I_INITIALIZE_DB

"Initializing document base %s"

CAUSE: This is an informational message generated when the document base is first initialized

ACTION: None: Informational message only.

PARAMETERS: The name of the document base.

DM_SESSION_I_NEW_CONN

"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.

PARAMETERS: The handle of the new session.

DM_SESSION_I_INIT_BEGIN

"Initialize %s."

CAUSE: This is an informational message generated when the document base is initializing each type.

ACTION: None.

DM_SESSION_I_INIT_END

"Initialized %s."

CAUSE: This is an informational message generated when the document base is initializing each type.

ACTION: None.

DM_SESSION_I_TRANSACTION_ABORT

"Transaction aborted because of client timeout"

CAUSE: The transaction begun by the client was aborted because of a timeout.

ACTION: None.

DM_SESSION_I_SESSION_AUTHENTICATED

"Session %s started and authenticated for user (%s)."

CAUSE: This is an informational message generated at session startup.

ACTION: None. Informational message only.

PARAMETERS: The id of the session and the client node name of the user

DM_SESSION_I_OPERATION_STARTED

"Operation %s started."

CAUSE: This is an informational message generated if operation logging has been turned on

ACTION: None. Informational message only.

PARAMETERS: The name of the operation completed

DM_SESSION_I_OPERATION_ENDED

"Operation %s completed."

CAUSE: This is an informational message generated if operation logging has been turned on

ACTION: None. Informational message only.

PARAMETERS: The name of the operation completed.

DM_SESSION_I_OPERATION_ARGUMENTS

"%s"

CAUSE: This is an informational message generated if operation logging has been turned on

ACTION: None. Informational message only.

PARAMETERS: The arguments for the current operation.

DM_SESSION_I_OPERATION_RESULTS

"%s"

CAUSE: This is an informational message generated if operation logging has been turned on

ACTION: None. Informational message only.

PARAMETERS: The result of the current operation.

DM_SESSION_I_RETRYING_DATABASE_CONNECTION

"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.

DM_SESSION_I_KILL_SESSION

"User '%s' is attempting to kill session '%s'."

CAUSE: There was an attempt to kill the session.

ACTION: None. Informational message only.

DM_SESSION_I_DEADLOCK_RETRY

"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.

DM_SESSION_I_DEADLOCK_INFO

"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.

DM_SESSION_I_ASSUME_USER

"Session %s is owned by user %s now."

CAUSE: Informational message when a session assumed by a different user.

ACTION: None. Informational only.

PARAMETERS: session id and user name

DM_SESSION_I_TRACE_ENABLED

"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.

PARAMETERS: Client session info (process_id, thread_id, machine_name) The trace facility

DM_SESSION_I_FIRST_ATTEMPT_FAIL

"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.

PARAMETERS: Two strings: "secure" and "native"

DM_SESSION_I_AUTH_PLUGIN_LOADED

"Loaded Authentication Plugin with code '%s' (%s)."

CAUSE: Informational message when an authentication plugin is loaded.

ACTION: None. Informational only.

PARAMETERS: The code and file path of the Authentication Plugin.

DM_SESSION_I_CONNECTED_TO_DATABASE

"Successfully connected to database %s on %s"

CAUSE: Informational message when a session establishes a database connection.

ACTION: None. Informational only.

PARAMETERS: Parameter 1 is the database name. Parameter 2 is the name of the server or machine on which the database resides.

DM_SESSION_I_PUSHING_OBJ_BY_CHUNKS

"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.

PARAMETERS: The name of the operation which is pusing the object by chunks.

DM_SESSION_W_NO_CONNECTION

"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.

PARAMETERS: None.

DM_SESSION_W_TRANSACTION_FAILURE

"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.

PARAMETERS: The handle for the session and the internal error string from the database system.

DM_SESSION_W_ROLLBACK_FAILURE

"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.

PARAMETERS: The handle for the session and the internal error string from the database system.

DM_SESSION_W_CANT_BEGIN_TRANSACTION

"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.

DM_SESSION_W_CANT_MAKE_TYPE_MANAGER

"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.

PARAMETERS: The name of the user.

DM_SESSION_W_CANT_MAKE_OBJECT_MANAGER

"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.

PARAMETERS: The name of the user and the name of the document base.

DM_SESSION_W_CANT_RESUME_SESSION

"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.

PARAMETERS: The handle of the session and the name of the user.

DM_SESSION_W_OBJECT_UPDATE_FAILED

"Save of object of type %s failed because attribute update to new values failed."

CAUSE: A request to save an object failed because the object's attributes could not be successfully updated.

ACTION: This is an internal failure and should be reported to Documentum technical support.

PARAMETERS: The type of the object that was attempted to be saved.

DM_SESSION_W_SAVE_OF_NULL_OBJECT

"Save of NULL object attempted."

CAUSE: A request to save an empty object.

ACTION: No action. The save is ignored.

PARAMETERS: None.

DM_SESSION_W_SAVE_OF_NONEXISTENT_OBJECT

"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.

PARAMETERS: The handle of the object.

DM_SESSION_W_SAVE_COMMIT_FAILED

"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 object's attributes were updated.

ACTION: Retry the save.

PARAMETERS: The handle of the object.

DM_SESSION_W_FETCH_FAILED

"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.

PARAMETERS: The handle of the object and the type of the object.

DM_SESSION_W_ENUMERATE_OF_NULL

"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.

PARAMETERS: None.

DM_SESSION_W_ENUMERATE_TYPE_FAILURE

"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.

PARAMETERS: The name of the type that was to be enumerated.

DM_SESSION_W_MATCH_TYPE_NULL

"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.

PARAMETERS: None.

DM_SESSION_W_MATCH_TYPE_FAILURE

"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.

PARAMETERS: The type name.

DM_SESSION_W_MATCH_ATTRIBUTE_ERROR

"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.

PARAMETERS: The number and type of the mismatched attributes.

DM_SESSION_W_DESTROY_FAILED

"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.

PARAMETERS: The handle of the object that was to be destroyd.

DM_SESSION_W_DESTROY_ABORTED

"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.

PARAMETERS: The handle of the object that was being destroyed. Session error codes.

DM_SESSION_W_DB_PASSWORD_FILE_OWNER

"The database password file, (%s), is readable by other users."

DM_SESSION_W_PASSWORD_STALE

"The password for user (%s) with user OS name (%s) is stale";

DM_SESSION_W_CANT_SET_CONVERSION_IDENTIFIER

"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.

DM_SESSION_W_EXEC_POOL_FULL

"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 this's been happening a lot, increase concurrent_session in the server.ini.

DM_SESSION_W_LAUNCH_DEFER_UPDATE

"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.

DM_SESSION_W_ZOMBIE_HOT_SESSION_FOUND

"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.

DM_SESSION_W_RESTART_AGENT_EXEC

"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.

DM_SESSION_W_LAUNCH_AGENT_EXEC

"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.

DM_SESSION_W_LAUNCH_CHANGE_CHECK

"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.

DM_SESSION_W_CHANGE_CHECK_ALIVE

"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

DM_SESSION_W_AGENT_EXEC_FAILURE_EXCEED

"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.

DM_SESSION_W_LIB_LOAD

"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.

DM_SESSION_W_LDAP_NOCONFIG

"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.

DM_SESSION_W_GENTICKET_FAIL

"Failed to generate login ticket for user %s."

CAUSE: Generating login ticket fails.

ACTION: Make sure unused login tickets are cleaned-up.

PARAMETERS: The user name and docbase base.

DM_SESSION_W_AUTH_PLUGIN_DUPL_CODE

"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.

PARAMETERS: The identifier and file path of the authentication plugin.

DM_SESSION_E_BAD_INFO

"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: Check to see that the dminfo.sys file exists and has the proper format

ACTION: Retired message.

DM_SESSION_E_INVALID_USER

"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.

PARAMETERS: The name of the user and the name of the document base.

DM_SESSION_E_CANT_ESTABLISH_CONNECTION

"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:

PARAMETERS:

DM_SESSION_E_CANT_FIND_DOCUMENT_BASE

"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: Check that the document base name and the $DOCU_HOME environment variables are correct.

PARAMETERS: The document base name.

ACTION: Retired message.

DM_SESSION_E_CANT_READ_DB_PASSWORD

"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.

PARAMETERS: The document base name.

DM_SESSION_E_WRONG_DOCBASE_ID

"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.

PARAMETERS: %1 The docbase id as recorded in the docbase. %2 The docbase id listed in server.ini file. %3 The docbase name.

DM_SESSION_E_CANT_FIND_VERSION_STAMP_TABLE

"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: Check that the entry for the document base in the dminfo.sys directory is correct.

PARAMETERS: The name of the document base.

ACTION: Retired message.

DM_SESSION_E_CANT_FIND_ID_TABLE

"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: Check that the entry for the document base in the dminfo.sys directory is correct.

PARAMETERS: The name of the document base.

ACTION: Retired message.

DM_SESSION_E_CANT_SET_DATABASE_IDENTIFIER

"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: Check that the entry for the document base in the dminfo.sys directory is correct, and that the DM_DBUSER for the document base can modify create and update tables in the database.

PARAMETERS: The name of the document base.

ACTION: Retired message.

DM_SESSION_E_CANT_INITIALIZE_SESSION

"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.

PARAMETERS: The name of the document base.

DM_SESSION_E_INIT_FAILURE

"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: Check that the database system has been properly installed.

PARAMETERS: The number of the initialization procedure that failed.

ACTION: Retired message.

DM_SESSION_E_CANT_SET_SESSION_STAMP

"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.

PARAMETERS: None.

DM_SESSION_E_CANT_SAVE_TRANS_TYPE

"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.

PARAMETERS: None.

DM_SESSION_E_CANT_SAVE_SESSION_TYPE

"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.

PARAMETERS: None.

DM_SESSION_E_SESSION_STAMP_FAILURE

"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.

PARAMETERS: None.

DM_SESSION_E_CANT_BUILD_SESSION_TYPES

"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.

PARAMETERS: The name of the user and the name of the document base.

DM_SESSION_E_BOGUS_STAMP_TABLE

"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.

PARAMETERS: None.

DM_SESSION_E_CANT_INSERT_STAMP

"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.

PARAMETERS: The error string returned by the database system.

DM_SESSION_E_CANT_UPDATE_STAMP

"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.

PARAMETERS: The error string returned by the database system.

DM_SESSION_E_CANT_UPDATE_ID_TABLE

"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.

PARAMETERS: The error string returned by the database system.

DM_SESSION_E_RPC_ERROR

"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.

DM_SESSION_E_CANT_MAKE_TEMP_CONNECTION

"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.

DM_SESSION_E_CANT_MAKE_IDENTIFIER

"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.

DM_SESSION_E_CANT_BUILD_IDENTIFIER_TABLE

"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.

DM_SESSION_E_CANT_FIND_IDENTIFIER_TABLE

"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.

DM_SESSION_E_DATABASE_ID_NOT_FOUND

"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.

DM_SESSION_E_START_FAIL

"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.

DM_SESSION_E_CANT_MAKE_TABLE

"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.

DM_SESSION_E_INIT_FAILURE1

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_ATTEMPT_TO_SAVE_TYPE

"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.

PARAMETERS: None.

DM_SESSION_E_CANT_FIND_SERVICE

"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.

DM_SESSION_E_CANT_CONNECT

"Could not connect to docbase (%s) at host (%s) because (%s). Network address: (%s)." CAUSE The client could not establish a connection to the service on the named host. ACTION This likely means that the server is not running

DM_SESSION_E_CONNECT_REJECT

"Connection request rejected by docbase (%s) at host (%s) because (%s). Network address: (%s)."

CAUSE: The server rejected the client connection request. ACTION 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.

DM_SESSION_E_BAD_CLIENT_DIRS

"Could not validate directories needed by client; errors were %s"

DM_SESSION_E_CANT_MAKE_ID

"Could not satisfy request to make %d ids for the tag %d"

DM_SESSION_E_NO_TRANSACTION

"Transaction was not open; commit failed."

DM_SESSION_E_CANT_COMMIT

"Transaction could not be committed -- RPC to server failed"

DM_SESSION_E_PASSWORD_CHECK_1

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHECK_FORK

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHECK_WAITPID

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHECK_GETPWNAM

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_NO_TRANSLATOR

"Unable to find character translator for client machine: (%s) with client Locale: (%s)"

DM_SESSION_E_CONNECT_DOCBROKER

"Unable to connect to docbase (%s). The Docbroker network addressing lookup failed"

DM_SESSION_E_DB_PASSWORD_FILE

"Unable to access database password file: (%s). The operating system error was: (%s)."

DM_SESSION_E_DB_PASSWORD_FILE_OPEN

"Unable to open the database password file: (%s)."

DM_SESSION_E_PASSWORD_CHECK_POPEN

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHECK_PCLOSE

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHECK_SEU

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHECK_SE1

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHECK_SE2

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHECK_SEP

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHANGE_FAILURE

"The server was unable to change your password";

CAUSE: The program failed during change password.

ACTION: Check that the dm_server_config.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_ELOC_NOT_CONFIGURED

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHANGE_SEU

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHANGE_SENP

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHANGE_SEOP

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHANGE_1

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_DOWNREV_SERVER

"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)."

DM_SESSION_E_PASSWORD_EXPIRED

"The Operating System password for user (%s) with user OS name (%s) has expired";

DM_SESSION_E_ACCOUNT_EXPIRED

"The Operating System account for user (%s) with user OS name (%s) has expired";

DM_SESSION_E_ACCOUNT_DROPPED

"The Operating System account for user (%s) with user OS name (%s) has been dropped";

DM_SESSION_E_ACCOUNT_LOCKED

"The Operating System account for user (%s) with user OS name (%s) has been locked";

DM_SESSION_E_UNEXPECTED_CHK_RES

"The return value from the external password validation program (%s) returned an unexpected value: (%d)"

DM_SESSION_E_CHK_PASS_OS_ERROR

"There was an unexpected error during validation of your user credentials. Please see your system administrator or check the server log"

DM_SESSION_E_RESTRICTED_ACCESS

"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."

DM_SESSION_E_CHGPASS_CRITERIA

"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"

DM_SESSION_E_CHGPASS_CRITERIA_V

"The changepassword API failed with the following error: %s"

DM_SESSION_E_CANT_ADVANCE_ID

"Could not advance id generation beyond %i for tag %i"

DM_SESSION_E_BAD_PARTITION_SPEC

"Illegal address partitioning specification -- partitions: %i, start: %i, end: %i"

DM_SESSION_E_CANT_KILL_TICKET

"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.

DM_SESSION_E_BAD_TICKET

"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=<num>

DM_SESSION_E_CHG_PASS_BAD_CRED

"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

DM_SESSION_E_SEC_MODE_UNKNOWN

"Failed to find out the docbase security mode, due to the sessionconfig doesn't 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.

DM_SESSION_E_BAD_INFOID

"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.

WHERE ENCOUNTERED: This error was encountered when using an API command against a 6.5 Repository to return object type information. In prior versions, the client app could issue a get call to retrieve information for a type, get,s0,tdm_sysobject,attr_length[0]. The tdm_sysobject document contains the type info for dm_sysobject. When connected to a 6.5 repository, this call returns a document/object not found error followed by this error with the message: "Bad Info ID given: 2e00000000000000".

RESOLUTION: The client application must be modified to retrieve type information in a different way.

DM_SESSION_E_DOCBASE_VSTAMP

"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.

DM_SESSION_E_HEAP_CREATION_FAILURE

"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

DM_SESSION_E_ASSUME_USER_FILE

"Unable to access the assume user program file. Error returned from Operating System: (%s). Program file: (%s)."

CAUSE: the

DM_SESSION_E_DUMMY1_MESSAGE

"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.

DM_SESSION_E_LAUNCH_VALIDATION

"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

DM_SESSION_E_ACE_CREATE

"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

DM_SESSION_E_SET_SECURITY

"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

DM_SESSION_E_NETWORK_TIMEOUT

"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

DM_SESSION_E_NOT_SYSADMIN

"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

DM_SESSION_E_CHANGE_CHECKING_ABORTED

"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.

DM_SESSION_E_STORESTAT_OVERFLOW

"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.

PARAMETERS: %d Size of overflowed array %s ID value of storage area that could not be added

DM_SESSION_E_PASSWORD_CHANGE_LAUNCH

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_PASSWORD_CHECK_LAUNCH

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_NO_LOG_LOC_DEFINED

"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.

DM_SESSION_E_LOG_DIR_ACCESS

"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)."

DM_SESSION_E_MISSING_PARAMETERS

"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.

DM_SESSION_E_MAKE_DATABASE_CONN

"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.

DM_SESSION_E_MAX_HEAP_SIZE

"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

DM_SESSION_E_INVALID_SESSION_ID

"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.

DM_SESSION_E_INVALID_VENGEANCE

"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.

DM_SESSION_E_KILL_FAIL

"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.

DM_SESSION_E_NT_UNIFIED_LOGON_FAILED

"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.

DM_SESSION_E_SESSION_NOT_FOUND

"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

DM_SESSION_E_UNEXPECTED_EXTERNAL

"The external password validation program (%s) returned an unexpected value: (%d). Error details: (%s)."

CAUSE: ACTION

DM_SESSION_E_NOT_SUPERUSER

"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

DM_SESSION_E_FILE_LIB

"The server failed to set up the file I/O library. Operating System error: %s."

CAUSE: cannot map the C-runtime library calls to server's function call.

DM_SESSION_E_DB_CONNECTION_FAILURE

"%s"

CAUSE: A database failure. The details of the failure are in the argument.

DM_SESSION_E_LAUNCH_BP_TRANSITION

"Unable to launch the BP transition evaluation process due to the error: %s"

CAUSE: Possible cause is Java Method is down.

ACTION: Start / Re-start the Java Method Server

DM_SESSION_E_TRANSACTION_ABORTED

"Transaction aborted by server due to client session timeout. Use abort API to re-establish connection to server."

DM_SESSION_E_PASSWORD_CHECK_GETPWNAM2

"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.

PARAMETERS: The number of the initialization procedure that failed.

DM_SESSION_E_DEADLOCK

"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.

DM_SESSION_E_LDAP_AUTHENTICATION_FAILED

"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.

DM_SESSION_E_LDAP_DOWN

"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.

DM_SESSION_E_LDAP_SEARCH

"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.

DM_SESSION_E_LDAP_NOENTRY

"The search in the Directory Server for user (%s) didn't produce any results."

CAUSE: The Directory Server doesn't contain a uid with the user's name.

ACTION: Inform your System Administrator.

DM_SESSION_E_LDAP_BIND

"The bind call to the Directory Server failed."

CAUSE: The password might be incorrect.

ACTION: Try again.

DM_SESSION_E_LDAP_MULTIPLE_UID

"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.

DM_SESSION_E_LDAP_INIT

"The initialization of the ldap library failed."

CAUSE: Unknown.

ACTION: Inform your System Administrator.

DM_SESSION_E_LDAP_OPT_RECONNECT

"The setting of the reconnect option failed."

CAUSE: Unknown.

ACTION: Inform your System Administrator.

DM_SESSION_E_LDAP_OPT_THREAD

"The setting of the thread safety option failed."

CAUSE: Unknown.

ACTION: Inform your System Administrator.

DM_SESSION_E_CHK_LDAP_NOSEARCHBASE

"The searchbase couldn't be determined. The authentication for user (%s) with user OS name (%s) failed";

DM_SESSION_E_CHK_LDAP_DOWN

"The LDAP server doesn't seem to run. The authentication for user (%s) with user OS name (%s) failed";

DM_SESSION_E_CHK_LDAP_SEARCH

"The search for user (%s) with user OS name (%s) in the LDAP server failed. The authentication failed";

DM_SESSION_E_CHK_LDAP_MULTIPLE_UID

"The search for user (%s) with user OS name (%s) found multiple entries in the LDAP server. The authentication failed";

DM_SESSION_E_CHK_LDAP_NOENTRY

"The search for user (%s) with user OS name (%s) didn't find any entries in the LDAP server. The authentication failed";

DM_SESSION_E_CHK_LDAP_BIND

"User (%s) with user OS name (%s) couldn't bind to the LDAP server. The authentication failed";

DM_SESSION_E_OPEN_TRANSACTION

"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.

DM_SESSION_E_AUTH_FAIL

"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.

PARAMETERS: The user name and docbase base.

DM_SESSION_E_LDAP_CHGPASS_USER

"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.

DM_SESSION_E_GETSVRCFG_FAIL

"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.

PARAMETERS: none.

DM_SESSION_E_CURSOR_ERROR

"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.

DM_SESSION_E_LOOKUP_DOCBASE_ID

"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.

PARAMETERS: %1 The docbase name.

DM_SESSION_E_TRANSACTION_ERROR

"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.

PARAMETERS: None.

DM_SESSION_E_UPGRADE_MAP_ERROR

"Please shutdown your client session and reconnect to the docbase."

CAUSE: Client side's "action proc map" is inconsisten with the one form server. The client session wasn't terminated during server upgrade causing this inconsistency.

ACTION: Close the client session and reconnect to the server.

DM_SESSION_E_CANT_ALLOCATE_NEXT_TICKET_BATCH

"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.

DM_SESSION_E_OBJECT_FILE_OPEN

"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.

PARAMETERS: The object stream file.

DM_SESSION_E_INVALID_APPLICATION_CODE

"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.

PARAMETERS: The value of application_code that is invalid.

DM_SESSION_E_AUTH_PLUGIN_LOAD_ERROR

"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."

PARAMETERS: The file path of the Authentication Plugin and the reason for the failure.

DM_SESSION_E_AUTH_PLUGIN_LOAD_CHARTRANS_ERROR

"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.

PARAMETERS: The plugin identifier, the codepage requested by the plugin and the codepage of the server.

DM_SESSION_E_AUTH_PLUGIN_LOAD_NO_ID_ERROR

"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.

PARAMETERS: The file path of the Authentication Plugin.

DM_SESSION_E_AUTH_PLUGIN_LOAD_INIT_ERROR

"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.

PARAMETERS: The file path of the Authentication Plugin and the error message returned by the plugin.

DM_SESSION_E_AUTH_PLUGIN_LOAD_EXCEPT_ERROR

"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.

PARAMETERS: The file path of the Authentication Plugin and the error message.

DM_SESSION_E_AUTH_PLUGIN_AUTH_FAIL

"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.

PARAMETERS: The user name, docbase base, plugin identifier and error message.

DM_SESSION_E_AUTH_PLUGIN_CHGPASS_FAIL

"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.

PARAMETERS: The plugin identifier and the error message returned by the plugin.

DM_SESSION_E_INVALID_LDAPCERTDIR

"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.

DM_SESSION_E_LDAPS_CLIENT_INIT

"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.

DM_SESSION_E_LDAPS_INIT

"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.

DM_SESSION_E_PLUGIN_LOAD_FAILED

"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.

PARAMETERS: Type of plugin, Error message

DM_SESSION_E_OUT_OF_TICKET

"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.

PARAMETERS: None.

DM_SESSION_E_CANNOT_DECODE

"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.

PARAMETERS: The first parameter tells whether this is a ticket/token while the second one is the ticket/token.

DM_SESSION_E_CANNOT_VERIFY_SIGNATURE

"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.

PARAMETERS: The first parameter tells whether this is a ticket/token while the second one is the ticket/token.

DM_SESSION_E_TICKET_EXPIRED

"The %s (%s) has expired."

CAUSE: The ticket/token has expired.

ACTION: Create a new ticket/token to use.

PARAMETERS: The first parameter tells whether this is a ticket/token while the second one is the ticket/token.

DM_SESSION_E_USED_TOKEN_ON_WRONG_MACHINE

"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.

PARAMETERS: 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.

DM_SESSION_E_INVALID_APPLICATION_ID

"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.

PARAMETERS: The first parameter is the application id while the second one is the access control token.

DM_SESSION_E_USE_TICKET_FOR_WRONG_USER

"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.

PARAMETERS: 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.

DM_SESSION_E_USED_LOCAL_TICKET_OTHER_DOCBASE

"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

PARAMETERS: The first one is the login ticket, the second one is the ticket originating docbase id, and the target docbase id.

DM_SESSION_E_SETUP_TICKET_ATTRIBUTES

"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.

PARAMETERS: The first one tells whether this is a ticket/token; the second one is the user name.

DM_SESSION_E_SIGN_TICKET

"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

PARAMETERS: The first one tells whether this is a ticket/token; the second one is the target user name.

DM_SESSION_E_CREATE_ENCODER

"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.

PARAMETERS: The first one tells whether this is a ticket/token; the second one is the user name.

DM_SESSION_E_OUT_MEMORY

"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.

PARAMETERS: The first parameter tells whether server is creating a ticket/token, and the second one is the user name.

DM_SESSION_E_INVALID_APPLICATION_TOKEN

"Invalid application token (%s).

CAUSE: Either no or invalid application token is provided.

ACTION: Make sure the application token is prefixed with "DM_TOKEN".

PARAMETERS: The parameter is the application token string.

DM_SESSION_E_RESET_TICKET_KEY

"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.

DM_SESSION_E_PASSWORD_REQUIRED

"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.

PARAMETERS: The name of the method that is missing the password argument.

DM_SESSION_E_NO_TICKET_KEY

"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.

PARAMETERS: the name of the docbase.

DM_SESSION_E_ENCODE_KEY_FAILED

"Encoding failed while exporting login ticket key from docbase (%s)."

CAUSE: Running out of memory.

ACTION: Be sure the system is not overloaded.

PARAMETERS: the name of the docbase.

DM_SESSION_E_DECODE_KEY_FAILED

"Decoding failed while importing login ticket key from docbase (%s)."

CAUSE: Running out of memory.

ACTION: Be sure the system is not overloaded.

PARAMETERS: the name of the docbase.

DM_SESSION_E_ENCRYPT_KEY_FAILED

"Encryption failed while exporting login ticket key from docbase (%s)."

CAUSE: Running out of memory.

ACTION: Be sure the system is not overloaded.

PARAMETERS: the name of the docbase.

DM_SESSION_E_DECRYPT_KEY_FAILED

"Decryption failed while importing login ticket key from docbase (%s)."

CAUSE: Running out of memory.

ACTION: Be sure the system is not overloaded.

PARAMETERS: the name of the docbase.

DM_SESSION_E_DOCBASE_NOT_TRUSTED

"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.

PARAMETERS: the name of the issuning docbase and the login ticket string.

DM_SESSION_E_REUSE_ONE_TIME_TICKET

"One-time login ticket (%s) has already been used."

CAUSE: Reuse a one-time login ticket.

ACTION: Generate a new ticket.

PARAMETERS: login ticket.

DM_SESSION_E_ONE_TIME_TICKET_SCOPE

"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.

PARAMETERS: login ticket.

DM_SESSION_E_SUPERUSER_RESTRICTED

"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.

PARAMETERS: The first parameter is the user name. The second is the docbase name.

DM_SESSION_E_TICKET_REVOKED

"The %s (%s) has been revoked."

CAUSE: The ticket/token has expired.

ACTION: Create a new ticket/token to use.

PARAMETERS: The first parameter tells whether this is a ticket/token while the second one is the ticket/token.

DM_SESSION_E_INVALID_GROUP_NAME

"Invalid group name (%s)."

CAUSE: The specified group is not valid in the target docbase.

ACTION: Specify a valid group name.

PARAMETERS: The parameter is the speified group name.

DM_SESSION_E_WRONG_GROUP

"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.

PARAMETERS: The first parameter is the token; the second is the group name; the third one is the user name.

DM_SESSION_E_NULL_TICKET_KEY

"A login ticket key must be provided."

CAUSE: Missing login ticket key argument for apply method IMPORT_TICKET_KEY

PARAMETERS: None

ACTION: Specify a login ticket key

DM_SESSION_E_INVALID_TICKET_FORMAT

"Invalid login ticket (%s). A login ticket must have prefix 'DM_TOCKET='.

CAUSE: The login ticket does not have prefix 'DM_TICKET='

PARAMETERS: None

ACTION: Specify a valid login ticket.

DM_SESSION_E_INLINE_AUTHENTICATION_FAILED

"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.

DM_SESSION_E_LDAP_BIND_FAILED

"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.

DM_SESSION_E_MACHINE_ONLY

"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.

DM_SESSION_E_LDAP_AUTH_FAILED

"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.

DM_SESSION_E_EXCEPTION_OCCURRED

"An exception occurred while %s."

CAUSE: An exception has occurred.

ACTION: Check the error message of the exception for more information.

PARAMETERS: The operation which caused the exception.

DM_SESSION_E_EMPTY_CHUNKED_OBJ_STR

"Either the chunked object string stored in session for the object '%s' is empty or the ID doesn't 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 doesn't 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.

DM_SESSION_E_CHUNKED_ID_NOT_MATCHED

"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 doesn't 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.

DM_SESSION_E_CHUNKED_ID_IS_NULL

"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 doesn't 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.

DM_SESSION_E_NON_EXIST_OBJ

"The object identified by %s does not exist."

DM_SESSION_E_NON_LOCAL_SERVER_RUNNING

"There are no running local content servers."

CAUSE: All local content servers are down.

ACTION: Make sure local content servers are up running.

DM_SESSION_E_NOID

"No id given for command %s."

CAUSE: An object id is required for this command.

ACTION: Correct the command to specify an object id.

PARAMETERS: The command as specified.

DM_SESSION_E_CLIENT_AUTHENTICATION_FAILURE

This issue has been seen when a Content Server's IP address or name has been changed.

CAUSE: Content Server IP address or name changed.

ACTION: Known issue: use EMC tool to fix issue. Tool can be downloaded from Powerlink: https://solutions.emc.com/emcsolutionview.asp?id=esg90932

DM_SESSION_F_EXEC_TOOMANY

"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).

DM_SESSION_F_EXEC_DUPDEFN

"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.

DM_SESSION_F_EXEC_TOOMANYARGS

"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).

DM_SESSION_F_EXEC_NO_DATATYPE

"No datatype specified in the argument description for %s (%d)."

CAUSE: The datatype (S, I, or B) must be specified.

ACTION: Specify the datatype.

PARAMETERS: The argument name and an internal code showing where the error was generated.

DM_SESSION_F_EXEC_BAD_DATATYPE

"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.

PARAMETERS: The invalid datatype specified.

DM_SESSION_F_TYPE_CONVERSION

"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

PARAMETERS: This is the name of the attribute being added.

DM_SESSION_F_AUDIT_CACHE_IS_FULL

"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).

DM_SESSION_F_INT1

"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.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox