search cancel

XCOMN0436E & Txpi errors for transfer to XCOM for Windows (UNC/NAS file share)

book

Article ID: 202103

calendar_today

Updated On:

Products

XCOM Data Transport XCOM Data Transport - Windows XCOM Data Transport - Linux PC XCOM Data Transport - z/OS

Issue/Introduction

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

There will also likely be a TXPI message 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

Release : 11.6
Component : CA XCOM Data Transport for Windows

Resolution

A problem using UNC file paths in SP03 was fixed in patch SO13670 (r116_SP03_20041).
XCOM patches are cumulative and the latest r11.6 SP03 XCOM for Windows patch will also contain this fix. The Solution Downloads page for XCOM for Windows here:
https://support.broadcom.com/download-center/solution-details-new.html?sku_code=XCOM..05500&release=11.6