Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Exit code for Script to install software

Created: 05 Apr 2013 | 6 comments

Hi, I have a task that runs a script to install some software. The software needs a reboot and as such the task reports as failed with error 3010 - even though it was successful and just needs a reboot. Is there anyway I can make this task report as successful ? (like a software deployment job)

Thanks

Joe.

 

Comments 6 CommentsJump to latest comment

Andrew_Shishkov's picture

Hi,

Do you use Quick Delivery task type to install the software?

 

Thanks,

Andrew.

BugTastic's picture

I do - but I'm having an issue with 1 particular PS where it doesn't copy the software to the client because there is no snapshot.xml file on the PS. I've tried regenerating the snapshots as per KB. it gets to a point where i try and gauge how long troubleshooing will take Vs creating a quick working alternative (the script works) - I think i've exhausted our customers patience with the amount of issues we've had with this software

Thanks

Joe.

 

OK - just seen another post that says adding 'exit 0' as the last line should do the trick - will give it a try

 

 

Andrew_Shishkov's picture

Hi Joe,

 

The native way to implement it is just to use one of the Software Delivery tasks (Quick Delivery or Package Delivery) or Managed Delivery policy. These tasks\policies will use success codes defined for command line that is used for software delivery (just make sure that exit code 3010 is added to the list of success codes).

If you cannot use SW delivery tasks and policies by some reason you can use job instead with adding condition which will return 0 for the entire job if your script task will return 3010 exit code.

 

Thanks,

Andrew.

Sachin Sawant's picture

go to the Report--> Task Server---> status---> Job/Task Status Detail