; $Id: dmsrvcnf.e,v 5.8 2002/11/21 01:30:36 zfan Exp $
;
; dmServerConfig class errors
;
.facility DM_SCNFG
;
.severity WARNING
;
QRY_CACHE_DIR "An error has occurred creating or validating your query cache path. Query caching is disabled for your session."
;
; CAUSE: This is an unexpected error. The types of things that could cause it include:
; 1) Your client local area path is invalid.
; 2) There was an error creating or accessing the qrycache directory.
; 3) There was an error creating or accessing the <hostname> directory,
; the <docbase id> directory, or the <username> directory.
; 4) There was an error while accessing an existing query cache map file.
;
; ACTION: Check your client local area. Look for the qrycache path and the <hostname>,
; <docbase id>, and <username> paths for your host, docbase, and user name.
; Make sure they all have accessible permissions. Check the cache.map file,
; if it exists. Consult your System Administrator. You may have to delete
; the directory structure up to the client local area to get the query cache
; to reinitialize. If the problem is with the client local area itself, see
; your System Administrator.
;
QRY_CACHE_QRY "An unexpected internal error has occurred while initializing your query cache. Query caching is disabled for your session."
;
; CAUSE: An internally generated query required to validate your query cache has
; failed to run properly. There should be additional error messages
; that indicate the nature of that failure.
; ACTION: Gather all error messages associated with this failure and consult your
; Documentum System Administrator. There may be a problem with the
; dm_docbase_config in your docbase. You could also ignore this error;
; query caching is turned off for your session.
;
QRY_CACHE_USER S "Query caching is disabled for your session. User %s is using your cache directory."
;
; CAUSE: To create the directory name for your cache, your Documentum user name is
; turned into a string of length eight, followed by a dot, followed by a
; string of length three. Another user's user name has be decomposed into
; the same directory name. You cannot share the same cache. Query caching
; is disabled for your session.
; ACTION: Change your client local area to a directory that the other user (named in
; the message) will not use.
;
;
.severity ERROR
CANT_FIND S "Cannot find %s server_config object."
;
;CAUSE: Could not find the server_config object with the specified name.
;ACTION: This is probably caused by invalid name.
;
CANT_CREATE "Cannot create a server_config object."
;
;CAUSE: Could not create a server_config object. Most likely
; the server is out of memory.
;ACTION: Restart your session and talk to your sysadmin.
;
CANT_FETCH_INVALID_ID D "Cannot fetch a server_config - Invalid object ID %s"
;
;CAUSE: Could not fetch an object with the given id.
;ACTION: This is probably caused by a bad ID. Or, possibly, a connection
; to the Documentum server could not be established.
;
CANT_SAVE S "Cannot save %s server_config."
;
;CAUSE: One or more operations has failed during this save.
; Consult the following error message(s) for more help.
;ACTION: Try again after fixing previous problems.
;
INVALID_SESSC I "Concurrent session count %d must be positive."
;
;CAUSE: User tried to specify an invalid concurrent session count.
;ACTION: Specify a positive number.
;
NO_CONFIG_NAME "No configuration name is specified."
;
;CAUSE: User has not specified a configuration object.
;ACTION: Specify a unique name.
;
NEED_PRIV_FOR_CHANGE SS "The current user (%s) needs to have superuser or sysadmin privilege to save or destroy %s server_config object."
;
;CAUSE: Must have Superuser or SysAdmin privilege to save/destroy server_config objects.
;ACTION: Consult your system administrator.
;
NEED_PRIV_FOR_REINIT S "The current user (%s) needs to have superuser or sysadmin privilege to reinit the server."
;
;CAUSE: Must have Superuser or SysAdmin privilege to reinit server.
;ACTION: Consult your system administrator.
;
NEED_PRIV_FOR_GETLOGIN SS "The current user (%s) needs to have superuser privilege to login as user %s."
;
;CAUSE: Must have Superuser privilege to issue "getlogin,session,other_user".
;ACTION: Consult your system administrator.
;
NEED_VALID_USER_FOR_GETLOGIN S "The user (%s) needs to be a valid user."
;
;
;CAUSE: Must have Superuser privilege to issue "getlogin,session,other_user".
;ACTION: Consult your system administrator.
;
INVALID_DEFAULT_ACL IS "Invalid value %d set for default_acl of the serverconfig '%s'."
;
; CAUSE: Invalid value is set to default_acl.
; ACTION: Provide a valid value (FOLDER: 1, TYPE: 2, USER: 3)
;
QRY_CACHE_FILE_NAME "A filename-generation error has occurred caching results of a cached query."
;
; CAUSE: A filename could not be generated to hold your cached query
; results. This is an unlikely situation that could be caused
; by caching too many queries in a session.
; ACTION: If you are an end user, you may be running an application that
; is caching too many queries. Try turning caching off for your
; session in your dmcl.ini. If you are an application programmer
; check all the queries in your application and make sure that
; the ones your are caching are good candidates for caching.
; Most queries should be run with readquery.
;
QRY_CACHE_FILE "A file error has occurred caching results of a cached query."
;
; CAUSE: The file created to hold your cached query results could not
; be opened.
; ACTION: This is an unexpected error that may be cause by a file system
; problem. Report this problem to your Documentum System
; Administrator. Meanwhile, to get past the immediate problem,
; turn caching off for your session in your dmcl.ini.
;
;
QRY_CACHE_FILE_WRITE "A file write error has occurred caching results of a cached query."
;
; CAUSE: A failure has occurred while writing your cached query results
; to the cache file.
; ACTION: The probable cause is that your file system is full. You may
; be caching too many query results, or very large result sets.
; Try flushing your cache and starting over, or turn off
; caching in your dmcl.ini. Make sure all the queries that are
; being cached are appropriate candidates for caching.
;
;
INCONSISTENT_TARGET_ATTRS "The value count of projection attributes (projection_targets,projection_proxval,projection_notes,projection_enable) are not consistent."
;
; CAUSE: Fail to maintain same value count while editing these attributes.
; ACTION: Add or remove attribute values to make them consistent.
;
DUPLICATED_TARGET_VALUES SI "The projection attributes contain duplicated target '%s' with port '%d'."
;
; CAUSE: Fail to maintain unique target value while editing these attributes.
; ACTION: Remove attribute values to make target unique.
;
INVALID_PROXVAL II "The projection_proxval[%d] contains invalid value %d."
;
; CAUSE: Invalid value is set for proximitity.
; ACTION: Reset proxval value to the valid value.
;
INVALID_PORT II "The projection_port[%d] contains invalid value %d."
;
; CAUSE: Invalid value is set for port.
; ACTION: Reset port value to the valid value.
;
INCR_LENGTH_NONEXISTANT_ATTR L "While upgrading to version %d: Failed while trying to increase the length of a non-existant attribute in dm_server_config."
; CAUSE: Attributes for which the length is being increased should already be in existence before they are lengthened. A previous upgrade step may have failed.
; ACTION: Contact your Documentum Site Representative.
;
INCR_LENGTH_TOO_LONG L "While upgrading to version %d: Failed when trying to increase the length of a dm_server_config attribute because the attribute is too long."
; CAUSE: The IncreaseLength function was called on an attribute which was too long. A previous upgrade step may have failed.
; ACTION: Contact your Documentum Site Representative.
;
INCR_LENGTH_FAILED L "While upgrading to version %d: The upgrade failed on widening dm_server_config's attribute lengths."
; CAUSE: The database server may have problems widening the column length
; ACTION: Check database server log or use sql script(under dba) to upgrade.
;
INCONSISTENT_APP_SERVER_ATTRS "The value count of app_server attributes (app_server_name, app_server_uri) is not consistent."
;
; CAUSE: Failed to maintain same value count while editing these attributes.
; ACTION: Add or remove attribute values to make them consistent.
;
DUPLICATED_APP_SERVER_NAME S "The repeating attribute app_server_name contains a duplicate for '%s'."
;
; CAUSE: Failed to maintain unique app_server_name values while editing these attributes.
; ACTION: Remove attribute values to make app_server_name unique.
;
NEED_PRIV_FOR_LOCK SD "The current user (%s) needs to have sysadmin privilege to lock a non-sysobject ('%s')."
;
;CAUSE: Must have SysAdmin privilege to lock a non-sysobject.
;ACTION: Consult your system administrator.
;
NEED_WRITE_PERMIT_FOR_LOCK SD "The current user (%s) needs to have WRITE permit to lock the sysobject ('%s')."
;
;CAUSE: Must have WRITE permit to lock the sysobject if the user doesn't have
; SysAdmin privilege.
;ACTION: Consult your system administrator. Note that starting from 5.3 SP1, this error
; is replaced with NEED_VERSION_PERMIT_FOR_LOCK.
;
INVALID_SECURE_MODE S "Invalid value (%s) specified for secure_connect_mode. Valid values are 'native', 'secure', and 'dual'."
;
; CAUSE: Specified value for secure_connect_mode is invalid. Valid values are 'native', 'secure', and 'dual'.
; ACTION: Reset secure_connect_mode to one of the valid values.
; PARAMETER: User specified value for attribute secute_connect_mode.
;
MAX_WF_THREADS II "Invalid value (%d) is specified for wf_agent_worker_threads. It must be between 1 and %d."
;
; CAUSE: Specified value for wf_agent_worker_threads is invalid. It must be between 0 and 1000
; ACTION: Reset wf_agent_worker_threads to a value between 0 and 1000.
; PARAMETER: User specified value for attribute wf_agent_worker_threads and its maximum.
;
TICKET_TIMEOUT_RANGE III "Invalid value (%d) is specified for login_ticket_timeout. It must be between %d and %d."
; CAUSE: Specified value for login_ticket_timeout is is out of range [1, max_login_ticket_timeout].
; ACTION: Specify a value in the allowed range.
; PARAMETER: User specified value for attribute login_ticket_time, the minimum value allowed for login_ticket_timeout, and the current value of max_login_ticket_timeout.
;
MAX_TICKET_TIMEOUT_RANGE II "Invalid value (%d) for max_login_ticket_timeout. It must be at least (%d)."
; CAUSE: Specified value for max_login_ticket_timeout is less than 1.
; ACTION: Specify a value greater than 1.
; PARAMETER: User specified value for attribute max_login_ticket_time and the minimum value allowed for max_login_ticket_timeout.
;
NEED_PRIV_FOR_GETTOKEN "Superuser privilege is required to execute command gettoken"
; CAUSE: Must have Superuser privilege to issue "gettoken,session,...".
; ACTION: try as a super-user.
; PARAMETER: None
;
NEED_VALID_USER_FOR_GETTOKEN S "The user (%s) must be a valid user or group."
; CAUSE: A valid user or group must be specified. If a group, it must be prefixed with "DM_GROUP=".
; ACTION: Make sure that the specified user or group is valid in the docbase. If a group is specified, make sure it is prefixed with "DM_GROUP="
;
MAX_TICKET_TIMEOUT_TOO_SMALL II "Value (%d) specififed for max_login_ticket_time is smaller than login_ticket_timeout (%d). Please first reset login_ticket_timeout to a smaller value and then try again."
; CAUSE: this message is displayed when sysadmin tries to set max_login_ticket_timeout to a value that is smaller than the value of login_ticket_timeout.
; PARAMETER: The current value of login_ticket_timeout and the value specified for max_login_ticket_timeout.
; ACTION: Set login_ticket_timeout to a smaller value first and try again.
;
NEED_VERSION_PERMIT_FOR_LOCK SD "The current user (%s) needs to have VERSION permit to lock the sysobject ('%s')."
;
;CAUSE: Must have VERSION permit to lock the sysobject if the user doesn't have
; SysAdmin privilege.
;ACTION: Consult your system administrator.
;
;
INVALID_SRV_CONFIG SS "You have specified an invalid server config (%s) for the %s command."
;
;CAUSE: If you specify a server config object name in the command, it must be an existing one.
;ACTION: You must specify an existing server config object name.
;
.severity FATAL
INIT1 "The server_config type was found in the database without a version stamp."
;CAUSE: Unknown.
;ACTION: Report this message and any parameters to your Documentum site
; representative.
;
INIT2 II "Version stamp %d was expected to be %d."
;CAUSE: The version stamp that the dmServer_Config object software expected was
; different from the actual version stamp in the database.
;ACTION: You must upgrade your DocuServer database to conform to the
; software that you are running. If your software and data are
; consistent, then report a bug.
; Also, Report this message and any parameters to your Documentum site
; representative.
INIT3 "The type manager returned an error storing the server_config type."
;CAUSE: Unknown.
;ACTION: Look at the error logged by the type manager.
; Report this message and any parameters to your Documentum site
; representative.
INT1 S "The following database query %s could not be executed."
;
;CAUSE: Inconsistency between the server and the server_config type.
;ACTION: Look at the error logged by the database.
; Report this message and any parameters to your Documentum Site
; Representative.
;
INIT4 "The type manager returned an error converting the dm_server_config type."
;CAUSE: Unknown.
;ACTION: Look at the error message logged by the type manager.
; Report this message and any parameters to your Documentum Site
; Representative.
SYBASE_INIT1 I "In-place conversion is not supported for the Sybase database with version stamp %d."
;CAUSE: For Sybase database, in-place conversion is only supported for version 2.0.5 or upper
;ACTION: You need to use dump and load method to upgrade your database.
;
;
TYPE_CONVERSION I "Failed to convert type dm_serverconfig to version %d."
;
; CAUSE: Type conversion failed.
; ACTION: Report the problem.
;
;