Skip to main content

Reading and Resolving PowerShell Errors - Part 2

By
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.
Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
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.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Error icon when creating a GPO Preference drive map

By
You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the
1 comment
Read more