Summary
Resource Manager is a multi-feature component of the Enterprise Edition of Presentation Server and requires Enterprise Edition licensing. This document is designed to help with troubleshooting the various components of Resource Manager. The Knowledge Center contains several documents on environment specific Resource Manager errors and issues. If this document does not resolve your issue, search the Citrix Knowledge Center using more specific search terms or call Citrix Technical Support.
Architectural Understanding
• Location and version of the Resource Manager subsystems of IMA
• Network topology and IMA communication
• Enterprise Licensing required
• Database Connection Server and summary files
Resource Manager features are largely controlled by Resource Manager subsystems of IMA. Each subsystem has one or more roles in the functionality of Resource Manager. These subsystems are DLLs that must be the correct version and in the correct location under Program FilesCitrixSystem32CitrixIMASubsystems in order to work properly. The specific role of a Resource Manager subsystem could vary with the version of Presentation Server. Each server must be properly licensed with the Enterprise Edition license. The Resource Manager summary database is populated by the Database Connection Server which obtains collected metrics from each server in the farm.
Other Resource Manager Files and their roles are below:
• Program FilesCitrixAdministrationPluginsResourceManager.jar – responsible for displaying Resource Manager tabs in the Management Console
• Program FilesCitrixCitrix Resource ManagerLocalDBRMLocalDatabase.mdb – collects metrics for 96 hours
• Program FilesCitrix Citrix Resource ManagerSummary Files – contains the metric data collected and sent to the Database Connection Server
• Program FilesCitrixMMCPluginsReportCenterExt – Driver Extension for Report Center in the Access Suite Console
Note: Any time the Management Console is involved, the IMA data store is involved which means that standard IMA troubleshooting steps should be taken such as restarting IMA, rebuilding the local host cache, and running the Management Console directly on the affected server as a full farm administrator.
See CTX759510 – Function of the Local Host Cache.
CTX107800 – DSCHECK Version 5.15 – For Presentation Server 4.0 – Discontinued. should be used to verify the data store.
Citrix Preferred Support Agreement holders can get more information on Resource Manager architecture by referring to CTX103807 – Resource Manager Architecture and Troubleshooting.
Mixed Farm Environments
• Database Connection Server
• Resource Manager Summary database schema version
• Farm Metric Server
Special considerations should be made when the Citrix Farm consists of different versions of Presentation Server. The Database Connection Server and the Farm Metric Server should both be the latest version of Presentation Server with the latest hotfixes applied. These servers play a key role and need to be backward compatible with the other servers in the farm.
Large Farm Environments
• Database Connection Server
• ODBC database server
• IMA communication
Special considerations should be made when the Citrix Farm consists of a large number of servers spread out across zones. The Database Connection Server should be located on the same subnet as the SQL or Oracle server containing the Resource Manager Summary Database. Each Zone Data Collector is the traffic cop in distributing the summary files (using IMA communication) across the network to the Data Connection Server.
For more information on Resource Manager design, see CTX102330 – Resource Manager (RM) Summary Database Planning.
Troubleshooting Metrics and Alerts
• Performance Monitor
• IMA data store
• Resource Manager subsystems of IMA
• SMTP / SNMP / SMS
Metrics can be added or removed from the default metric set on a per server basis. Metric thresholds are dependent on the environment and a baseline should be developed in the actual environment. The configuration of metrics and thresholds are stored in the IMA data store. The same counters and objects are used for Resource Manager metrics from the registry that Perfmon.exe uses. Always verify that counters can be added and monitored with Performance Monitor when Resource Manager issues arise. Consider the type of alert (SMTP / SNMP / SMS) and verify that these work from the Presentation Server outside of Resource Manager. For example, can you ping the SMTP server by name? Can you receive an SNMP trap from the Presentation Server?
Troubleshooting “Server Down” in Management Console
• Farm Metric Server
• Resource Manager subsystems of IMA
• Network Topology and state of health
When the IMA Service on a server crashes or hangs and it looses contact with the Farm Metric Server, the “Server Down” message is displayed in the Management Console and an alert is sent (if alerts are configured). These alerts should only be generated where IMA on the specified server did not shut down normally. Under normal circumstance, IMA sends a broadcast event when it shuts down, and when the Farm Metric Server gets this it automatically logs the server as down without sending the alert. Network issues can prevent the Farm Metric Server from maintaining communication with the server and report it as down.
Troubleshooting Reboot Schedule Issues
• IMA data store
• Resource Manager subsystems of IMA
• API function ExitWindowsEx
The reboot schedule is configured in the Management Console and written to the IMA data store. The scheduled reboot function in Presentation Server calls the Windows API function ExitWindowsEx in order to accomplish the shutdown.
Test the shutdown.exe command with AT (command line scheduler) in a batch file on the problem server to see if the problem also occurs outside of Resource Manager. This helps determine if the internal API function is failing within Resource Manager.
Troubleshooting Summary Database Issues
Database Connection Errors
• MDAC version
• ODBC Permissions and Authentication
• Resource Manager subsystems of IMA
ODBC connectivity is used between the Database Connection Server and the Resource Manager Summary database. The MDAC version on the Database Connection Server must provide the latest or supported version of the ODBC driver. Some MDAC versions require the format “domainusername” in the DSN and in the Management Console. The user account that configures the DCS in the Presentation Server console must have DBO rights to the Resource Manager Summary database so they it can create tables and read and write data from the tables. This should be the same user account that is used in the System DSN (named RMSummaryDatabase).
Failed to Import Summary Files
• Schema Version
• Metrics Set on each server
• Zone Data Collector
• Resource Manager subsystems of IMA
Each server in the farm has its own schema version for summary files. This is determined by the version of Presentation Server that is running on the server. Each server in the farm has a unique set of metrics that is being collected and written to the summary file. (By default, this metric set is the same on all servers). The Resource Manager Summary database has a s
chema version which must be newer than the summary files that the DCS receives. IMA distribution is the mechanism used to send summary files to the DCS and the Zone Data Collector handles the traffic within its zone and determines when a file should be sent to the DCS.
Purging Data Issues
• IMA data store
• Resource Manager subsystems of IMA
• Hard coded to purge at midnight
• Stored Procedures
The purge schedule for Resource Manager events, metrics, and session/process data is configured in the Management Console and written to the IMA data store. The retention periods are compared at midnight and if data is older than the retention period, it is purged from the Resource Manager Summary database. Stored Procedures in the Resource Manager Summary database are triggered to remove the unwanted records.
Report Center Issues
• ADO connectivity to Resource Manager Summary database
• User account running Access Suite Console
Most report types in Report Center use an ADO connection to the Resource Manager Summary database using and OLE DB provider. The version of the OLE DB provider can prevent the connection from working or the user account specified in the ADO connection can cause errors if it does not have enough access to the tables in the database. If Windows NT integrated security is chosen, the user running the Access Suite Console must have read and write access to the Resource Manager Summary database. The user name and password fields in the Data Link properties are for SQL authentication only. If you enter a Windows account in these fields, the logon will fail unless you select “Windows NT integrated security” which in this case it will ignore the user name and password and use the account that is running the Access Suite Console.
Timestamps of processes and session connections are written to the SDB in UTC. The server time zone offset based on the time zone that the server is located in is also recorded and then reports can be generated with the actual time that makes sense to the reader.
Resource Manager Web Console (CTX107026)
Troubleshooting Tool
Advanced Reporting Tool
The Resource Manager Web Console contains SQL queries designed to troubleshoot and monitor various server farm activities as well as be used for a reporting tool.
CTX107026 – Resource Manager Web Console 4.1
Using Microsoft SQL Profiler
• Troubleshooting Tool
• SQL Performance Monitor
SQL Profiler can be used for advanced troubleshooting Resource Manager issues. The Profile traces an application’s SQL statements and stored procedures and captures transactions occurring on the SQL server. A template can be created to determine exactly which items will be traced and then a trace is started and can be saved as a file or a database.
Extracting SQL Statements from Report Center
Run a trace while generating a report in Report Center. Use the SQLProfilerStandard template. The SQL statements for the report are found in the trace by highlighting the line where Event Class = SQL:BatchCompleted and TextData = Declare @pk_JobID.
Troubleshooting Purge Issues
Run a trace at midnight when the purge settings are hard coded to be read and the purge takes place. Use the SQLProfilerStandard template.
Troubleshooting Import Summary Files Issues
Run a trace while clicking the UPDATE NOW button in the Management Console. Use the SQLProfilerStandard template. The application is listed as IMA and each line of the trace shows metrics being written into the database. Look for errors in the trace.
For more information on using SQL Profiler:
http://support.microsoft.com/kb/224587
More Information
The Advanced Concepts Guide for Presentation Servers contain important and detailed information about Resource Manager.
CTX104144 – Advanced Concepts Guide MetaFrame Presentation Server for Windows Version 3.0
CTX107059 – Advanced Concepts Guide for Presentation Server 4.0
Resource Manager Hotfixes
• File version, date, and timestamp
• Hotfix Readme
Resource Manager hotfixes are released with the Hotfix Rollup Packs for Presentation Server. The readme for each rollup specifies the issues that were fixed and also lists the Resource Manager subsystems that were replaced. See the Hotfix Rollup Schedule for more information.
CTX107180 – Hotfix Rollup Pack Schedule
