Yesterday I upgraded to version 6.1.0. Today the notifications for SQL tasks are reporting errors in some variables that previously worked.

"[Error in SetVariables, string: {TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,ConnectionString)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,QueryType)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,Query)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,Id)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,Type)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,Name)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,ExitCode)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,ExitCodeDesc)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,StdOut)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,StdErr)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,Status)}
{TASK(dc2e9d2c-64f6-444f-9f14-3ea7fe8f1101,Result)}, err: Object reference not set to an instance of an object.]"

I have established that some variables still work, but these are the variables which don't work:
{TASK(Active,ConnectionString)}
{TASK(Active,QueryType)}
{TASK(Active,Query)}
{TASK(Active,StdErr)}

Is this a known problem, and can I expect a fix any time soon?

Error text follows

TIA
John

1. Is the Notification attached to the Task or Job?
2. it was not clear if you use Active or hardcoded the Id?

---

Could you try this version:

http://www.visualcron.co....aspx?g=posts&t=2434 

---

1. Is the Notification attached to the Task or Job?
2. it was not clear if you use Active or hardcoded the Id?

Hi, sorry to confuse. The notification is attached to a task. The Id are hard coded, but when I investigated the same error appears in the variable picker for the active variables (the preview for {TASK(Active,ConnectionString)} gives the same error.

1. Is the Notification attached to the Task or Job?
2. it was not clear if you use Active or hardcoded the Id?

Hi, sorry to confuse. The notification is attached to a task. The Id are hard coded, but when I investigated the same error appears in the variable picker for the active variables (the preview for {TASK(Active,ConnectionString)} gives the same error.

It is one thing that it is not working in Preview. This is a runtime value so it is set when running Task. Please test with 6.1.1 in runtime.

---

It is one thing that it is not working in Preview. This is a runtime value so it is set when running Task. Please test with 6.1.1 in runtime.

Again I'm being confusing. The error appears both in preview and at runtime with both active and hard coded id's. I'm testing the beta version now.

Right, version 6.1.1 fixes the problem for me, both in the active and the hardcoded id's. Thank you for that. I don't want to put beta software on my production servers, I think I'll wait for the official release.

The issue isn't a stopper for me, it's just that my product support tesm were worried about the false positive error messages they were seeing.

regards
John

I'm in the same situation as John here. Don't want to deploy beta code to production systems.

This is a moderate severity for us, as it affects our outbound email communications.

thanks,

Drew

6.1.1 will be released this week. Thank you for your patience.

---