I'm testing a new Job on v5.1.2 that includes an Execute Script task for the first time, and get various errors that appear to be related to the Credentials. The Credentials setting for the Job and its Tasks uses the domain administrator's account, which is what all the other jobs successfully use.

The first Task in the Job runs a VB script, which creates a .csv file in a directory on a network share and adds data to it.

When I run the script file manually, I have no trouble.

I've tried three ways to have the script save the file:
1. When the script uses a function that returns the name of our file server in a text file, located in the same folder as the script, the error returned is "File not found".
2. When my script ignores that function and uses a full UNC for the path, the error returned is "Path not found".
3. When my script uses a mapped drive name and path, the error returned is "Path not found".

The "Task Process - Execute script " Credentials instructions on this site says:

Credentials
You must specify a Credential, a remote server name, user name and pass word for a user on the remote server which the command will execute as. Click on the Manage credentials button to add a new Credential.

But the remote server name setting in Manage Credentials doesn't exist.

The "Using VBScript for scripting " instruction on this site says to use the basic Execute task instead of the Execute Script task, and gives examples of task settings to use.
When I change the Job to use the basic Execute task and tested it, client stopped showing updated information about the job's progress, the .csv files weren't created. Evenually the client created multiple jobs with the same database values and I had to restore from a backup. I've just now posted a topic about that .

What am I missing?

(I've left out the client version from the topic subject because the "New version available!" information doesn't doesn't say that this problem was addressed in updates since v5.1.2.)

I am sorry but we seem to have missed this question.

The simple answer is that Execute script is very limited to the WMI (which it uses for remote execution).

And it seems like network drives are not shared when using this function. You can only use local paths on that machine.

---

You can only use local paths on that machine.

Thank you.
That was the problem; the script task runs successfully now that I've changed the path to a local one, instead of a network share.

Sorry for the last confusing message - it was meant for another post.

---