none
Could not load file or assembly ADODB, Version=7.0.3300.0

    Question

  • I have an application broadly deployed (about 10 computers). As of yesterday, two of these computers are unable to start the application, and failing with the error below. All other computers run the application just fine.

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

    I checked and ADODB.dll version 7.0.3300.0 is in the GAC in the deployment target machines.

    I find ADODB.dll in my C:\Program Files\Microsoft.NET\Primary Interop Assemblies folder (development computer), but this is version 7.10.3077.0 (file properties version)

    I see ADODB.dll as a project reference, but this shows version 7.0.3300.0, and shows the path to the PIA folder. I have no clue why these are not showing the same version number. Local Copy is false.

    Installing MDAC 2.8 on the failing deployment target machines did not help.

    Any clues or ideas or things to try??
    Thursday, January 26, 2006 6:04 PM

Answers

  • sounds like a versioning issue ...try installing the upgraded version to the non-qworking machines..

     

    HTH

    Thursday, January 26, 2006 6:36 PM

All replies

  • sounds like a versioning issue ...try installing the upgraded version to the non-qworking machines..

     

    HTH

    Thursday, January 26, 2006 6:36 PM
  • Lee:
    I am having the same problem. I didn't understand HTH's reply about "installing the new version". Do you have any idea what version he was talking about?.

    More importantly, wWere you ever able to resolve the problem? Thanks!

    Jim

    Monday, February 13, 2006 4:52 PM
  • HTH:

    I am having the same problem but don't understand your response. What product "version" are you referring to when you say it is a "versioning problem"?

    Thanks!

    Jim

    Monday, February 13, 2006 4:54 PM
  • Not a clue. It was not helpful to me. This has happened subsequently to us on other computers. What I found I needed to do was place a copy of ADODB.dll into the application folder. Even though the very SAME version of ADODB was ALREADY installed at the deployment computer's GAC. This should not be necessary, and makes no sense to me. I really believe there is some other problem here.
    Monday, February 13, 2006 7:56 PM
  • Hey Lee (or anyone),

    I have the same exact issue.  Has anyone found a solution ?

    Thanks !
    Dwain

    Monday, February 13, 2006 9:47 PM
  • I just had this problem today and I found a solution to it:

     

    if you look in c:\program files and cannot find the folder Microsoft.NET

    then that is the first cause.

     

    or if you dont see the file adodb.dll in

    c:\program files\Microsoft.NET\Primary Interop Assemblies

     

    Solution:

    go to a machine that has this folder and copy it (or the adodb.dll file if you have the folder) to the machines that cannot find the adodb file

    Go into this folder and into the primary interop folder

    copy this folders contents to the GAC (c:\windows\assembly)

    your app should find the adodb.dll now

     

    Hope this helps

    Jason

    Monday, February 27, 2006 4:17 PM
  • I have a web application that is reporting the same error.  It runs fine on my developement box but when I try to publish the site through the Publish function in VS 2005, I get the same error on the server.  My web server is a Win2K server.  I did what Jason said in his post and it didn't correct the error.  Any ideas?

    Wes

    Thursday, May 18, 2006 3:40 PM
  • hi, I made as Jason K said and it works for me, be sure after load into de gac every dll , to restart your iis, and read carefully the new message error (if there is something else), it could be a new one error
    Thursday, May 18, 2006 8:57 PM
  • I have a cuestion...

    how assembly the ADODB version 7.0.3300.0 in PC?


    Wednesday, June 07, 2006 1:22 PM
  • Works great. Thanks.

    My production Windows XP Pro box did not have "C:\Program Files\Microsoft.Net," so I copied this folder from my development Win2000 Pro box onto it.

    My production box login account did not have Administrator previledges and/or could not copy to "C:\Windows\Assembly" so I found the GACUtil.Exe on this box, which happened to be in "C:\Windows\Microsoft.NET\Framework\v1.1.4322," and relied on my DOS days to invoke this utility against each of the .dlls from the command prompt; registering them to the GAC.

    The location of the GACUtil.Exe was not in my search path on this Windows XP box so the command was a bit weird looking, as it included the location of the GACUtil.Exe:

    "C:\Windows\Microsoft.NET\Framework\v1.1.4322\GACUtil.Exe"   /i   adodb.dll

    I actually registered all the .dlls in one command as follows:

    For %J In (*.dll) do "C:\Windows\Microsoft.NET\Framework\v1.1.4322\GACUtil.exe"    /i   %J

    Note: These commands were invoked at the Command prompt from within the "C:\Program Files\Microsoft.NET\Primary Interop Assemblies" directory; Alternatively I could have prefix the .dll names with their path (i.e. C:\Program Files\Microsoft.NET\Primary Interop Assemblies\adodb.dll in the case of adodb.dll).

    GD.

    Wednesday, November 22, 2006 2:46 PM
  • salam all,

    this is how i solved the issue:

     I copied:

    c:\WINDOWS\assembly\GAC\ADODB\   from the development machine to the other machines ( same location ).

    Hope this helps.

     

    Friday, December 15, 2006 9:00 AM
  • Hi,

    I am using VS 2005 and SQL server2005. When I run application it build successfully but in place of login page following exception occured

    "System.IO.FileNotFoundException: Could not load file or assembly 'AnyDLL' or one of its dependencies. The system cannot find the path specified."

    Pre-bind state information ===
    LOG: User = CLIENT07\ASPNET
    LOG: DisplayName = AnyDLL
    (Partial)
    LOG: Appbase = file:///C:/Develop
    LOG: Initial PrivatePath = C:\Develop\bin
    Calling assembly : (Unknown).
    ===
    LOG: This bind starts in default load context.
    LOG: Using application configuration file: C:\Develop\web.config
    LOG: Using host configuration file: c:\windows\microsoft.net\framework\v2.0.50727\aspnet.config
    LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
    LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
    LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/develop/8638167d/1d65244e/Interop.ADSSECURITYLib.DLL.
    LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/Temporary ASP.NET Files/develop/8638167d/1d65244e/AnyDLL/Any.DLL

    LOG: Attempting download of new URL file:///C:/Develop/bin/Any.DLL

    LOG: Using application configuration file: C:\Develop\web.config
    LOG: Using host configuration file: c:\windows\microsoft.net\framework\v2.0.50727\aspnet.config
    LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
    LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
    ERR: Failed to complete setup of assembly (hr = 0x80070003). Probing terminated

    Please help me regarding this.

    Thanks

     

    Mahen

     



     

    Tuesday, January 16, 2007 10:34 AM
  • I am facing the same problem. However I solved it differently. I just removed the following line from the web.config:

    <add assembly="ADODB, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

    However, now I have to remember removing that line everytime I provide the build. Because the VS 2005 adds that line back in and I dont know how to tell VS not to add that thing in.
    Tuesday, April 24, 2007 3:05 AM
  • The Safest way would be to Find the "adodb.dll" ver 7.0.3300.0 and paste it to your Project's BIN folder.
    • Proposed as answer by Joshy Joseph Tuesday, March 27, 2012 3:20 PM
    Friday, May 04, 2007 11:51 PM
  • Hi, I resolved that problem by creating a Web Setup Project for my Web Site, then I added to the bin directory the adodb.dll from the GAC, by using the right button/Add/Assembly/adodb (from the GAC) and OK

    Then this Interop Assembly is copied to the msi file and installed on the bin directory of the virtual directory.

    It works!

    Thursday, May 10, 2007 4:34 PM
  • Well after reading all of the suggestions above, I tried the following and it resolved my issue that I was having that was similar to everyones above.

     

    In the setup part of my project, I did an 'Add' ---> 'Assembly...' Then from the resulting dialog box, I picked 'ADODB'. After I rebuilt the package and installed it on the problem machines, the program is running fine now. Thanks everyone for your insight as to possible solutions. For my situation, this seems to be the cleanest solution.

     

    Thanks again everyone! - ERic-

    Monday, May 21, 2007 6:03 PM
  • I have the same error message after deploiying to 2 machines (I have 3 that are OK)., but the problem I have is that one (for certain) DOES NOT HAVE ADODB anywhere on it even though I've installed the dotnetframework.
    Monday, June 11, 2007 12:48 PM
  • I was having the same issue on a W2K3 server. I found that it did work on my dev server, so I poked around and found a newer adodb.dll on my dev server in the same folder as the application that was throwing the error in prod. I renamed the existing dll on my prod server to .old then copied the later dll from my dev server to my prod server. This doesn't appear to be an OS related issue, more of an application dependency issue. If you are writing your own applications, be sure to check that your dependent dll's are up to date and packaged with your app when you do your final compile.

     

    Wednesday, August 15, 2007 1:11 PM
  •  

    Resume is find Adodb.dll by anyway and open the target assembly folder, then Drag and Drop the dll file to the folder listed.

    it's the simple way to import the Adodb.dll , no command, no headache

    Tuesday, September 11, 2007 7:20 AM
  • I found your solution is the better and best then the others posted.

     

    Thanks a Lot

     

    Balu

    Monday, November 26, 2007 11:01 AM
  •  Lee Gillie wrote:
    I have an application broadly deployed (about 10 computers). As of yesterday, two of these computers are unable to start the application, and failing with the error below. All other computers run the application just fine.

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

    I checked and ADODB.dll version 7.0.3300.0 is in the GAC in the deployment target machines.

    I find ADODB.dll in my C:\Program Files\Microsoft.NET\Primary Interop Assemblies folder (development computer), but this is version 7.10.3077.0 (file properties version)

    I see ADODB.dll as a project reference, but this shows version 7.0.3300.0, and shows the path to the PIA folder. I have no clue why these are not showing the same version number. Local Copy is false.

    Installing MDAC 2.8 on the failing deployment target machines did not help.

    Any clues or ideas or things to try??
    Thursday, January 31, 2008 9:14 AM
  • Safest and simple way of adding the adodb.dll ver 7.0.3300.0 is right click on the setup file go to add-->Assembly You will get  the Select Component Dialog Box Select the Adodb.dll ver 7.0.3300.0 and click Ok the adodb.dll will be added to the setup file....by default the adodb.dll will be added to the application folder on setup ..


    Happy Programming

    Thursday, March 13, 2008 1:51 AM
  • just in web.config put <clear/> or  use
      <remove assembly="ADODB, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

     <compilation defaultLanguage="c#" debug="true">
             <assemblies>
                       <clear />
             </assemblies>
        </compilation>

    Thanks!
    Satyadev

    Tuesday, July 08, 2008 2:34 PM
  • I had the same issue where it works in a computer but not in another. For the one machine that was not working, I added that above key to the web.config and it worked like a charm. Thank you AmolB!

    Friday, August 08, 2008 4:58 PM
  •  

    I encountered the same problem as I was publishing a new, lightweight .Net 2.0 app using ClickOnce. Since i have published quite a few of these, I got to looking around and saw that I needed to include a reference to the file (ADODB.dll). Then, in the Project Properties, on the Publish page, I went to the Application files tab, selected ADODB.dll and changed the 'Publish status' to 'Include'. the next time I ran the installer, it automatically installed the dll for me, problem solved.

     

    Hope this helps someone.

     

    Bob Ives

    Code Blue Designs

    • Proposed as answer by ToddTFPCorp Tuesday, October 25, 2011 6:00 PM
    Thursday, August 21, 2008 3:30 PM
  • Hi

                This is Deepak, and I developed a windows application, and create it’s setup. Now one error is in my application in running crystal report error description is given bellow.

     

    Could not find load assambaly

    ‘crystal Decisions.windows.forms,

    version = 10.2.3600.0, culture = natural.

    PocketKey Token = 692fbe95521el130’ or one of its dependencies, the system cannot find the file specified.

                                                    Please tell me how I can solved it.

                                                                           

    Deepak parkas

     

    Friday, August 29, 2008 11:58 AM
  • hey everyone thanks for the answers it helps me to resolve my problem with the adobd.dll

    you are the best
    Friday, September 05, 2008 10:47 AM
  • I have been looking for an anwer places and found that SHRIMANT PATEL's solution is the simpliest and actually work. Yes, just copy and paste the dll to the bin directory.

     

    Thanks.

     

    Monday, October 06, 2008 3:29 AM
  • I had the same problem today on 2 workstations running a .NET application.  Looking into the folder that the application is locally installed in I noticed that adodb.dll was missing.  Downloaded the latest version, copied it into this folder on each machine and voila - all works fine!

     

    Thursday, December 04, 2008 9:49 AM
  • Hello my name is Marcel, I'm from Brazil.
    Here is an installation package done in Visual Studio to various errors including GAC this error on the number 7.0.3300.0 of ADODB , is a page downlods, seize before it expires.


    http://www.ziddu.com/download/6687294/InstalaodoPacoteVSTO.zip.html


    msn: joaomarcelgomes@hotmail.com

    Monday, September 28, 2009 8:03 PM
  • I notice that some of my users have the directory c:\program files\Microsoft.NET\Primary Interop Assemblies as well as having the adodb installed while others do not.

    Is there already a package that should install this on a users PC..like does a .NET framework x.x   install this?

    I really want to avoid having to set this up in my Windows Installer MSI

     

    Thursday, July 08, 2010 8:39 PM
  • Thank you so much! This problem on my computer has been fixed. Your directions for clear and concise and fixed the problem immediately. Thanks again!
    Tuesday, December 14, 2010 3:40 PM
  • This worked thank you...
    Todd Lerew
    Tuesday, October 25, 2011 6:00 PM