While testing a new Job on v5.1.2 (on Win2k SP4) the Client never showed updated information about the job and the things that the job was supposed to do didn't happen.
When I closed and re-opened the Client, an unhanded exception error appeared with this information:

The newly-created Job has a Task that's been giving me permissions-related problems. (I've posted a different topic about that.)

I was able to get the Client working again from backed-up settings.
The information in the client about versions since v5.1.2 don't say anything about fixing database-related bugs such as this.

Is that bug fixed in a newer version?

We have got another report about this but not able to reproduce this ourselves. Were you cloning a Task or Job?

---

Actually, I wasn't *trying* to clone anything.
While testing the job after having set it to use the basic Execute task to run the script, the Client wasnn't showing how the Job test was running and the actions I expected the script to cause weren't happening.

After closing the Edit Job form while the test was still running, I tried refreshing the status to no avail with F5, and then tried refreshing the status by collapsing and re-expanding the Job info, and then finally by disconnecting and re-connecting the client.
It was upon re-connecting that the first Unhandled Exception appeared.

(Why didn't I think to include this detail in my original post? I dunno; I know better than that.)

OK, that brings us closer.

1. Did you click on Test before or after the Job had been created and saved?
2. Can you reproduce this on a new Job?

---

Wealthbridge/Support, Please change the title to the right version of Visualcron.

Regards
Erik

---

OK, that brings us closer.

1. Did you click on Test before or after the Job had been created and saved?
2. Can you reproduce this on a new Job?

1. I clicked Test Job after changing the task from the Execute Script to the basic Execute.
One other note: while the Test was running I closed the Edit Job form by clicking the [X].
2. We're running multiple important jobs throughout the day. Will those other jobs be affected if I am able to reproduce this problem?

Wealthbridge/Support, Please change the title to the right version of Visualcron.

I left out the client version from the topic subject because the "New version available!" information doesn't doesn't say that this problem was addressed in updates since v5.1.2.

BTW- we do have an activation code for 5.1.2. I just couldn't get to it while the Unhanded Exception errors were happening, and I don't want to post it in this thread.

2. Other Jobs settings will not be affected. But you will run into the same problem if you can reproduce it (and you have to restart the services)

I am not understanding the problem with the activation - please contact Sales for all activation/license issues.

---

2. Other Jobs settings will not be affected. But you will run into the same problem if you can reproduce it (and you have to restart the services)

I am not understanding the problem with the activation - please contact Sales for all activation/license issues.

Yeah- the settings won't be lost; my question was if the *running* of the other jobs would be affected if the database problem were to be replicated.

We haven't had a problem with activation; my co-worker hadn't yet had the chance to copy the Activation Code anywhere. Before we had restored the settings from the backup, the Client crashed because of the Unhandled Exception errors so we couldn't get the Activation Code from it.
We don't know if job-running would be affected by the cause of the Unhandled Exception, and I needed to get support help coming asap so I started this topic because this support forum doesn't require an activation code.

It affects running Jobs if you need to restart the Service (while it is being down).

We would appreciate if you could test this while we will try to reproduce it here as well.

---

We managed to reproduce this. We will fix this for next version. Thank you for your report.

---

Hurra! (Well, kind of.)
What do I need to avoid doing so that I don't accidentally cause this problem again?

Currently, while a Test Job is running, it is causing new clients problems to Connect. To avoid this you should not currently test Job from Job editor but by running it normally (right click on Job).

---

Good to know. Thanks.

Please install version 5.1.9. It has a fix for this issue.

---