none
How To Identify A DLL That Access Cannot Load. RRS feed

  • Question

  • We are having a problem with an old application that runs under Runtime 2007 and is compiled (.accde).  It is relatively complicate and is distributed in an installation that includes a lot of thinks.  (We are in the process of upgrading it to a newer version of Access but have to support the old version in the meantime.) 

    It was installed and working on a Windows 10 system with Access 2007 installed.

    Microsoft pushed out an series of updates to Windows 10 and broke the application.  That is the application started throwing errors and failed to load forms.

    If we put the source (.accdb) on the Windows 10 system and open the data base we get:

    Please note the error is thrown the first time the code window (Alt-F11) is opened.  The application is not running.

    However, the database will compile clean and the compiled version works on the Windows 10 machine.

    How do we identify the DLL that won't load?


    http://www.saberman.com

    Monday, January 18, 2016 11:04 PM

All replies

  • Hey, There!

    Check out maybe it can help you:

    https://support.microsoft.com/en-us/kb/2019235


    C#.NET / VB.NET
    Aulas de VB.NET

    Não se esqueça! Se uma resposta/post te foi útil, é generoso reconhece-lo clicando em votar e se uma resposta foi fundamental para o desenrolar dum problema marque como resposta, você ajuda(visitantes) e motiva(quem te respondeu)!

    Monday, January 18, 2016 11:33 PM
  • Hi. Unless somebody knows exactly which DLL  it is, I would probably open the database in another computer and start unchecking the references one at a time until the Win10 computer indicates which one is causing the problem. Just a thought...
    Monday, January 18, 2016 11:33 PM
  • I think as a first quick test is to create a blank database, and then import everything from  that accDB and then try compiling the code.

    Regards,

    Albert D. Kallal (Access MVP)

    Edmonton, Alberta Canada

    Tuesday, January 19, 2016 3:32 AM
  • If we put the source (.accdb) on the Windows 10 system and open the data base we get:

    Please note the error is thrown the first time the code window (Alt-F11) is opened.  The application is not running.

    However, the database will compile clean and the compiled version works on the Windows 10 machine.

    How do we identify the DLL that won't load?


    http://www.saberman.com

    Hi saberman,

    As the compiled version runs, you can question whether it is a real Access problem related to the DLL, or a problem in the internals of your computer.

    Last December I had an experience where Access did not let me paste forms in an application. See the thread:

    https://social.msdn.microsoft.com/Forums/en-US/1db3bf1a-95a8-418b-98ec-69cf2658efe0/failure-to-import-a-form-from-another-database?forum=accessdev

    It finally had nothing to do with Access as such, and the problem only disappeared after "cleaning" the computer.

    Imb.

    Tuesday, January 19, 2016 7:17 AM
  • I am not trying to run a wizard -- I am just trying to open the code.

    http://www.saberman.com

    Tuesday, January 19, 2016 7:49 AM
  • I am not trying to run a wizard -- I am simply opening the code windows.

    http://www.saberman.com

    Tuesday, January 19, 2016 7:54 AM
  • Once the code window is 0pened the problem goes away.  So unchecking the references is already too late.

    http://www.saberman.com

    Tuesday, January 19, 2016 7:55 AM
  • Did your read my posting? I don't have to import everything into a new database I just have to open the code window and recompile on a Windows 10 machine. The real question is what DLL is causing the problem.

    http://www.saberman.com

    Tuesday, January 19, 2016 7:57 AM
  • If you go back in time you will find that that one of the service packs for Windows that Microsoft pushed out led to a situation where applications compiled with the Service Pack would not work on machines that did not have the service pack.  This seems to be the reverse -- applications compiled without whatever Microsoft pushed out to Windows 10 won't run on Windows 10.

    http://www.saberman.com

    Tuesday, January 19, 2016 8:01 AM
  • Are you saying that an update pushed out to Windows 10 removed critical keys from the registry?

    http://www.saberman.com

    Tuesday, January 19, 2016 8:07 AM
  • Are you saying that an update pushed out to Windows 10 removed critical keys from the registry?

    Hi saberman,

    I do not know who you are answering.

    In my case I do not know what caused the problem, only that it disappeared after resetting the computer to factory installation.

    Imb.


    edit:  and re-installing Office.
    • Edited by Imb-hb Tuesday, January 19, 2016 8:15 AM
    Tuesday, January 19, 2016 8:15 AM
  • >Are you saying that an update pushed out to Windows 10 removed critical keys from the registry?
    I don't know what an update did.  All I know is that the application was working fine on a Windows 10 machine and then, after a number of updates for Windows 10 were pushed out by Microsoft, the application stopped working.

    http://www.saberman.com

    Tuesday, January 19, 2016 9:40 AM
  • Once the code window is 0pened the problem goes away.  So unchecking the references is already too late.

    http://www.saberman.com

    Hi saberman,

    To minimize confusion when there are multiple responders, it might be a good idea to address the person you're replying to. I will assume the above quote was for me.

    To clarify my suggestion, you said you installed the application into a Win10 machine, and it now gives an error when you open the code window. So, my suggestion was to open the code window in a different machine, for example, a Win7 machine. If it allowed you to open the code window without an error, you can uncheck one of the references and then try the new database back on the Win10 machine. You keep doing this back and forth checking between the machine without the error and the other machine that has the error until you figure out which reference, and therefore which DLL, was causing the problem.

    Hope that makes sense...

    Tuesday, January 19, 2016 3:58 PM
  • Actually, yes I did read your question. You state when you launch the application the first time you get that prompt. You do not state nor imply or can anyone by mind reading infer that additional runs or when you have the IDE open that such an error does not occur.

    The first time I put a key in my car and try to start it I find my car does not start. There is NOTHING in this statement that suggests or infers that subsequent attempts at staring the car means it will now start! No reasoning human will infer that additional attempts work.

    I certainly agree some “update” may be making some mess here, but that is EXACTLY why I suggest creating a new blank database and importing the objects. If the copy does NOT error, then we can learn a number of things.

    If the new fresh copy works, then this would be due to the previous copy corruption, or simply that the “new” created copy works because of some “unknown” update to access/office that allows as such.

    So the reading public likely did not (could not) grasp that additional launching of the application works, no more than stating your car does not start the first time you try it – no one here is going to figure out or realize that you are suggesting additional runs DO WORK! (but now that this is clear, I would try running the application as an administer).

    The suggestion still stands – creating a new blank database on that machine and importing the code and objects is still a worthwhile test.

    Regards,

    Albert D. Kallal (Access MVP)

    Edmonton, Alberta Canada

    Tuesday, January 19, 2016 4:19 PM
  • @Albert,

    Initially, the application was installed on the client's Windows 10 machine via an installation package which only included the compiled version.  It work without problems.

    After a series of Windows Updates it stopped working properly.  It would start and, depending on the options chosen, start throwing errors or failed to load forms.

    The client happen to have Access 2007 installed on the machine.  To trouble shoot we took the source database and placed it on the client machine.  We then used Access to open the database without starting the application.  When we opened the code window (Alt-F11) we got the message about a dll failing to load.  However, the database compiled clean and the compiled version worked. 

    Although we are in the process of upgrading the application we still have many people using the current version.  Our concern is that if they migrate to Windows 10 the application installed on their machines will stop working.  We need to find out why the current distributed version of the application doesn't work on Windows 10 after Windows Updates are applied.  The missing DLL is probably one that an update replaced or moved to a new location.


    http://www.saberman.com

    Wednesday, January 20, 2016 12:57 AM
  • @Imb-hb

    Resetting the machine will probably get the original application working again -- until the machine gets updated by Microsoft pushing out the updates.


    http://www.saberman.com

    Wednesday, January 20, 2016 1:01 AM
  • Hi saberman,

    >>Once the code window is 0pened the problem goes away.  So unchecking the references is already too late.

    Do you mean it worked correctly if the code window is opened? If you close this access file, and open it again, would you get error again? I suggest you create a new Access database to check whether this issue still exist.

    In addition, I suggest you try the suggestion from Imb, re-install or repair Office.

    Best Regards,

    Edward


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Wednesday, January 20, 2016 2:12 AM
  • Fair enough!

    While importing into a clean 2007 db “might” work, the dll prompt on VBA editor load is “strange”. (and the first load/try issue while not 100% clear was missed by me).

    I can say that I experienced a “rash” of recent issues in which our 2010 accDE does not work with 2013 runtime. A good day of troubleshooting and we much are now simply installing Access 2010 runtime to fix the problem until such time we have more time to fix the error.

    So you “do” have my sympathy here, since I sure you would rather spend your time doing something productive as opposed to tracking down some pesky issue.

    Your error remains a “strange” one – one I don’t think I seen before. Also, keep in mind that 2007, and 2010 runtimes do NOT update their service packs (they are separate installs and downloads for the Access runtime – NOT even the office sp update will affect the runtime). And often worse is the full editions of Access ARE updated automatic.

    For 2013 runtime, the sp updates are now included, but for 2010, they are not. So on machines will full office, they can auto receive updates to Access, but not the runtime versions.

    Regards,

    Albert D. Kallal (Access MVP)

    Edmonton, Alberta Canada

    Wednesday, January 20, 2016 2:55 AM
  • Resetting the machine will probably get the original application working again -- until the machine gets updated by Microsoft pushing out the updates.

    Hi saberman,

    After resetting the computer (last December) the problem did not return. All new updates did not repeat the problem.

    Are you sure your problem is the caused by a new update, or something that "happened" at about the same time of the new update?

    Is your problem computer specific, or application specific? That is, when you run the application on a different computer, do you have the problem there too?

    Anyway, I was glad I could continue on my projects, and did not spend any further time in trying to understand what had happened exactly.

    Imb.

    Wednesday, January 20, 2016 7:27 AM