6.6-dm_inbox

DM_INBOX


ERROR: [DM_INBOX_F_PINIT9]

SEVERITY: FATAL

DESCRIPTION: SS Error renaming the table %s to %s

CAUSE: DB Error.

ACTION: check the RDBMS. Information Facility errors

PARAMS:

 

ERROR: [DM_INBOX_F_PINIT6]

SEVERITY: FATAL

DESCRIPTION: Could not access the registry data

CAUSE: DB Error

ACTION: Check the RDBMS

PARAMS:

 

ERROR: [DM_INBOX_F_INIT3]

SEVERITY: FATAL

DESCRIPTION: The type manager returned an error storing the dmi_queue_item type.

CAUSE: Unknown.

ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum Site representative.

PARAMS:

 

ERROR: [DM_INBOX_F_INIT6]

SEVERITY: FATAL

DESCRIPTION: I The dmi_queue_item type could not be converted %d.

CAUSE: Failure to convert dmi_queue_item cookie generator.

ACTION: Report this message to your Documentum Site representative.

PARAMS:

 

ERROR: [DM_INBOX_F_INIT2]

SEVERITY: FATAL

DESCRIPTION: II Version stamp %d was expected to be %d.

CAUSE: The version stamp that the dmi_queue_item object software expected was different than the actual version stamp in the database.

ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report this error, and other recent errors on your session, to your Documentum Site Representative.

PARAMS:

 

ERROR: [DM_INBOX_F_INT1]

SEVERITY: FATAL

DESCRIPTION: S The following database query %s could not be executed.

CAUSE: Inconsistency between the server and the sysobject type.

ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site Representative.

PARAMS:

 

ERROR: [DM_INBOX_F_INIT8]

SEVERITY: FATAL

DESCRIPTION: L The dmi_queue_item type could not be converted to version %d. The type initialization steps for the dmi_queue_item type failed because the type could not be upgraded to the current server version.

CAUSE: It is likely that a type/table alter command failed.

ACTION: Check for other related errors in the server log. Also check the RDBMS error logs for database errors. Report this message to your Documentum Site representative.

PARAMS: %1d – The version the server was attempting to upgrade to.

 

ERROR: [DM_INBOX_F_PINIT5]

SEVERITY: FATAL

DESCRIPTION: Could not create the new registry type

CAUSE: Unknown.

ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.

PARAMS:

 

ERROR: [DM_INBOX_F_INIT7]

SEVERITY: FATAL

DESCRIPTION: The dmi_queue_item type could not be altered.

CAUSE: Failure to alter dmi_queue_item type.

ACTION: Report this message to your Documentum Site representative.

PARAMS:

 

ERROR: [DM_INBOX_F_INIT1]

SEVERITY: FATAL

DESCRIPTION: The dmi_queue_item type was found in the database without a version stamp.

CAUSE: Unknown.

ACTION: Report this message and any parameters to your Documentum site representative.

PARAMS:

 

ERROR: [DM_INBOX_F_INIT4]

SEVERITY: FATAL

DESCRIPTION: S Unable to validate or create the event log location as specified using directory (%s). This error message is obsolete (see TroyO)

CAUSE: Failed to create the event log directory, during the initialization.

ACTION: Examine the docbase directory structure and look for possible security access problems.

PARAMS:

 

ERROR: [DM_INBOX_F_PINIT4]

SEVERITY: FATAL

DESCRIPTION: Could not remove the registry type

CAUSE: Unknown.

ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.

PARAMS:

 

ERROR: [DM_INBOX_F_PINIT7]

SEVERITY: FATAL

DESCRIPTION: Could not save the new registry entry

CAUSE: Unknown.

ACTION: check the RDBMS.

PARAMS:

 

ERROR: [DM_INBOX_F_PINIT8]

SEVERITY: FATAL

DESCRIPTION: Error creating the temporary registry table

CAUSE: DB Error.

ACTION: check the RDBMS.

PARAMS:

 

ERROR: [DM_INBOX_F_INIT5]

SEVERITY: FATAL

DESCRIPTION: SS Failure to create view %s: database error was: %s

CAUSE: Failure to create a database view for queues

ACTION: Report this message to your Documentum Site representative

PARAMS:

 

ERROR: [DM_INBOX_E_CANT_GETEVENTS1]

SEVERITY: ERROR

DESCRIPTION: S GetEvents failed because of the following: %s.

CAUSE: GetEvents failed because of the specified database failure.

ACTION: Correct the database operation or talk to your System Administrator.

PARAMS:

 

ERROR: [DM_INBOX_E_ONLY_SYSADMIN_SU]

SEVERITY: ERROR

DESCRIPTION: SS Only a sysadmin or super user can perform %s operation on %s inbox item.

CAUSE: An non-privileged user tried to destroy any inbox item or save another user inbox item.

ACTION: None.

PARAMS:

 

ERROR: [DM_INBOX_E_QUERY_EXECUTION_FAILURE]

SEVERITY: ERROR

DESCRIPTION: SS The dmi_queue_item object upgrade encountered an error while trying to execute the following query: %s. Database error was %s.

CAUSE: Query execution failed.

ACTION: Check the error message from the database in order to determine the cause of the query failure.

PARAMS: The first parameter is the query that was being executed. The second parameter is the resulting error from the database.

 

ERROR: [DM_INBOX_E_INIT4]

SEVERITY: ERROR

DESCRIPTION: SS Unable to validate or create the event log location as specified using directory (%s). Operating System Error: (%s)

CAUSE: Failed to create the event log directory, during the initialization.

ACTION: Examine the docbase directory structure and look for possible security access problems.

PARAMS:

 

ERROR: [DM_INBOX_E_NOEVENTS]

SEVERITY: ERROR

DESCRIPTION: An error was encountered initializing the server shared Events area which prevents registering inbox events to any session clients.

CAUSE: An attempt was made to use the events area (presumably to post an event to a client), but the server was unable to initialize the events subsystem. Previous error messages should indicate the specific reason for the failure.

ACTION: Have the sysadmin resolve the events problem and restart the server.

PARAMS:

 

ERROR: [DM_INBOX_E_CANT_GETINBOX]

SEVERITY: ERROR

DESCRIPTION: S GET_INBOX failed because of the following: %s.

CAUSE: GET_INBOX failed because of the specified database failure.

ACTION: Correct the database operation or talk to your System Administrator.

PARAMS:

 

ERROR: [DM_INBOX_E_EVENT_FILE_CREATE]

SEVERITY: ERROR

DESCRIPTION: SS Error creating the event notification file (%s) used to indicate to a session that an inbox event has occurred. Operating system error (%s).

CAUSE: The file used for event notification could not be created.

ACTION: Check for existence of the events location directory and for check permissions in it.

PARAMS:

 

ERROR: [DM_INBOX_E_CANT_FIND_OBJ]

SEVERITY: ERROR

DESCRIPTION: SS Could not find the object to queue the event %s for id %s

CAUSE: The object identified by the id could not be found for that event.

ACTION: Check the id to make sure that it is a valid sysobject.

PARAMS:

 

ERROR: [DM_INBOX_W_EVENT_LOC]

SEVERITY: WARNING

DESCRIPTION: SS Unable to validate or create the event log location as specified using directory (%s). Operating System Error: (%s)

CAUSE: Failed to create the event log directory, during the initialization.

ACTION: Examine the docbase directory structure and look for possible security access problems.

PARAMS:

 

ERROR: [DM_INBOX_W_NO_ROWS]

SEVERITY: WARNING

DESCRIPTION: No results were returned from the GetEvents statement.

CAUSE: Your GetEvents method has returned an empty result set.

ACTION: No action is required.

PARAMS:

 

ERROR: [DM_INBOX_W_EVENT_NOLOC]

SEVERITY: WARNING

DESCRIPTION: S The server events location is currently undefined. There is no location object for the events area (%s).

CAUSE: An attempt was made to use the events area (presumably to post an event to a client), but the server was unable to initialize the events subsystem due to there being no definition for the server events location. There should be a dm_location object in the docbase with an object_name which matches the value of the server config object events_location attribute. Until this location object is defined events cannot be used.

ACTION: Have the sysadmin define an events location.

PARAMS:

 

ERROR: [DM_INBOX_W_PINIT10]

SEVERITY: WARNING

DESCRIPTION: S Error dropping the table %s

CAUSE: DB Error.

ACTION: manually remove table

PARAMS:

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: