I'm attempting to run a program on a remote machine using the remote execute task in VisualCron. The program in question is a syncing software program that syncs an FTP/SFTP directory with a location on network/disk.

Its actually a great little program but I am having difficulty writing to a UNC path (or mapped UNC path for that matter) when I run it as a remote script. It works fine if the program is installed on the same server as VisualCron and ran as a execute task.

Unfortunately, my VisualCron server is running close to 100% CPU due to an influx in the number of jobs I need to run with this syncing software. I really want to get this working on another server (using remote execute) to offload the CPU cycles that uses to another box. Not only that, i don't want that syncing software to bring down my other scripts.

What is actually happening is that when the sync runs normally, it tries to identify that the folder/files its trying to sync exist and create said folders/files if they do not exist or have been altered.

Like I said, it works fine as a execute task on same box as VC. When I run it remotely, it fires the script properly but it does not identify the folder/files as existing and tries to create them again. Upon attempting the first folder creation, it throws an error because the folder already exists.

The user I have running the remote task is a network credential. The network user has administrator access to the machine. I attempted to run the task where the user has "local" checked and unchecked in the credentials screen. I always have "load profile" checked. Not sure if that's really an issue because I'm using UNC paths.

I've tried running the program using a BAT file and the "net use" command to map drives before running the program to no avail.

Any thoughts here?

The log files for my syncing software just tell the story of not finding the folder at the UNC path (even though it exists). Weird.

On a whim, I tried another remote execute task with a different program that accesses data from a UNC path.



Feels like I got something wrong here.

Im using the 2nd Smatbatch user for these tasks. Both do not work.

Local login and Load profile options should not matter when using Remote execute. I think the problem is security settings of the user - not sure which though. Perhaps you can map it temporary in the batch file when executing the script?

---

Just so I understand correctly, the current remote execute command is something like.

C:\Program Files\Program.exe

You want me to create a bat file which does the same thing but instead map a UNC path to a drive letter and connect drives using the net use command?

Exactly, use the NET USE command in a batch file before starting the executable.

---

I had done this before and got same results but wanted to be sure and tried it again. Yet, same problem.

I tried to just write hello world in the bat file to the mapped drive (as well as UNC).




When I run it manually from the remote server it works.

When I run it in VisualCron using remote execute I get the following error.



The bat file runs from the following location:

C:\Bat\Test.bat

Hmmmm.

I am not sure where the permission problem is. I just tried the same on a Windows 2008 machine and it worked.

---

Okay, Ill ask around and get some more info. Thanks for digging into this. Ill report back what I find.