Advanced Windows PowerShell Scripting Video Training

Advanced Windows PowerShell Scripting Video Training
Advanced Windows PowerShell Scripting Video Training

Monday, January 11, 2016

Reading and Resolving PowerShell Errors - Part 8

This is part 8 of my series of the most common PowerShell errors that are made in my PowerShell classes.  I will be posting one a day to help you understand why an error occurred and what the error’s meaning is.

Today’s error: No data returned from a remote command

Here is our starting code:
Invoke-Command -ComputerName DC, SVR1 -ScriptBlock {
        Param ($ID, $MT)
        Get-CimInstance -ClassName Win32_Logicaldisk |
        Where {$_.DeviceID -eq $ID -and $_.MediaType -eq $MT}
    } -ArgumentList 12,"C:"

And here is the full error:
There is no error except nothing comes back.

Resolution:
Change the order of the arguments.
In this example, we are passing information from the local device to the remote device.  The problem is in order of information being passed from the –ArgumentList to the PARAM() variables.  They are being passed in the wrong order.  The first item in the –ArgumentList will be past to the first variable in the PARAM() list.  The second to the second and so on and so forth. 
I have had people argue with me that they should be able to choose which value is saved to which variable.  Well, you do.  This is an ordered list.  Order it correctly.
Invoke-Command -ComputerName DC, SVR1 -ScriptBlock {
        Param ($ID, $MT)
        Get-CimInstance -ClassName Win32_Logicaldisk |
        Where {$_.DeviceID -eq $ID -and $_.MediaType -eq $MT}
    } -ArgumentList "C:",12

DeviceID DriveType ProviderName VolumeName Size        FreeSpace  PSComputerName
-------- --------- ------------ ---------- ----        ---------  --------------
C:       3                                 10368315392 1352790016 DC           
C:       3                                 10368315392 2048032768 SVR1  



No comments: