D2 com.documentum.fc.common.DfException: [DM_EVENT_E_INVALID_ID]error: "Invalid handle error

Hello,

We are getting below error when we try to open document from D2. It is opening fine from DA.

Kindly suggest if there is any solution to fix this error.

2020-10-27 15:43:30 [ERROR] [https-openssl-nio-8443-exec-59] - c.e.d.d.a.InjectSessionAspect[ ] : {}

com.documentum.fc.common.DfException: [DM_EVENT_E_INVALID_ID]error: "Invalid handle (0901e6118001b282) for system event dm_getfile."

at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(DocbaseExceptionMapper.java:57)

at com.documentum.fc.client.impl.connection.docbase.MessageEntry.getException(MessageEntry.java:39)

at com.documentum.fc.client.impl.connection.docbase.DocbaseMessageManager.getException(DocbaseMessageManager.java:137)

at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.checkForMessages(NetwiseDocbaseRpcClient.java:329)

at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.applyForInt(NetwiseDocbaseRpcClient.java:600)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection$6.evaluate(DocbaseConnection.java:1343)

2020-10-27 15:43:30 [WARN ] [https-openssl-nio-8443-exec-59] - c.e.d.d.s.d.Download[ ] : error in downloading file:com.emc.d2fs.exceptions.D2fsException: [DM_EVENT_E_INVALID_ID]error: "Invalid handle (0901e6118001b282) for system event dm_getfile."

2020-10-27 15:43:30 [ERROR] [https-openssl-nio-8443-exec-59] - c.e.d.d.s.D2HttpServlet[ ] : Download failed

com.emc.d2fs.exceptions.D2fsException: [DM_EVENT_E_INVALID_ID]error: "Invalid handle (0901e6118001b282) for system event dm_getfile."

at com.emc.d2fs.dctm.aspects.InjectSessionAspect.exceptionHandling(InjectSessionAspect.java:363)

Find more posts tagged with

Documentum

Comments

DCTM_Guru

What kind of object is this "0901e6118001b282"? Use dump API in DA to find out.

MaheshNalapaneni

This is I_chronicle_id of the document we are trying to open. This version (all In Progress state documents) was deleted from system when document was promoted to Approved state.

DCTM_Guru

Your comments seem to be conflicting. How can you view the version 1.0 (which i_chronicle_id is pointing to) in DA if it was deleted? If it was really deleted, then you should not be referencing that ID in D2.

MaheshNalapaneni

Apologies for the confusion, please find below details on the issue.
User has created multiple minor versions (0.1,0.2, ... 0.7) on a document and promoted it to Major version.
When a Document is promoted to Major version, we have configured to delete all non current Minor versions and current Minor version is promoted to Major version. In this case, it deleted 0.1..0.6 and 0.7 was made to 1.0.
We are getting above error when we are trying to open 1.0 version of the document from D2. It is giving "Invalid handle (0901e6118001b282) for system event dm_getfile" referring to chronicle id.
We are getting same error when we execute getfile command from API.
But document is opening fine when we view it from DA.

DCTM_Guru

Are you using the same user account in D2 and DA when validating this scenario? Assuming the permissions on v1.0 are the same for major version, then there shouldnt be any reason that you cant see previous version in D2 as you can see in DA.

MaheshNalapaneni

Thank you Jhonny.
I have tried with same user in DA to open the current (Major) version of the document, getting the same error though user is having write permission on the document.
It is working with Installation owner account from DA but we have disabled access to D2 client for installation owner.
Document is not opening with any other user account though they have permissions on the document.

DCTM_Guru

What error message are you getting in DA? DA doesnt use D2fs, so you should be getting different message.

MaheshNalapaneni

I am getting this error in DA. Could not download content file for document 'RIMS-IMP-0000051-1.0 '. : "Invalid handle (0901e6118001b282) for system event dm_getfile." Object ID (0901e61180040abc) of document I am trying to open is different.

Hicham Bahi

Normally when you delete the root of the version tree, Documentum doesn't really delete it but sets the i_is_deleted attribute to True. This object should not show up in queries but you should still be able to fetch it when you are superuser (e.g. fetch,c,0901e6118001b282). I suspect that in your case, the object is gone and the reason you see the error is that you have enabled auditing on dm_getfile (which tries to get the chronicle ID to store it in the audit record).

Can you run the ConsistencyChecker job to see if it reports this object (under "Checking for sysobjects with non-existent i_chronicle_id")? If it does, do you remember how your deleted that object?

MaheshNalapaneni

Hello Bacham,

Yes, you are correct. it is showing in ConsistencyChecker job report.
This was deleted by system(lifecycle) when the document was promoted to major version.

How can we fix this?.

Hicham Bahi

I see no other way than fiddling with the database and inserting the missing records. Is it the only object reported ? If not, then there's probably something wrong in the code which performs the promote. Is this a D2 lifecycle and do you have custom code behind it?

MaheshNalapaneni

This is the only object missing in the repository. We are not using custom code for deletion, it is done by Lifecycle only.

Hicham Bahi

So perhaps some admin destroyed the object. Or perhaps it's due to a Content Server bug. You may want to log a support ticket to ask for the best way to rectify the issue. In my opinion, the cleanest option is to copy the document and then destroy the original document (all versions included). Of course you will lose audit trail information. Otherwise, recreate the missing records directly in the database but you have to know what you are doing.