|
|
Custom Search
Guy recommends : 
Get more ideas for your PowerShell scripts with SolarWinds' WMI Monitor. Funny computer jokesCode 800 Errors in VBScript / WSHTroubleshooting Code 800 Errors found in VBScriptThis 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. 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 errorsErrors 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 Tool
|
