Transfer to XCOM Windows fail "XCOMN0602E unable to open queue data file"

Products

• XCOM Data Transport
• XCOM Data Transport - Windows

Issue/Introduction

Remote requests to an XCOM for Windows server fail with the error message:

XCOMN0602E unable to open queue data file

Environment

XCOM™ Data Transport® for Windows 11.6 SP03, 12.0.

Cause

This is normally a security issue. The user id used for the transfer request is missing permission to write to the files within the XCOM queue folder.

Resolution

• Write permission must be given to the folder where the queue data file is.  This is %XCOM_HOME%\q by default.  It can be set to a different location using the QUEUE_PATH parameter in the xcom.glb file in the \config subdirectory.  Each and every XCOM transfer writes into that folder during processing.
  
  
• Write permission must also be given to the folder where the xcom.log file is. This is %XCOM_HOME%\q by default.  It can be set to a different location using the XLOGFILE parameter.

Additional Information

The command icacls can be used to check the required permissions.
After a new XCOM for Windows 11.6 SP03 or 12.0 install below are the correct values for the %XCOM_HOME% and %XCOM_HOME%\q directories:

C:\>icacls "%XCOM_HOME%"
C:\Program Files\CA\XCOM NT SERVICE\TrustedInstaller:(I)(F)
                         NT SERVICE\TrustedInstaller:(I)(CI)(IO)(F)
                         NT AUTHORITY\SYSTEM:(I)(F)
                         NT AUTHORITY\SYSTEM:(I)(OI)(CI)(IO)(F)
                         BUILTIN\Administrators:(I)(F)
                         BUILTIN\Administrators:(I)(OI)(CI)(IO)(F)
                         BUILTIN\Users:(I)(RX)
                         BUILTIN\Users:(I)(OI)(CI)(IO)(GR,GE)
                         CREATOR OWNER:(I)(OI)(CI)(IO)(F)
                         APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(I)(RX)
                         APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(I)(OI)(CI)(IO)(GR,GE)
                         APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(I)(RX)
                         APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(I)(OI)(CI)(IO)(GR,GE)

C:\>icacls "%XCOM_HOME%\q"
C:\Program Files\CA\XCOM\q Everyone:(OI)(CI)(F)
                           NT SERVICE\TrustedInstaller:(I)(F)
                           NT SERVICE\TrustedInstaller:(I)(CI)(IO)(F)
                           NT AUTHORITY\SYSTEM:(I)(F)
                           NT AUTHORITY\SYSTEM:(I)(OI)(CI)(IO)(F)
                           BUILTIN\Administrators:(I)(F)
                           BUILTIN\Administrators:(I)(OI)(CI)(IO)(F)
                           BUILTIN\Users:(I)(RX)
                           BUILTIN\Users:(I)(OI)(CI)(IO)(GR,GE)
                           CREATOR OWNER:(I)(OI)(CI)(IO)(F)
                           APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(I)(RX)
                           APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(I)(OI)(CI)(IO)(GR,GE)
                           APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(I)(RX)
                           APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(I)(OI)(CI)(IO)(GR,GE)

NOTES:
The user id assigned to a remote transfer is determined by: 

• Transfer parameters specified by the partner (USERID=, PASSWORD= and optionally DOMAIN=). If domain is specified, the user id needs to be defined in the domain. Otherwise it needs to be defined locally in the Windows box. 
  
  
• If the incoming transfer does not specify user credentials, the default user id set by xcom.glb parameters XCOM_USERID and XCOM_PASSWORD is used. 
  
  
• If no default use rid is set, the transfer runs under the security inherited from the xcomd service. 
  
  

Please use Contact Support - Broadcom Software if further assistance is required.