Hi,

On finish of a loader procedure I want to drop a file
on a shared directory of an other server. I have
setup a drive mapping to the target server on the
server running the 24x7 service.
In first instance the log file reported succesful
execution of job but apparantly, it did not copy the
file. Then I changed the RunAsUser into the user
account of the server and checked that this user has
the "log on as a batch job" rights.
Now the logfile shows: Create process failed.
Return code: 1314 - A required privilege is not held
by the client.
Any idea how to fix this?

Don't use drive mapping. Mapping is not available to services. Use UNC share and file names (like \\server\share\dir\file) and make sure the service account has direct permissions for referenced share

: Hi,

: On finish of a loader procedure I want to drop a file
: on a shared directory of an other server. I have
: setup a drive mapping to the target server on the
: server running the 24x7 service.
: In first instance the log file reported succesful
: execution of job but apparantly, it did not copy the
: file. Then I changed the RunAsUser into the user
: account of the server and checked that this user has
: the "log on as a batch job" rights.
: Now the logfile shows: Create process failed.
: Return code: 1314 - A required privilege is not held
: by the client.
: Any idea how to fix this?

I removed drive mapping from my cmd file and changed to \\server\share etc.
Again, manually launching the cmd file works perfect but 24x7 still returns
error 1314.
The target server is in another domain. I have setup a local user on that
server with a share on the target directory.
Which user and domain should I use as "RunAsUser"? The user of the
target-server or the user of the server running 24x7?

: Don't use drive mapping. Mapping is not available to services. Use UNC share
: and file names (like \\server\share\dir\file) and make sure the service
: account has direct permissions for referenced share

Local user won't work here. It must be a domain user having permissions for the share. If you use RunAsUser then the user of that command must have permissions for the share. In addition, the account running 24x7 service must have "act as part of operation system" permissions and the user in RunAsUser must have "logon as a batch job" and "logon as a service" permissions. If you don't run 24x7 as a service then you don't need all that. You can do pretty much everything without these complications.

: I removed drive mapping from my cmd file and changed to \\server\share etc.
: Again, manually launching the cmd file works perfect but 24x7 still returns
: error 1314.
: The target server is in another domain. I have setup a local user on that
: server with a share on the target directory.
: Which user and domain should I use as "RunAsUser"? The user of the
: target-server or the user of the server running 24x7?