Hi

Delphi XE8 on Win10.

I am trying to install 2.23 build 2 to see if that is the reason for another problem I am having. I have had EDB installed on D drive for the last few upgrades, but after I installed 2.23 b2 I got multiple error messages saying "Can't load package C:\Users\Public\Documents\Embarcadero\Studio\16.0\Bpl\edbutilcompsdesign.bpl. The specified module could not be found. Do you..."

A file named edbutilcompsdesign.bpl remained in that folder on C:. Thinking it might be an old version, I renamed the edbutilcompsdesign.bpl so it wouldn't be found again, uninstalled all edb units, and prepared for another install.

I thought that my previous habit of installing to D drive was the problem, so re-installed on C drive.

There is still no edbutilcompsdesign.bpl file on c:, even though I did a fresh install.

When I restart Delphi, I get the same "Can't load package " message. I tried restoring the name of the edbutilcompsdesign.bpl

Any idea where I should look?

Regards

Peter

On 4/22/2016 5:32 AM, Peter wrote:
> Delphi XE8 on Win10.
> I am trying to install 2.23 build 2 to see if that is the reason for another problem I am having. I have had EDB installed on D drive for the last few upgrades, but after I installed 2.23 b2 I got multiple error messages saying "Can't load package C:\Users\Public\Documents\Embarcadero\Studio\16.0\Bpl\edbutilcompsdesign.bpl. The specified module could not be found. Do you..."
> A file named edbutilcompsdesign.bpl remained in that folder on C:. Thinking it might be an old version, I renamed the edbutilcompsdesign.bpl so it wouldn't be found again, uninstalled all edb units, and prepared for another install.
> I thought that my previous habit of installing to D drive was the problem, so re-installed on C drive.
> There is still no edbutilcompsdesign.bpl file on c:, even though I did a fresh install.
> When I restart Delphi, I get the same "Can't load package " message. I tried restoring the name of the edbutilcompsdesign.bpl
> Any idea where I should look?

This is edb components which you can just compile and install into IDE
so here's what i would do :

1. remove existing edbutilcompsdesign from IDE

2. i would also make sure you clean up any old EDB install references
(the other EDBManager compile issue you had might be due to mix of older
and newer versions)

3. open edbutilcompsdesign.dproj (in ..\ElevateDB 2 ADD\utilcomps\)

4. Build it to make sure it builds without error

5.  Install it - you should get a prompt that bunch of new components
have been added

Raul

Thanks Raul,

I messed with a bit more, now all the Elevate components appear on the palette as they should, but when I try to build the project I get the dreaded "[dcc64 Fatal Error] ViewINI_U.pas(8): F2048 Bad unit format: 'C:\Program Files (x86)\ElevateDB 2 VCL-CS\RAD Studio XE8 (Delphi Win32)\code\edbcomps.dcu' - Expected version: 29.0, Windows Unicode(x64) Found version: 29.0, Windows Unicode(x86)" message.

In the past (3 times since January) I have had the uninstall Delphi and start again.

I now run DXE8 with the /nocastalia switch, in an effort to keep the environment stable, but it appears that every day I get more and more major errors, such as this one, and I have to reinstall Delphi. In my opinion, XE8 is unfit for the purpose for which it was sold. </rant>.

Thanks anyway.

Regards

Peter

On 4/22/2016 9:01 AM, Peter wrote:
> I messed with a bit more, now all the Elevate components appear on the palette as they should, but when I try to build the project I get the dreaded "[dcc64 Fatal Error] ViewINI_U.pas(8): F2048 Bad unit format: 'C:\Program Files (x86)\ElevateDB 2 VCL-CS\RAD Studio XE8 (Delphi Win32)\code\edbcomps.dcu' - Expected version: 29.0, Windows Unicode(x64) Found version: 29.0, Windows Unicode(x86)" message.

This looks like 32 vs 64 bit issue.

> I now run DXE8 with the /nocastalia switch, in an effort to keep the environment stable, but it appears that every day I get more and more major errors, such as this one, and I have to reinstall Delphi. In my opinion, XE8 is unfit for the purpose for which it was sold. </rant>.

I think i do have a XE8 VM so if i get free time i'll try to start it up
and see what happens for me.


Raul

On 4/22/2016 9:11 AM, Raul wrote:
> I think i do have a XE8 VM so if i get free time i'll try to start it up
> and see what happens for me.

I just tried it out and in fact installed 2.22 build 2 on XE8 (it was
running a lot older version) - all worked fine here.

I think in your case the issue is not the delphi install but the
existing config etc - that remains in registry during reinstall.
Possibly also combined with some older EDB source files haning around.

I would suggest 2 things
1. uninstall edb and search for delete any edb files (especially if you
might have them on C and D)
2. reinstall EDB

For IDE try a clean config : start the IDE with the -R switch to init a
new registry hive (i.e. http://support.embarcadero.com/article/42597)
and try again.




Anwyays my steps are as straightforward as can be :
1. removed the existing edbutilcomp package from ide
2. uninstalled older EDB (32, 64 and add-on utils)
3. reinstalled 2.22 b2 (32, 64 and add-on utils)
4. opened the edbutilcompsdesign.dproj and did build, install -> all
components installed fine
5. opened the edbmgr.dproj - this one could not find the ebdutilcomps
unit on compile so i ended up adding the ...\ElevateDB 2 ADD\utilcomps
to search path
7. Edbmanager compiled ok after

Raul

Raul

Atempting to follow your advice, I...

Uninstalled ElevateDB - all.
Removed every edb* file from C: and D:..
Removed almost every occurrence of elevate from the Registry - left the Library paths in the Registry.
Opened an INI project that does not contain edb components, and removed Elevate library paths.
Installed 2.23 b2. Re-opened the 64 bit INI project.
There were no references to the Elevate Library Paths, so I added them. Innocently, I added the 32 bit path first, then the 64 bit.
Added an EDBEngine component to an EDB-free app. Attempted to build the project, and got the message "[dcc64 Fatal Error] ViewINI_U.pas(8): F2048 Bad unit format: 'C:\Program Files (x86)\ElevateDB 2 VCL-CS\RAD Studio XE8 (Delphi Win32)\code\edbcomps.dcu' - Expected version: 29.0, Windows Unicode(x64) Found version: 29.0, Windows Unicode(x86)".

I thought "This is it, time to reinstall Delphi". Had a coffee, then desperately switched the Target platform to 32 bit. The build worked, and the app ran fine.

The 64 bit target wouldn't build, so I went back to the library and put the 64 bit path above the 32 bit path, clicked on Build and it all went swimmingly. Then I tried to open edbutilcompsdesign, to compile, but it appears BitDefender (or something) is blocking bds.exe from saving any of the necessary files to the path in C:\Program Files(x86)\ElevateDB 2 ADD. Perhaps I needed to 'Run as Admin'.

I set bds.exe as a trusted app in BitDefender, but the problem persisted. I uninstalled EDB again, and reinstalled on D:, and I believe the registry and file cleanup helped, as it installed perfectly after I added the paths to D:. I did a few builds in various projects, then tackled edbutilcompsdesign again. It compiled the bpl, and added the components. I had added the D:\ElevateDB 2 ADD\utilcomps path to the Library, so it went well. I then opened the standard EDBManager and after a build, it worked too.

There is some weird stuff afoot, regarding old files and registry entries, which I have had pointed out to me by Tim previously, and the problems downstream manifest themselves as black magic.

I am left to wonder why the edbutilcomps aren't installed into the palette in the same way the other EDB components are, and why the Uninstaller doesn't clean up the old files and Registry entries.

Thanks for your advice.

Regards

Peter

Peter,

<< I am left to wonder why the edbutilcomps aren't installed into the palette in the same way the other EDB components are, >>

Because they are for customizing/recompiling the utilities, something that most customers *don't* do.  They're just there (as is the source code for the utilities) as an additional benefit to customers that want to mess with the source code or re-brand the utilities.

<< and why the Uninstaller doesn't clean up the old files and Registry entries. >>

Are you talking about *our* uninstaller ?  Our installer *does* clean up all registry entries, etc.  The only thing that it doesn't delete are the .ini files for the manager and server, and it does not deal with anything that you manually compile and install, such as the EDB utility component packages.

Tim Young
Elevate Software
www.elevatesoft.com