After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 452382 - qt3-wizard.exe prefers DLLs from system directories to $prefix\bin
qt3-wizard.exe prefers DLLs from system directories to $prefix\bin
Status: VERIFIED FIXED
Product: GnuCash
Classification: Other
Component: Windows
2.1.x
Other Windows
: Normal normal
: ---
Assigned To: Andreas Köhler
Christian Stimming
Depends on:
Blocks:
 
 
Reported: 2007-06-29 21:59 UTC by Steve Cisler
Modified: 2018-06-29 21:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Steve Cisler 2007-06-29 21:59:56 UTC
Please describe the problem:
Whenever the AqBanking Setup wizard is run it errors with
-----------------
qt3-wizard.exe - Entry Point Not Found
The procedure entry point BIO_clear_flags could not be located in the dynamic link library libeay32.dll
OK
------------------

Steps to reproduce:
1. Select Tools - Online Banking Setup...
2. Click Forward on the Initial Online Banking Setup dialog
3. Click the AqBanking Wizard button


Actual results:
Windows error window pops up.

Expected results:
No error - sets up online banking accounts

Does this happen every time?
Yes

Other information:
Clean install of GnuCash 2.1.4 on Windows XP SP1.
Comment 1 Andreas Köhler 2007-06-30 08:30:16 UTC
"Clean install of GnuCash 2.1.4 on Windows XP SP1."  I do not believe that, given bug 450601 and bug 452170.
Please remove your prior/existing installation completely (all files), then reinstall.
Comment 2 Steve Cisler 2007-06-30 11:52:16 UTC
(In reply to comment #0)
> Please describe the problem:
> Whenever the AqBanking Setup wizard is run it errors with
> -----------------
> qt3-wizard.exe - Entry Point Not Found
> The procedure entry point BIO_clear_flags could not be located in the dynamic
> link library libeay32.dll
> OK
> ------------------
> 
> Steps to reproduce:
> 1. Select Tools - Online Banking Setup...
> 2. Click Forward on the Initial Online Banking Setup dialog
> 3. Click the AqBanking Wizard button
> 
> 
> Actual results:
> Windows error window pops up.
> 
> Expected results:
> No error - sets up online banking accounts
> 
> Does this happen every time?
> Yes
> 
> Other information:
> Clean install of GnuCash 2.1.4 on Windows XP SP1.
> 

(In reply to comment #1)
> "Clean install of GnuCash 2.1.4 on Windows XP SP1."  I do not believe that,
> given bug 450601 and bug 452170.
> Please remove your prior/existing installation completely (all files), then
> reinstall.
> 

I am surprised you accuse me of lying.  I have never had GnuCash installed on this machine before yesterday.  Second, I did see bug 452170 yesterday and even did an uninstall, including deleting out c:\program files\gnucash, and then reinstalled.  Had the same problem so then I submitted my bug.  Before I submitted my bug I also did a quick search on the internet for libeay32.dll and only found one dated from 2002. The one in my system32 folder is dated 2005.  Additionally I checked the libeay32.dll with Depends Walker and did not see a BIO_clear_flags entry point.  So I think I've done a few things to try to solve the problem initially before submitted the bug.  Please give me something more to work with to fix the problem or I'll just skip gnucash and go back to MSMoney.
Comment 3 Steve Cisler 2007-06-30 12:36:11 UTC
(In reply to comment #2)
> (In reply to comment #0)
> > Please describe the problem:
> > Whenever the AqBanking Setup wizard is run it errors with
> > -----------------
> > qt3-wizard.exe - Entry Point Not Found
> > The procedure entry point BIO_clear_flags could not be located in the dynamic
> > link library libeay32.dll
> > OK
> > ------------------
> > 
> > Steps to reproduce:
> > 1. Select Tools - Online Banking Setup...
> > 2. Click Forward on the Initial Online Banking Setup dialog
> > 3. Click the AqBanking Wizard button
> > 
> > 
> > Actual results:
> > Windows error window pops up.
> > 
> > Expected results:
> > No error - sets up online banking accounts
> > 
> > Does this happen every time?
> > Yes
> > 
> > Other information:
> > Clean install of GnuCash 2.1.4 on Windows XP SP1.
> > 
> 
> (In reply to comment #1)
> > "Clean install of GnuCash 2.1.4 on Windows XP SP1."  I do not believe that,
> > given bug 450601 and bug 452170.
> > Please remove your prior/existing installation completely (all files), then
> > reinstall.
> > 
> 
> I am surprised you accuse me of lying.  I have never had GnuCash installed on
> this machine before yesterday.  Second, I did see bug 452170 yesterday and even
> did an uninstall, including deleting out c:\program files\gnucash, and then
> reinstalled.  Had the same problem so then I submitted my bug.  Before I
> submitted my bug I also did a quick search on the internet for libeay32.dll and
> only found one dated from 2002. The one in my system32 folder is dated 2005. 
> Additionally I checked the libeay32.dll with Depends Walker and did not see a
> BIO_clear_flags entry point.  So I think I've done a few things to try to solve
> the problem initially before submitted the bug.  Please give me something more
> to work with to fix the problem or I'll just skip gnucash and go back to
> MSMoney.
> 

I did some more work on my own and noticed that the gnucash bin folder has all the dlls in it.  I temporarily renamed the libeay32.dll in the system32 folder and then ran gnucash again. The AqBanking setup wizard now finds the dll in the gnucash\bin folder and seems to work.
Why is the install putting all the dlls in the gnucash folder?  Shouldn't system and shared dlls be put in the system/system32 folder?
Comment 4 Andreas Köhler 2007-06-30 14:50:53 UTC
I am so sorry.
Thank you a lot for this additional information.  This is likely a duplicate of bug 450052 and I think I know how to resolve it now.  Unfortunately, I will probably not finish this until Wednesday, so 2.1.5 will lack a fix.
I will try to post a workaround though.
Comment 5 Christian Stimming 2007-06-30 15:51:33 UTC
(In reply to comment #2)
> I am surprised you accuse me of lying.  I have never had GnuCash installed on
> this machine before yesterday.  Second, I did see bug 452170 yesterday and even
> did an uninstall,

We're sorry for sounding offensive to people here. Both Andreas' and my mother tongue is not english, so we're sorry if our question for information turned out a bit rude. We're just trying to resolve as many issues with gnucash as possible, even though we are very limited in our resources as well. 

Thank you very much for your initial report and even more so for your additional information. Indeed we know the DLL locations of the Windows are a source of regular confusion and we're working on a resolution.

As for your other question, "Why is the install putting all the dlls in the gnucash folder?" - That's a fundamental technical fault of the MS Windows operating system. Gnucash depends on approx. 50 other DLLs. We don't know whether any of them happen to exist already in the windows/system32 folder. Because if they did, the are probably vitally important for some other application on your computer. However, as most likely the existing DLL has a different API interface version, overwriting the existing one with the one that is needed by gnucash will most likely kill your already installed other application. This should better be avoided, and on MS Windows the only possibility to really avoid crashing your other existing application unfortunately requires shipping our own DLL into our own Program folder of gnucash. That's the reason. 

Feel free to add any further ideas, hints, or issues you find. Thanks.
Comment 6 Andreas Köhler 2007-07-06 13:55:49 UTC
Could you please try the following:
* resurrect your bad libeay32.dll in your system32 directory
* move lib\aqbanking\plugins\16\wizards\qt3-wizard.exe to bin\
* save redirect.exe (attachment 91302 [details]) to lib\aqbanking\plugins\16\wizards\qt3-wizard.exe
* retry

See also bug 450052.
Comment 7 Andreas Köhler 2007-07-08 13:19:52 UTC
This issue should be solved as of r16277 or GnuCash 2.1.6.  If anyone tests it
earlier by building from sources, this would be even better, of course.
Comment 8 John Ralls 2018-06-29 21:41:03 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=452382. Please update any external references or bookmarks.