Hi
using network drives in WIN via UC4 is a bit complicated thing because OS agents do not load the complete environment and RA FTP agent uses only existing drives.
So it might work, if the
* user who starts the RA FTP agent is able to map the networt drive
* the network drive is visible when the RA FTP agent starts
In practice most companies split it up (as already discussed) in 2 parts, the network drive part and the FTP part.
Hint for the OS part: the user who starts the OS agent and the user in LOGIN object (preferably the same user) must be able to see the network drive.
In general if you have issues or different users, for a win job its recommended to map the network drive as non-persistent, do your copy commands and afterwards delete the network drive.
btw. you could try workin with unc path definitions, at least for OS jobs it should work well.
I personally would not rely on mapped network drives over different OS jobs or OS job and RA FTP jobs.
cheers, Wolfgang
------------------------------
Support Info:
if you are using one of the latest version of UC4 / AWA / One Automation please get in contact with Support to open a ticket.
Otherwise update/upgrade your system and check if the problem still exists.
------------------------------
Original Message:
Sent: 08-12-2021 01:33 PM
From: Tim Osgood
Subject: Mapped Drive on Agent Server Not Visible
Automic version 12.3
I have a request to create an Automic RAFTP process that moves files from a file server to Google Drive. I mapped the Google drive as G on my agent server.
When I test the job by changing directory, it can go to D and back to C but it does not go to G. I have given the G drive full control to everyone. I also added administrators with full control.
Executing command: cd g:\ on Local File Systemcom.uc4.ftpjob.DataTransferException: directory g:\ does not exist
What do I need to do to allow Automic to see the mapped drive?
Thanks
Tim
------------------------------
Developer
State of Colorado
------------------------------