Code 800 Errors in VBScript / WSH

Troubleshooting Code 800 Errors found in VBScript

This page is designed to help you cure 800xxxxx error messages in your VBScript.  To solve your problem look for clues in the Windows Script Host message box.  In particular always check the Line: (number), the Source: and what the Error: message says.

The Symptoms of code 800 messages

The error happens when you execute, run, or double click a VBScript script (.vbs file).  Most probably you are trying to create a Logon script.  One possible scenario is that you are creating a Windows logon script and there is a typing mistake in the server name.Code 800 Errors in VBScript / WSH

Alternatively, you are writing an Active Directory VBScript, which adds computers or amends users properties.

Yet another scenario is that you are creating a WMI scripts to interrogate the operating system.  In each case, what you see is a message box with Windows Scripting Host in the title.

Categories of VBScript 800xxxxx error codes


Code 80005xxx – ADSI errors

Errors beginning with 80005xxx point to an ADSI error in your VBScript.  While the message box calls them ADSI, I think of them as LDAP errors.  For example, suppose that you are scripting a user’s properties and you type givename instead of givenName (two ns), that mistake in the ADSI / LDAP name would generate an 80005xxx error.

Sundry Errors – Including WMI and MSN

Recommended: Solarwinds’ Permissions Analyzer – Free Active Directory ToolFree Permissions Analyzer for Active Directory

I like thePermissions Analyzer because it enables me to see WHO has permissions to do WHAT at a glance.  When you launch this tool it analyzes a users effective NTFS permissions for a specific file or folder, and takes into account network share access, then displays the results in a nifty desktop dashboard!

Think of all the frustration that this free SolarWinds utility saves when you are troubleshooting authorization problems for user’s access to a resource.  Give this permissions monitor a try – it’s free!

Download SolarWinds’ Free Permissions Analyser – Active Directory Tool

Code 8007xxxx – Operating System Error e.g. Windows 7 / Server 2003 / 8

If your error begins with 8007xxxx then look for an factor outside VBScript.  For instance, check the spelling of the name of your share or printer.  Another possibility is that the server named in the script, is simply down or otherwise unavailable.

Code 8009xxxx

Code 800Axxxx  Syntax Errors

In VBScript, there are 53 syntax errors all beginning with 800Axxxx.  These errors should be among the easiest to cure because the message often includes the missing punctuation mark or bracket.

Solarwinds Free WMI MonitorGuy Recommends: WMI Monitor and It’s Free!

Windows Management Instrumentation (WMI) is one of the hidden treasures of Microsoft operating systems.  Fortunately, SolarWinds have created the WMI Monitor so that you can examine these gems of performance information for free.  Take the guess work out of which WMI counters to use for applications like Microsoft Active Directory, SQL or Exchange Server.

Download your free copy of WMI Monitor

Do you need additional help?

Give something back?

Would you like to help others?  If you have a good example of this error, then please email me, I will publish it with a credit to you:

If you like this page then please share it with your friends