Guy's Scripting Ezine 7 - On error resume next

Guy recommends:
VBScript Training Video on CD

Is your server running slowly?  Check with SolarWinds ipMonitor

Get a free evaluation copy of ipMonitor

Contents of Guy's Scripting Ezine 7 - On error resume next

• This week's secret
• Example 1 - Designed to fail with error message
• Example 2 - Half the script works
• Example 3 - On error resume next
• Troubleshooting and Resources

This week's secret

I will let you into a secret, sometimes you need to know a little theory. So before we get on with this week scripts, here is some background information. VBScript is an interpreted language; whereas other languages like Perl and C++ are compiled first then executed. I hear you saying, 'So what. Who cares?'  Well, how the scripting language behaves matters when you are troubleshooting.

When I first I saw a VBScript error message, I was surprised, not because there was a mistake, but because part of the script had actually worked. I had wrongly expected that the WSH engine would abort the whole code. My message is this: watch out when you are experimenting, a faulty script may work up to the error and then the second part fails.

To illustrate this point I would like you to experiment with the classic map network drive script. Firstly let us get in synch, please check these three learning goals:

1. To troubleshoot VBScript
2. To understand what happens when you get an error message
3. To decide whether to use: 'on error resume next'

Secondly preparing and editing my scripts is particularly important this week.
When you examine the three Example scripts:
a) Substitute one of your real servers and shares for \\alan\home
b) Leave \\offline\home as it is - this is the deliberate error.

Example 1: A script designed to fail with an error message

Note: This Example is designed to fail! The result should be no drives get mapped and you get an error message.

Troubleshooting: Try this reference

Example 2: A script designed to partially work with an error message

Warning – disconnect the network drive that you created in Example1.
Note: This Example is designed to HALF work and generate error message - 800704B3. The difference here is the order of Network2 and Network1. I have also changed the order of RemotePath2 and RemotePath1 to emphasise the difference.

Double check that you have altered \\alan\home to a real server and share, leave \\offline\home to generate the error.

Troubleshooting: Try this reference

Try disconnecting the Y: drive from the previous example.

Example 3: Try - On error resume next

Warning – disconnect the network drive that you created in Example1.
Note this Example is designed to map the SECOND network drive and give no error message because of line 6: on error resume next

Troubleshooting Resources

• Try disconnecting the Y: drive from the previous example.
• Troubleshooting: Try this reference.
• Feeling adventurous? Try incorporating RemoveNetworkDrive method in your test scripts.
• For more information try Logon Script Home
• or Try WSH Home

Guy Thomas recommends Computer Training Software. 

Their topics and material are ideal for getting you started with VBScript.  The videos are easy to follow and you can control the pace.  Try their free demo material and then see if you want to buy the full package. See more about VB Script Training CD.

Home Copyright © 1999-2008 Computer Performance LTD All rights reserved

Please report a broken link, or an error.