Windows could not start the XCOMD CA XCOM Scheduler service

Products

• XCOM Data Transport
• XCOM Data Transport - Windows

Issue/Introduction

XCOM for Windows service XCOMD does not start and this message is seen:

Windows could not start the XCOMD CA XCOM Scheduler service on
Local Computer. For more information review the System Event Log. 

There may also be an extra message:

If this is a non-Microsoft service, contact the service vendor, and refer
to service-specific error code nnn.

Environment

XCOM™ Data Transport® for Windows
Releases: 11.6 SP03, 12.0

Resolution

1. For service-specific error code 473 please see article 4011: Windows could not start the XCOMD CA XCOM Scheduler service with code 473
   
   
2. If this occurs immediately after a new install please try an uninstall and reinstall.
   
   
3. If the problem persists after a reinstall please collect the following information and upload it via a new XCOM support case created on the Broadcom Support Portal:
   
   
   1. Provide more details i.e.
      Either: The error occurred the first time the XCOMD service was started immediately after the initial install.
      Or: XCOMD had previously started successfully and this problem occurred later.
      
      
   2. Upload a screenshot of the full error message dialog box showing any other "service-specific error code".
      
      
   3. If an xcom.log file exists in directory set by environment variable XCOM_HOME i.e. "%XCOM_HOME%" (defaults to "C:\Program Files\CA\XCOM"), upload it to the case. Also upload a zipped copy of the "%XCOM_HOME%\config\xcom.glb" (zipping will preserve the file format/encoding in case that is causing the problem)
      
      
   4. Start a command prompt and run these commands:
      *****
      C:\>cd %XCOM_HOME%
      C:\Program Files\CA\XCOM>xcomqm -r
      *****
      The 'xcomqm -r' command will display the fix level of XCOM and also will parse the configuration files to check for any potential errors.
      Upload the output of the command.
      
      
   5. Review the Windows Event Viewer sections "Windows Logs > Application" and ""Windows Logs > System".
      Use right mouse button on sections Application and System & then use Find for string "xcomd" to see if any error events are listed.
      Upload the details e.g. stack traces of any events found.
      
      
   6. Upload the version of Windows being used.