Error: “Cannot connect to server: please check network and try again” on Citrix Workspace

The request for resources/list can be very time consuming and can take upto 30 seconds in worst cases (depending on the performance of the network, StoreFront server or other components). This can cause timeout on the Receiver UI. But the response has been received successfully on the Receiver side.

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

We can figure out whether this issue is caused by network latency by adding the following registry key on the client:

HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixDazzle

Reg_SZ WebUILoadingWatchDogTimeoutMs

WebUILoadingWatchDogTimeoutMs controls the timeout value of watchdog.

Alternately, turn off the Unified Experience in StoreFront (if Receiver 4.4 is being used).

Related:

  • No Related Posts

Error: “Cannot connect to server: please check network and try again” on Citrix Workspace

The request for resources/list can be very time consuming and can take upto 30 seconds in worst cases (depending on the performance of the network, StoreFront server or other components). This can cause timeout on the Receiver UI. But the response has been received successfully on the Receiver side.

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

We can figure out whether this issue is caused by network latency by adding the following registry key on the client:

HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixDazzle

Reg_SZ WebUILoadingWatchDogTimeoutMs

WebUILoadingWatchDogTimeoutMs controls the timeout value of watchdog.

Alternately, turn off the Unified Experience in StoreFront (if Receiver 4.4 is being used).

Related:

  • No Related Posts

Error: “Cannot connect to server: please check network and try again” on Receiver

The request for resources/list can be very time consuming and can take upto 30 seconds in worst cases (depending on the performance of the network, StoreFront server or other components). This can cause timeout on the Receiver UI. But the response has been received successfully on the Receiver side.

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

We can figure out whether this issue is caused by network latency by adding the following registry key on the client:

HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrixDazzle

Reg_SZ WebUILoadingWatchDogTimeoutMs

WebUILoadingWatchDogTimeoutMs controls the timeout value of watchdog.

Alternately, turn off the Unified Experience in StoreFront (if Receiver 4.4 is being used).

Related:

  • No Related Posts

Workspace App for Windows – Error “Cannot start app” intermittently

In Receiver’s error file you will find following message:

Launch error code: 3

Error launching the ICA file

Unable to launch using CCM (url)

at Dazzle.LaunchUtils.ICALaunchUtils.LaunchViaFile(String quotedIcaFilePath, String cmdline, String url)

Create the following exclusions for Imprivata hooking files in the client/end point registry:

[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeSSOProviderISXAgentHookInit]

“Concentr.exe”=””

“SelfService.exe”=””

“AuthManSvr.exe”=””

“Receiver.exe “=””

“SelfServicePlugin.exe”=””

“wfcrun32.exe”=””

Related:

  • No Related Posts