Cisco Cisco Workload Automation 6.3 Installation Guide

Page of 194
191
Cisco Systems, Inc.
www.cisco.com
16
Troubleshooting
Many problems with the installation and operation of the Cisco Workload Automation can be eliminated by strictly 
following the hardware and software specifications recommended by Cisco. Due to the variance between the 
environment of one customer system from another customer’s system, many different issues may still occur during 
installation of CWA components.
Two CWA documents can be of great assistance as you troubleshoot your CWA system:
Cisco Workload Automation Essential Knowledge Guide—Provides guidance for working with Cisco’s Technical 
Assistance Center (TAC), key tips for logging and troubleshooting, basic configuration information, how to start and 
stop all components, and how to perform many of the basic processes.
Cisco Workload Automation Product Compatibility Guide—Provides a complete list of supported platforms, 
hardware, and software with version information for each.
You can access these and other CWA documents at:
While all of the possible procedures for troubleshooting installation issues cannot be covered, some of the more common 
ones are listed in this chapter. 
Java Path Mismatch 
The "Adapter Host has gone down" message covers many cases.
One case which is not obvious from the error message is that the system cannot find the JAVA path (or similar).
By default, the system will try to reconnect the Adapter Host every 5 seconds.
Access Violation During Installation
Installation of CWA components requires access to COM objects. The installation cannot proceed without access to COM 
objects. If you get an access violation during installation of any CWA component, verify that the user doing the installation 
has access to COM objects and if necessary enable COM object access.
CWA Fails to Install a Copy of msvcr71.dll 
Occasionally, CWA fails to install a copy of msvcr71.dll (Windows 2003) or msvcr100.dll (Windows 2008) in the same 
directory as saMaster.exe, instead it depends on this .dll to already be installed in the System32 directory by optional 
components which are not found in a fresh, fully patched, install of Windows.