Scribd
Upload
167 views7 pages

Xendeskto

This document provides troubleshooting steps for various errors that may occur when launching virtual desktops or applications through Citrix XenApp/XenDesktop, including: - No Desktop Machine is Available (Event 1101) - No suitable machines were available to satisfy the launch request. Ensure enough machines are added and none are in maintenance mode. - Desktop Machine Refused Connection (Event 1102) - The agent on the selected machine refused the launch request. Ensure the machine is configured correctly and check its event log. - Desktop Machine Session Already Active (Event 1103) - The selected machine already had an active session. Allow reconnection if needed by changing a registry entry. - Desktop Machine in M

Uploaded by

sudharaghavan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
167 views7 pages

Xendeskto

This document provides troubleshooting steps for various errors that may occur when launching virtual desktops or applications through Citrix XenApp/XenDesktop, including: - No Desktop Machine is Available (Event 1101) - No suitable machines were available to satisfy the launch request. Ensure enough machines are added and none are in maintenance mode. - Desktop Machine Refused Connection (Event 1102) - The agent on the selected machine refused the launch request. Ensure the machine is configured correctly and check its event log. - Desktop Machine Session Already Active (Event 1103) - The selected machine already had an active session. Allow reconnection if needed by changing a registry entry. - Desktop Machine in M

Uploaded by

sudharaghavan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 7

http://svkit.com/joomla/index.

php/citrix/xenapp-xendesktop-7-5/151-06-provisioningservices-power-management-and-vdisks
https://support.citrix.com/article/CTX126991

Background
When the user requests a connection to a virtual desktop, a number of tests are performed and checks
made to select the correct virtual desktop to which they must be connected. If one or more of these tests
fails in some way, the desktop launch is refused and the user is informed that the resource is
unavailable. An event log message is also produced on the DDC machine describing why the launch
was refused, and this article is to aid troubleshooting these situations.

No Desktop Machine is Available (Event 1101)


No suitable desktop machine was found which was ready to satisfy the failing launch. This might be
because of some machines being marked as in maintenance mode, or simply running out of desktop
machines. Either add more desktop machines to the site using the Desktop Studio console, or remove
the maintenance mode setting on one or more of the relevant desktops or machines using the Desktop
Studio console or the Broker PowerShell SDK.

Desktop Machine Refused Connection (Event 1102)


The agent software running on the select desktop machine actively refused a request to make the
machine ready to accept a connection from the user. If registry-based controller discovery is in use,
which is the default mechanism, ensure that the desktop machine in question has been configured with
a list of controllers that includes the controller that attempted the failed launch. See CTX118976 - How
to Configure XenDesktop to Function Without an Organizational Unit in Active Directory.
Examine the event log on the desktop machine in question for further error indications, and if necessary
use logging of the workstation agent service to capture traces of the launch sequence actions.

Desktop Machine Session Already Active (Event 1103)


The desktop whose launch failed was already running a connected session for the user and active
session reconnected has been configured to be disabled. If active session reconnection must be allowed,
change the value of the DisableActiveSessionReconnect registry entry. See CTX126704 - Registry
Entries Used by XenDesktop 5.x Broker Service for a description of this and other registry entries.

Desktop Machine in Maintenance Mode (Event 1105)


The desktop or machine selected to be used for the launch is currently flagged as being in maintenance
mode. This might be because the user already has a session on that machine, which prevents the system
choosing to use another machine for that user, or the machine might be permanently assigned to the
user. Either remove the maintenance mode setting on the desktop or machine using the Desktop Studio
console or the Broker PowerShell SDK, or end the running session on the desktop or remove the

permanent assignment.

Requested Protocol Type is Not Supported (Event 1106)


The protocol requested to be used for the failing launch, for example HDX or RDP, is not supported to
be used with the selected desktop machine. The protocols, which are supported, can be configured
through the Broker PowerShell SDK, using the cmdlets relating to the Access Policy Rule (see the
about_Broker_AccessPolicy help topic).

Application is Disabled (Event 1107)


VM-Hosted application, which defines the failing launch application, is marked as disabled. If
required, enable the application through the Broker PowerShell SDK, using the Set-BrokerApplication
cmdlet.

Desktop Machine already has a Session (Event 1108)


The desktop or machine selected to be used for the launch is already running a session, and this session
is not suitable to be used in the failing launch circumstances. This might occur if a desktop has been
permanently assigned to a user, but then a different user logs on to the machine, for example through
the machine console. End the running session on the desktop or remove the permanent assignment.

Desktop No Longer Available (Event 1109)


The desktop group, which would provide the desktop for the failing launch is marked as disabled or has
been deleted. If the desktops available to the user are re-evaluated, for example, the user logging on to
Web Interface again, this resource would not be offered to the user. If required, enable the desktop
group through the Broker PowerShell SDK, using the Set-BrokerDesktopGroup cmdlet.

Other Launch Failure (Event 1100) or Other Launch Failure on Reconnect (Event
1104)
If the launch failure cannot be categorized to a particular failure reason, one of these events occurs.

Machine Start Failures (Event 3012)


The behavior occurs when XenDesktop fails to start the required machine for the requested session. If
the machine is running on a hypervisor, this might occur when the hypervisor is Off, the hypervisor
does not have enough resources to launch the virtual machine (for example out of memory) or VDA is
in maintenance mode.

The connection to "virtual_desktop" failed with status (1110)


Unable to access XenApp/XenDesktop with internet error: "The connection to "virtual_desktop" failed
with status (1110)".
To resolve this, change self-signed Root CA certificate common name from wildcard to regular one.

The applications/desktop can be launched.


Refer to Citrix Discussions: Failed with status (1110) and CTX200890 - Error: "Failed with status
1110" When Launching Desktops or Apps Through NetScaler Gateway.

Troubleshooting Actions
If the preceding descriptions of the event circumstances do not provide sufficient clues to determine the
problem, logging of the Citrix Broker Service must be used to capture traces of the launch sequence
actions. So, collect CDF tracing, and select the following modules to be traced:
CdsController
CdsBroker
CdsXmlServices
ControllerDAL
BrokerDAL
CdsLicensing
CdsHostingManagement
CdsTicketStore
CdsHostingPlugin
CdsInterService
PRODLIC_Library_Common
PRODLIC_LicPolEng

Citrix Personal vDisk Failed to Start Status


Code 7 Error 0xb7
Issue
On Citrix XenDesktop 5.6, you receive the following error when logging on to a desktop:
Citrix Personal vDisk failed to start.
Status code: 7
Error code: 0xb7

Cause
Most likely the drive selected in Desktop Studio wizard user interface (or Provisioning Services
XenDesktop wizard user interface) was V.
Personal vDisk utilizes now two drive letters which default to P and V. The Desktop Studio Wizard
(or Provisioning Services XenDesktop wizard user interface) does not present the option for the second
drive which by default is V.

Resolution
In order to avoid this issue simply avoid selecting V as the drive letter in the Wizard interface.

If you still need to use V as the drive letter, then you can change the following registry key to some

other drive letter so that it will not conflict with the drive letter in the XenDesktop Setup wizard.
Key : HKEY_LOCAL_MACHINE\Software\Citrix\personal vDisk\Config
Value : VHDMountPoint [REG_SZ]
Set this to the drive letter of your choice. Ensure that :\ is appended to the end of your entry
(Example: X:\ )
For further information, refer to article http://support.citrix.com/article/CTX131432

Citrix Broker Service fails to initialize XML


services with the error: "'Input string was not in
a correct format"
Solution
To resolve the issue, complete the following steps on the Xendesktop Delivery Controller:
1. Run the following command:
LodCtr.exe /R
2. Start perfmon service from Services Console.
3. Restart Citrix Broker Service.
Note: When you restart Broker Service, all the events related to the XML must stop.

Error: "Power State Unknown" in XenDesktop


Solution
To update the correct host machine ID on the DDC, complete one of the following solutions:

Solution 1
Restart the Citrix Site services on all the DDCs.
Note: This may result in momentary disruptions of new connections, however current
sessions are not affected.ObjectType : Vm
Open PowerShell as admin and run the following commands:
Get-Service Citrix* | Stop-Service -Force

Get-Service Citrix* | Start-Service


Id : 7d1d6004-5319-7a7e-59cb-2662e212a3e5
IsContainer : True
IsMachine : True
IsSnapshotable : True
ObjectPath : /PVS0003.vm
FullPath : XDHyp:\Connections\XenServer\PVS0003.vm
IsSymLink : False
AdditionalData : {}

Note: The machine ID is as follows:


Id : 7d1d6004-5319-7a7e-59cb-2662e212a3e5.
Your result will vary.
1. Run the following command:
Get-BrokerMachine -PowerState Unknown
This identifies the machines that have the unknown power state. Compare the resulting Machine
Ids to the response from the hypervisor.
2. Run the following command to change the XendDesktop Database's record for the machine ID
to match the Hypersvisor's Machine ID:
Set-BrokerMachine -MachineName 'MyDomain\MyMachine' -HostedMachineId
[machine ID from preceding output]
This corrects the HostedMachineId for the problem machines using the ID that was retrieved
from xdhyp.txt.
3. Check Desktop Studio or Desktop Director and refresh the list of results.
The power state must now match the state indicated in the hypervisor.
Note: It might be necessary to restart the Citrix Broker Service on all DDCs and/or restart the virtual
machine.

Solution 3
Remove the affected virtual machines from the Desktop Group in Desktop Studio and add them again.
NOTE: Removing machines from an MCS catalog cannot be reversed. Once the VM is removed you
will only be able to add that machine to a catalog of the "Existing" type.

Solution 4
Ensure the SCVMM console version and hotfix level, installed on the DDCs, is the same version and
hotfix level as the SCVMM server.
For example: Install the upgraded version of the SCVMM Console, version 8, KB3097539 on both
controllers, which matched the SCVMM server hotfix level.

Problem Cause
The DDC must communicate with the hypervisor using the virtual machine ID. If the DDC has an
incorrect machine ID for the virtual machine, it is unable to read the machine power state and throws
an exception in the broker log. If the power status is Unknown, the DDC will not be able to manage
any power functions on the virtual machine.

Solution 2
This can be caused by changes made on the hypervisor to VM metadata. If the VM's unique ID has
changed then the XenDesktop database may be unaware of this UID mismatch. This process will verify
the UID known to XenDesktop for the VMs and compare against the UID provided by the hypervisor.
Warning! Back up the XenDesktop database before completing these actions.
4. Open DDC using the PowerShell console and run the following commands to display all
machine IDs of the virtual machines from the hypervisor. .
asnp Citrix*
$ErrorActionPreference=Continue
Get-ChildItem -Path XdHyp:\ -force -recurse | ?{ $_.IsMachine } | Out-File
Filepath c:\xdhyp.txt

5. The xdhyp.txt output file contains the correct machine IDs from the hypervisor. Open that file
and press Ctrl+F or Edit > Find. Search for the name of the Virtual Machine, in this case the
name of the Virtual Machine is PVS0003.
Example output
PSPath :
Citrix.Host.Admin.V1\Citrix.Hypervisor::XDHyp:\Connections\XenServer\PVS0003.
vm
PSParentPath :
Citrix.Host.Admin.V1\Citrix.Hypervisor::XDHyp:\Connections\XenServer
PSChildName : PVS0003.vm
PSDrive : XDHyp
PSProvider : Citrix.Host.Admin.V1\Citrix.Hypervisor
PSIsContainer : True
Name : PVS0003
FullName : PVS0003.vm
http://www.rootzones.net/2014/01/citrix-xendesktop-interview-question.html

You might also like