6.6-dm_note

DM_NOTE


ERROR: [DM_NOTE_F_INIT3]

SEVERITY: FATAL

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

CAUSE: Unknown.

ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative. $Id: dmobject.e,v 5.5 2002/06/20 00:19:48 ziff Exp $ dmObject class errors

PARAMS:

 

ERROR: [DM_NOTE_F_INIT1]

SEVERITY: FATAL

DESCRIPTION: The dmNote 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_NOTE_F_INIT2]

SEVERITY: FATAL

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

CAUSE: The version stamp that the dmNote 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.

PARAMS:

 

ERROR: [DM_NOTE_E_CANT_ADDNOTE2]

SEVERITY: ERROR

DESCRIPTION: SS Can not relate %s sysobject to %s note object.

CAUSE: Could not build a relation object to establish annote relationship.

ACTION: See the previous error messages.

PARAMS:

 

ERROR: [DM_NOTE_E_CANT_FETCH_INVALID_ID]

SEVERITY: ERROR

DESCRIPTION: D Cannot fetch a note – 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.

PARAMS:

 

ERROR: [DM_NOTE_E_CANT_ADDNOTE1]

SEVERITY: ERROR

DESCRIPTION: SS Can not relate %s sysobject to %s note object.

CAUSE: The sysobject and note object are part of the same version tree.

ACTION: None.

PARAMS:

 

ERROR: [DM_NOTE_E_CANT_CLEAN_UNUSED]

SEVERITY: ERROR

DESCRIPTION: S Could not complete the cleanup of unused note objects for %s docbase.

CAUSE: Previous operations have forced the server to stop the clean up operations.

ACTION: See the previous errors messages for the specific reasons.

PARAMS:

 

ERROR: [DM_NOTE_E_CANT_SAVE]

SEVERITY: ERROR

DESCRIPTION: S Cannot save %s sysobject.

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.

PARAMS:

 

ERROR: [DM_NOTE_E_ALREADY_ANNOTATED]

SEVERITY: ERROR

DESCRIPTION: SS The %s Sysobject is already annotated by %s note object.

CAUSE: The given sysobject is already related to the current note object.

ACTION: None.

PARAMS:

 

ERROR: [DM_NOTE_E_NO_ANNOTATION]

SEVERITY: ERROR

DESCRIPTION: SS No annotation relationship exists between %s note and %s sysobject.

CAUSE: No annotation relation exists between note object an given sysobject.

ACTION: None.

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: