Can't get Connect-Pfa2Array to work correctly on Windows Task Scheduler

[lemastermj]

We are wanting to backup a large MS SQL database using the pure array. It successfully works when ran manually. But when we attempt to put it in Windows Task Scheduler we receive errors.

To narrow the error down I created a more simple power shell script that attempts to connect to the pure array. As with the other the file runs successfully when executed manually. However when we execute in Windows task scheduler we receive an error:

Error connecting to Pure Flash Array: Could not load file or assembly 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxxxx' or one of its dependencies. The system cannot find the file specified.

I found a KB related to this on:

https://support.purestorage.com/bundle/m_microsoft_platform_guide/page/Solutions/Microsoft_Platform_Guide/a_Windows_PowerShell/topics/concept/c_issue_11.html

It mentioned using the MSI installer (which we didn't.) It goes on to mention modifying the the machine.config which we attempted to with no change.

I checked the permissions on the PEM file and even if I manually run the windows sheduled task (I am admin of the box,) it still fails. Note I currently have the job set to run in my name.

We have explicitly given the path to the PEM file code.

Hello_Pure_bogus_var.txt

Note: this is a powershell (not txt)

Any help or suggestions? Thank you all.

[japod]

Thanks for reporting your use case and taking the time to put together a reproducer script. I appreciate it. We do not test such a scenario but i believe it is an important one. We will look into what we can do to support this use case in one of our next SDK releases.
Could you please help me understand your environment setup better? It would be great to know at least your OS and PowerShell versions. Thanks.

[lemastermj]

Thanks,

In our scenario we are using a Window 2019 Server to initiate the powershell script using windows task scheduler. We are using powershell version 5. The same box can run the script when the user starts the job. Additionally we had our ansible team setup the script in their environment and attempt to run the powershell and they received the same error. I'm not an ansible guy so I can't speak to their setup and settings. I ran the error through AI and got several suggestions like explicitly giving the path to the module repository and that didn't do anything. I believe it is the inability of the newtonsoft.json to either function or access the pem file in a non-interactive powershell environment.

Suggestions from AI (saying to put at the top of the script)
$env:PSModulePath += ";C:\Program Files\WindowsPowerShell\Modules"
add-type -path "C:\Program Files\WindowsPowerShell\Modules\PureStoragePowerShellSDK2\2.43.46\Newtonsoft.Json.dll"

Our overall goal is to use this to backup some very large MS SQL databases.

Lastly, if there is another method besides windows task scheduler we could accomplish the job of freezing the db, and taking a snap I can look into that.

As a testing method, I am having our Pure adminitrator create a username and password so we can bypass the PEM file.

Thanks again

[lemastermj]

Update, when I use username and password the scripts work. So I think it is just the function of using the PEM file.

Thanks.