Problems with hotfolders on Helios servers?
Posted: Thu Feb 07, 2013 9:13 am
Hi,
We are running into problems with Switch (Win, v11 update 3) with
hotfolders that are on a network drive on a Helios server. Have any of you run into similar problems? Basically this is what happens:
When a flow has a not-automanaged folder (a hotfolder or a final output folder) set up on a network location which is on a Helios (PC Share UB2) server, the flow validates and starts fine, but after a few seconds (up to a few minutes) the numbers showing the number of files in different flow elements change to 0 and Windows Explorer (when trying to view the folder) gives an error where it says that "servernameshare is not accessible. You might not have permission to use this network resource. Contact the administrator... Not enought server storage is available to process this command."
When I exit Switch the problem immediately goes away and the network location becomes available in Explorer again. The problem returns when Switch is reopened and the flow restarted.
Same flow works fine when I set the fixed folders into a different network drive not on that Helios server.
Any ideas what the problem could be? Have any one of you met similar problems?
--patrik
We are running into problems with Switch (Win, v11 update 3) with
hotfolders that are on a network drive on a Helios server. Have any of you run into similar problems? Basically this is what happens:
When a flow has a not-automanaged folder (a hotfolder or a final output folder) set up on a network location which is on a Helios (PC Share UB2) server, the flow validates and starts fine, but after a few seconds (up to a few minutes) the numbers showing the number of files in different flow elements change to 0 and Windows Explorer (when trying to view the folder) gives an error where it says that "servernameshare is not accessible. You might not have permission to use this network resource. Contact the administrator... Not enought server storage is available to process this command."
When I exit Switch the problem immediately goes away and the network location becomes available in Explorer again. The problem returns when Switch is reopened and the flow restarted.
Same flow works fine when I set the fixed folders into a different network drive not on that Helios server.
Any ideas what the problem could be? Have any one of you met similar problems?
--patrik