Skip to main content

Reading and Resolving PowerShell Errors - Part 10

This is part 10 of my series of the most common PowerShell errors that are made in my PowerShell classes.  This is the last one!
Today’s error: My data file does not have my data.

Here is our starting code:
Get-Process |
    Measure-Object -Property CPU -sum |
    Select-Object -Property Name, CPU |
    Export-CSV -Path c:\temp\data.csv

And here is the full error:
No error, just the wrong data.  Here is the contents of the CSV.
PS C:\temp> import-csv -Path C:\temp\Data.csv

Name CPU
---- ---

Resolution:
The problem here is that the programmer did not keep track of what is in the PowerShell Pipeline. I see this very often.  When you are constructing a pipeline, you need to keep track of what is in the pipeline.  After each statement, pipe to object to Get-Member and verify that you are still working with the object type that you expect.
PS C:\temp> Get-Process | Get-Member


   TypeName: System.Diagnostics.Process

Here you can see that the original object is System.Diagnostics.Process.  Now look at the member information after the execution of the second command.
PS C:\temp> Get-Process |
    Measure-Object -Property CPU -sum | Get-Member


   TypeName: Microsoft.PowerShell.Commands.GenericMeasureInfo

Name        MemberType Definition                               
----        ---------- ----------                               
Equals      Method     bool Equals(System.Object obj)           
GetHashCode Method     int GetHashCode()                        
GetType     Method     type GetType()                           
ToString    Method     string ToString()                        
Average     Property   System.Nullable[double] Average {get;set;}
Count       Property   int Count {get;set;}                     
Maximum     Property   System.Nullable[double] Maximum {get;set;}
Minimum     Property   System.Nullable[double] Minimum {get;set;}
Property    Property   string Property {get;set;}               
Sum         Property   System.Nullable[double] Sum {get;set;}

The object typename is now Microsoft.PowerShell.Commands.GenericMeasureInfo.  In other words, you have a completely new object.  Many cmdlets alter the object in the pipeline. The next command, Select-Object will attempt to filter out all but two properties.  The problem here is that the properties that are being asked for are from the object System.Diagnostics.Process, not the current object in the pipeline.
To fix this, remove the Measure-Object cmdlet.
Get-Process |
    Select-Object -Property Name, CPU |
    Export-CSV -Path c:\temp\data.csv


This mistake is most often the result of not wanting to make the effort.  Once you are experienced working with a set of cmdlets, you will know what they put into the pipeline.  Until you are experienced with a set of cmdlets, make sure you check the pipeline often.  This will save you a lot of work in debugging.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.