How to Enable the Streaming Client Debug Console

Note: The following procedure must be completed on the server if “Streaming to Server” is required and on the workstation if “Streaming to Client” is required.

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

To enable the Streaming Client Debug Console on a 32-bit device

Make the following changes to the registry on the machine that is running the Streaming Client:

Under HKEY_LOCAL_MACHINE/Software/Citrix/Rade/

ADD DWORD “EnableDebugConsole”

ADD Value =1

To enable the Streaming Client Debug Console on a 64-bit device

Make the following changes to the registry on the machine that is running the Streaming Client:

Under HKEY_LOCAL_MACHINE/Software/Wow6432/Citrix/Rade/

ADD DWORD “EnableDebugConsole”

ADD Value =1

Note: The Streaming Client Debug Console sends the real-time information to the command prompt and not to a text file.

To save the data

  1. Use the MARK/COPY/PASTE options. Use MARK, then select ALL, and then COPY.

  2. Paste the text into Notepad.

Note: For large applications, it might be necessary to increase the buffer in the command prompt before running the Streaming Client Debug console (edit the properties of the command prompt).

To disable the Streaming Client Debug Console

To disable the debugger, change the EnableDebugConsole value from 1 to 0.

Related:

XDDS:6D813B19 – “An error has occurred with the Citrix License Server. Check the license server to make sure it is running, then try again.” on the Search node in Citrix Studio.

The error message “An error has occurred with the Citrix License Server. Check the license server to make sure it is running, then try again.” might be displayed on the Search node in Citrix Studio when user opens or refreshes the node.

Error details:



Error Id: XDDS:6D813B19

Exception:

Citrix.Console.Common.CitrixAggregateException One or more parallel operations failed

at Citrix.Console.Common.CitrixParallel.InternalForEach[TIn](IEnumerable`1 items, Action`1 operation, Int32 maxSimultaneous)

at Citrix.Console.PowerShellSdk.SiteInformationService.SiteInformationService.Refresh()

at Citrix.Console.Desktops.UI.Mmc.Tabs.VdiMachineTabViewModel.<AddRefreshHandlers>b__4_0(Object s, EventArgs e)

at Citrix.Console.CommonControls.Mmc.SearchNodeTabViewModel`1.<>c__DisplayClass54_0.<PerformSearchInternal>b__0()

at Citrix.Console.CommonControls.ViewModelBase.<>c__DisplayClass90_0.<RunBackgroundTask>b__0(Object s, DoWorkEventArgs e)


Inner Exception:

Citrix.Console.Models.Exceptions.ScriptException An error has occurred with the Citrix License Server. Check the license server to make sure it is running, then try again.

at Citrix.Console.PowerShellInteraction.CmdletExecutionMethods.CreateException[T](ICommonLog logger, ExecutionResults`1 results, ICmdletExecutionHost host)

at Citrix.Console.PowerShellInteraction.CmdletExecutionMethods.Execute[T](ISdkCmdlet`1 sdkCmd, ICmdletExecutionHost host, Boolean allowFailover)

at Citrix.Console.PowerShellSdk.LicensingService.Scripts.GetCertificateScript.RunScript()

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

at Citrix.Console.PowerShellSdk.SiteInformationService.SiteInformationService.GetLicenseAlert()

at Citrix.Console.PowerShellSdk.SiteInformationService.SiteInformationService.<>c__DisplayClass33_0.<Refresh>b__7()

at Citrix.Console.Common.CitrixParallel.<>c__DisplayClass4_1`1.<InternalForEach>b__0(Object arg)

DesktopStudio_ErrorId : UnknownError

Sdk Error Message : UnknownError

Sdk Error ID : Citrix.PowerShell.LicensingAdminStatus.UnknownError,Citrix.Licensing.Admin.SDK.Commands.GetLicCertificateCommand

ErrorCategory : NotSpecified

DesktopStudio_PowerShellHistory : Get the certificate for the Licensing Service

Date Time

Get-LicCertificate -AdminAddress “https://LICENSE_SERVER_ADDRESS:PORT_NUMBER/”

Get-LicCertificate : UnknownError

+ CategoryInfo : InvalidOperation: (Get-LicCertificate:String) [Get-LicCertificate]、InvalidOperationException

+ FullyQualifiedErrorId : Citrix.PowerShell.LicensingAdminStatus.UnknownError,Citrix.Licensing.Admin.SDK.Commands.GetLicCertificateCommand

Related:

Cannot access non-http traffic via full VPN but telnet works

As the application doesn’t work but telnet works the problem is at layer 7. Looked into the configuration observed a traffic policy configured on the Netscaler Gateway VIP.

The Traffic policy was configured with expression “true”.

The action was for SSO to HTTP services and http.req.xxx expressions were used.

Herein lies the problem, where the policy with expression true will hit for all traffic, but the action being HTTP specific will fail to execute for non-HTTP traffic, due to this the traffic gets dropped and never forwarded to the back-end.

Telnet to the affected non-HTTP services works because it is just the three-way handshake as there is nothing to be processed.

Related:

Secure Web 10.7-cannot compose SMS within the app

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

XD 7.15 LTSR – Installation failed on Local Host Cache Storage Error 1619

When migrating from XD 7.6 LTSR to XD 7.15 LTSR, installation could failed with the following error :

Installation of The Local Host Cache Storage (LocalDB) failed with error code 1619.

User-added image

Installation logs are not giving more details.

=== Verbose logging started: 3/8/2018 14:21:03 Build type: SHIP UNICODE 5.00.9600.00 Calling process: C:WindowsSYSTEM32msiexec.exe ===

MSI (c) (A4:B0) [14:21:03:289]: Resetting cached policy values

MSI (c) (A4:B0) [14:21:03:289]: Machine policy value ‘Debug’ is 0

MSI (c) (A4:B0) [14:21:03:289]: ******* RunEngine:

******* Product: E:SupportSQLLocalDB2014x64SqlLocalDB.msi

******* Action:

******* CommandLine: **********

MSI (c) (A4:B0) [14:21:03:289]: Client-side and UI is none or basic: Running entire install on the server.

MSI (c) (A4:B0) [14:21:03:289]: Grabbed execution mutex.

MSI (c) (A4:B0) [14:21:03:289]: Cloaking enabled.

MSI (c) (A4:B0) [14:21:03:289]: Attempting to enable all disabled privileges before calling Install on Server

MSI (c) (A4:B0) [14:21:03:289]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (80:B4) [14:21:03:289]: Running installation inside multi-package transaction E:SupportSQLLocalDB2014x64SqlLocalDB.msi

MSI (s) (80:B4) [14:21:03:289]: Grabbed execution mutex.

MSI (s) (80:58) [14:21:03:419]: Resetting cached policy values

MSI (s) (80:58) [14:21:03:419]: Machine policy value ‘Debug’ is 0

MSI (s) (80:58) [14:21:03:419]: ******* RunEngine:

******* Product: E:SupportSQLLocalDB2014x64SqlLocalDB.msi

******* Action:

******* CommandLine: **********

MSI (s) (80:58) [14:21:03:421]: Machine policy value ‘DisableUserInstalls’ is 0

MSI (s) (80:58) [14:21:03:426]: Note: 1: 2203 2: C:WindowsInstallerinprogressinstallinfo.ipi 3: -2147287038

MSI (s) (80:58) [14:21:03:429]: SRSetRestorePoint skipped for this transaction.

MSI (s) (80:58) [14:21:03:431]: File will have security applied from OpCode.

MSI (s) (80:58) [14:21:49:798]: Note: 1: 2203 2: C:WindowsInstaller5384d.msi 3: -2147287035

MSI (s) (80:58) [14:21:49:799]: MainEngineThread is returning 1619

MSI (s) (80:B4) [14:21:49:799]: No System Restore sequence number for this installation.

MSI (s) (80:B4) [14:21:49:825]: User policy value ‘DisableRollback’ is 0

MSI (s) (80:B4) [14:21:49:825]: Machine policy value ‘DisableRollback’ is 0

MSI (s) (80:B4) [14:21:49:825]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (80:B4) [14:21:49:828]: Note: 1: 1402 2: HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionInstallerRollbackScripts 3: 2

MSI (s) (80:B4) [14:21:49:828]: Note: 1: 1402 2: HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionInstallerRollbackScripts 3: 2

MSI (s) (80:B4) [14:21:49:828]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

MSI (c) (A4:B0) [14:21:49:841]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

MSI (c) (A4:B0) [14:21:49:842]: MainEngineThread is returning 1619

=== Verbose logging stopped: 3/8/2018 14:21:49 ===

Related:

Unable to Delete Resources: There is currently an active background action

  • From this step, note HostingUnitUid of the Resources that you are trying to delete (highlighted in the preceding screen shot) and then run the following command, substituting HostingUnitUid from your environment:

    Get-ProvTask | Where-Object { $_.ImagesToDelete | Where-Object { $_.HostingUnit -eq “a3284d3e-848c-4f98-ad74-61457b990a7f” } }

    Running the preceding command gives a list of tasks that still need to complete before the Resources can be deleted, and will look similar to the following:

    User-added image

    From the preceding screen shot, it is noticed that the last attempt which was made to delete the disks is in the LastUpdateTime field, and the next attempt that will be made is in the RetryInterval field (specified in hours:minutes:seconds). In this case, the next attempt is made at 10/10/2013 2:48:82 PM.

    To remove this task execute command Remove-ProvTask -TaskID <EnterTaskID>

    If no tasks are listed then all tasks have already been completed. Attempt to remove storage with the following commands:

    Storage :

    Remove-HypHostingUnitStorage -LiteralPath XDHyp:HostingUnitsMyHostingUnit -StoragePath ‘XDHyp:HostingUnitsMyHostingUnitsnewStorage.storage’

    PersonalvDiskStorage:

    Get-ChildItem XDHyp:HostingUnitsMyHostingUnit*.storage | Remove-HypHostingUnitStorage -LiteralPath XDHyp:HostingUnitsMyHostingUnit -StorageType PersonalvDiskStorage

    TemporaryStorage:

    Get-ChildItem XDHyp:HostingUnitsMyHostingUnit*.storage | Remove-HypHostingUnitStorage -LiteralPath XDHyp:HostingUnitsMyHostingUnit -StorageType TemporaryStorage

    Hosting Resource Name

    Remove-Item -path XDHyp:HostingUnitsMyHostingUnit

  • Related:

    • No Related Posts

    How to launch virtual desktop and application without using Citrix Receiver on local machine

    Tradução automática

    Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

    Related:

    • No Related Posts

    How to Upgrade Machine Catalog vCPU

    How to increase the VCPU of MCS provisioned machines.

    The VCPU and memory for a machine in the machine catalog is displayed in the Studio.

    User-added image

    To increase the VCPU follow the following steps

    1) On the XenDekstop controller launch the powershell

    2) Load the snapins asnp citrix*

    3) Run the command Get-ProvScheme “Name of Catalog to Modify VCPU”

    User-added image

    In the image the VCPU is set to be 2.

    4) Run the command

    Set-ProvScheme -ProvisioningSchemeName “Name of Catalog to Modify CPU” -VMCpuCount “Number of CPU you want to add”

    User-added image

    In the Image the VCPU has been increased to 4 from 2

    5) Run the Update catalog wizard from the Citrix Studio

    6) After the wizard completes the check if the VCPU has been modified or not either on the Citrix studio or using the powershell

    User-added image

    User-added image

    Related:

    Optimization of VDA is by default included on VDA upgrade


    VDA optimization is by default included on VDA upgrades. Users will not be able to uncheck the optimization options on VDA upgrade wizard. Refer CTX125874 to understand the Specific Optimizations Performed by the Virtual Delivery Agent 7.x Installer​.

    VDA Upgrade wizard does not list the option Features on which we can select/deselect ‘Optimize performance’. It skips everything before and starts with Firewall tab in the Wizard.

    User-added image
    User-added image

    As part of the optimization, the Maximum Event Log size on the VM will be reduced to 1.028MB (1028KB) from the default size.

    User-added image

    Solution:

    Those who have set additional size for event logs and need these logs on the server for future investigations should back up event logs on the VM before starting the VDA upgrade on it. Since optimization of performance is forcibly applied irrespective of the user’s intention, user data such as event logs disappear by the amount reduced by optimization.

    Note: For example, If a user set their maximum size of the event logs to 1 GB, then after the VDA upgrade it will change to 1028 MB. Because of this, the event log data of about 999 MB is lost. There is no means to restore the logs of the differential capacity which will disappear due to the reduction of the event log file size, unless there is a backup. Hence it is recommended to take a backup of the logs before upgrading VDA.

    You can resize the Event log file size to the desired value manually after the upgrade and restore the backed up logs. (https://technet.microsoft.com/en-us/library/cc748849(v=ws.11).aspx)

    Workaround:

    There is a command line switch that controls this option so that you can avoid the optimizations in an upgrade scenario, which is to do command line upgrade using “XenDesktopVdaSetup.exe /quiet /components vda”, with expected behavior that TargetOSOptimizer.exe will not being called by installer and the maximum event log size does not get reduced.

    Related:

    • No Related Posts

    Can a Citrix Hardware Device run on a Single Power Source.

    Please, refer to the below mentioned article for more reference,

    “https://docs.citrix.com/en-us/netscaler/11-1/netscaler-hardware-installation/field-replaceable-units.html”

    “”Power Supply For appliances containing two power supplies, the second power supply acts as a backup””

    “”Replacing an AC Power Supply Citrix NetScaler MPX platforms can accommodate two power supplies, except the MPX 22040/22060/22080/22100/22120 and MPX 24100/24150 platforms which can accommodate four power supplies. All NetScaler appliances function properly with a single power supply, except the MPX 22040/22060/22080/22100/22120 and MPX 24100/24150 platforms which need two power supplies for proper operation. The other power supplies serves as a backup. All power supplies must be of the same type (AC or DC).””

    “”Replacing a DC Power Supply Citrix NetScaler MPX platforms can accommodate two power supplies, except the MPX 22040/22060/22080/22100/22120 and MPX 24100/24150 platforms which can accommodate four power supplies. All NetScaler appliances function properly with a single power supply, except the MPX 22040/22060/22080/22100/22120 and MPX 24100/24150 platforms which need two power supplies for proper operation. The other power supplies serves as a backup. All power supplies must be of the same type (AC or DC).””

    Related: