#XCOMN0417E Error opening temporary file name when transferring specifying the remote filename using UNC conventions with CA XCOM Data Transport.

Document ID : KB000005269
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

Getting this message when #XCOMN0417E Error opening temporary file name when sending a file and specifying the remote filename using UNC conventions.

 

Cause:

XCOM generated a misleading error message.

The displayed error message was:

XCOMN0417E Error opening temporary file name

The actual error message should be:

XCOMN0403E Cannot open output file: Permission denied

Resolution:

XCOMN0403E Cannot open output file: Permission denied means that XCOM cannot create the temporary file name on the final destination because the userid specified does not have permission to an existing UNC path.

  • The user must have write permission to the UNC path.
  • When using UNC conventions the same userid and password must be present on the XCOM partner and the final destination.
  • Make sure that the userid and password specified for the transfer have write access to the entire UNC path.

This apar was written so that the correct message will be displayed in the future:  (you will still have to correct the credentials)

APAR #: RO71470  XCOMN0417E ERROR OPENING TEMPORARY FILE NAME 
Remote transfers will fail when user does not have access to UNC path with an error "#XCOMN0417E Error opening temporary file name" instead of "XCOMN0403E Cannot open output file: Permission denied

 

 

 

 

Additional Information:

Universal Naming Convention (UNC) is the naming system commonly used in Microsoft Windows for accessing shared network folders. 

UNC names consist of three parts - a host device name, a share name, and an optional file path. These three elements are combined using backslashes as follows:

\\host-name\share-name\file_path