"XCOMN0436E TP ended abnormally" using remote UNC/NAS share

Products

• XCOM Data Transport - Windows

Issue/Introduction

File transfer to XCOM for Windows server with REMOTE_FILE set to UNC file share/path i.e. \\\server_name\directory1\file1.txt, fails and receiving side xcom.log file shows:
XCOMN0436E TP ended abnormally

There will also likely be a TXPI messages received at the XCOM server initiating the transfer e.g.
XCOM for Windows: XCOMN0297E Error requesting header confirmation: Txpi  227: Socket received 0 bytes: partner closed socket. Last error: ...
XCOM for z/OS: XCOMM0780E Txpi  228: Select exception condition for socket 0

The event log shows that xcomtcp.exe is faulting in module MSVCR120.dll:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: xcomtcp.exe
P2: 0.0.0.0
P3: 5e67908c
P4: MSVCR120.dll
P5: 12.0.21005.1
P6: 524f83ff
P7: c0000005
P8: 0000000000036a00
P9: 
P10: 

Environment

XCOM™ Data Transport® for Windows 11.6

Cause

Product Defect 

Resolution

A problem using UNC file paths in the base SP03 version r11.6 20035 was fixed in patch SO13670 TRANSFERS FAILS WITH TXPI ERROR WHEN FILE=UNC (r11.6 20041).

Additional Information

XCOM patches are cumulative and the latest r11.6 SP03 XCOM for Windows patch will also contain this fix.
As a general point XCOM Support advise to install the latest patch available even if an earlier patch fixes the specific problem encountered. That is because being on the latest maintenance reduces the chance of encountering any other known problems that have already been fixed.

The Solution Downloads page for different XCOM versions/OS platforms can be found here: XCOM Solutions.
For XCOM for Windows expand "XCOM Data Transport for Windows Family Server WINDOWS-ALL" to access the latest SP03 patch for the required version 11.6.