Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

run post job script - file not found

Status
Not open for further replies.

prinand

MIS
Jun 13, 2000
98
GB
We are running windows 2000 / arcserve 2000 build 1100

I am running a post task at the end of the job. (vbs script).
On the servers I tested, I was not able to execute the *.vbs extension, so I just bypassed that by creating a xxx.cmd file, which just called the vbs script

but now some servers do not even execute the xx.cmd batch file(also tried .bat extension)

does anyone know where it is defined which extensions are allowed to be executed or has a suggestion how to resolve this issue ???
 
anything which can be run basically, although the file you are trying to run/execute must reside in the ARCserve home directory, or you must explicitly supply the path to it in the post script line.
 
I have the full path specified, but still it is not executing the script

I tried your suggestion. I moved the cmd file to the arcserve folder and did only refer to the cmd file without path and got the same results
then instead copied the VBS script also to the arcserve folder and tried that, and provided the full path to the arcserve folder and again a failure

NO PATH :
Run Command: backupscan.cmd
E9003 Unable to execute command. (CMD=backupscan.cmd, EC=FILE NOT FOUND)

WITH PATH :
Run Command: C:\Program_Files\ComputerAssociates\ARCserve\backupscan.vbs.

E9003 Unable to execute command. (CMD=C:\Program Files\ComputerAssociates\ARCserve\backupscan.vbs, EC=FILE NOT FOUND)

the original path was c:\scripts\backupscan.cmd.

none of the solutions works....
 
Hi ,

Does the script runs from the command line?
If the script runs okay from a command line, I would then assume it does not have an Environment variable, such as correct PATH, when called as a post-job.
I suggest calling the script from within a batch file, as the post-job, with all Paths etc set.

Make sure the account has following permissions and rights
listed in the below document

Input the username and password in the pre/post tab

Have u tried using the file from the job scheduler wizard?

cheers
 
yes the script runs from the command line.
if I log in as the service account provided to arcserve is also runs the script properly

it is arcserve 2000 though, so the link you provide is not applicable since that refers to brightstor 9 / 11

I scheduled a job to execute the .cmd file and provided the same service account as username / password, and the scheduled task executed properly.
so it is a workaround, but it is just puzzling me why arcserve is not executing this.

I did build almost the same server with the same setup / software and the same arcserve 2000 SP4 build 1100 and there the script is executed properly...

 
HI,

set the activity log in debug mode.. you can do this from the server admin..

now run a small test backup with the same script on the post job..

if the batch fails to execute.. from the log find out if the job called the batch file.. if the batch file was not called for some reason.. that would be the problem area and not the batch itself..

please paste the last 10-15 entries of the activity log.. would be very useful..


So it Shall be Written!
So it Shall be Done!!
 
Still better..

create 2 identical jobs.. one on the problem server.. and the other on the server where the batch works..

now generate the debugged activity.log.. now you can compare apples to apples..

So it Shall be Written!
So it Shall be Done!!
 
I did generate 2 identical jobs, enabled the debugging but there are no special lines for / around the failure

they are exactly the same as in my second entry in this posting.

however I have the feeling that this has something to do with services not being allowed to execute certain programs or extensions

so, does anyone know maybe where it is defined which extensions are allowed to be called by a service ?
(I assume the jobmanager runs as a service, and thus is it a service who is calling the script ?)
 
Hi prinand,

You have to type something like :

cmd /C C:\Path\FileToRun.cmd
 
it is embarrassing but the issue is resolved. my biggest issue is that I am not even sure what fixed the issue.

My best guess is that McAfee was not linked properly to EPo yet, so that was done last thursday / friday, and after the system was restarted on monday, the script is now executing OK.

McAfee does some weird things and is blocking the execution of certain tasks too, so it may very well be caused by a misconfiguration of McAfee....

I tried the last siggestion, and it works, but it did that already, so all I can confirm is that it does work...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top