IBM E027SLL-H - Tivoli Monitoring - PC, Troubleshooting Manual

Page: 106 / 310

Deploying an agent instance gives a KUICAR020E error
You get a KUICAR020E error after you have already successfully deployed a
multi-instance agent (such as a database agent) to a node, and then tried to deploy
another instance without providing any configuration properties (which is an
error).
KUICAR020E: The addSystem command did not complete because a deployment
error occurred. Refer to the following error returned from the server: The
monitoring server encountered an error while deploying the managed
system.The kuiras1.log file may provide more information about this error.
If you require further assistance resolving the error, contact IBM Software
Support.The agent received incorrect SQL.The CONTEXT column was not
specified and is a required parameter.
A correct message would tell you that required configuration properties were not
provided when using the -p|--property|--properties command line option. After
you have provided the required configuration properties using the
-p|--property|--properties command line option, the agent instance is properly
deployed.
Uninstallation is not available for Application Support on
Windows systems
Currently, there is not a workaround.
Problems installing directly from the .zip file
Instead of installing directly from the
.zip
file, extract the files from the
.zip
, and
then install from the
setup.exe
file.
Installation hangs or loops after presenting initial splash
screen
When installing IBM Tivoli Monitoring or IBM Tivoli Monitoring agents on
Windows systems, IBM Tivoli Monitoring installation should present a pop-up
requesting reboot if files are locked. However, there are times when the IBM Tivoli
Monitoring installation does not inform you of locked files. This can cause the IBM
Tivoli Monitoring installation to loop or hang. If you experience a delay longer
than fifteen minutes during an IBM Tivoli Monitoring Windows installation, cancel
the IBM Tivoli Monitoring installation processes and reboot the system.
Unable to discover systems within a specified IP range when
running the Startup Center from eclipse.exe
If you run the Startup Center from
eclipse.exe
, the distributed installation process
might not discover systems within the IP range that you specify. Instead, run the
Startup Center from
launchStartup.bat
. Note that this behavior is limited to
distributed installations of Windows systems, not of Linux or UNIX systems when
running the Startup Center from
launchStartup.sh
.
UNIX-based system installation problems and resolutions
Review the symptoms and possible resolutions to solve IBM Tivoli
Monitoringinstallation problems on Linux or UNIX system.
88
IBM Tivoli Monitoring: Troubleshooting Guide