After upgrading from 9.3 -> 9.6, all my powershell tasks are failing with errors related to parameters. I had to quickly revert to 9.3 because of prod critical tasks. After reverting to 9.3, I'm unable to look at the task log history to find the exact error as it crashes the client with error "System.ArgumentException: Column 'TaskSesult' does not belong to table ." That's a direct copy/paste, so the misspell "TaskSesult" may have something to do with that crashing.

edit

I'm able to look at the task log by drilling into the job log. The powershell error I was getting on 9.6 was
A command is required to add a parameter. A command must be added to the Windows PowerShell instance before adding a parameter.

I've never used commands in the past, only parameters.

A second powershell task had the following error:
Cannot bind argument to parameter 'Path' because it is an empty string.

This empty string is a parameter that should not be empty. Both tasks started working again as soon as I reverted to 9.3.

I am having the same issue. I have powershell scripts that I used the parameter tab and since upgrading to to 9.6, they are failing with no parameter being passed.

param(

[parameter(mandatory=$true,position=0)]
[string]$nodename,

[parameter(mandatory=$true,position=1)] [string]$time
)

Under parameter tab

nodename value {servername}
time value 10

Task never seems to read the values in the parameter tab.
I have confirmed if I manually pass parameters to powershell script outside of visualcron, it works.

Experiencing the same issue. Where is support?

Same issue here however I am on a new install and not an upgrade to 9.6.0.
I changed the parameters from using the old way of <<Variable1>> (This is how JAMS did it) to using:


The resulting variables are empty. Note I had to place the param command as the first line in the script. Any ideas?

RickH

Message from Support "This is fixed in 9.6.5."
Sure enough they are correct. NICE!

Message from Support "This is fixed in 9.6.5."
Sure enough they are correct. NICE!

Correct, this issue is fixed in 9.6.5

---