Pre Job - The system cannot find the path specified.

Try moving batch files to C drive

Also add BE service account to security of this folder with full rights.

Check win event viewer- for any message -why could not run the batch file?

Hi,

I tried drive C, Symantec installation path and other drives.

The event viewer is just saying, that BE cannot start the job, no more informations.

What do you mean with "BE service account", the user which runs the BE Services? That's the local administrator and the administrator has full rights on the directory where the scripts are stored.

Does the backup work without selecting pre/post options?

Go to BE console -network -logon accounts -look for account which say BE System account

also make it default and add to local admin on server.

Are these pre/post commands running on the local media server or on the remote server being backed up ?

The BE System account is already set as default and it is as default local admin.

Also I gave this account domain admin rights, restart the server and tested it again, no way.

These pre/post commands running a batch file on the local media server, and this batch file runs other batch files on the remote server. 

Pre <d:\scripte\server_down.bat> 

PsExec.exe \\server -u domain\SYSadm -p SYSpw "\\server\d$\Backup_Script\sapdown.bat"

When I start the batch files with the BE Service account user, outeside from BE, it runs very well. So what's the deal?

Thank you!

The RAWS service on both the media and the remote servers should be using the Local System Account...Does the remote server's credential account have access to the local media server ?

When the Pre and Post jobs run, there is no environmental variable for PATH

So you must either add a PATH statement as the first line of the CMD file that will include all the directories that contain non system commands, or you must use absolute paths for all commands

In your example try
 

path=c:\utils (and any other dirs referenced in sapdown.bat)

PsExec.exe \\server -u domain\SYSadm -p SYSpw \\server\d$\Backup_Script\sapdown.bat

(or whatever that path is)

or

C:\Utils\PsExec.exe \\server -u domain\SYSadm -p SYSpw \\server\d$\Backup_Script\sapdown.bat   

and also include absolute paths in the sapdown.bat file

(or whatever that path is)

Of course I've set the PATH env var, system wide <C:\Program Files (x86)\SysinternalsSuite> and yes I've restarted the server.

The scipts, pre and post, running well when I start them with the BE system account, so why I have to set absolute paths in the batch files? There are many for loops, which searches for running services and stop them if some are running. But the error message says it cannot find the batch file itself .. or am I wrong?

Both, the local and the remote service are using the Local System Account.

All remote server, system users of the remote servers, have got local admin rights and they can connect to the admin shares (c$, <drive>$).

1) Why don't you start with a batch/command file that contains an echo statement to a text file (with a specific path) just to confirm whether or not it is a problem inside your batch file or whether Backup Exec is not even calling the batch file

 So create a batch file in D:\script called testbat.bat

and inside the bat file just put one line

ECHO Batch file was activated by Backup Exec >d:\scripte\testoutput.txt

Then put this as a pre-command on a test backup job and run it - if the text file is created then BE is calling the batch file and at least will help you narrow down the problem.

2) Try running your pre command using WIndows task scheduler but set to run as SYSTEM instead of a user (as Beremote process uses Local System for credentials.)