[6.1.0] Job fires twice - VisualCron

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

Welcome Guest! To enable all features please Login or Register.

ErikC
Free support Topic Starter

2012-07-18T11:47:46Z

Hi,

I have a job and this runs twice after it is triggered (by a file create trigger).
The job is setup as put in queue and do not run if it's running.

There are three tasks in there:

Create random string with .NET task (temp string)
Copy files to Path containing random string (Verplaats de file naar de dropbox)
Rename directory using random string (Add .Ready to begin upload)

Today I had two files triggering this job and this happened:

7/18/2012 12:59:55 PM	Info	Job started: TripleA - ZV files naar Profnet2
7/18/2012 12:59:55 PM	Info	Job started: TripleA - ZV files naar Profnet2
7/18/2012 12:59:55 PM	Info	Task started: temp string (281548)
7/18/2012 12:59:55 PM	Info	Task started: temp string (281549)
7/18/2012 12:59:55 PM	Info	Task completed: temp string (281548)
7/18/2012 12:59:55 PM	Info	Task started: Verplaats de file naar de dropbox (281550)
7/18/2012 12:59:55 PM	Info	Task completed: Verplaats de file naar de dropbox (281550)
7/18/2012 12:59:55 PM	Info	Task started: Add .Ready to begin upload (281551)
7/18/2012 12:59:55 PM	Info	Task completed: temp string (281549)
7/18/2012 12:59:55 PM	Info	Impersonation result 2: True
7/18/2012 12:59:55 PM	Err	Exception in Task: Could not find a part of the path 'H:\Profnet2Dropbox\Q264SL20UJ'.
7/18/2012 12:59:55 PM	Info	Task completed: Add .Ready to begin upload (281551)
7/18/2012 12:59:55 PM	Info	Task started: Verplaats de file naar de dropbox (281552)
7/18/2012 12:59:55 PM	Info	Task completed: Verplaats de file naar de dropbox (281552)
7/18/2012 12:59:55 PM	Info	Task started: Add .Ready to begin upload (281553)
7/18/2012 12:59:55 PM	Info	Job completed: TripleA - ZV files naar Profnet2
7/18/2012 12:59:55 PM	Info	Impersonation result 2: True
7/18/2012 12:59:55 PM	Info	Task completed: Add .Ready to begin upload (281553)
7/18/2012 12:59:55 PM	Info	Job completed: TripleA - ZV files naar Profnet2

You can see the jobs runs twice simultaneously and you can see an error here. During the 1st run, the last task is using the temp string from the 2nd run.

The 2nd run has to put in queue and can't run any tasks before the 1st run completes. This is how I set it up. This is a bug..

For now I removed my checkboxes in at job level, saved it, put the boxes back and saved it again. Hopefully this will not happen again.

Regards,
Erik.

Uses Visualcron since 2006.

Sponsor

Forum information

Wanna join the discussion?! Login to your Forum forum account or Register a new forum account

Support
Official support

2012-07-18T21:06:49Z

I wonder if this is a bug that is related to cloning or similar. If you have cloned the Job. If this is the case you should test keeping the checkboxes and just stop and start the service. Let us know if it disappears. Then we can try to find a way to reproduce this.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

ErikC
Free support Topic Starter

2012-07-19T05:56:18Z

Hi,

I don't know if this is a cloned job.
And I did re-check te checkboxes, so the situation is changed.

Hope you find something.

Regards,
Erik

Uses Visualcron since 2006.

trevinom
No customer

2012-07-25T11:59:55Z

Henrik,
I'm having this problem too. It started after I upgraded to 6.1.1. It originally only happened with 1 job but last night that number increased to 3. It correctly executes all the tasks from the initial trigger, but it immediately starts running the first task again, since my first task is to copy the trigger file to a temporary location, it errors out because it can't find the trigger file. I've made no changes to any of those jobs in several months. I originally created the jobs in 6.0.9 and upgraded to 6.1.1 about 3 weeks ago.

Support
Official support

2012-08-10T08:09:50Z

Did you use the Run once setting on Job? If so, there is a bug involved that is fixed in latest beta 6.1.3.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

ErikC
Free support Topic Starter

2012-08-13T09:23:55Z

Hi,

No I did not use the Run Once option.
The job has:

Do not run job if it's running
Put Job in queue
Run tasks in order
Activate

During my 3 weeks holiday this issue did not happen again.

Quote:

I don't know if this is a cloned job.
And I did re-check te checkboxes, so the situation is changed.

This might be the solution to it...

Regards,
Erik

Uses Visualcron since 2006.

Support
Official support

2012-08-15T14:46:00Z

Hi all,

please update to this version and turn on Extended debugging in Server tab->Log.

http://www.visualcron.co....aspx?g=posts&t=2575

Hopefully it will help us finding the cause.

If it happens again please send log_serverDATE.txt to support@visualcron.com

This does not concern the issue jtnelso had as that is another issue that is fixed.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

trevinom
No customer

2012-08-15T15:25:02Z

I've been keeping an eye out for this, but it has not reared it's head again.
Still running 6.1.1
Don't have 'run once' checked.
I am, however, rebooting the server once a week.

ErikC
Free support Topic Starter

2012-08-28T06:38:17Z

Hi all,

Here on 6.1.0 and till now this did not happen again.

Regards,
Erik

Uses Visualcron since 2006.

trevinom
No customer

2012-08-28T14:19:56Z

#10

I am still on 6.1.1. I left the server running continuously without rebooting and it happened again about a week ago. It seems that if I let it run for more than a couple of weeks, it will start having weird issues like triggers setting jobs off multiple times and dependencies not working properly. Once I reset the server, everything goes back to normal.
I have re-enabled my once-a-week reboot task.

Support
Official support

2012-08-28T20:29:35Z

#11

Originally Posted by: trevinom

I am still on 6.1.1. I left the server running continuously without rebooting and it happened again about a week ago. It seems that if I let it run for more than a couple of weeks, it will start having weird issues like triggers setting jobs off multiple times and dependencies not working properly. Once I reset the server, everything goes back to normal.
I have re-enabled my once-a-week reboot task.

You say dependencies. Are you saying that this happens only on Jobs using Trigger dependencies?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!