Network folder path issue

Discuss RoboTask here
Post Reply
elwayfan446
Posts: 46
Joined: Tue Mar 28, 2017 3:05 pm

Network folder path issue

Post by elwayfan446 »

Hi,

I am having issues when using a task that executes a .cmd file on a network share. For whatever reason, and it could be something with corporate policy, I am only able to use the UNC path sporadically when pointing to the share. If I browse to the folder using my map drive, it works correctly. The problem is that anytime my computer is rebooted, robotask doesn't recognized that the drives have been mapped again on startup. Because of this, all jobs that I have created that point to a folder on a network share fail. I have to go in and browse out to each folder again to get the task to recognize it again. This is becoming a huge problem because I have so many jobs now. It isn't feasible to go in and remap each job every time my computer reboots. Is there a way to correct this?
Oleg
Site Admin
Posts: 3000
Joined: Thu Jan 01, 1970 1:00 am
Contact:

Re: Network folder path issue

Post by Oleg »

It seems RoboTask has bee started earlier than drives mapping. So RoboTask inherits another environment.
Also you can map drives yourself
read about the command line
net use ...
To get help use
net use /?
Also you can read detailed information here
Oleg Yershov
Post Reply