Skip to main content

Reading and Resolving PowerShell Errors - Part 3

By
This is part 3 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: A parameter cannot be found that matches parameter name

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

And here is the full error:
Get-Date : A parameter cannot be found that matches parameter name 'ComputerName'.
At line:1 char:38
+ Get-Date -Year 2018 -Month 9 -day 23 -ComputerName DC1
+                                      ~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Get-Date], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.GetDateCommand

This is one of my favorites.  TAB Completion is a wonderful thing.  It helps us understand what parameters are available to us and prevents typos.  Many times I catch my students forcing a parameter into a cmdlet.  If the parameter will not TAB complete, then 1 of 2 things is the problem.
1 – The Parameter is not available for the cmdlet.  Just because one cmdlet has a ComputerName parameters does not mean every one does.
2 – The parameter is not part of the current parameter set.

To help with #1, take a look at the syntax block of the cmdlets help file.
SYNTAX
    Get-Date [[-Date] []] [-Day []] [-DisplayHint {Date | Time | DateTime}] [-Format []] [-Hour
    []] [-InformationAction {SilentlyContinue | Stop | Continue | Inquire | Ignore | Suspend}] [-InformationVariable
    []] [-Millisecond []] [-Minute []] [-Month []] [-Second []] [-Year []]
    []
   
    Get-Date [[-Date] []] [-Day []] [-DisplayHint {Date | Time | DateTime}] [-Hour []]
    [-InformationAction {SilentlyContinue | Stop | Continue | Inquire | Ignore | Suspend}] [-InformationVariable
    []] [-Millisecond []] [-Minute []] [-Month []] [-Second []] [-UFormat
    []] [-Year []] []

Get-Date has 2 syntax blocks.  This is because there are two parameters that cannot be used at the same time.  In any case, you will not find a –ComputerName parameter listed.  In other words, you cannot use this parameter with this cmdlet.

As for the parameter set, this can be a bit tricky.  If you Type Get-Date in the PowerShell ISE, you will see both –Format and –Uformat­ parameters listed

If you use one of those two parameters, the other is filtered out.


Resolution:
Use TAB completion or the cmdlets help file so you know what parameters can be used.  Also, do not force a parameter into a cmdlet.  It will not work.

For those of you who want a dinfinative list of which parameters can work together, check out my post on Finding the Required Parameters in Parameter Sets.  The code will list each parameter in each set for any cmdlet you want to examin.

Labels:

Comments

Post a Comment

Popular posts from this blog

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

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

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