| View previous topic :: View next topic |
| Author |
Message |
jkrfs
Joined: 27 Mar 2010
Posts: 47
|
 Posted: Thu Apr 28, 2011 9:53 am Post subject: CommandLine error, when there is no error |
 |
|
Greetings fellow automizers!
I am using a Command task to run a dos command that silently unzips a file.
file.exe /s
when I run it, it unzips the file fine. however I keep receiving exit code = 1.
any idea why? and is there anyway to just ignore it? (i have it set to notify by email if there are any errors, and i wouldnt mind ignoring this one)
Thanks! |
|
| Back to top |
|
 |
Robert
Site Admin
Joined: 25 May 2006
Posts: 1140
|
| Posted: Fri Apr 29, 2011 10:43 am Post subject: |
|
|
is there anything in the output or debug logs?
You may have a generic notification profile that sends email if exit code > 0. you would have to change that and select all tasks that you need notification for (except this one). |
|
| Back to top |
|
|
jkrfs
Joined: 27 Mar 2010
Posts: 47
|
| Posted: Thu May 12, 2011 8:52 am Post subject: |
|
|
| I just had the task continue in the chain if it had an exit code of > 0. Nothing in the output or debug logs that would tell me why. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
