Powershell Value of argument path is NULL

[CmdletBinding()] Param ( [Parameter(Mandatory=$True,Position=0)] [string]$foldersource, [Parameter(Position=1)] [string]$folderdest, [Parameter(Position=2)] [string]$file, [Parameter(Position=3)] [string]$instance ) foreach ($cluster in GC "$foldersource\Servers_List.txt") { $output = "Server: $cluster Patch Installation on: $(Get-Date -format 'u')" try{ Invoke-Command -ComputerName $cluster -ScriptBlock { cd $folderdest .\$file /X:$folderdest Start-Sleep -s 10 .\SETUP.exe /action=patch /instancename=$instance /quiet /IAcceptSQLServerLicenseTerms } -ErrorAction Stop; $output += " SUCCESS" } catch { $output += "Failed - $($_.exception.message)" } $output | Out-File -Append $foldersource\Patch_Result_Non_SP.txt }

ERROR: Cannot process argument because the value of argument "path" is null. Change the value of argument "path" to a non-null value. + CategoryInfo : InvalidArgument: (:) [Set-Location], PSArgumentNullException + FullyQualifiedErrorId : ArgumentNull,Microsoft.PowerShell.Commands.SetLocationCommand + PSComputerName : The term '.\$file' 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. + CategoryInfo : ObjectNotFound: (.\$file:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException + PSComputerName : The term '.\SETUP.exe' 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. + CategoryInfo : ObjectNotFound: (.\SETUP.exe:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException + PSComputerName :

You've to pass your arguments either via -ArgumentList or via $using convention to the Invoke-Command cmdlet. Since you are not doing it that way $folderdest, $file will be null in the scope of the Invoke-Command scriptblock -> the scriptblock defines a seperate scope!

From Microsoft:

-ArgumentList

Supplies the values of local variables in the command. The variables in the command are replaced by these values before the command is run on the remote computer. Enter the values in a comma-separated list. Values are associated with variables in the order that they are listed. The alias for ArgumentList is Args.

Also checkout the exmamples of the Invoke-Commandcmdlet via Get-Help Invoke-Command -Examples.

If you don't like the ArgumentList solution you can also use remote variables.

Additionally you should also define an absolute path to your Setup.exe!

So your code should look like:

....
 Invoke-Command -ComputerName $cluster -ArgumentList $file, $folderdest, $instance -ScriptBlock 
{
    Param(
       [string] $rFile,
       [string] $rfileDest,
       [string] $rInstance
    )
    
    # Remove Write-Host after the script block works fine -> Write-Host is only a quick and dirty way to dump the variables content

    Write-Host $rFile
    Write-Host $rfileDest
    Write-Host $rInstance

    cd $rfileDest

    $someArgs = "/X:{0}" -f $rfileDest
    Start-Process -FilePath  $rFile -ArgumentList $someArgs -Wait -PassThru

    Start-Sleep -s 10

    $setupArgs = "action=patch /instancename={0} /quiet /IAcceptSQLServerLicenseTerms" -f $rInstance

    Start-Process -FilePath ".\Setup.exe" -ArgumentList $setupArgs -Wait -PassThru

}
....

Hope that helps.

Recommended topics

Hot tags