Xendesktop ‘Site Test’ might fail when the network connectivity among Delivery Controllers in different satellite zones is blocked.

The site test might fail when the network connectivity among Delivery Controllers in different satellite zones is blocked.

Test fails with below exception,

Error Id: XDDS:8CABB6CB

Exception:

System.InvalidOperationException Sequence contains no elements

at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)

at Citrix.Console.PowerShellSdk.EnvironmentTestService.Scripts.RunTestTaskScript.UpdateProgress(Guid taskId)

at Citrix.Console.PowerShellSdk.EnvironmentTestService.Scripts.RunTestTaskScript.RunScript()

at Citrix.Console.PowerShellInteraction.PowerShellScript`1.Run()

at Citrix.Console.Shared.UI.Tests.TestLauncher.Start()

at Citrix.Console.DeliveryCenter.UI.Mmc.Commands.ExecuteDeliveryCenterTestCommand`1.ExecuteWithItem(T item, IProgressReporter reporter, Canceller canceller)

at Citrix.Console.Common.OperationTimer.TimeBlock(Action operation)

at Citrix.Console.CommonControls.ProgressDisplay.GenericProgressOperationWithFeedBack.PerformOperationInternal()

at Citrix.Console.CommonControls.ProgressDisplay.ProgressWindowOperation.PerformOperation()

at Citrix.Console.CommonControls.ProgressDisplay.ProgressWindowViewModel.PerformAction(Action operationComplete)

DesktopStudio_PowerShellHistory : Run Tests

New-EnvTestDiscoveryTargetDefinition -AdminAddress “DDC.domain.com:80” -TestSuiteId “Infrastructure” | Set-Variable -Name “testTarget0”

Get-Variable -Name @(“testTarget0″) -ValueOnly | Start-EnvTestTask -AdminAddress “DDC.domain.com:80” -RunAsynchronously

Remove-Variable -Name “testTarget0”

From the eventvwr, we also noticed that Citrix.Env.Test.exe service crashed due to an unhandled exception.

image.png

Related:

  • No Related Posts

Citrix Access Gateway OAUTH IDP: Getting ” Failed to login the user due to insufficient claims. Please contact your administrator”

Customer has configured Citrix Access Gateway as OAuth IDP with Workspace in Cloud and after user authentication is completed, users were getting the error as shownbelow

” Failed to login the user due to insufficient claims. Please contact your administrator”

The Attributes sent by Citrix Access Gateway (OAuth IDP) can be seen in /var/log/ns.log.

In the below log snippet, you could see that the Attributes such as ( Name, UPN, CIP and SID, etc ) sent by Citrix Access GAteway (OAuth IDP) are BLANK.

ns.log:

=======


Nov 6 13:55:09 <local0.info> XX.XX.XX.XX 06/11/2019:12:55:09 0-PPE-0 : default AAATM Message 3795 0 : “OAUTHIDP: CC IDTOKEN: user: <test@example.com>’s claims are: sub:, name:, upn:, email:, ctx_auth_alias:, cip_domain:, cip_forest: sid:, oid:, amr:[“otp”], nonce:637085983001757588.Mjg2NWQ2YWMtZDI5OC00ZjQ4LTk0NDQtNTJlM2I1ZmVlNjBlOGQ0NzQ0OWUtNjZlMi00NjI0LWIzMWQtNTNjYzMzY2VkYzk0, familyname:, givename:, domain: , groups len 0

Related:

  • No Related Posts

Failed to launch session with the error code “Your session ‘AppName’ did not launch successfully due to error code 3505. Please contact your administrator for more information about the error.” on Citrix Workspace App During App/Desktop Launch

This article is intended for Citrix administrators and technical teams only.

Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.

When launching an application or desktop session using Citrix Workspace App, the session fails to launch with the error code “Your session ‘AppName’ did not launch successfully due to error code 3505. Please contact your administrator for more information about the error.”

Related:

  • No Related Posts

Failed to launch session with the error code “Your session ‘AppName’ did not launch successfully due to error code 3500. Please contact your administrator for more information about the error.” on Citrix Workspace App During App/Desktop Launch

Causes and Solutions

Cause 1: For Multi-session OS machines, the VDA machine is reaching the maximum load you specified in one of following load management policies:

  • Maximum number of sessions
  • CPU usage
  • Disk usage
  • Memory usage
  • Memory usage base load

Solution 1: Please confirm if the VDA Server has reached the settings you specified in above HDX policies. This can be checked:

  • Using Citrix Director: Trends => Load Evaluator Index tab.
  • Using PowerShell:
Get-BrokerMachine |Select DNSName, LoadIndex, LoadIndexes

When troubleshooting the issue, please consider:

  • Logging off idle or disconnected sessions
  • Increasing the number of VDA servers hosting the published resource to the Delivery Group.
  • Resolving the performance issue on the VDA server if it is running into performance problems.

Cause 2: The Random single-session OS or multi-session OS machine the user is connecting to is in maintenance mode.

Solution 2: Please turn off Maintenance Mode for that machine from Citrix Studio or PowerShell cmdlet:

Set-BrokerMachineMaintenanceMode -InputObject <domainname><hostname> $false

Cause 3: The user attempts to launch an app or desktop in Citrix Workspace app after access to the resource in the Delivery Group has been removed, but before the user has refreshed avaialbe apps in Citrix Workspace app.

Solution 3:

  • If Citrix Workspace app Self-Service Plug-in is disabled by Manage SelfServieMode policy , right click the Citrix Workspace app icon in Windows notification area and click Refresh.
  • From the Citrix Workspace app, click the user name, in the dropdown list, and click Refresh Apps.

Cause 4: The VDA machine to host the HDX session is not registered to any of the Delivery Controller servers in the site.

Solution 4: Please refer to How to Troubleshoot Virtual Delivery Agent (VDA) Registration issues to resolve VDA registration issue.

Cause 5: There are insufficient random/non-persistent Windows desktop VDA machines available for the user to successfully launch one.

Solution 5: Please power on more VMs in the Delivery Group or add more VDA machines to the Delivery Group.

Cause 6: Pass-through authentication to Citrix Workspace app is attempted but the XML trust service is not correctly configured.

Solution 6: Please run the following PowerShell command as an administrator on the Delivery Controller:

Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $True

Cause 7: SSL related registry settings under “HKLMSYSTEMCurrentControlSetControlTerminal ServerWdsicawd” are rolled back to the default values after installing CU on VDA 1912 LTSR. (This is problem only when HdxSslEnabled is true on your delivery group.)

Solution 7: Please refer to Configure TLS on a VDA using the PowerShell script and enable TLS with “Enable-VdaSSL.ps1” on VDA. This is a bug. Investigation is in progress under CVADHELP-17421. Please contact technical support if you need help.

Related:

  • No Related Posts

Receiver 4.0 for Windows Unable to Use Least Loaded Server Using Custom ICA file with “HTTPBrowserAddress=”

This article is intended for Citrix administrators and technical teams only.

Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.

When using Receiver version 4.0 and a custom ICA file with a value set for an Application name for the tag “HTTPBrowserAddress=”, it might not be possible to connect to the least loaded server.

Steps to reproduce the issue:

  1. Install Receiver for Windows 4.0.
  2. Try to launch a published application via Citrix Quick Launch tool.

    Ensure “Launch on this server” check box is cleared.

Expected behavior: The application can be launched successfully.

Actual behavior: Cannot launch the application. The following message is displayed:

“Unable to launch your application. Contact your help desk with the following information: Cannot connect to the Citrix XenApp server. There is no Citrix XenApp server configured on the specified address.”

Related:

  • No Related Posts

Receiver for Mac Support on macOS Sierra (macOS 10.12) Beta Builds

This article is intended for Citrix administrators and technical teams only.



Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.


The Citrix Receiver for Mac team is working on product updates to support the upcoming release of macOS Sierra (macOS 10.12) in Fall 2016. Citrix is committed to provide zero-day compatibility for Receiver for Mac when Sierra is generally available. Zero-day compatibility means Receiver for Mac will operate with the new operating system platform from Apple at release.

In addition to zero-day compatibility, Citrix is reviewing new features that take advantage of Sierra. We will keep our customers informed as we learn more about the changes needed to support any of the new features.

The Sierra beta is available to the general public. Based on our early assessment of the current beta, we are aware of issues making ICA connections over SSL using Receiver 12.1.100 for Mac. Citrix has started to fix gaps and areas of incompatibilities with Sierra to ensure our commitment to Zero-day compatibility.

Receiver for Mac 12.2 (available August 1, 2016) does not suffer from the SSL issue on Sierra. Be aware however that Sierra beta is still not a supported platform. If Apple releases a new Sierra beta that causes Receiver for Mac to stop working, there is no guarantee that we will release a fix before the official release of Sierra. Citrix recommends that our customers not install the Sierra beta in production.

Related:

  • No Related Posts

“.NET Framework Initialization Error” on Receiver

This article is intended for Citrix administrators and technical teams only.

Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.

If a computer has .NET Framework version 4 installed and there are no older versions of the .NET Framework, .NET Framework initialization error messages are displayed in the following scenarios:

  • Scenario 1: When you start Citrix Receiver earlier than version 3.0 from the Start menu, the following error message is displayed:

    "ControlPanel.exe - .NET Framework Initialization ErrorUnable to find a version of the runtime to run this application."

    Note: Citrix Receiver earlier than version 3.0 does not start automatically during installation.

  • Scenario 2: Citrix Receiver Updater 3.0 for Windows is installed without errors. The first time you select the Preferences option, the Citrix Receiver – Preference dialog box is not displayed. The .NET initialization error message is displayed. This message is not displayed during subsequent attempts.

    Note: Occasionally, the Updater.exe – .NET Framework Initialization Error message is displayed.

  • Scenario 3: When you start the Citrix Receiver Settings applet from the Windows Control panel, the .NET Framework initialization error message is displayed.

Occasionally, application error messages are displayed in addition to the .NET Framework initialization error messages.

Related:

  • No Related Posts

Error: “There are no apps or desktops assigned to you at this time” after Logging into StoreFront

CTX141317 – NetScaler Gateway 10.5, Maintenance Release 54.9

Known Issue: When you use the Set Up NetScaler for XenApp/XenDesktop wizard in NetScaler, apply optimization settings, and bind the cache policy globally, when users log on with the NetScaler Gateway Plug-in and open Citrix Receiver, the applications and desktops do not appear. The following message appears: There are no apps or desktops assigned to you at this time. Citrix recommends disabling the optimization settings.

[From NG_10_5_53_9][#411152]

Related:

  • No Related Posts

Error “XDDS: 2367399E Cannot Create a Catalog Using AWS Host : Image Preparation VM Failed, Message No Facility Available for Disk Upload”

Exception:

Citrix.Console.Models.Exceptions.ProvisioningTaskException A volume service instance could not be launched in your cloud connection. In Studio, select Hosting in the left pane and then select the cloud connection. Click Test Connection in the Actions pane. The test results should provide additional information.

at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.CheckForTerminatingError(SdkProvisioningSchemeAction sdkProvisioningSchemeAction)

at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.WaitForProvisioningSchemeActionCompletion(Guid taskId, Action`1 actionResultsObtained)

at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.StartProvisioningAction()

at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.RunTask()

at Citrix.Console.PowerShellSdk.BackgroundTaskService.BackgroundTask.Task.Run()

DesktopStudio_ErrorId : UnknownError

ErrorCategory : NotSpecified

ErrorID : NoDiskContentTransferService

TaskErrorInformation : Terminated

InternalErrorMessage : No facility available for disk upload.”,””

Related:

  • No Related Posts