ADTS 6.7 Uninstall Tips

I recently had to uninstall ADTS 6.7 after a failed upgrade from ADTS 6.0. If you upgrade Java from 32-bit to 64-bit as part of the ADTS 6.7 upgrade, you MUST revert to Java 32-bit before you can uninstall ADTS. Otherwise you get an error from the installer and it will not perform the uninstall.

After uninstalling, if you still have artifacts, you can try these steps:

  1. Delete any remaining services using the command “sc delete [service name]” (workaround for DTS-3587).
  2. Delete the following registry nodes (including all sub-nodes):
    1. HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun
      2.0\CtsAdminAgent
    2. HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\ContentDetectors
    3. HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\DFC Runtime Environment
    4. HKEY_LOCAL_MACHINE\SOFTWARE\wow6432node\Microsoft\Windows\CurrentVersion\Uninstall and remove all the entries for adlib
  3. Delete the folders C:\Program Files\Documentum and C:\Documentum (or the
    corresponding locations where the product was installed on your system).
Advertisements

About Scott
I have been implementing Documentum solutions since 1997. In 2005, I published a book about developing Documentum solutions for the Documentum Desktop Client (ISBN 0595339689). In 2010, I began this blog as a record of interesting and (hopefully) helpful bits of information related to Documentum, and as a creative outlet.

2 Responses to ADTS 6.7 Uninstall Tips

  1. Per Zester says:

    Hi Scott.
    Good points, thanks for posting.
    Downloading both 32 and 64b java versions is an integral part of my current ADTS install scheme, keeping both in \Program Files\Documentum\java with an _32 and _64 extension (ie. 1.6.0_27_32 and 1.6.0.27_64), in addition to the “real” 1.6.0_27 folder. Makes the switch quite easy when necessary.
    Cheers, Per

    Like

    • Scott says:

      I now do the same as well. However, I found that to uninstall ADTS, I have to completely uninstall Java 64 fist, and make the uninstaller ask me to identify the JRE to use. I then choose Java 32 and all works well. Strange, but it works.

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: