Error "Cannot find file or path" when executing Powershell script?

Question

Trying to create a custom command to run a powershell script, but I keep getting an error saying it can't find the file or path supplied for launching powershell. Specifically:

 $powershellPath = "$env:windir\system32\windowspowershell\v1.0\powershell.exe"

Line is failing.

This path does exist on my computer, and I can launch powershell from this location using Command Prompt. Am I missing something?

Comments

Hello,

Please, provide the full script you are using and a screenshot of the error. You can post the details here or send to us at support@adaxes.com.

---

The full script is as below:

Function Execute-Procedure {
    $Context.CloudServices.ConnectExchangeOnline()   
    $waitTimeMilliseconds = 9 * 60 * 1000


    # Start a new instance of Windows PowerShell and run the script
    $powershellPath = "$env:windir\system32\windowspowershell\v1.0\powershell.exe" #"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
    $process = Start-Process 'X:<filepathreadacted>PowerShellQuery.ps1' -NoNewWindow -ArgumentList ("-Users %username% -AccessRights PublishingEditor -IncludeFolders '\%param-SelectedFolder%' -Recurse -Confirm:$false") -PassThru
    $process.WaitForExit($waitTimeMilliseconds)

    #Run the below in powershell manually to do this manually for now
    #& "X:<filepathreadacted>PowerShellQuery.ps1" -Users %username% -AccessRights PublishingEditor -IncludeFolders "\%param-SelectedFolder%" -Recurse -Confirm:$false
}

# Run this procedure
Execute-Procedure 

The error is as shown

Line 7 being the powershell launch line:

At first, I thought it was the ps1 file being on a network location but after swapping it to a local location and looking closer at the error, it is the powershell launch line that is the error.

Powershell is indeed in that location however:

I've restarted Adaxes service and my PC, yet the issue remains. Even launching the custom command with only the launch line and no other commands, it is still the error of can't find file or path. But I can launch it from this location using command prompt.

Please let me know what I have done wrong? Does Adaxes need some Import or other statement to access the powershell .exe?

Answer 1

Hello,

The $powershellPath variable is not used anywhere in the script so you can just remove the corresponding line. At the same time, it is generally not required to force Adaes to start/import PowerShell or anything of the kind. Additionally, we recommend you to just place the full code into the Adaxes action rather than storing it in a file. The main reason is that such scripts are no part of Adaxes functionality and require additional maintenance.

Comments

OK. The entire script file is very large, but when moving it into adaxes, I get two more errors:

" The term 'Get-Recipient' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. Stack trace: at GetUserIdentities, <No file>: line 79 ↲ at Execute-Procedure, <No file>: line 207 ↲ at <ScriptBlock>, <No file>: line 281 The term 'Get-PublicFolder' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. Stack trace: at FindFoldersToUpdate, <No file>: line 44 ↲ at Execute-Procedure, <No file>: line 223 ↲ at <ScriptBlock>, <No file>: line 281 "

I've seen this before, where Adaxes doesn't have the same cmdlets as full powershell, which is why I was trying to run the file itself in Powershell directly.

The affected lines are:

        $id = (Get-Recipient $user).PrimarySmtpAddress

        $foldersFound = @(Get-PublicFolder -Recurse:$recurseOnFolders $includeFolder -ResultSize Unlimited | Sort-Object Identity)

I can attach the entire file if needed, but it is a big one.

What should I do in this case? Is there some Adaxes equivalent to these, or is there some better way to run a Powershell script with cmdlets that Adaxes doesn't recognize?

---

Hello,

Whenever you run a cdlet and it is not recognized, there can be two possible causes. One is that the corresponding PowerShell module is not installed on the computer where Adaxes service runs. The other is that the Adaxe service account (specified during Adaxes installation) does not have access to the module (for example, due to the module installation peculiarities).

As for Exchange cmdlets, the error occurs because they are executed outside the connection being established. For an example of the proper approach, see https://www.adaxes.com/script-repository/connect-to-exchange-with-powershell-s506.htm.

---

The connection to Exchange line added fixed it, you are absolutely correct!

# Connect to Exchange Online
$Context.CloudServices.ConnectExchangeOnline() 

Thank you so much for the detaild and quick guidence! Everything is working as it should now.