We are unable to XCOM files and are experiencing the Socket closed errors again.
XCOMM0811I STARTING SECURE TCP/IP CONNECTION TO PORT=08045, IP=<ipadress>
XCOMM0813I SECURE TCP/IP CONNECTION REQUESTED WITH DEST=**NONE**, PORT=<portnumber>, IP=<ipadress>
XCOMM1510E System SSL Function gsk_secure_socket_init: RC = 420: Reason = Socket closed by remote partner
XCOMM0093E ERROR ACTIVATING SESSION - SESSION NOT ESTABLISHED
XCOMM1168I PLEXQ LISTENER TASK STOPPING
XCOMM0071I XCOMJOB NOW TERMINATING
XCOMM0897I TOTAL ELIGIBLE zIIP TIME = 0 MICROSECONDS
XCOMM0897I TOTAL ACTUAL zIIP TIME = 0 MICROSECONDS
In the xcom.log from the Windows side you can find message:
XCOMN1004E CA XCOM TCP/IPV4 listener failed to start on port 8044
I had the user capture an xcomd trace on Windows:
XCOMd PRG=xcomd PID=14908; XCOMN0088I The XCOMD CA XCOM Data Transport Scheduler Service started....
XCOMd service 404: InitService routine
XCOMd service 591: Event CAXCOMTERMINATIONEVENT already exists. Resetting event state.
XCOMd service 623: Event CAXCOMSUSPENDEVENT already exists. Resetting event state.
XCOMd service 655: Event CAXCOMRESUMEEVENT already exists. Resetting event state.
XCOMd service 1176: PostServiceInit routine
After reviewing the service trace provided I had them reboot the server. This resolved the problem.
Taking an xcomd trace for us to to review: