XCOMN0473E error(s) parsing xcom.glb; The XCOMD CA-XCOM Scheduler Service cannot start in the xcom.log and Service Specific Error Code 473 Starting the CA XCOM XCOMD Scheduler Service. How to troubleshoot and resolve these errors.
XCOM Data Transport for Windows
There are two possible causes:
To trace the parsing of the xcom.glb file to determine where the error is:
NOTE: CA XCOM will automatically remove the trace.trc file from the trace subdirectory after the time period specified by the EXPIRATION_TIME parameter in xcom.gbl has passed.
Previously up through Windows 2012: By default the encoding of the xcom.glb file was UTF-8, but when edited with Notepad and saved, Notepad altered the encoding and saved it as UTF8 BOM. XCOM is unable to handle that type of file, and that is why the xcomd service wouldn't start.
However Microsoft made changes to the Notepad application as part of the Windows update 19H1 (version 1903) released on May 21, 2019. After this update, the GLB file can be modified with Notepad and there should not be any problems as Notepad is modified to preserve the File encoding when being modified. Also, it will use "UTF8 without BOM" as a default encoding to save the files.