I'm using a PowerShell task to execute a script stored on disk. The exact location of the script file is specified and the Working Folder is set to the script's location. lt The script completes and gives me the output it is supposed to, but VC shows this in the error log each time I run the task:

Cannot bind argument to parameter 'Path' because it is null.
Exception in Task: Cannot bind argument to parameter 'Path' because it is null.

Any idea what I'm getting wrong?

This?

https://social.technet.m...ecause-it-is-null-in-ise 

I'm using a PowerShell task to execute a script stored on disk. The exact location of the script file is specified and the Working Folder is set to the script's location. lt The script completes and gives me the output it is supposed to, but VC shows this in the error log each time I run the task:

Cannot bind argument to parameter 'Path' because it is null.
Exception in Task: Cannot bind argument to parameter 'Path' because it is null.

Any idea what I'm getting wrong?

Like Joey S pointed out, could be something like that? It's something in your script that is the cause of this, not within VisualCron. Try to debug it within your script.

---

Like Joey S pointed out, could be something like that? It's something in your script that is the cause of this, not within VisualCron. Try to debug it within your script.

The script in question does not invoke anything on a remote computer, and the script completes all of it's tasks as expected. It does not throw an error outside of the VisualCron PowerShell task. I do not get the error when running it manually, so I have nothing to debug.

I tried creating an Execute task that ran C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe, passing the script and its parameters with the -File argument. It still worked fine, and this time no error appeared in VisualCron.

Like Joey S pointed out, could be something like that? It's something in your script that is the cause of this, not within VisualCron. Try to debug it within your script.

The script in question does not invoke anything on a remote computer, and the script completes all of it's tasks as expected. It does not throw an error outside of the VisualCron PowerShell task. I do not get the error when running it manually, so I have nothing to debug.

I tried creating an Execute task that ran C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe, passing the script and its parameters with the -File argument. It still worked fine, and this time no error appeared in VisualCron.

Can you export the task and send the script to support@visualcron.com so we can take a look and see if we can reproduce this?

---

Can you export the task and send the script to support@visualcron.com so we can take a look and see if we can reproduce this?

Done. Thanks.

Most likely the problem is this line:



This seems like a property that works in a shell cmd window. We do not use the shell for execution as we use the PowerShell host for execution (no cmd window is involved). I suggest you pass this as a parameter.

---

Most likely the problem is this line:

Split-Path $script:MyInvocation.MyCommand.Path | Set-location 

This seems like a property that works in a shell cmd window. We do not use the shell for execution as we use the PowerShell host for execution (no cmd window is involved). I suggest you pass this as a parameter.

That was it. I removed that line and the errors have stopped. Thank you.