Random issue: arguement passed to the -SettingsFile does not exist
Random issue: arguement passed to the -SettingsFile does not exist
Product: PowerShell Universal Version: 5.42
Well, PSU VS. 5 is a lot of fun but I am not here to complain. I’m having a litany of issues, but I don’t know where this error can be fixed. This error is thrown by certain scripts that have been running for months. Here is a screenshot:
It looks like this is the setting where you specify the JSON appsettings file when you start the executable from command line, but I’ve literally never done that.
I’ve checked the settings file as well as the GUI settings under Automation and there is a file path to change or set as far as I can see.
Can someone simply help me and tell mere what system file (I assume) I can correct this in? Thanks
b49daee4d43ccc041f9ed37bca58c597d13a7ab3.png
All Comments (2)
-SettingsFile is a parameter for pwsh.exe. I would check your environments page for the environment you are trying to run this script. What does the environment have configured? We will pass in a settings file if you have Disable Windows Compatibility checked. Otherwise, PSU doesn’t use this parameter.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
That’s what I missed. I recently have been working through other issues. Primarily environments and module behaviors. I think I’m finally on the other side of those issues but I for sure was flipping the checkbox for the disablement of the Windows Compatibility during my ‘debugging’. I didn’t correlate the two actions because checking the box in the GUI didn’t have a constraint to validate whether or not I had a value for that parameter. It’s possible that after years I’m still not fluent enough in Powershell to know that this is a required parameter for during off that compatibility option.
Thank you for replying, this makes total sense. Especially since the issue was with path and it looked like a formatting issue and\or something was missing.
I appreciate you taking the time to reply.