Ticket Q454184
Visible to All Users

Problems installing DevExpress for XE2

created 12 years ago

I have been using version 11.2.6. with Delphi XE2. Due to a smal problem I was advised to install a later version (12.2.2).
I aso have XE3 installed but had not previously installed DevExpress for it.
I ran the automated installation program. It seemed to run OK.
XE3 insallation seems to have processd OK.
XE2:
When starting XE2 various errors come up. See sc.eren shots attached.
Reran installation program & removedall DevExpress.
Reran again to reinstall, running as administrator
Didn't work for XE2, removed again, rebooted, reinstalled.
Still no go. Experimented quite a few times.
When loading, XE2 is lookng for C:\Users\Public\Documents\RAD Studio\9.0\Bpl\RVDevXE2.bpl.
How do you reset this? The folder on my system is similar but is C:\Users\Public\Public Documents\RAD Studio\9.0\Bpl. It has other software installed in it so should not be changed. My system does not allow another folder just called C:\Users\Public\Documents… (it seems to think it's the same folder & tries to merge it if you try to create a new one named as above)…
The file RVDevXE2.bpl from the new version of DevExpress is not being saved anywhere along with other files. Similarly the DevExress VCL\Library\R16… files would not save in the Programs folder, however I was able to reallocate this to a different folder and the files in it were all in that folder for the new version aftr installation.

After installation, when starting the XE2 IDE, if you say OK yes to all the error messages, it does seem to load all or most of the objects into the IDE. but does not complete all startup initialisations. However, trying to compile previous programs using Dev Express(Grids) gives the error procedure entry point @ cxgeometry… could not be located in the dynamic link librabry cxLibraryRS16.bpl. It seems to be picking up that library from the previous version.
Seems like if we can redirect the folder C:\Users\Public\Docments\RAD Studio\9.0\Bpl\ to another folder that exists it may fix the problem, but how do you change that setting in the installation process?

Show previous comments (9)
DevExpress Support Team 12 years ago

    We are working on your request, but it can take us some time to examine it. We will get back to you once we have any results or need additional information. Thank you for your patience.

    DevExpress Support Team 12 years ago

      Hello,
      Please accept my apologies for the delayed reply. It seems that your environment is specific because the solution provided by Gregory works in most cases. Moreover, I personally installed VCL 12.2.2 on the XE2 IDE multiple times and there were no "The procedure entry point …" exceptions.
      By design, it is not possible to install older and recent VCL builds alongside because they use the same shared code. Possible ways out are described in the How to have several build versions installed on one machine Knowledge Base article. Would you please check whether or not one of these solutions is acceptable for you?
      As we still cannot find out why using the BPLFinder tool during the reinstallation process did not help, I kindly ask you help us a bit (once you have time for it). Perhaps, this will help us avoid such issues in the future. Here is a new algorithm:

      1. Please download the slightly modified BPLFinder tool that I attached to this message. It can save a log file now;
      2. Completely remove our components by launching our VCL Installer in a "Remove" mode;
      3. Delete all OUR remaining BPL files manually using the new BPLFinder tool;
      4. Perform the BPLFinder search once again and save the log file to a certain folder. This file will contain names of remaining BPLs;
      5. Remove invalid paths using the PATHEnvironmentVariablePatcher from the Windows PATH is corrupted when its length limit is exceeded during the installation ticket;
      6. Restart Windows;
      7. Launch your IDEs (XE2 and XE3). If there is a notification that some packages cannot be loaded, click the "No" button to prevent these packages from being loaded on the next IDE launch;
      8. Install our components from scratch;
      9. Download the UserInfoBuilder tool from the FAQ: Migrating to the new version Knowledge Base article, choose your IDEs there, click the "Build and save report" button, and send us the report with your next message along with the log file from the fourth paragraph.
        Thanks in advance. We are looking forward to your reply.

        Thank you. I will try again when I get back in a fortnight after a trip away.

        Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

        Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.