List of all VBScript error codes.

In class we talked about the ability to handle errors in our scripts. The question came up as to how many potential error codes there are. Run the script below to find out. Remember that the function your are attempting to provide error handling for will not be capable of generating all these errors. You only need to script against the most likely ones, and then a catch all for anything unusual that pops up. This script uses a method that we did not talk about in class, Err.Raise. You use Err.Raise followed by the error number that you are interested in to help you test your error handling. This will cause your script to believe that the error actually occurred and invoke your error handling.

Dim errDef, i

WScript.Echo "VBScript-Errors:"
WScript.Echo "Number", "Description"

On Error Resume Next
Err.Raise 1
errDef = Err.Description

For i=1 to 2^16-1
Err.Clear
Err.Raise i
If Err.Description <> errDef Then
WScript.Echo Left(Err.Number & ":" & Space(6), 6), Err.Description
End if
Next

Reference: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.scripting.vbscript&tid=22ee5a58-d2e2-4e54-9c19-0856c2e70eb1&cat=en-us-msdn&lang=en&cr=US&sloc=en-us&m=1&p=1

Comments

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.

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

Jason Yoder, MCT

Search This Blog