Workspace troubleshooting

Table 7 shows problems that might occur with workspaces. This chapter provides agent-specific troubleshooting information. See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting information.

Table 7. Workspace problems and solutions
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. Do the following to confirm that this problem exists and resolve it: Choose Run in the Windows Start menu. Type perfmon.exe in the Open field of the Run window. The Performance window is displayed. Click the plus sign (+) in the tool bar located above the right pane. The Add Counters window is displayed. Look for Process in the Performance object pull-down menu. Perform one of the following actions: If you see Process in the pull-down menu, the PerfProc performance object is enabled and the problem is coming from a different source. If you do not see Process in the pull-down menu, use the Microsoft utility from the following Web site to enable the PerfProc performance object: http://blogs.technet.com/mscom/archive/2008/12/18/ the-mystery-of-the-missing-process-performance- counter-in-perfmon.aspx The Process performance object becomes visible in the Performance object pull-down menu of the Add Counters windows, and IBM Tivoli Monitoring is able to detect Availability data. 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 there is sufficient space to display all characters of the attribute name.
At the bottom 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.
You start collection of historical data but the data cannot be seen.	Managing options for historical data collection: Basic historical data collection populates the Warehouse with raw data. This type of data collection is turned off by default. See the IBM Tivoli Monitoring Administrator's Guide for information on managing this feature including how to set the interval at which data is collected. By setting a more frequent interval for data collection you reduce the load on the system incurred every time data is uploaded. You use the Summarization and Pruning monitoring agent to collect specific amounts and types of historical data. Be aware that historical data is not displayed until the Summarization and Pruning monitoring agent begins collecting the data. By default, this agent begins collection at 2 AM daily. At that point, data is visible in the workspace view. See the IBM Tivoli Monitoring Administrator's Guide to learn how to modify the default collection settings.
Historical data collection is unavailable because of incorrect queries in the Tivoli Enterprise Portal.	The column, Sort By, Group By, and First/Last functions are not compatible with the historical data collection feature. Use of these advanced functions makes a query ineligible for historical data collection. Even if data collection has been started, you cannot use the time span feature if the query for the chart or table includes column functions or advanced query options (Sort By, Group By, First / Last). To ensure support of historical data collection, do not use the Sort By, Group By, or First/Last functions in your queries. See the IBM Tivoli Monitoring Administrator's Guide or the Tivoli Enterprise Portal online help for information about the Historical Data Collection function.
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. 100 bytes is the maximum name length.
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.
Navigator items and workspace titles are labeled with internal names such as `Kr6:KR60000` or `Knt:KNT0000` rather than the correct names (such as Disk).	Ensure application support has been added on the monitoring server, portal server, and portal client. For more information and instruction on installing application support see "Installing and enabling application support" in the IBM Tivoli Monitoring Installation and Setup Guide.