It is possible that all servers may be running with same UID.Ĥ) If session reliability is enabled, XTE service should be in running state. Note that, more than one farm can use STA server from one farm, as long as the WebInterface can talk to the STA servers(best practice is to have at least one STA server from each farm configured)Ģ) Verify CAG is able to reach the XenApp servers in the farm via ports 1494 or 2598(if session reliability is enabled).ģ) If you are using provisioning services or template or cloning to spin up XenApp servers, verify the UID of the servers are unique. Verify the STA server entries and make sure they are exactly the same. Here are the likely reasons for this error and how to troubleshoot:ġ) STA servers configured in the WebInterface is not matching to the STA entries in CAG. (In my case the same applications worked fine when launched internally without coming through the CAG. If Citrix receiver is installed, it would say “protocol driver error”, older versions of citrix clients report the other confusing message “there is no XenApp server configured at the mentioned address”. The error message varies with the Citrix client version. Protocol Driver Error.Applicable Products : Citrix Gatewa圜itrix Virtual Apps and Desktops. For 32-bit version of Windows Server the file can be located by navigating to the Program Files\Citrix\XTE\conf folder. This error is bit confusing, as the the applications are in fact published from valid servers. CTX284942 NewGateway: Cannot connect to the Citrix XenApp Server. For 64-bit version of Windows Sever the file can be located by navigating to the Program Files (x86)\Citrix\XTE\conf folder.
Issue: When users launch applications from Web Interface, they get an error message “Protocol Driver Error….” OR “there is no xenapp server configured for this application”.
0 kommentar(er)
