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

Page: 192 / 310

Unable to configure the Warehouse Proxy agent with modified
parameters from the Tivoli Enterprise Portal GUI
In an environment with an OS agent and the Warehouse Proxy agent, your attempt
to modify the Warehouse Proxy agent parameters from the Tivoli Enterprise Portal
GUI might result in the following message:
KDY1024E: The agent failed to
respond to the command command did not start or stop agent.
This message indicates that the configuration attempt failed. For example, after
you specify "Run As User" for an agent, this value cannot be cleared back to not
having "Run As User" because the code that triggers updates is based on a value
being set for a property. In this case, you are trying to unset a property by not
passing a value. To avoid this issue, supply the same user name for the WPA agent
as you have for the OS agent (typically, root or Administrator).
Workspaces
Review the monitoring agent workspaces entries for a description of problems in
the Tivoli Enterprise Portal with accessing and displaying workspaces.
AMS workspace remains unavailable, even if the OS Agent is
started
You might notice that the Agent Management Services (AMS) workspace remains
unavailable, even if the OS agent is started. Changes to the behavior of the login
process make the Proxy Agent Service (PAS) initialization asynchronous. The AMS
workspace remains unavailable until PAS initialization completes. This is an
expected behavior.
The link to an OS agent workspace is pointing to a superseded
version of the workspace
Links point to specific object names and are not automatically updated to return
the latest version of a workspace. A link from an external agent pointing into the
OS agent must be updated to point to the current release. If the current version of
the agent is not truly "versioned" using the VRF appendage to the object name, but
is a different object name to facilitate 64-bit data workspace exposure, the external
anchor should have two links associated with it: one pointing to the existing
version of the workspace and a second pointing to the new 64-bit enabled
workspace.
Non-OS agents should not expect a specific version of the workspace to be
available unless their respective agent requires that base version. In this case, it
might not be feasible to update agents until the next required release.
Unable to view data for a default query in a workspace
A default query should display data when it is assigned to the view on the
workspace. However, if this is a view that has links, a link must be selected in
order to see the data in the workspace.
A workspace view is showing an error
It is possible that the workspace definition was saved incorrectly. An example
workspace would be the IBM Tivoli Monitoring for Databases: Oracle Agent's SQL
Text workspace.
174
IBM Tivoli Monitoring: Troubleshooting Guide