Good morning,

We just installed the latest version (5.3.1) and we are seeing these issues.(At least it feels like a bug to me)

We have a simple .EXE job we need to run on the background. It executes a .vbs file from a network drive that is properly permissioned. We use UNC paths, not mapped drives.

I try to run the job, and immediately get the error "Job Could not find the specified Connection for execution." This problem seems to only go away when we start the VCTray process. This is especially problematic because that process occasionally crashes out and goes away (VisualCronService.exe keeps running). How do I make sure this error doesn't happen.

Another related issue is that when I try to run the job with a specific credential (even 'With Profile'), I get "Directory name is Invalid". Please help.

Regards,
Alan.

PS: I can mail the server log if necessary, just don't want to attach it to a public post.

Hi Alan,

there are two things that could cause this:

1. the VC Tray Client (which runs in lower right corner) is probably not running or it is not running as your user (may happen at first install). You can open the task manager to see if it runs as your user or SYSTEM. If SYSTEM, then kill it and open it again from Start menu.

2. You have set it to foreground execution that uses a Credential that no longer exists. Please check the foreground execution settings.

---

Definately not #2.

The VCTray is not running. Once I turn it on it works. Still --

Are you saying that the VCTray Client must be running in order to be able to run this job? If so, can I set the jobs to automatically start it if it isn't already running?

We are already monitoring the VisualCronService.exe windows service to make sure that it is running. Should we be monitoring the VCTray.exe process as well? If so, this is a little disturbing since .EXE's don't come with the same built-in recovery facilities as windows services.

Thanks,
Alan.

If you want to run it as a Foreground Task - then yes, it has to be running. But, you should avoid using Foreground Tasks as they require more resources (and that someone is logged in).

Perhaps someone just set it as Foreground Task and you can just set it to Background Task (in Task main settings).

What are you trying to do in the Task?

---

Regretably, some of our jobs (for legacy reasons) simply require the HKEY_CURRENT_USER portion of the registry, so they must run on the foreground.

We run as much as we can on the background. Thanks for the clarification.

Regards,
Alan.