nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error: Unable to get folder structure if retention policy is applied

Naik_Sheetal

Hi,

I am trying to export documents from Captiva using documentum advanced export module to the DCTM repository to an existing folder. If the folder has retention policy applied then it fails to get access these folder errors out as unable to find the the object. It also tries to create the object but fails with error " Unable to cast object of type 'java.lang.Object' to type 'com.documentum.fc.client.IDfPersistentObject'." But if the folder does not have any retention policies applied the export is success. Any help would be appreciated.

Thanks

Find more posts tagged with

Comments

DCTM_Guru

What version of Captiva are you running? Not sure if this is a bug, you can export it to folder structure that doesnt have retention and then write a Documentum job to move them to folder structure that has retention appliecd to it.

Naik_Sheetal

We are using version 6.5.

I am new to Documentum, can you explain me about documentum job?

DCTM_Guru

Job is like a cron job or windows service that you can tell to run at specific interval. Its custom code, but there are plenty of examples on Developer Network.

DCTM_Guru

Also, did you specify in the dfc.properties file that Captiva is privleged client? See RPS documentation on this parameter setting.

Naik_Sheetal

I have added only the connection broker info in dfc.properties.

In DA, I added the Captiva Client (the host where DCTM export module is running) as a priviledged client.

DCTM_Guru

Does the user that you are using for Captiva Client belong to one of the RPS roles? You may need to be a member of one of the RPS roles in order to do this.

Naik_Sheetal

Thanks for your responses.

Still I am having the same issue, the user is having the contributor role and retention manager role.

The error I get is while setting the definition of a step, while browsing the location of the retained folder is "Unable to get the folder structure. But I can browse other folders.

DCTM_Guru

Submit a ticket to EMC Support.

Naik_Sheetal

Thanks for your reply, I will submit a ticket.

Venkata_Chalapathi_Banala

Hi Naik Sheetal,

I am also facing the same problem while exporting documents from Captiva 6.5 Documentum Advanced Export module to DCTM Repository to the retention policy applied folder. If you have got solution to this, please share it with us.

Thanks,

Venkat

community

Hi,

DcmRecords.jar which is coming from DFC installation is differ from the jar which is in RPSA, this is may be documentum bug, they are not updated this.

Resolution:

1). Stop InputAccel DCTM Export Service

2). Copy DmcRecords.jar(154 KB) from rpsa (rpsa.war\WEB-INF\lib) and replaced with DmcRecords.jar(44 KB) under Captiva server(C:\Program Files\Documentum\Shared).

3). Start InputAccel DCTM Export Service

Naik_Sheetal

Thanks for your reply, I followed this steps but still getting the same error.

community

Hi,

To narrow down whether the issue is from Captiva Advanced Documentum Export itself or DFC the Captiva export is using, could you please check whether the issue can be reproducible with Documentum iapi32.exe by following steps?

1. Create a sample txt file (using like Notepad) and name it RetentionTest.txt, then try to export it to the folder with retention policy via Captiva export. If fails, place RetentionTest.txt on C:\ on Captiva export machine, then try below ;

2. Place copy of iapi32.exe and dmcl.dll from the Content Server to where dfc.jar is on the Captiva export machine

3. From Captiva export machine, open DOS window and navigate to directory where you copied of iapi32.exe and dmcl.dll into, then enter iapi32.exe > enter > enter docbase name > enter > user name > enter > password > - use the same docbase name, user name and password that you run Captiva export to

4. After iapi32.exe got connected to the docbase, try following commands to move the content of RetentionTest.txt to a document named RetentionTest in the folder with retention policy

API> create,c,dm_document
API> set,c,l,object_name
SET> RetentionTest
API> save,c,l
API> link,c,l,/JIL/Company/Branch/Dept
API> save,c,l
API> setfile,c,l,C:\RetentionTest.txt,crtext
API> save,c,l

If above fails, then details will be displayed and problem due to dfc,

If it's success than problem with Advanced export. (DocumentumAdvancedExport 6.5 patch available install and try)