XCOM transfer to windows "XCOMN0602E General error in queue function; rc=-2701"

Products

• XCOM Data Transport
• XCOM Data Transport - Windows

Issue/Introduction

XCOM transfer from source to Windows 2019 Server is failing intermittently with this error in the xcom.log file.
XCOMN0602E General error in queue function; rc=-2701

The XCOMD service then seems to hang and has to be restarted for the transfer to work again. 
The problem has occurred multiple times.
This is a failover cluster and the primary should automatically failover to the secondary when the problem occurs.

XCOM version is r12.0 23053 SP00 64bit.

Environment

XCOM™ Data Transport® for Windows

Resolution

There are multiple entries in the xcom.log due to port scanning (health check pings) to the secure port 8045 e,g.

2025/01/01 03:50:03 TID=REMOTE PRG=xcomtcp PID=15288 IP=##.##.#.#:44430
    XCOMN0812I Remote Secure TCP/IP Connection Requested.

2025/01/01 03:50:03 TID=REMOTE PRG=xcomtcp PID=15288 IP=##.##.#.#:44430
    XCOMN0780E : 

2025/01/01 03:50:03 TID= PRG=xcomtcp PID=15288 IP=##.##.#.#:44430
    XCOMN0818I Secure TCP/IP Connection Ended.

The "XCOMN0602E General error in queue function; rc=-2701" messages start after the first occurrence of message "XCOMN0780E Txpi  308: TxpiInitSSL Failed msg = <> value = 4294967295" also from a health check ping:

2025/01/01 03:50:08 TID=REMOTE PRG=XCOMTCP PID=15824 IP=##.##.#.#:45522

    XCOMN0812I Remote Secure TCP/IP Connection Requested.

2025/01/01 03:50:08 TID=REMOTE PRG=XCOMTCP PID=15824 IP=##.##.#.#:45522

    XCOMN0780E Txpi  308: TxpiInitSSL Failed msg = <> value = 4294967295:

2025/01/01 03:50:08 TID= PRG=XCOMTCP PID=15824 IP=##.##.#.#:45522

    XCOMN0818I Secure TCP/IP Connection Ended.

Conclusion

After extensive research XCOM Engineering has come to the conclusion that there is no problem with XCOM 12.0 itself and the problem has been caused by a corruption with the queue files in the %XCOM_HOME%\Q directory due to some abnormal action e.g. the xcomd process has terminated unexpectedly.
In this scenario it is suspected that the failover setup is the root cause.

In another scenario several upgrades of 11.6 SP02 machines to 12.0 worked successfully and one resulted in the reported error.
The 11.6 SP2 > 12.0 upgrade process converts the Q entries.
For those upgrades the systems were very busy with frequent transfers systems, about one transfer every 1.5 seconds, as well as the regular port scanning.
To properly upgrade would have required stopping the transfers, stopping the XCOM service and then performing the upgrade. The xcom.log files provided indicated that process did not occur so that was a good reason to cause 12.0 to experience a queue file corruption.