Event viewer reports the failure; however, the parameter is correct and running GetParameters pulls in the same parameter. The task is working properly.

In addition Web Macro is reporting Credential issues as well:


Other web macros were having the same issue. I'm not entirely sure where the credential is being triggered in those macros that it could be causing the issue.

Update for WebMacro:
Under the proxy settings, Proxy type was set to No proxy; however, the use credentials box was checked. I changed the No proxy to anything else, unchecked the Use credentials, and changed proxy settings back to No proxy. It appears that removed the credential error for the web macro.

Update for WebMacro:
Another discovery. All of the variable substitutions were wiped out from the macro. Anywhere we injected a variable was replaced with the original text instead of the variable substitution string (i.e. {JOB(Active|Variable|SubmissionCheck)}).

Event viewer reports the failure; however, the parameter is correct and running GetParameters pulls in the same parameter. The task is working properly.

In addition Web Macro is reporting Credential issues as well:


Other web macros were having the same issue. I'm not entirely sure where the credential is being triggered in those macros that it could be causing the issue.

From the log it looks like no proper Credential is being used as it is just logging @ in the log file.

Is the web macro working as expected now?

---

Hello Henrik, Yes. The web macro is working now without issue. I needed to update the variables and everything is good. The crystal report issue still persists. I'm not sure where it is trying to do the impersonation.

Hello Henrik, Yes. The web macro is working now without issue. I needed to update the variables and everything is good. The crystal report issue still persists. I'm not sure where it is trying to do the impersonation.

In one of these locations: https://www.screencast.com/t/yoeuxIUNdBPP 

---

Looking at the crystal issue some more. I've been watching the log file and I saw this as it is processing records:

It looks like the credentials are not matching between runs.

Also, not sure if this is related, but something seems to be consuming a fair amount of memory:


About 20 minutes later, approaching 4 gb of memory:

Looking at the crystal issue some more. I've been watching the log file and I saw this as it is processing records:

It looks like the credentials are not matching between runs.

Also, not sure if this is related, but something seems to be consuming a fair amount of memory:


About 20 minutes later, approaching 4 gb of memory:

Handling this via email for now

---

I can report that version 9.8.0 solves the memory issue. I do not see the memory consumption issues I was seeing in 9.6.5 and the lingering VisualCronWebMacro.exe tasks do clean up.

I can report that version 9.8.0 solves the memory issue. I do not see the memory consumption issues I was seeing in 9.6.5 and the lingering VisualCronWebMacro.exe tasks do clean up.

Thanks for reporting this!

---