“Cannot connect to the Citrix XenApp server. Unable to locate the requested Citrix XenApp name. The server may be unavailable or you may have entered the server name incorrectly.”

A common problem I’ve experienced working on Citrix XenApp 5.0 running on Windows Server 2008 is corrupt performance counters.

The story goes likes this:

Users call the Helpdesk explaining that they cannot connect to Citrix Xenapp and the following message occurs:

“Cannot connect to the Citrix XenApp server. Unable to locate the requested Citrix XenApp name. The server may be unavailable or you may have entered the server name incorrectly.”

Rebooting the server will not resolve the issue.

From the Server 2008 Start Menu > Citrix > Administration Tools, if we open the XenApp Advanced Configuration utility in XenApp 5, we can tell if the problem is due to Windows Server 2008 corrupt performance counters.

In the Citrix XenApp Advanced Configuration window, under the Server Farm, we expand the Servers tab and select the problem XenApp server on the left column.  On the right column select the Load Manager Monitor tab.

If All 4 of the Load Evaluator percentages are either 100% or 0% then you know that your performance counters are corrupt.

2016-12-09_1630

To resolve corrupt performance counters on Windows Server 2008 running Citrix XenApp, it is necessary to do the following:

Citrix Load Evaluator Memory/CPU Utilization at 100% Fix

  1. Copy Perfstringbackup.ini from a Citrix server which is working.  Perfstringbackup.ini is located in %systemroot%\System32\Perfstringbackup.ini
  2. Rename Perfstringbackup.ini to Perfstringbackup.bak on server experiencing issues.
  3. Paste Perfstringbackup.ini to the same location (%systemroot%\System32) on the server experiencing  the issue.
  4. Open a command prompt on the server experiencing issues and type lodctr /R:perfstringbackup.ini.  You should receive a Successful message after entering the command.  If not, it may be necessary to run the command prompt with elevated privileges.
  5. Reboot the server.

Once the server reboots check that not all 4 Load Evaluator percentages are either at 100% or 0%.  Users should now be able to log in.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s