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

ADTS Start/Stop Order and Process Owners

A few years ago I posted an article detailing the correct process owners for each of the ADTS 6.0 processes .  Since then, I have had the opportunity(?) to work with ADTS 6.7 a little, and noticed that the process names and owners have changed a bit. Following are the processes and their owners from my successful ADTS 6.7 installation.

Service Startup Type Logon User
Adlib Exponent Connector Manual Docbase Install Owner
Adlib Exponent Manager Automatic Docbase Install Owner
Adlib FMR Automatic Local System
Adlib Process Manager Automatic Local System
Documentum Content Transformation Monitor Service Automatic Local System
Documentum Content Transformation Service Automatic Docbase Install Owner
Documentum CTS Admin Agent Automatic Local System

I learned the hard way that once ADTS is installed and running, do not logon to the ADTS server as the install owner.  When you logoff, it will terminate the AdLib Express session and ADTS will stop working.  If you need to view logs or do other maintenance on the ADTS server, logon using a local admin account.

The order to safely stop ADTS services:

  • Documentum Content Transformation Service (this will stop Documentum Content Transformation Monitor Service also)
  • Documentum CTS Admin Agent
  • Adlib Process Manager
  • Adlib FMR
  • Adlib Exponent Manager
  • Adlib Exponent Connector

The order to correctly start ADTS services:

  • Adlib Process Manager (This will start the Adlib Exponent Connector and a few other Adlib services like AdLib Express and the AdLib RDP session — watch the Task Manager to see these.)
  • Adlib FMR
  • Adlib Exponent Manager
  • Documentum Content Transformation Monitor Service (this will start Documentum Content Transformation Service also)
  • Documentum CTS Admin Agent

HTA Monitor Update

I updated the HTA monitor code to include ADTS and xPlore processes.  I also zipped the source code to make it easier to download.  Here is the link.

See original post here.

%d bloggers like this: