Error in the most recent version? (4.1.3.0)

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
stojo303
Posts: 22
Joined: Mon 25 Apr 2011 07:31

Error in the most recent version? (4.1.3.0)

Post by stojo303 » Sat 26 Nov 2011 08:55

Hi,

I just updated to the most recent version of UniDac, 4.1.3 and when I nos start Delphi 2010, each time I'm met by the error message:


---------------------------
bds.exe - Entry Point Not Found
---------------------------
The procedure entry point @Memutils@_UpperCase$qqrx20System@UnicodeString could not be located in the dynamic link library dac140.bpl.
---------------------------
OK
---------------------------

I have tried to uninstall and reinstall UniDac, but I'm still met by this message.

If you need any further details, please let me know. I'm a registered user.

Thanks in advance.

stojo303
Posts: 22
Joined: Mon 25 Apr 2011 07:31

Post by stojo303 » Mon 28 Nov 2011 07:47

Any updates/input on this one?
It's getting quite annoying to get this dialog upon each start of Delphi...

AndreyZ

Post by AndreyZ » Mon 28 Nov 2011 08:52

Hello,

Such problem can occur if there are still files from the old UniDAC version on your computer. Please try the following:
- remove UniDAC;
- remove all *dac*.bpl files from your computer;
- remove *.dcu files from your project;
- reinstall UniDAC.

stojo303
Posts: 22
Joined: Mon 25 Apr 2011 07:31

Post by stojo303 » Mon 28 Nov 2011 09:24

No, sorry that does not help neither. I'm still met by the previously mentioned error message, followed by:

[Window Title]
Error

[Content]
Can't load package C:\Program Files (x86)\Embarcadero\RAD Studio\7.0\Bin\dclunidac140.bpl.
Can't load package c:\program files (x86)\embarcadero\rad studio\7.0\Bin\CrControls140.bpl.
The specified procedure could not be found.
Do you want to attempt to load this package the next time a project is loaded?

[Yes] [No]

I have upgraded UniDAC before but have never had these problems before.
According to the first error message, it seems like something might be missing/an incorrect BPL is shipped with the Delphi 2010 installer?

Please advise.

Thanks

AndreyZ

Post by AndreyZ » Mon 28 Nov 2011 14:51

Please try the following:
- close RAD Studio 2010;
- remove UniDAC;
- remove all *dac*.bpl and crcontrols*.bpl files from your computer (please make sure there are no such files on your computer);
- remove *.dcu files from your project;
- reinstall UniDAC.
If it doesn't help, try the following:
- remove UniDAC;
- reinstall UniDAC with the /force parameter like this: unidac41d14pro.exe /force

stojo303
Posts: 22
Joined: Mon 25 Apr 2011 07:31

Post by stojo303 » Mon 28 Nov 2011 18:36

Thanks, it seems to have worked upon my first tests.
I will do more tests the next days and report back if something odd is found.

AndreyZ

Post by AndreyZ » Tue 29 Nov 2011 12:46

We are looking forward to hearing from you.

jrshedden
Posts: 1
Joined: Thu 01 Dec 2011 23:53

Same Issue

Post by jrshedden » Fri 02 Dec 2011 00:27

Hi,

Some quick notes to be helpful not critical, apologize for brevity.

Win7x64, Unidac 41d15pro, Rad Studio XE load error '@memutils... missing from dac150.bpl'.

Did the uninstall, cleaned all *dac*.bpl, and crccontrols*.bpl and was able to get the IDE running again. IDE failed because uninstall didn't clean a bin folder in rad studio.

Reinstalled Unidac, IDE still ran, no Unidac components on tool selector. Re-ran install with \force and tools appeared. No further tests. Installer was run with admin rights.

Installers/Uninstallers are sometimes more challenging than the programs themselves because you don't deal with them often and the environment they run in is always changing. This installer may need a review. There is nothing more frustrating than debugging an 'upgrade', especially when it crashes the main IDE.

Best Regards,
Jim S.

AndreyZ

Post by AndreyZ » Fri 02 Dec 2011 10:33

The point is that sometimes our uninstaller cannot remove all files (especially .bpl) because they are hold by Windows. In this case files from the old version are left on the computer, and it causes problems with installation of the new version. We will investigate this question.

Post Reply