Error - Could not load file or assembly ADODB 1

[jbehrne]

Hi All,

I recently depolyed an app. on several computers that I built using VB.Net 2005. All of the computers are running Win XP w/SP2 with all of the latest patches, etc. applied.

On one computer whenever I run the application I get the following error:

Unhandled exception has occurred in your application. If you click  Continue, the appliction will ignore the error and attempt to continue. If you click Quit, the application will close immediately.

Could not load file of assembly, 'ADODB, Version=7.0.3300.0. Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Any ideas as to what is going wrong? Thanks for any help...

jbehrne

If at first you don't succeed, call in an airstrike. - Murphy's Laws of Combat Operations

 

[djj55]

Hello, have you looked at the .net framework version?
Good luck,
djj

 

[jbehrne]

DJJ,

The computer currently has 1.0, 1.1 and 2.0 installed. Will it run with all of the frameworks installed (this isn't a problem on the other computers...).

Thanks,

jbehrne

If at first you don't succeed, call in an airstrike. - Murphy's Laws of Combat Operations

 

[macleod1021]

ADODB isn't framework, it's COM. You need to make sure that the dll is on the system. The easiest way is to copy it from your computer and do regsvr32 from a command line.

 

[jbehrne]

macleod1021,

I'll give your suggestion a shot and see what happens.

jbehrne

If at first you don't succeed, call in an airstrike. - Murphy's Laws of Combat Operations

 

[ThatRickGuy]

The ADO libraries should be included in XP SP2. I would recommend running windows update and see what is out dated.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[jbehrne]

In case anyone else runs across this error here is how I solved it:

Copied "ADODB.dll" from another computer and dropped it in the folder "C:\Windows\Assembly"

If at first you don't succeed, call in an airstrike. - Murphy's Laws of Combat Operations

 

[jbehrne]

ThatRickGuy,

I initially thought that the samething but Windows update did not turn up any updates. The Windows XP Pro disk that I used for the problem computer has all of the lastest critical and recommened updates slip streamed in it... I got it from my universities Computing Services department.. Maybe thier copy is messed up.

jbehrne

If at first you don't succeed, call in an airstrike. - Murphy's Laws of Combat Operations

 

[ThatRickGuy]

Interesting. And you are positive that it is XP SP2? Last time I went through the documentation I could have sworn that MDAC 2.8 (ADODB included) was built into SP2.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[jbehrne]

Yes, I'm positive. I even went so far as to download and try to install MDAC 2.8 (which would not install because it found SP 2 had already been installed). I thought that it was included too!

If at first you don't succeed, call in an airstrike. - Murphy's Laws of Combat Operations

 

[AtlantaStu]

I just had this problem on a windows service app. Solved it by adding a reference to adodb. Didn't need it when testing on my own development machine, but the problem became apparent when I deployed to the target server. The reference includes the dll in the installation kit.