Telemetry silently fails due to stale license server connection key

book

Article ID: CTX696915

calendar_today

Updated On:

Description

On an on-premises site, telemetry stops reaching the Citrix License Server, and telemetry events are no longer recorded, with no obvious error surfaced in the console or Windows event log (the failure is silent on affected versions). 

When CDF tracing is enabled on a Delivery Controller, you see repeated HTTP 401 (Unauthorized) responses on the POST ls_token/create request made by the Configuration service to the License Server. These repeated errors are also logged in License Server logs.

 

Impacted Environment Details:

  • Citrix Virtual Apps and Desktops (CVAD, on-prem only)
    • LTSR: 2203CU7, 2402CU4, 2507CU1 

Cause

The Configuration service authenticates to the Citrix License Server using a stored connection key. If that key becomes out of sync with the License Server (for example after a License Server reinstall, re-registration, or certificate change), the License Server rejects the token request with HTTP 401. On affected versions this error was caught and logged but not acted upon — the stored key was not invalidated, so the controller kept reusing the stale key and never re-registered. As a result, license-usage telemetry failed silently and indefinitely. 

Resolution

  • Prerequisites 

    • The fixed, Citrix-signed Citrix.Configuration.Logic.dll for your exact product version. Do not use a file of other product versions. 

     

    Procedure - perform on one Delivery Controller at a time (so the site stays serviceable), then repeat on every controller. 

    1. In Windows Services: stop "Citrix Configuration Service" 
      • image.png

    2. Back up the existing binary, "C:\Program Files\Citrix\Configuration\Service\Citrix.Configuration.Logic.dll". Rename the file to “Citrix.Configuration.Logic.backup.dll” 
      • image.png

    3. Move the downloaded “Citrix.Configuration.Logic.dll” file to the above location "C:\Program Files\Citrix\Configuration\Service\”
    4. Start "Citrix Configuration Service" 
    5. Repeat steps 1–4 on every Delivery Controller in the site. 
       

    Verify the fix:

    1. Confirm the service starts cleanly 
    2. Telemetry and usage are resumed in CC dashboard 

    Rollback If needed, stop the service, restore Citrix.Configuration.Logic.dll.backup over the replaced file, and start the service - on each controller where the change was made.



    Fix Locations:

    CVAD 2203 CU7 Update 1 
    CVAD 2402 CU4 Update 1

Issue/Introduction

Telemetry in Citrix Virtual Apps and Desktops on-premises environments can silently fail due to a stale license server connection key causing HTTP 401 errors. This issue prevents telemetry data from reaching the Citrix License Server, impacting usage reporting without visible errors.

 

Powered by Wolken Software