UNC path issue for file transport in a Windows Environment.

UNC path issue for file transport in a Windows Environment.

book

Article ID: KB0091201

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect -
Not Applicable -

Description

Resolution:
Description:
============
When the UNC path is specified for Outbound file transport like "\\UKDBT81TIBC01V\FileShare2\ESB\HermesFTP\IN\"
the file is send to "D:\tibco\bc\5.3\null\UKDBT81TIBC01V\FileShare2\ESB\HermesFTP\IN" location of the machine where the BC is running. The audit log shows as:
File has been sent to "null\UKDBT81TIBC01V\FileShare2\ESB\HermesFTP\IN\Hermes_tracking.txt" instead of sending it to the "UKDBT81TIBC01V\FileShare2\ESB\HermesFTP\IN'"

Environment:
============
BusinessConnect 5.x versions
Windows Operating System

Symptoms:
=========
The file is send to "D:\tibco\bc\5.3\null\UKDBT81TIBC01V\FileShare2\ESB\HermesFTP\IN" location of the machine where the BC is running. The audit log shows as:
File has been sent to "null\UKDBT81TIBC01V\FileShare2\ESB\HermesFTP\IN\Hermes_tracking.txt" instead of sending it to the "UKDBT81TIBC01V\FileShare2\ESB\HermesFTP\IN'"

Resolution:
===========
1). Create a persistent mapped drive as the SYSTEM account with the following command
"net use z: \\servername\sharedfolder /persistent:yes"

2). Update the File transport URL to use absoulte path (include drive name).

3). Restart BC.

Issue/Introduction

UNC path issue for file transport in a Windows Environment.