Tuesday, September 30, 2008

How to fix DM_API_E_EXIST/DM_SYSOBJECT_E_CANT_FETCH_INVALID_ID in DAB for DCM doc

How to fix the following errors in DAB for DCM docapp? This can happen if the DCM docapp has been installed multiple times. [DM_API_E_EXIST]error: "Document/object specified by 4b0027ed800f26a9 does not exist." [DM_SYSOBJECT_E_CANT_FETCH_INVALID_ID]error: "Cannot fetch a sysobject - Invalid object ID 4b0027ed800f26a9"

Here are the step to clear out the DAB errors:


1. Clean up the dmcl cache on the DAB box, delete the content under these subfolders located in c:\documentum\dmcl and c:\documentum\[docbase_name]

2. Re-run the DAB to open up dcm docapp. Write down the object_id of the orphaned objects

3. Once you got the list of errored object ids, log into DA, navigate to

* /system/Application/dcm, select 'how all object on the filter' on the upper right hand side

* open up the dcm docapp(the virtual document one) by clicking on it

* then select all _ref_4Bxxxxx that got from step2.

* from the pull down menu, Document->Virutal Document->remove child from dcm docapp, repeat this for all the orphaned object ids

4. Checkin the dcm docapp as the same version.

Now you should be able to open DCM docapp from DAB without errors.

No comments: