All Scripts Stopped Working

[Paul Sorauer]

Hi there

I'm using the new experimental scripts system, all ps1 scripts, and getting context using $env:CURRENT_DIR etc. It's been working well for several months with no problem, including using nested subfolders for organisation.

I noticed a around a week ago that I tried to run a script and it failed. I'm just troubleshooting now and it seems that none of the scripts work no matter where in my folder structure they sit - it simply says "The system cannot find the file specified". That's in the OC notification panel (at the bottom) and also in logs. It doesn't give any more information than that.

It's odd, because when I use the "Scripts" button at the top I can navigate all my folders of scripts and they're displaying correctly with the associated icons, and even if I select "open scripts folder" I can see and open my scripts in a text editor with no problem.

It appears that it's just the execution of the script that is failing (there's also no command prompt window that appears) and literally all it says in the logs is "The system cannot find the file specified".

I restarted both OC and my machine and that makes no difference.

What else can I try?

Anecdotally, I haven't used scripts in a while and seem to remember an update being pushed out several weeks ago, so it may have been broken since then but I'm not sure if it's tied to the new release or not.

[OneCommander Support]

Does the built-in one still work

"Example parsing selection with PowerShell.ps1"

Do you remember editing ScriptsExecutor.json ?

Try also triggering error once and check any additional errors logged by RMB on system tray icon > View logs

[Paul Sorauer]

I removed and archived the example scripts or those I wouldn't use so I can't test with your original scripts. But none of the scripts in any subfolder will run. The "Selection to Opposite Window" script that you can see below is actually yours, just renamed and moved to a diff folder. It had been working since I made these changes and I just tried it again.

I in no way touched ScriptsExecutor.json. I had previously turned on the checkbox in advanced settings for the new script system, but that was a while ago and all my scripts had been running for months after that (opening in a new CMD window as opposed to under the OC process). I hadn't touched anything else. That particular file hasn't been touched since Oct 2024:

When I try to execute a ps1 script I just get an error notification:

And the log literally just says it couldn't find the file:

Whether that means it can't find some dependency file (such as ScriptsExecutor.json) or the actual target script, I don't know.

As you can see from the first screenshot, it correctly traverses the script folders and identifies not only the ps1 scripts, but also attaches the correct icon files.

I think it's just something about how it tries to execute the scripts that fails.

What else can I look at?

Cheers,

Pau

[OneCommander Support]

Did you update powershell, or replace it with something else since then?

Press F10 in any OC folder to open cmd in that folder and just try typing 

powershell

does it throw an error?

If not, try extracting beta of v4 in a new folder and see if it works there

https://onecommander.com/OneCommander0.0.37.0.zip

If not, I will add some more verbose output as at this time I am not sure what part throws that error

[Paul Sorauer]

Ok, that was all I needed to troubleshoot, thank you.

Powershell 1.0 was missing from my PATH so as soon as I added it back in, the scripts started working again.

Thanks for the pointer!!!