Skip to main content

Reading and Resolving PowerShell Errors - Part 3

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.




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.