XCOM does not start ERROR 193 : 0xc1

Products

XCOM Data Transport XCOM Data Transport - Windows XCOM - SUPPORT

Issue/Introduction

Just installed XCOM Data Transport for Windows Server. Based on documentation first thing to do is to start windows scheduler service.

And

The action returned the following error:

Below Windows Event Log

The XCOMD CA XCOM Scheduler Service service failed to start due to the following error:
XCOMD CA XCOM Scheduler Service is not a valid Win32 application.

Below a subset of “xcomjni.tra”

========================================================================
                === CA XCOM Data Transport Trace r11.6 17090 SP02 64bit for Windows Family (TCP/IP)
                === Copyright (c) 2012 CA. All rights reserved.
                === Starting XCOM6.2 Trace
                === Trace_File is C:\Program Files\CA\XCOM\trace\xcomjni.tra
                ========================================================================

DEFAULT PARMBLOCK INITIALIZATION

Wed Aug 28 09:03:44 2019
                parmblk   662: InitParmblock: initializing at p=1381268528
                parmblk   719: Allocated 2 bytes at 0000000000E2B7B0.
                parmblk   755: InitParmblock: TRANSFER_TYPE(4):=3(0000000000E2B7B0)
                parmblk   719: Allocated 65 bytes at 0000000000E14F90.

........

                parmblk   719: Allocated 4 bytes at 0000000000E325C0.
                parmblk   755: InitParmblock: GATEWAYONWARD(487):=NO(0000000000E325C0)
                util      628: Allocated 33 bytes at 0000000000E277A0.
                util      628: Allocated 41 bytes at 0000000000E1C620.
                util     1261: xfree: freeing 0000000000E277A0
                util      521: xfree: freeing 0000000000E1C620
                set_config_file_name: name=C:\Program Files\CA\XCOM\config\xcom.cnf
                util      628: Allocated 33 bytes at 0000000000E277A0.
                util      628: Allocated 41 bytes at 0000000000E1C820.
                util     1261: xfree: freeing 0000000000E277A0
                util      521: xfree: freeing 0000000000E1C820
                util      628: Allocated 33 bytes at 0000000000E277A0.
                util      628: Allocated 41 bytes at 0000000000E1C620.
                util     1261: xfree: freeing 0000000000E277A0
                util      521: xfree: freeing 0000000000E1C620
                Opening queue with name: 000026
                sdu.c(1549) Error in OpenFileMapping : Error 2
The system cannot find the file specified.

                util      628: Allocated 14 bytes at 0000000000E32F40.
                sdu      1552: xfree: freeing 0000000000E32F40
                sdu.c(1555) Error in OpenFileMapping(Global) : Error 2
The system cannot find the file specified.

GetSharedSeg returned 0000000000000000
XCOMN0461E Cannot get shared memory.

                OpenPublicQ: Returning Qrcode= -9900 Returning rc= -9900
                XcomJNI_1init reports that CA XCOM Scheduler is down
                XcomJNI_1init end
                XcomJNI_1getOSType ending with OSType 105
Wed Aug 28 09:03:45 2019
                XcomJNI_1isXcomUp reports that CA XCOM is down

Environment

XCOM Data Transport for Windows 11.6

Cause

This issue is caused when a file or folder called "C:\Program" is present on the installation drive.

Resolution

There is a known problem on Windows with same symptoms - more details here: "Event ID 7000 and "%1 Is Not a Valid Win32 Application" Error Message When You Start a Service"
https://support.microsoft.com/en-us/help/812486/event-id-7000-and-1-is-not-a-valid-win32-application-error-message-whe
===
This issue may occur if the path of the executable file for the service contains spaces.
When Windows starts a service, it parses the path of the service from left to right.
If both of the following conditions are true, Windows may locate and try to run the file or folder before it locates and runs the executable file for the service:
The path of a service’s executable file contains spaces.
There is a file or folder on your computer’s hard disk that has the same name as a file or folder in the path to the service's executable file.
For example, if the path of the executable file for a service is C:\Program Files\MyProgram\MyService.exe,
and if a folder that is named C:\Program also exists on your hard disk, Windows locates the C:\Program folder on your hard disk before the C:\Program Files\MyProgram\My Service.exe file, and then tries to run it.
===
The XCOM service "xcomdsrv" ImagePath C:\Program Files\CA\XCOM\xcomd.exe does contain spaces

Client found file named c:\Program file and renaming it to "c:\Program1" resolved the problem.

Additional Information

If the File Name warning below appears when starting a new interactive session

Choose "Rename". This will rename the offending File or Folder to "C:\Program1" and the issue will be corrected.