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