Once you have finished Installing the Management Pack (Citrix Virtual Apps & Desktops) and Configuring the Management Pack (Citrix Virtual Apps & Desktops), check the Collection State and Collection Status for the adapter instance on the Solutions page. If they show as Not Collecting or No Data Receiving, respectively, the following troubleshooting topics can help you diagnose and correct common problems with your adapter instance.

Test Connection Errors

When Creating an Adapter Instance (Citrix Virtual Apps & Desktops), click Test Connection after entering all of your configuration settings to ensure vROps can connect to the specified host.

The following errors are possible:

Bad OData Domain, Username, or Password

Error Message: Unable to establish a valid connection to the target system. Failed to test adapter: argument type mismatch.

Description: The specified OData domain, username, or password is incorrect.

Bad Windows PowerShell Domain, Username, or Password

Error Message: Unable to establish a valid connection to the target system. Wait for response of task 'Test connection' is timed out for collector 'vRealize Operations Manager Collector-vRealize Cluster Node'.

Description: The specified PowerShell domain, username, or password is incorrect.

Bad Hostname

Error Message: Unable to establish a valid connection to the target system. java.net.UnknownHostException: some_system: unknown error.

Description: Cannot connect to the specified hostname.

Adapter and Collector Log Files

You can review XenDesktop Adapter errors in the adapter and collector log files, which can be viewed in the vROps UI or in an external log viewer.

  • Adapter log files are located in the $VCOPS_BASE/user/log/adapters/XenDesktopAdapter/ folder.
  • Collector log files are located in the $VCOPS_BASE/user/log/ folder.

To set the base log level for the collector in vROps:

  1. Navigate to Administration > Logs.
  2. Expand the MASTER folder, then select the COLLECTOR folder.
  3. Click the Edit Properties configure_iconicon.
  4. In the Root logger level drop-down menu, select the desired option.
  • The default logging level is warning.
  • To troubleshoot issues, set the logging level to info.
  • To view detailed messages, including micro steps, queries, and returned results, set the logging level to debug.
Caution: If you set the logging level to debug, log files can become large very quickly. Set the logging level to debug only for short periods of time.

For more information about viewing log files and modifying levels, refer to the vROps online help.