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

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
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