Table of Contents
Advertisement
If only a single hub monitoring server is available during an agent's application
support installation and the hub is stopped, the mirror hub is started, the
application support installation to the new (mirror) hub is initiated. In such a
scenario, it is possible to get no predefined managed system group for a product.
To verify that the managed system group is present, run tacmd listsystemlist at
the command line. If the managed system group is not listed, recycle the
monitoring agent.
Self-describing agent installation completes successfully but
sqlStatus 79 error messages are logged
After the product is successfully installed, the self-describing agent mechanism
tries to delete all prior versions of the installation record for the same product. If
there is no prior version of the installation record, the deletion attempt returns a
code of 79.
As an example, consider the following error messages that were logged even
though the installation was successful. Such messages can be disregarded.
(0002-E9A166E3:kfasdwlm.c,1961,"KFASDM_RequestMgr") Self-Describing Install
my "05100173".
(003-E9A166E3:kfasdsrm.c,1531,"KFASDM_DeleteTapplpropLocal") Open request for
status <79> product <CP> product version <05100173>
(0004-E9A166E3:kfasdwlm.c,1976,"KFASDM_RequestMgr") KFASDM_DeleteTapplpropLocal
Self-describing agent overwrites most recent manually installed
z/OS monitoring server support
An older version of a self-describing agent might overwrite the most recent version
of Tivoli Enterprise Monitoring Server application support that is manually
installed on a z/OS monitoring server.
The most recent version of the monitoring server application support is not
installed through the self-describing mechanism.
To resolve this issue, disable self-describing mode on the agent that has the older
application support and add the most recent version of application support to the
z/OS monitoring server or use the self-describing mechanism to install the new
monitoring server support across your environment. See "Adding application
support to a monitoring server on z/OS" in the Configuring IBM Tivoli Enterprise
Monitoring Server on z/OS guide.
Windows installation problems and resolutions
On Windows systems, the installation fails randomly when
installing different features
On Windows systems, the installation fails randomly when installing different
features. Here is an a example of the error (timestamp removed):
OnMiaMoving - Processing Feature [KIWWICNS]
OnMiaMoving - Error log [C:\IBM\ITM\InstallITM\MiaError.log] created.
OnMiaMoving - Feature KIWWICNS [Tivoli Enterprise Portal Server Extensions]
OnMiaMoving - CMD[C:\temp\tmv621-d8185a-200807040554.base_windows\WINDOWS\
KIWWICNS.exe] Parameters[backup=n force=y silent=y "installdir=C:\IBM\
ITM" "backupdir=C:\IBM\ITM\Backup\MIA"
84
IBM Tivoli Monitoring: Troubleshooting Guide
Completed Successfully for PRODUCT "CP", VER "05100173", ID "TMS", IDVER
delete local TAPPLPROPS failed.
returned sqlStatus 79. product <CP> product version <05100173>
will be installed.
"-lC:\IBM\ITM\InstallITM\MiaInstall.log"] issued.
Advertisement
Table of Contents
Troubleshooting
