Skip to main content

Reading and Resolving PowerShell Errors - Part 4

This is part 4 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: Missing an argument for parameter

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

And here is the full error:
Get-Date : Missing an argument for parameter 'Year'. Specify a parameter of type 'System.Int32' and try again.
At line:1 char:10
+ Get-Date -Year -Month 9 -day 23
+          ~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Get-Date], ParameterBindingException
    + FullyQualifiedErrorId : MissingArgument,Microsoft.PowerShell.Commands.GetDateCommand

Many PowerShell cmdlets require some type of argument.  An argument is information.  I know, odd name.  The parameter in quest is –Year. Let’s take a look at its help file.
PS C:\> Get-Help Get-Date -Parameter Year

-Year []
    Specifies the year that is displayed. Enter a value from 1 to 9999. The default is the current year.
   
    Required?                    false
    Position?                    named
    Default value                none
    Accept pipeline input?       false
    Accept wildcard characters?  false

According to the help file, we need to provide an integer value between 1 to 9999.  Also in the error message, we were told to provide a System.Int32 object.  In other words, an integer.  That is just the .NET object name for an integer.
Resolution: Give it a number
PS C:\> Get-Date -Year 2018 -Month 9 -day 23

Sunday, September 23, 2018 2:55:59 PM




Comments

Popular posts from this blog

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.

How to run GPResult on a remote client with PowerShell

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.

Error icon when creating a GPO Preference drive map

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