Problem

We have identified a runtime initialization error that persists across both cluster and standalone installations on Windows Server.

When a Windows UNC path (such as a SAMBA or SMB share) contains special characters like the dollar sign ($), the application may fail to resolve the path correctly during this step.

In Windows networking, the $ suffix is commonly used to designate administrative or hidden shares (e.g., \\IP\Folder_name$\).

If Axway CFT runtime or other application points directly to a path like \\IP\Folder_name$\Axway\CFT\runtime, the special character may cause resolution errors or runtime creation failures.

Resolution

No changes are required to the permissions of the hidden SAMBA share.

To eliminate runtime errors caused by character parsing issues, create a Symbolic Link (Directory Junction) with a "clean" name that does not contain special characters. This link will act as a transparent bridge to the real location.

Steps to implement:

1. Open the Command Prompt as an Administrator

2. Use the mklink command to create a directory link without the $ sign.

Command Syntax : mklink /D "Alias_Name" "\\Real_Path\With_Special_Character$"

Example : mklink /D "Folder_name" "\\IP\Folder_name$\"