Skip to main content

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.

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.