Advanced Windows PowerShell Scripting Video Training

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

Tuesday, January 5, 2016

Reading and Resolving PowerShell Errors - Part 2

This is part 2 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: is not recognized as the name of a cmdlet

Here is our starting code:
Get -Date -Year 2018 -Month 9 -day 23

And here is the full error:
Get : The term 'Get' 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.
At line:1 char:1
+ Get -Date -Year 2018 -Month 9 -day 23
+ ~~~
    + CategoryInfo          : ObjectNotFound: (Get:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

The reason for this is very simple. Look at the first sentence of the error message.  It is telling you to look at ‘Get’.  PowerShell syntax says that you start with a cmdlet, function, script, program or a keyword.  PowerShell cmdlets are verb-noun.  This is just a verb.  A space was added.  The correct command is Get-Date.
Resolution: Remove the extra space in the middle of the cmdlet.
Get-Date -Year 2018 -Month 9 -day 23 


Some can argue that the intent was to use an alias.  Well, how did that work out?  This is why I advocate the usage of Full Command Syntax in scripts.  If this was an alias, it is not an alias on this device.  When programing PowerShell code, never use a custom alias in your scripts. TAB completion will help you type faster if that is the reason why you are using aliases.  If you inadvertently put in an personal alias in your code and tested the code on your device, it will work.  Hand that code off to your client and they will receive the error above.  Probably not what you want to happen.

No comments: