This is another blog posting an our Documentum upgrade project. This time, the following issue occured: the ActiveX could not be installed using the D2-Client. We had to access the D2-Config url to have it installed. For a normal user, this could not be used.

Analyzes

The workstation had the ActiveX for D2 3.0 installed, the version before the upgrade. Under C:WindowsDownloaded Program Files, we had:

ctx
ctx.ocx
D2UIHelper.dll

On my workstation where I could install (using D2-Config) the D2 3.1.1 ActiveX, I also had C:WindowsDownloaded Program FilesCONFLICT.* folders containing D2UIHelper.dll and ctx.inf

By checking the content of ctx.inf of this new cab I saw that we had the wrong version (see FileVersion) of the

[ctx.ocx]
file-win32-x86=thiscab
RegisterServer=yes
clsid={8C55AA13-D7D9-4539-8B20-78BC4A795681}
DestDir=
FileVersion=3,0,0,2

By checking the “ctx.cab” file in “D2-Client/install” and “D2-Config/install” on the application server I found that we did not have the same version, both ctx-cab had the same date and size but the digital signature was different:

D2-Config ctx-cab: &8206;17 &8206;September &8206;2013 10:56:11,
D2-Client: 19 &8206;April &8206;2013 17:03:08

Solution

To solve the issue I copied the ctx.cab” from “D2-Config/install” path to “D2-Client/install/”. Once this was done the activeX could be installed using the D2-Client url.

It was confirmed by the vendor that this is a bug in the delivered package