Troubleshooting workspaces

Edit online

Problems can occur with general workspaces and agent-specific workspaces.

The following table contains problems and solutions related to workspaces.

Table 1. Workspace problems and solutions

This table contains 2 columns, one for the problem and one for the solution.
Problem Solution
The process application components are available, but the Availability status shows PROCESS_DATA_NOT_ AVAILABLE. This problem occurs because the PerfProc performance object is disabled. When this condition exists, IBM Tivoli Monitoring cannot collect performance data for this process. Use the following steps to confirm that this problem exists and to resolve it:
  1. In the Windows™ Start menu, click Run.
  2. Type perfmon.exe in the Open field of the Run window. The Performance window is displayed.
  3. Click the plus sign (+) in the toolbar. The Add Counters window is displayed.
  4. Look for Process in the Performance object menu.
  5. Complete one of the following actions:
    • If you see Process in the menu, the PerfProc performance object is enabled and the problem is coming from a different source. You might need to contact IBM® Software Support.
    • If you do not see Process in the menu, use the Microsoft™ utility from the Microsoft.com Operations website to enable the PerfProc performance object.

      The Process performance object becomes visible in the Performance object menu of the Add Counters windows, and IBM Tivoli® Monitoring is able to detect Availability data.

  6. Restart the monitoring agent.
The name of the attribute does not display in a bar chart or graph view. When a chart or graph view that includes the attribute is scaled to a small size, a blank space is displayed instead of a truncated name. To see the name of the attribute, expand the view of the chart until sufficient space is available to display all characters of the attribute name.
At the end of each view, you see the following Historical workspace KFWITM220E error: Request failed during execution. Ensure that you configure all groups that supply data to the view. In the Historical Configuration view, ensure that data collection is started for all groups that supply data to the view.
When you use a long process name in the situation, the process name is truncated. Truncation of process or service names for situations in the Availability table in the portal display is the expected behavior. The maximum name length is 100 bytes.
Regular (non-historical) monitoring data fails to be displayed. Check the formation of the queries you use to gather data. For example, look for invalid SQL statements.
No row of data for 64-bit applications is displayed in the workspaces when the monitoring agent is running on a 64-bit operating system. The Tivoli Enterprise Portal shows data only for 32-bit applications. No solution is available for this problem at this time.