HiCommand Dynamic Link Manager User's Guide (for Windows(R))

3.9.2 Notes on uninstalling HDLM

Note the following when uninstalling HDLM:

Depending on the environment, uninstalling HDLM might take some time. Do not terminate the uninstallation process while a progress bar for uninstallation is displayed. The following is an approximate calculation of the time required for uninstallation:
(1 x number-of-connected paths) seconds ^#

#

To uninstall HDLM, you must reconfigure the system to a single-path configuration. The time for doing this does not affect the time required for uninstallation. Since the uninstallation time depends on the value of the maximum number of paths that can be configured in your environment, use this value for an approximate calculation.

Before uninstalling HDLM 5.5 or later, make sure that no other application is using an HDLM management-target LU.

Uninstalling HDLM 05-00 or later also uninstalls Hitachi Network Objectplaza Trace Library (HNTRLib2). If, however, any program other than HDLM is using HNTRLib2, only HDLM will be uninstalled. Before uninstalling HNTRLib2, see the relevant manuals and documentation provided for each program to check whether any program is using it. Uninstall HNTRLib2 only when no programs, other than HDLM, are using it. For details on uninstalling HNTRLib2, see 3.9.4 Uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib2).

Uninstalling version of HDLM earlier than 05-00 does not uninstall Hitachi Network Objectplaza Trace Library (HNTRLib). Uninstall HNTRLib only when no programs, other than HDLM, are using it. See the relevant manuals and documentation provided for each program to check whether any program is using HNTRLib. For details on uninstalling HNTRLib, see 3.9.5 Uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib).

If you disabled the setting for automatically shortening file and folder names (8.3 format) when you installed HDLM, shortened names might not be generated in the Intel 32 folder in which the HDLM uninstallation program is stored. Therefore, attempts to uninstall HDLM will fail because the uninstallation program cannot be started. If shortened names are not generated in the Intel 32 folder, use the steps below to uninstall HDLM:

Use the registry editor to determine whether Intel 32 is included in the UninstallString value that is used when uninstalling HDLM. If Intel 32 is included, shortened names are not generated in the Intel 32 folder. UninstallString is included in the following registry keys:
For Windows 2000 Server and Windows Server 2003 (IA32):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DFF378A1-240E-11D5-8A43-0000E2382F13}
For Windows Server 2003 (IPF) and Windows Server 2003 (x64):
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{DFF378A1-240E-11D5-8A43-0000E2382F13}

If the UninstallString value includes Intel 32, then change Intel 32 to a folder name that contains 8 single-byte alphanumeric characters.
The following example shows the output before and after the change when Ctor.dll is installed in C:\Program Files\Common Files\InstallShield\Engine\6\Intel 32.
Before the change:
RunDll32 C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\Intel 32\Ctor.dll,LaunchSetup ""C:\Program Files\InstallShield Installation Information\{DFF378A1-240E-11D5-8A43-0000E2382F13}\Setup.exe"" -uninstdlm
After the change:
RunDll32 C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\folder-name-with-8-single-byte-alphanumeric-characters\Ctor.dll,LaunchSetup ""C:\Program Files\InstallShield Installation Information\{DFF378A1-240E-11D5-8A43-0000E2382F13}\Setup.exe"" -uninstdlm

Copy the Intel 32 folder to the folder described in step 2.

Uninstall HDLM according to the procedure described in 3.9.3 Uninstalling HDLM.

Delete the folder you copied in step 3.

When uninstalling HDLM on a host where a Device Manager Agent 5.0 or later is installed, do not execute any of the following commands of Device Manager Agent during uninstallation. Also, do not uninstall HDLM while executing any of the following Device Manager Agent commands:
hbsasrv, HiScan, hdvmagt_account, hdvmagt_schedule, hldutil, TIC

[Contents][Back][Next]

[Trademarks]