Windows Agent service does not start when Wise Package Studio Pro 4.62 is installed
|Article:TECH108889|||||Created: 2004-01-02|||||Updated: 2004-01-12|||||Article URL http://www.symantec.com/docs/TECH108889|
After installing Wise Package Studio Pro in client-server mode from a network installation on a file share, the CCM agent fails to load on the next restart with the keyboard and mouse locked. The situation does usually not happen on later restarts.
Wise Package Studio Pro installs a registry entry:
The HookDLL.DLL file is part of the SmartMonitor feature of Wise Package Studio. SmartMonitor is a form of application capture which does not use snapshots, but rather tries to determine which files to include in an installation package by recording which resources an application accesses while it is run.
HookDLL.DLL uses an .INI file, wisehook.ini, to determine what other DLL files to load. In most cases the .INI file is similar to the following content:
Edit the INI file associated with wisehook.ini, removing the paths to the DLL files on the server share, or temporarily disable the mentioned registry key . This allows the ON Command CCM Agent to start. Once the agent is started, you can read add the values to the registry or the INI file without any ill effects.
A workaround for this issue is to install the Wise Package Studio client with an MSI transform applied to the installation package. The transform should remove the Wisehook.ini file from the installation.
Article URL http://www.symantec.com/docs/TECH108889