/tags/rds/ Recent content in RDS on lettucebuns.io Hugo -- gohugo.io en-us Sun, 13 Sep 2026 11:30:03 +0000 /posts/horizon-2603-rds-app-volumes-bug/ Sun, 13 Sep 2026 11:30:03 +0000 /posts/horizon-2603-rds-app-volumes-bug/ <h1 id="tldr">tl;dr</h1> <p>If you deploy published applications using Omnissa App Volumes and Omnissa Horizon 2603 or 2606, users may encounter an error message when launching the application. This is a known bug with Horizon 2603 and Horizon 2606. A hot patch connection server build is available from Omnissa Support to resolve the issue.</p> <h1 id="the-problem">The Problem</h1> <p>After upgrading 2 of our Omnissa Horizon pods to version 2603, users reported error messages when attemping to launch published applications delivered through App Volumes. Users would see the error message: &lsquo;Loading Failed: This application is currently not available. Please try connecting to this application again later, or contact your system administrator.&rsquo; <img src="/img/horizon-client-error.png" alt="Horizon Client Error" class="center" /> </p> <h1 id="tldr">tl;dr</h1> <p>If you deploy published applications using Omnissa App Volumes and Omnissa Horizon 2603 or 2606, users may encounter an error message when launching the application. This is a known bug with Horizon 2603 and Horizon 2606. A hot patch connection server build is available from Omnissa Support to resolve the issue.</p> <h1 id="the-problem">The Problem</h1> <p>After upgrading 2 of our Omnissa Horizon pods to version 2603, users reported error messages when attemping to launch published applications delivered through App Volumes. Users would see the error message: &lsquo;Loading Failed: This application is currently not available. Please try connecting to this application again later, or contact your system administrator.&rsquo; <img src="/img/horizon-client-error.png" alt="Horizon Client Error" class="center" /> </p> <p>In the connection server debug logs, we would see errors like this:</p> <blockquote> <p>2026-08-27T13:38:49.786-04:00 DEBUG (1860-13DC) <!-- raw HTML omitted --> [LinkedModeDesktopsHandler] LMV: Unsuccessful launch of CN=APPLICATION_NAME,OU=Applications,DC=vdi,&gt;DC=vmware,DC=int for user USERNAME: Cannot invoke &ldquo;String.startsWith(String)&rdquo; because &ldquo;<!-- raw HTML omitted -->&rdquo; is null</p> <p>2026-08-27T13:38:49.786-04:00 INFO (1860-13DC) <!-- raw HTML omitted --> [AbstractSessionLaunchContext] DOMAIN\username, Application=APPLICATION_NAME: Session request failed.       (null) [DOMAIN\username, Application=APPLICATION_NAME] (5ms): Application launch failed, exception was: Cannot invoke &ldquo;String.startsWith(String)&rdquo; because &ldquo;<!-- raw HTML omitted -->&rdquo; is null</p> </blockquote> <p>The issue is caused by a bug querying user GUIDs. Horizon is attempting to pull the user GUID and is only finding a null value.</p> <h1 id="the-solution">The Solution</h1> <p>As a temporary workaround for this issue, you can do the following on your connection servers:</p> <ol> <li>Login to the connection server</li> <li>Launch an elevated command prompt</li> <li>Change directory to C:\Program Files\Omnissa\Horizon\Server\tools\bin</li> <li>Run vdmadmin.exe -F</li> <li>Do this on all connection servers in each pod</li> </ol> <p>See the documentation for this command <a href="URL" title="https://docs.omnissa.com/Horizon-Administration-V2603/UpdatingForeignSecurityPrincipalsUsingthe-FOption">here</a>.</p> <p>The permanent fix will be a dot release for Horizon 2603 and 2606. We were provided Horizon 2603 connection server build 32686627688 which has resolved the issue for us prior to the dot release.</p>