- #CITRIX VIEWER INITIALIZATION FAILED HOW TO#
- #CITRIX VIEWER INITIALIZATION FAILED UPDATE#
- #CITRIX VIEWER INITIALIZATION FAILED WINDOWS#
#CITRIX VIEWER INITIALIZATION FAILED HOW TO#
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. If AD-based discovery is configured to be used, find and validate the Organizational Unit (OU) for the farm in an Active Directory (AD).
#CITRIX VIEWER INITIALIZATION FAILED UPDATE#
The initialization for the Broker component is as explained in the following procedure:Ĭonnect the Broker component to the Broker tables of the database server.ĭetect any database server update scripts and add that version changing capability to the device. The following sections outline the key operations in the parallel initialization of the components: Broker Component Initialization The primary components are initialized in a sequence but run in parallel initialization, such as Broker, XML Service, and Hosting Management. The Broker service functionality is grouped into distinct components. The initialization sequence occurs over multiple threads of execution, so the event messages might be generated in a different order other than the one explained in the preceding sequence.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. The service cannot run with an account other than Network Service.Ī fatal exception encountered early during the start-up of the service results in an event log message 501 being generated. The following entries include event log message Type, Event ID, and Notes regarding the root cause:Ĭheck the identity of the account that the service is running as The initialization sequence is outlined in the following list, which also indicates where the event log messages might be generated. The service initialization follows dependency load.
#CITRIX VIEWER INITIALIZATION FAILED WINDOWS#
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 “\圆4\Citrix Desktop Delivery Controller\Broker_Service_圆4.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. To resolve the preceding issues, you can either repair the installation or re-install the service. Refer to CTX129510 - XenDesktop 5 Error 1053: Could not start the Citrix Service on Local Computer for more information. Error details: Exception '1' of type 'Configuration system failed to initialize'. To avoid excessive event logging, the service is suppressing related messages (event ID 502) until the problem is resolved. A previously detected problem still exists. The Citrix Broker Service failed to initialize again. The service might also fail to start or initialize if the configuration file, is unusable, for example, by an attempt to edit the settings for the service. This process might fail if any of the dependencies are missing or becomes unusable. When BrokerService.exe file starts, the device first load dependent Dynamic Link Library (DLLs) before control is passed to the program code. To troubleshoot the Citrix Broker Service Startup issues, complete the following procedure: Troubleshooting Citrix Broker Service Startup