Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Kshitij
2016-04-30T08:25:56Z
  log_server20160430.txt (32kb) downloaded 45 time(s).Hi Team,

I have activated the 'Log to event Log' and checked on 'Server Logs' under Settings --> Log Settings. My scheduler is calling a batch file that is executing a script. At the script level I have set up a log to see whether my task is executed successfully or not by activating 'Logging Module' in Django. When I check the server logs 'log_serverYYYYMMDD.txt' located at "C:\Program Files\VisualCron\log\" folder then I can see the following server logs :

0/4/2016 3:39:59 PM Info Task started: Execute (110)
30/4/2016 3:40:56 PM Info Task completed (Failure)->'Execute' (109)
30/4/2016 3:40:57 PM Info Job completed (Failure)->'GV1'
30/4/2016 3:41:09 PM Info JobAPI->Save->Saving Jobs (3) - in shut down: False
30/4/2016 3:42:54 PM Info Task completed (Failure)->'Execute' (110)

However by looking at the Django server logs I am sure that the job of id '110' (shown above) has not failed as the script wrote some successful logs (meaning that it actually got executed). However the Visual Crno server logs show that it has failed, gives a result of 'Failed' status and an exit code of 77777 consistently for all jobs. I am not sure what could be the reason here. My .bat file works perfectly fine on running it standalone .

Could you please help me explain why is this server logs showing that task 110 has failed.

I have also attached the error logs from the server in a .text attachment.

Any help will be much appreciated :)

Thanks,
Kshitij
Sponsor
Forum information
Support
2016-05-02T07:28:44Z
An exception can be raised anytime within the execution. In your case it sounds like the batch files returns another exit code than 0 - in the end of the batch file. So, probably it does everything as expected but still throw an error. As it is VisualCron that is executing this batch file it monitors the exit code and captures that.

I suggest you try to find out which line causes the non-zero exit code by removing line by line.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top