__error__ in PowerShell ISE

error in PowerShell ISE

Wow, I finally got around to doing a little blogging. This has thus far been a very busy year. I’m actually writing this in the air heading to teach a PowerShell class in North Carolina and prepping my sessions for PowerShell Summit Europe in a few months.

When I start helping my students debug their issues in class, I often walk up to their monitors and see the error right away. I am very cautious to point out at the beginning of class that the reason that I see their errors so fast is because I have made the same errors so often. Here is one that left me scratching my head.

While adding a valid parameter to a function that I was developing, I had this error in the ISE.

I’ll be honest, this was a new one for me. Looking at the message, I realized that there was a casting of string. This pointed me to my param block. Sure enough, I placed a comma where I should not have.

You can see it right after [String]. My bad. Hey, all of us make mistakes.

Comments

Paul said…

Hi Jason,
I was in your NC class in Morganton. Very informative, really appreciated your time and expertise.

Unfortunately, I left the code for our last day's work on the VM and forgot to copy it to my laptop before class was over. It was the module dealing with writing our own cmdlets/modules using params and scriptblocks with try/catch. I'm working on a project where I could really use that information at work. Do you happen to have your copy of the project that we worked on in class?

February 13, 2017 at 1:41 PM

Jason Yoder, MCT said…

Paul,

Check the MISC folder on the class OneDrive Friday. I'll upload a copy after we re-create it this week.

Jason

February 13, 2017 at 1:49 PM

Sticky Key problem between Windows Server 2012 and LogMeIn

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 .

Where did a User’s Account Get Locked Out?

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...

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.

Jason Yoder, MCT

Search This Blog