Troubleshooting XenDesktop Service Startup Issues

This article contains information about troubleshooting Citrix Broker Service startup issues in the XenDesktop 5 site. These issues can be identified by the event log messages.

Background

Startup of the Citrix Broker Service Windows service on a device in a XenDesktop site generates a number of error logs.

For troubleshooting Citrix Broker Service startup issues in the XenDesktop 5 site, complete the following procedures. The Citrix Broker Service Startup has the following initializations:

• Broker Component Initialization

• Hosting Management Component Initialization

Troubleshooting Citrix Broker Service Startup

To troubleshoot the Citrix Broker Service Startup issues, complete the following procedure:

When BrokerService.exe file starts, the device first load dependent Dynamic Link Library (DLLs) before control is passed to the program code. This process might fail if any of the dependencies are missing or becomes unusable. The service might also fail to start or initialize if the configuration file,?? BrokerService.exe.config?? is unusable, for example, by an attempt to edit the settings for the service.

CTX127492 -?? How to Enable the Controller Service Logging Feature of XenDesktop 5

Log Name: Application

Source: Citrix Broker Service

Date: 4/17/2013 4:59:55 PM

Event ID: 503

Task Category: None

Level: Warning

Keywords: Classic

User: N/A

Computer: XD5A.2k8.com

Description:

The Citrix Broker Service failed to initialize again. A previously detected problem still exists. To avoid excessive event logging, the service is suppressing related messages (event ID 502) until the problem is resolved. Initialization attempts will continue. Error details: Exception '1' of type 'Configuration system failed to initialize'.

Refer to CTX129510 -?? XenDesktop 5 Error 1053: Could not start the Citrix Service on Local Computer?? for more information.

To resolve the preceding issues, you can either repair the installation or re-install the service. To repair the installation, you must use the?? msiexectool specifying the /f?? command line switch (to select installation repair) and the path of the?? MSI install?? file (that installed the controller service), which is on the installed CD as?? “\x64\Citrix Desktop Delivery Controller\Broker_Service_x64.msi” or?? “\x86\Citrix Desktop Delivery Controller\Broker_Service_x86.msi", depending on whether the controller is a 64-bit or 32-bit Windows system.

The service initialization follows dependency load.

The initialization sequence is outlined in the following list, which also indicates where the event log messages might be generated. The following entries include event log message Type, Event ID, and Notes regarding the root cause:

Initialization begins

Info

500

Initialization has started

Check the identity of the account that the service is running as

Error	1000	The service cannot run with an account other than Network Service.
Error	501	A fatal exception encountered early during the start-up of the service results in an event log message 501 being generated. The exception type or message provided in the Error details section of the event log message may provide some indication of the source of the problem, but problems of this type may indicate a systemic issue with the DDC machine, in which case a machine reboot may help, or a re-install of the DDC components may be required.

Info

509

Early initialization completed successfully.

Warn	504	Cannot contact database.
Info	505	Successfully contacted database.

Initialize Broker component

Error	1001	Any of a number of operations (see Broker Component Initialization) may have failedCheck the exception data included in the message for clues.
Warn	1003

Error	2000	Any of a number of operations (see Xml Service Component Initialization) may have failed. Check the exception data included in the message for clues.
Warn	2001
Info	2003	Successfully initialized XML service.

Warn	3001	Any of a number of operations (see Hosting Management Component Initialization) may have failed. Check the exception data included in the message for clues.
Info	3000	Successfully initialized hosting management component.

An error occurred during initialization. The service will retry later.

Warn

502

Any of a number of operations may have failed. Check the exception data included in the message for clues.

Initialization complete

Info

506

Initialization has completed

Notes:

The Broker service functionality is grouped into distinct components. The primary components are initialized in a sequence but run in parallel initialization, such as Broker, XML Service, and Hosting Management. The following sections outline the key operations in the parallel initialization of the components:

Broker Component Initialization

The initialization for the Broker component is as explained in the following procedure:

1. Connect the Broker component to the Broker tables of the database server.

2. Detect any database server update scripts and add that version changing capability to the device.

3. If AD-based discovery is configured to be used, find and validate the Organizational Unit?? (OU) for the farm in an Active Directory (AD).
   Notes:
   This preceding step is only performed when the configuration is set such that an OU is required in an AD.Refer to the Knowledge Center article CTX118976 -?? How to Configure XenDesktop to Function Without an Organizational Unit in Active Directory?? for more information.
   This is not the default setting for XenDesktop 5.

4. Purge any out-of-date tickets in the Windows Kerberos cache.

5. Start the Web services offered by the Broker service.

6. Update the Service Connection Point (SCP) object in an AD for this controller device.

   Note: This preceding step is only performed when the configuration is set, such that an OU is required in an AD. Refer to the Knowledge Center article CTX118976 -?? How to Configure XenDesktop to Function Without an Organizational Unit in Active Directory?? for more information.

7. Connect to the license server.

8. Receive registrations from any Virtual Desktop (VD) device.

XML Service Component Initialization

The initialization for XML Service component is as explained in the following procedure:

Hosting Management Component Initialization

The initialization for Hosting Management component is as explained in the following procedure: