We recently updated our production servers to v.8.2.6 and unfortunately we found bugs in this venison.

We created a new task to an existing job and we moved it between the other existing tasks of that job. The task was never executed. All the other previous tasks of the job were run in order, but the new task was skipped. We investigated this issue and we run some tests.
We created a new job with 3 tasks in it with the order bellow:
1.task1
2.task2
3.task3

When the job is executed with the original order of the tasks, everything is ok and the tasks are run in order.
1.task1- runs
2.task2- runs
3.task3- runs

But if task3 is moved to place2 and task2 is moved to place3 - task3 is skipped:
1.task1 - runs
2.task3 - skipped
3.task2 - runs

If task3 is moved to first place - it is run in a loop, and the rest of the tasks are not run:
1.task3 - loops
2.task1 - skipped
3.task2 - skipped

We found another issue when testing a sql connection to an Oracle database, we always get this error message:

But the SQL tasks that use the same connection run successfully.

Also the logic of the task FLOW is changed in v.8.2.6.
Before it we were using v.8.0.2 and the tasks that had this flow:

when their output was not equal to OFF, the execution of the job was cancelled. But now all the tasks in the job are executed, regardless of the output of the task with the flow above. We had to change the flow this way:


When we were applying v.8.2.6 to three of our preprod servers, after the update of one of them, there were not jobs at all, they disappeared. However this was not reproduced when we updated the production servers.

Hi,

we are very interested in resolving this. Do you think you can create a reproducable case with zero other dependencies and then export that Job and send to support@visualcron.com?

---

We have updated version from 8.2.5 to 8.2.6 and got an issue - all jobs with task type execute process Failed.
Jobs are running with credentials of local admin with Background execution context.
OS - Windows Server 2012
In Event Viewer I can see an errors, like:

Faulting application name: conhost.exe, version: 6.3.9600.17415, time stamp: 0x5450410b
Faulting module name: USER32.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc0000142
Fault offset: 0x00000000000ecdd0
Faulting process id: 0xdfc
Faulting application start time: 0x01d2d087ef5c5a7b
Faulting application path: C:\Windows\system32\conhost.exe
Faulting module path: USER32.dll
Report Id: 2d0b48ed-3c7b-11e7-80e1-005056a24b3d
Faulting package full name:
Faulting package-relative application ID:


upd. SOLVED - removed local login checkmark from ad user credentials and it worked. Weird - earlier it was working with those checkmark set.

We have updated version from 8.2.5 to 8.2.6 and got an issue - all jobs with task type execute process Failed.
Jobs are running with credentials of local admin with Background execution context.
OS - Windows Server 2012
In Event Viewer I can see an errors, like:

Faulting application name: conhost.exe, version: 6.3.9600.17415, time stamp: 0x5450410b
Faulting module name: USER32.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc0000142
Fault offset: 0x00000000000ecdd0
Faulting process id: 0xdfc
Faulting application start time: 0x01d2d087ef5c5a7b
Faulting application path: C:\Windows\system32\conhost.exe
Faulting module path: USER32.dll
Report Id: 2d0b48ed-3c7b-11e7-80e1-005056a24b3d
Faulting package full name:
Faulting package-relative application ID:


upd. SOLVED - removed local login checkmark from ad user credentials and it worked. Weird - earlier it was working with those checkmark set.

This does not have anything to do with the other issue. Two solutions for this issue:

1. do not use a Credential
2. enable Extended debugging in server settings. Edit the Credential that you use and set it to "CreateProcessAsUserW"

---