Page 1 of 1
Indy error when upgrade to 7 from 6
Posted: Fri 17 Jun 2016 23:51
by corneliusd
I upgraded from SecureBridge 6 to version 7 in Delphi 2010 and am now encountering a problem with Indy:
The procedure entry point @Idiohandler@TIdIOHandler@InputLn$qqrx20System@UnicodeStringoiip18Sysutils@TEncoding could not be located in the dynamic link library IndyCore140.bpl.
Is this a bug in SB or is Indy not installed correctly?
Thanks,
David
Re: Indy error when upgrade to 7 from 6
Posted: Sun 19 Jun 2016 08:48
by corneliusd
I was in a bit of a hurry to get this fixed and I realize I posted it just before the weekend, but after trying to upgrade Indy and dig into the root of this problem, I quickly decided it wasn't going to be the best way to go.
So I tried upgrading the project to Delphi XE2, which I found did NOT have the conflict with SB and Indy. That worked very smoothly, so I'm very happy!
However, it seems like SecureBridge 7 doesn't work with Indy 10 in Delphi 2010. Or I have something really screwed up in my Indy installation.
Dav.d
Re: Indy error when upgrade to 7 from 6
Posted: Mon 20 Jun 2016 06:36
by ViktorV
Since you have updated SecureBridge, you should rebuild and reinstall Devart SecureBridge Components for Indy. You can find source files for Devart SecureBridge Components for Indy in the 'Demos\IndyX' folder of the SecureBridge demo projects installation directory. X is the version of the used Indy.
To solve the problem try to perform the following steps:
- remove Devart SecureBridge Components for Indy from [Components]->[Install Packages] ;
- rebuild the packages: indyXsbridge140.dpk;
- install indyXsbridge140.dpk;
- restart IDE.
Re: Indy error when upgrade to 7 from 6
Posted: Mon 20 Jun 2016 14:50
by corneliusd
That's good to know. I'll keep that in mind if I run into this problem again.
Thanks very much for responding.
David.
Re: Indy error when upgrade to 7 from 6
Posted: Tue 21 Jun 2016 10:21
by ViktorV
Thank you for your interest to our products.
If you have any questions during using our products, please don't hesitate to contact us - and we will try to help you solve them.