Hello -

I am trying to use the standard output from a SQL task in the body of an email. The email sends correctly, but instead of the query results, I get an error message:


"[Error in SetVariables, string: {TASK(caf97553-5e66-4f99-85aa-8b47812073cc,StdOut)}, err: Array cannot be null.
Parameter name: bytes]"


This would indicate to me that the SQL task is where the error is coming from - however, I know the SQL in question works. I've tried using the query directly as SQL text as well as using a Stored Procedure.

Here is the SQL:



Is the error related to how the output is formatted (under the output settings tab)? I'm using the Pipe delimiter and crlf for new line.

Thanks,
Trent

Hi,

the problem might be a conflict with the parameter delimiter which is comma "," and the fact that you use comma in the actual SQL string. Try using our alternate pipe "|" separator like this instead:

{TASK(caf97553-5e66-4f99-85aa-8b47812073cc|StdOut)}

---

I tried using the pipe in place of the comma as described - I still get the same error.

Anything else I can try?

Could you attach the actual output to a file here?

---

The SQL output? Or the email output?

The SQL output. It is probably something in that output that consired "garble" to VisualCron. You know that you can control the way it outputs the SQL?

---

Yes, I've tried to output a single string of text, as well as output a complete multi-record set - using the delimiters per line ( pipe & crlf, comma & crlf, nothing & comma).

I had a co-worker try the job and it worked for him with no errors. I then opened it back up, changed a recipient and got the error again. My co-worker then got the error as well.

I then changed the recipient list and made sure to end the list with the delimiter (we are using ; as the delimiter). Worked once, then errored on subsequent tests. Closed out the desktop client completely, re-launched and re-opened the task in question - it works.

Now, if I get the error it seems to clear up if I close out the client and re-launch - but only if the recipient list for the email ends with the delimiter (or so it seems).

I can attach the output from the SQL, as well as the email if needed.

Please attach the sql output.

---

Here is the SQL output file.

Are you sure that you refer back to the right Task?

If the SQL Task is the Task before the Email Task then please try with this Variable instead:

TASK(PrevTask|StdOut)}

---

Yes, the SQL task is the task immediately before the email. I will try that variable instead.

EDIT: That variable works without any issues so far. Looks good after many tests. Thanks!

Henrik, this solution worked PERFECT... I did make sure to
have both the leading and trailing curly bracket.

For clarification... Can you tell me is this in the documentaion ?
Will this variable be available on the variable list in the future ?

Thanks Sooo much I needed a quick fix, and I got it.

Visual Cron is great !

Paul.

Henrik, this solution worked PERFECT... I did make sure to
have both the leading and trailing curly bracket.

For clarification... Can you tell me is this in the documentaion ?
Will this variable be available on the variable list in the future ?

Thanks Sooo much I needed a quick fix, and I got it.

Visual Cron is great !

Paul.

We are currently updating our documentation about this. This Variable is in the list in a way that you can always select the PrevTask alternative like in the screen shot.

---