Solution to error 800401f9 - Error in the DLL 
Author Message
 Solution to error 800401f9 - Error in the DLL

When using ADO to open a database, you may get the wonderfully
descriptive error "Error in the DLL" with an error code of 800401f9,
or maybe a 80040e37 "table does not exist" when you know good and well
it's there.

It is a known problem that Cold Fusion will cause this, but apparently
several other software packages will also cause it, if our experience
is typical.  On Windows 2000, since you can't just reinstall MDAC,
execute the following commands to unregister and re-register two
essential DLLs:

regsvr32 -u "c:\program files\common files\system\ado\msado15.dll"
regsvr32 -u "c:\program files\common files\system\ole db\oledb32.dll"
regsvr32 "c:\program files\common files\system\ado\msado15.dll"
regsvr32 "c:\program files\common files\system\ole db\oledb32.dll"

In our case, this fixed the following lines of WSH VBScript code that
we use to get a user's full distinguished name in active directory:

=====
Set ActiveDir  = CreateObject("ADODB.Connection")
ActiveDir.Provider = "ADSDSOObject"
ActiveDir.Open "ADs Provider"

Query = "select adspath from 'LDAP://dc=Archon,DC=Com' where
sAMAccountName='" & WshNetwork.Username & "'"

set ResultSet = ActiveDir.execute (Query)
set ActiveDir = nothing
=====



Tue, 03 Jun 2003 07:48:26 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. Error 800401f9 Error in the DLL

2. Error in DLL 800401F9

3. Access 2.0 Asset Solution Provider DLL error

4. SOLUTION: Error 3447 - VBAJET32.DLL could not be initialized

5. Error: could not load dll, error 0

6. Compile error: Automation error, Error 32811: Unexpected error

7. Error no. 48: Error opening DLL

8. Acc97 creating MDE receive Error In Loading DLL error

9. Run-time error 48 Error in loading DLL in XP

10. Error in loading DLL (Error 48)

11. Error 48: Error Loading DLL

12. Error message : "Error in loading DLL"

 

 
Powered by phpBB® Forum Software