Citrix Storefront 3.16 HTML5 and Receiver for Linux Issue


Fellow Citrix CTA René Bigler highlighted an issue in the IGEL Community Slack channel that when using Storefront enabled for ‘Use Receiver for HTML5 if local Recevier is unavailable’ it would automatically default to HTML5 and fail to launch the app/desktop.

20181031_105753

I did further testing to isolate exactly where the issue might lie. Here’s my testing and results carried out.

Environment
-Citrix XenApp 7.15 CU2
-Storefront 3.15 and 3.16
-IGEL OS 10.05.100
-Citrix Receiver 13.9.1 and 13.10.0

Test #1
-Storefront 3.15, Receiver Deployment Option: Install locally
-IGEL OS 10.05.100
-Citrix Receiver 13.9.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #2
-Storefront 3.15, Receiver Deployment Option: Install locally
-IGEL OS 10.05.100
-Citrix Receiver 13.10.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #3
-Storefront 3.15, Receiver Deployment Option: Use Receiver for HTML5 if local Recevier is unavailable.
-IGEL OS 10.05.100
-Citrix Receiver 13.9.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #4
-Storefront 3.15, Receiver Deployment Option: Use Receiver for HTML5 if local Recevier is unavailable.
-IGEL OS 10.05.100
-Citrix Receiver 13.10.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #5
-Storefront 3.16, Receiver Deployment Option: Install locally
-IGEL OS 10.05.100
-Citrix Receiver 13.9.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #6
-Storefront 3.16, Receiver Deployment Option: Install locally
-IGEL OS 10.05.100
-Citrix Receiver 13.10.1

Result: Logged into Storefront browser, launched XenApp desktop successfully using native Receiver

Test #7
-Storefront 3.16, Receiver Deployment Option: Use Receiver for HTML5 if local Recevier is unavailable
-IGEL OS 10.05.100
-Citrix Receiver 13.9.1

Result: Logged into Storefront browser, launched XenApp desktop, attempted to use HTML5 and failed

Test #8
-Storefront 3.16, Receiver Deployment Option: Use Receiver for HTML5 if local Recevier is unavailable
-IGEL OS 10.05.100
-Citrix Receiver 13.10.1

Result: Logged into Storefront browser, launched XenApp desktop, attempted to use HTML5 and failed

Issue

Issue appears to be with any Receiver for Linux version running on Storefront 3.16 (1808)

Workaround

If you are running Storefront 3.16 (1808) and the Receiver for Linux, ensure you have ‘Install Locally’ set rather than ‘Use Receiver for HTML5 if local Recevier is unavailable’ then your XenApp desktops/apps will launch.

image (1)

 

Advertisements

Citrix Self-Service Password Reset “Cannot access your server address!”


Environment:

  • Windows Server 2016
  • Citrix XenApp 7.15
  • Citrix XenApp Self-Service Password Reset 1.1.0.15097

Issue:

Creating a new ‘User Configuration’ in the ‘Enable Self-Service Password Reset’ section

SSPR

  • The Service Address returns and error “Cannot access your service address!”.

sspr_error

  • Browsing to https://fqdn/MPMService returns “Error 403 – Forbidden: Access is denied”
  • Event Viewer has the following:

SSPR_EV

 

Resolution:

Either:

  1. Disable the Internet Explorer proxy server, if possible
  2. Enable ‘Bypass proxy server for local addresses’
  3. Create a proxy server exception

 

 

 

 

Citrix Storefront – HTTP Error 503. The service is unavailable.


UPDATED

Issue

Service Unavailable

HTTP Error 503. The service is unavailable.

Event Viewer error

Source: IIS-W3SVC-WP

Event ID: 2293

Description: The Module name ManagedEngine64 path C:\Windows\Microsoft.NET\Framework64\v2.0.50727\webengine.dll returned an error from registration.  The data is the error.

Application Pool ‘DefaultAppPool’ won’t start.

Resolution

Browse to: %Windir%\system32\inetsrv\config

Backup the ApplicationHost.config file

Open ApplicationHost.config

Look for <add name=”ManagedEngine64″ (around line 267) and delete the whole line

<add name=”ManagedEngine64″ image=”%windir%\Microsoft.NET\Framework64\v2.0.50727\webengine.dll” preCondition=”integratedMode,runtimeVersionv2.0,bitness64″ />

Save the file and run IISRESET

 

The cause was related to the fix of making the Storefront console load faster, by putting <generatePublisherEvidence enabled=”false”/> into C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet.config or c:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet.config

 

This fix is still valid but needs to be done AFTER installing and configuring Storefront the first time.

Error: The Citrix Credential Wallet service is not running, users will not be able to log on using passwords


Under the file ->
C:\Program Files\Citrix\Receiver Storefront\Services\CredentialWallet\ Citrix.DeliveryServices.CredentialWallet.ServiceHost.exe.config

<runtime>
<!– Set enabled=false, if this machine does not have external access to the internet –>
<generatePublisherEvidence enabled=”false”/>
</runtime>

 

NOTE: Make sure there are no white spaces within the Citrix.DeliveryServices.CredentialWallet.ServiceHost.exe.config file

Receiver Storefront Logging and Tracing


Using an account with local administrator permissions on the Receiver Storefront server, start Windows PowerShell and, at a command prompt, type the following commands.

> Add-PSSnapin Citrix.DeliveryServices.Framework.Commands

> Set-DSTraceLevel -All -TraceLevel Verbose

 

2. To disable tracing, type the following commands.

> Add-PSSnapin Citrix.DeliveryServices.Framework.Commands

> Set-DSTraceLevel -All -TraceLevel Off

 

Due to the large amount of data that potentially can be generated, tracing may significantly impact the performance of Receiver Storefront. Accordingly, Citrix recommends that you disable tracing unless specifically required for troubleshooting.

 

When tracing is enabled, tracing information is written to files in the \Admin\Trace\ directory of the Receiver Storefront installation, typically located at c:\Program Files\Citrix\Receiver Storefront\.

Remove “Activate” from Storefront Website


If you are not using provisioning file to configure your Receiver you can remove the “Activate” option under the users name when logged into the Storefront website.

On the Storefront 1.2 server(s), open the web.config in the C:\inetpub\wwwroot\[Store]Web\ directory

Locate the following:

<receiverConfiguration enabled=”true” …./>

Change the value from “true” to “false” and it is gone.

Set ‘Apps’ as the default landing page in Receiver for Web


Go to the web.config file of Receiver for Web site (c:\inetpub\wwwroot\Citrix\<StoreWebName>;) and search for the following entry:

<uiViews …… defaultView=”desktops” /> (default parameter value)

Change it to:

<uiViews …… defaultView=”apps” />

Save the file and close it.

Note: Make sure make changes to the web.config file while Citrix StoreFront console is closed.