Search

GlobalSCAPE Knowledge Base

AWE Workflow cannot read or access hidden shares

Karla Marsh
EFT Express (SMB) & Enterprise

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • EFT Server, v6.3.x - v7.4.5
  • This issue was resolved in Automate v9; EFT v7.4.7 and later use Automate v10 for the AWE module

SYMPTOM

AWE Workflow cannot read or access hidden shares.

WORKAROUND

Add an extension to the end of the directory. For example, use:

\\192.168.102.129\TEST$\user\*.*

Instead of

\\192.168.102.129\TEST$\user

MORE INFORMATION

Using v6.4.1, GlobalSCAPE Support tested an AWE Workflow that loops through a hidden share (\\192.168.102.129\TEST$\user) and passes the filename, but when it ran in the AWE interface, the Workflow would start and immediately end the loop without any errors. It appeared to ignore the hidden share because it did not see it, even though the "Everyone" group had full permissions to the share. When the share was modified as described above, the same Workflow worked as desired. Hidden shares worked properly in 6.2.31 which used Automate v7, but not in subsequent versions which use Automate v8.

Details
Last Modified: Last Month
Last Modified By: kmarsh
Type: BUG
Rated 1 star based on 3 votes.
Article has been viewed 7.8K times.
Options
Also In This Category
Tags