We have a job that starts a process and then exits (using a script.) It has the setting configured to not run the task if the process already exists. The first time, this works fine. Everytime after that, if the process is already running, we get this error notification:

From: SERVER09 [mailto:SERVER09@pridedallas.com]
Sent: Saturday, March 23, 2013 6:29 PM
To: # IT
Subject: VisualCron - SERVER09 - Error - Run MedEDocs Print Application

"[Error in SetVar, string: Computer: {COMPUTER(Name)}
Date/Time: {DATETIME()}
Task: {TASK(Active|Name)}
Executed at: {TASK(Active|LastRun|M/d/yyyy h:mm tt)} Job Error: {TASK(Active|Result)} Task Output: {TASK(Active,StdOut)} Errored On: {LOOP(CurrentValueXArray,0)}, err: Object reference not set to an instance of an object.]"

Also, Exit code is 77778 .

We have a job that starts a process and then exits (using a script.) It has the setting configured to not run the task if the process already exists. The first time, this works fine. Everytime after that, if the process is already running, we get this error notification:

From: SERVER09 [mailto:SERVER09@pridedallas.com]
Sent: Saturday, March 23, 2013 6:29 PM
To: # IT
Subject: VisualCron - SERVER09 - Error - Run MedEDocs Print Application

"[Error in SetVar, string: Computer: {COMPUTER(Name)}
Date/Time: {DATETIME()}
Task: {TASK(Active|Name)}
Executed at: {TASK(Active|LastRun|M/d/yyyy h:mm tt)} Job Error: {TASK(Active|Result)} Task Output: {TASK(Active,StdOut)} Errored On: {LOOP(CurrentValueXArray,0)}, err: Object reference not set to an instance of an object.]"

Also, Exit code is 77778 .

Hard to say by just looking at the email. You should look at the error output of the Task and the log file to determine the error.

---

Task has no error output. Output (stderr) = no output

Log:

3/24/2013 7:00:01 AM Info Task started: Run MedEDocs Print Application (578)
3/24/2013 7:00:01 AM Err Job "MedEDocs Print Application" was NOT executed because it was already running.

Log:

3/24/2013 7:00:01 AM Info Task started: Run MedEDocs Print Application (578)
3/24/2013 7:00:01 AM Err Job "MedEDocs Print Application" was NOT executed because it was already running.

How is this Task or this Job related? Is the Notification added on Task or Job level?

You are using a Loop Variable but at the same time you seem to fork another Job - I do not think that loop Variable will be available then. Please explain more about the Job structure and what you want to do.

---

That's the thing, there are no loops on this server and this job, nor the email notification are using loop variables. I'll give you screen shots to prove it when I get back to my computer.

This notification is on the Task Level. Notify on Error.

The error seems to be generated because the process is already running, but that is the intended behavior.

Your comments confirms two issues:

1. Why is the notification trying to use a loop variable?
2. Why is a notification being generated at all? There is no error.

1. you tell me, what does the Notification look like? I see this in your previous message which is a Loop Variable:

{LOOP(CurrentValueXArray,0)}

2. The error we are talking about here is not an error resulting in a failure. Just that the Loop variable (and other) are not able to be resolved.

Somebody must at least recognize the output in the mail?

---

So, this is resolved even if there is no error?

Yea, I see that in the Notification now. I'm going to strange whomever put that in there.

However, this same notification is used on many other tasks and we are only getting this message on this one task. Some error is being generated and I believe it is due to the process already running....but that should not be an error.

I can't test this right now, due to an issue with the process that it is running, but I will test again when I can.

So, this is resolved even if there is no error?

Yes, it tries to resolved Variables anyway (and to not raise errors when that fails). The error happens in a Notification which has no error handling (that affects the Job).

---

But I have other tasks that use this notification and no loop and they are not throwing an error.

What happens if you just remove the Loop Variable - since you said you do not use Loops.

---

I can't tell you with this task, because we have another issue with it so that I can't run it right now. But my point is, this issue ONLY exists on this task. I think the task IS throwing an error, but instead of getting the actual error, we are getting this message because of the loop variable. I've removed it and created a separate notification for the tasks that have loops. I'll test when I can, and then we'll see.

I can't tell you with this task, because we have another issue with it so that I can't run it right now. But my point is, this issue ONLY exists on this task. I think the task IS throwing an error, but instead of getting the actual error, we are getting this message because of the loop variable. I've removed it and created a separate notification for the tasks that have loops. I'll test when I can, and then we'll see.

I see, we will see what happens if that variable is removed.

---