CTX284942
{{tooltipText}}
Article
|
Configuration
|
{{likeCount}} found this helpful
|
Created:
{{articleFormattedCreatedDate}}
|
Modified:
{{articleFormattedModifiedDate}}
Symptoms or Error
Launch Fails with Error: «Cannot connect to the Citrix XenApp Server. Protocol Driver Error.»
Solution
Possible Solution 1:
NOTE: This solution only applies if the Citrix ADC/Gateway version is lower than the following: 11.0.70.16, 11.1.55.13, 12.0.53.22, no versions of 12.1 are affected
.
MBF mode is enabled on ADC
ADC has the support for DTLS with MBF with all the builds for the 12.0/12.1/13.0 series. In the 11.1 series, builds prior to 11.1 52.x doesn’t support DTLS with MBF, and builds starting from 52.x has the support for DTLS with MBF. MBF must be disabled to make DTLS work on builds prior to 11.1 52.x.
Before disabling MBF, be sure that your architecture and configuration on ADC allow you to disabled this feature.
To disable MBF, on your ADC GUI,
1. Go to Configuration > System > Settings
2. Click on Configure Modes. Uncheck MBF. Click OK to validate.
Possible Solution 2:
UDP port 2598 is blocked between ADC SNIP and VDA. If you have a security device, like a firewall between your ADC SNIP and VDA who do not allow UDP on port 2598, this error message will be raised.
Possible Solution 3:
DTLS traffic MTU is lower or greater than 1500. This is a specific issue known by Citrix support. The fix will is available on release 11.1 55.x and 12.0 53.x or higher.
Problem Cause
* MBF Enabled
* Port blocked
Additional Resources
I’m going to preface this with: I have no access to the Citrix Presentation server. I have no training in Citrix. My googling tells me that this is an issue on the other side, however, they are insisting it’s an issue with our desktops. This is also kind of long and convoluted, sorry.
We have access to another facility’s EMR, via Citrix. This arrangement has worked very well for quite a while, although, they haven’t let me know about some changes over the years until after they started affecting staff here.
We had a complete system down emergency a few weeks ago, due to a transformer outside the clinic exploding. Since that time, we’ve had a ton of users having issues connecting to the other facility’s Citrix farm. 99% of them get this error:
Google tells me that this on the server side. The staff over the servers told me to delete the user’s profile from their computer and that should fix it.
I can’t really delete that without causing a big fuss, though. On a whim, I noticed that one of the user’s had a folder redirection error, they weren’t owner of their home folder. When I fixed that, and deleted the ICAClient folder out of their %appdata% folder, they were able to launch the Citrix app. Until they logged out and back in. Then the error came back. Deleting the ICAClient folder doesn’t seem to help any more.
Also, to make things really strange, if people log in via our VDI system, it works fine, most of the time.
I’m stuck, any help is appreciated.
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”.
This error is bit confusing, as the the applications are in fact published from valid servers. The error message varies with the Citrix client version. 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”. (In my case the same applications worked fine when launched internally without coming through the CAG. )
Troubleshooting:
Here are the likely reasons for this error and how to troubleshoot:
1) STA servers configured in the WebInterface is not matching to the STA entries in CAG. Verify the STA server entries and make sure they are exactly the same. 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)
2) Verify CAG is able to reach the XenApp servers in the farm via ports 1494 or 2598(if session reliability is enabled).
3) If you are using provisioning services or template or cloning to spin up XenApp servers, verify the UID of the servers are unique. It is possible that all servers may be running with same UID.
4) If session reliability is enabled, XTE service should be in running state.
Having difficulties accessing accessing Citrix Server / launching applications from the outside thru firewall.
I can get to the Cirtix Logon Screen from the outside but after inicial login / authentication when I try and launch application It does not function appropriatly. Cannot lauch any applications. Receive this error. (Unable to lauch your application. Contact your heldesk with the following information. Cannot connect to the Citrix Xenapp server. protocol Driver Error)
The Website/Citrix is also using SSL Cert for HTTPS.
Having some issues setting this up correctly «Manage secure client access» in «Citrix Access Management Console».
I can access the Citrix environment from inside the firewall on the local network and access / launch applications without any issues running Citrix Apps from internal. Issue is only coming from public side.
Also only port 80 and 443 is open on our juniper firewall.
The Server is running (Windows 2008 Server 64-Bit, Citrix XenApp 5.0 Advanced Edition.
The Server is connected to local network 192.168.x.x all of the Cirtix Modules / Applications are running a on 1 single Server/Box.
Example: Private IP Internal 192.168.x.x NATs to 170.2.2.2
Recommendation #3:
If the /forceinstall switch doesn’t fix the Protocol Driver Error/Error 1046 issue, the Cleanup Utility may still be something to try as even with versions 1909 and greater of Workspace there may be remnants of older/corrupt installations that may affect performance.
If the workstation is still exhibiting the issue, next verify that the following Registry key is set to True:
- Key location: HKLM\SOFTWARE\Wow6432Node\Policies\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Logon\Local Credentials
- String Name (REG_SZ): LegacyLocalUserNameAndPassword
- Data: True
Test again.
Recommendation #4:
If the problem persists, try increasing the following timeout values in the registry:
- Key location: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Citrix\ICA Client
- Value Name (REG_DWORD): VdLoadUnLoadTimeOut
- Data (in Decimal): 5
The default for VdLoadUnLoadTimeOut is 1 second, this increases it to 5 seconds. Attempt reconnection. If the problem persists, try increasing this value to 10, 15, and 20 to see if the issue continues.
Note, the above registry locations are valid for 64-bit versions of Windows. For more information or for the Registry values for 32-bit versions of Windows, check Citrix’s article at https://support.citrix.com/article/CTX133536.
About Goliath Technologies
At Goliath we are passionate about helping IT Pros quickly troubleshoot and resolve end-user performance issues within their Citrix or VMware Horizon environment. To achieve this, we offer software to monitor and troubleshoot end-user experiences to anticipate, troubleshoot, and document performance issues. Visit our Goliath Performance Monitor product page to learn how software can reduce the time you spend troubleshooting end-user experience issues.