6.6-dm_server
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 authentication attempts.
dm_misc: Miscellaneous Documentum Information 