Skip to content

Digitalization

Managing documents and working together in the digital workplace: Documentum, M-Files, Alfresco, SharePoint, Microsoft Teams and web platforms. Our consultants write about content management, collaboration, integration and the compliance questions that come with them.

Documentum Upgrade – Missing DARs after upgrade

As part of the same migration & upgrade project I talked about in previous blogs already (corrupt lockbox, duplicate objects & wrong target_server), I have seen a very annoying and, this time, absolutely not consistent behavior in some upgrade from Documentum 7.x to 16.x versions. The issue or rather the issues I had was that random DAR files were not… 

Documentum Upgrade – Switch from Lockbox to AEK key

As you probably know already, Documentum removed the support for RSA Libraries and RSA Lockbox starting with Documentum version 16.7. This means that if you are planning to upgrade to 16.7 or higher versions, you will first need to remove the lockbox from your installation and extract your AEK key from it before starting the upgrade process. To be completely… 

Documentum Upgrade – dm_DataDictionaryPublisher with wrong target server

As part of the same migration & upgrade project I talked about in previous blogs already (corrupt lockbox & duplicate objects), I have seen a strange but consistent behavior in each upgrade from Documentum 7.x to 16.x versions. During this process, just before the upgrade, a cloning is done to a staging environment, to keep the source untouched.   As… 

Documentum Upgrade – Duplicate JMS and ACS config objects

I have seen several times in the past duplicate JMS and/or ACS objects created by OpenText (and Dell/EMC before) installers. I opened several tickets with the OpenText Support over the past 4/5 years to try to get a reason and a fix (had the issue with all versions, 7.1, 7.2, 7.3, 16.4). The first few tickets (2 or 3, I… 

Documentum Upgrade – Corrupt Lockbox with CS 16.4

A couple months ago, I was working on an upgrade project from Documentum 7.x to 16.4. During this upgrade, I faced a few issues so I will try to write some blogs about all that in the coming weeks, starting today with an alleged “corrupt” Lockbox. This upgrade was part of a migration as well from Virtual Machines to Containers… 

Documentum – xPlore installer refuses to start because of ‘Multiple launches’

While working with xPlore, you might have faced before a message saying that an xPlore installer refused to start because it is not allowed to run multiple instances at the same time. This could have happened while running any installer: binaries, patches, dsearch, aso… However, when checking the processes, there is only one running and that’s the one you just… 

Documentum – DA fail to load if accessed after D2 because of ESAPI

In some specific cases, you might have faced an issue where Documentum Administrator is loading properly but then suddenly it’s not working anymore and all you did in between was accessing D2. I don’t remember seeing that before DA 16.x but maybe it’s just my memory that is playing me tricks! When this happen, you will see the usual pop-up… 

Documentum – D2 Folder structure import failure with wsctf browser plugin

Earlier today, I talked about the Export/Download that wasn’t working randomly. In the end, it was both linked to the wsctf browser plugin (that didn’t provide the necessary cookies in the download request) as well as the “loadBalancedContentServer” parameter (that was wrongly set to false). For the previous issue, setting the “loadBalancedContentServer” property to true was sufficient to solve it… 

Documentum – D2 Export/Download random failure with wsctf browser plugin

The D2 clients were, until recently (D2 version 16.4 included), working by default with the java plugin mode and therefore, many actions were using a JVM on the client workstation. This setting can be controlled/set in the “WEB-INF/classes/settings.properties” file of D2 applications (D2, D2-REST, D2-Smartview) and the default value was therefore “browser.plugin.mode = java“. Starting with D2 16.5, this was… 

Documentum – Rename of Lockbox on RCS/CFS

As you probably know, Documentum introduced the optional use of a Lockbox since version 7. It was done initially to contribute to the security of the AEK key which is one of the central components of a Content Server. Time showed that, well, it’s not so easy and since then, nothing much changed on the Lockbox layer. With the version… 

Documentum – dm_DMFilescan fails with invalid method_verb?

Recently in a project, one of the Documentum environments we were working on started showing failure on the execution of the dm_DMFilescan job and only this one. After a couple minutes of investigation, I quickly found the root cause of the issue which wasn’t very important, but I thought I would share it because of the implications it has. In…