Code Error 80005000 -
An invalid ADSI pathname was passed

Guy recommends:
VBScript Training Video on CD

---

Funny computer jokes

Troubleshooting Code Error 80005000 - An invalid ADSI pathname was passed

My main interest is in VBScript code errors, however code 80005000 is also a common error when installing Exchange.  The common thread is an error with the directory pathname.  This error is also referred to as E_ADS_BAD_PATHNAME.

Two variations of Code Source: 80005000  Errors

1. An invalid ADSI pathname was passed (Exchange).
2. An invalid directory pathname was passed (VBScript)

  ‡

1) An invalid ADSI pathname was passed

When you run Microsoft Exchange 2003 (2000) Server Setup with the /forestprep switch, the installation fails and you may receive the above error message.

The Cause of error 80005000 in Exchange

You run setup /forestprep, but it does not complete properly.  Active Directory 'flags' that it has been run, but in reality it did not finish.

Check the server progress log for entries like.

(G:\admin\src\udog\setupbase\basecomp\baseatom.cxx:775)
Error code 0X80005000 (20480): An invalid ADSI pathname was passed.

The Solution for Exchange

Open ADSI Edit.
Navigate to this location under the Configuration container:
CN=Configuration; CN=Services; select CN=Microsoft Exchange

Right-click CN=Microsoft Exchange, and then click Properties. From the Attributes tab, under Select which properties to view, click Both.
From the Select what property to view pull-down menu, select Heuristics.
If the value is set to 2, then you have already run ForestPrep.

Solution, reset the Heuristics property, click Clear, and then click Apply. The Value(s) field will have change to 'not set'.

2) Error Code 80005000 in VBScript

This variation of error code 80005000 occurs when you execute a VBScript.

Error: An invalid directory pathname was passed

Source: Active Directory

The Symptoms you get 80005000

When you execute the script you get a WSH message box like this (See diagram).  The VBScript does execute as you hoped.  One possibility is that you are using an LDAP object which has been misspelled.  Another cause could be missing speech marks in a value.

The Cause of Code Error 80005000

Your VBScript contains an illegal LDAP reference, probably a typing mistake, maybe an extra letter.

In this particular instance there is a knock on effect of a variable not being properly declared.  When the script needs to use the variable in line 8, WSH flags the error as Code 80005000.

The Solutions to Error 80005000

Check the spelling of all your objects and methods.  Look for clues particularly in the Line: x number.  However, in this particular example the root cause is earlier in line 4.

Another plan would be to introduce error correcting code using E_ADS_BAD_PATHNAME for example:

Const E_ADS_BAD_PATHNAME= &h80005000

Example of a Script with Error 80005000

Briefly, the idea of the script is to create a new user using the variable guyname.  The problem is that the value of guyname is not in speech marks.

Problem Line 4 - strNewUser = bilbo277
Solution Line 4 - strNewUser = "bilbo277"

Solution with double quotes around the variable.

Guy Recommends: SolarWinds Engineer's Toolset v10

The Engineer's Toolset v10 provides a comprehensive console of utilities for troubleshooting computer problems.  Guy says it helps me monitor what's occurring on the network, and the tools teaches me more about how the system literally operates.

There are so many good gadgets, it's like having free rein of a sweetshop. Thankfully the utilities are displayed logically: monitoring, discovery, diagnostic, and Cisco tools.  Download your copy of the Engineer's Toolset v 10

Another Example of Error 80005000

The problem is the order of group, domain

The correct sequence is group, domain.  Also ou, domain.

Perhaps you can spot the error on line 16, domain, strContainer.

Another Example of Error 80005000

Try a different solution, download SolarWinds ipMonitor

Here is my thinking, ipMonitor will give you valuable data about your network and servers.  This extra information just may unlock the solution to your error code.  One more thing, sometimes when troubleshooting you go around in circles; therefore if you try a different, but related approach, you may just crack the problem.  Free Download of SolarWinds ipMonitor (21 day eval).

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.

Do you need extra help?

For interpreting the WSH messages check Diagnose 800 errors.

For general advice try my 7 Troubleshooting techniques

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:

 *