Spectrum OneClick "Server Down" or UI Issues in Citrix Environments

Products

• Network Observability
• Spectrum

Issue/Introduction

• The Primary OneClick server intermittently appears as "Down" in the OneClick Administration or Monitored Landscapes page.
• OneClick processd logs report: Failure to send heartbeat message.
• The OneClick console UI fails to render, menus are missing, or the interface is unresponsive when accessed via Citrix

Environment

• DX NetOps Spectrum (All Supported Versions)
• OneClick Server accessed via Citrix / Virtual App Delivery

Cause

While OneClick may function within Citrix, DX NetOps Spectrum does not officially certify or provide direct support for Citrix as a delivery platform. Issues often arise due to:

1. Session Latency: Citrix sessions may require additional time to properly initialize and format the OneClick Java/Web components.
2. Browser/Session Cache: Persistent Citrix sessions can harbor corrupted cache, leading to UI rendering failures or "Down" status reports

Resolution

To isolate and resolve these issues, follow the mandatory testing steps below:

1. Bypass Citrix (Mandatory Troubleshooting Step): If OneClick appears down or unresponsive within a Citrix session, testing without Citrix is required to isolate the root cause. Attempt to access the OneClick URL directly from a local machine or a supported browser outside of the Citrix environment Primary Oneclick Down.

2. Use Private/Incognito Browser: Launch a Private/Incognito browser window to bypass any session-specific cache. If OneClick renders correctly in a private window, clear the browser and Citrix session cache Primary Oneclick Down.

3. Allow UI Stabilization: In some Citrix deployments, OneClick requires 2–5 minutes to fully format the menus and UI components. Monitor the status for several minutes before concluding the server is down Primary Oneclick Down.

4. Verify Heartbeat Ports: Ensure that network policies within the Citrix environment are not blocking the required communication ports:

   • TCP 14001: Required for SpectroSERVER to send heartbeats/callbacks to OneClick.
   • TCP 14002: Required for OneClick requests to SpectroSERVER

5. Restart Tomcat: If the issue persists after bypassing Citrix, restart the OneClick Tomcat service to refresh the connection pool and reset the heartbeat listeners