First off, just to be clear, this only applies to Infinity license holders. Why? Because an Infinity license is required to use the 64-bit edition of Report Runner. It's the only licensing type where the 64-bit edition is made available.
---
As always, you should not install/update during production. Due to the required installation of the Microsoft 64-bit VC++ library, you will have to REBOOT to do this installation.
If the machine can not be rebooted at this time, do not continue.
---
PREREQUISITE - Verify the prerequisites for the 64-bit editon (and install the 64-bit VC++ library if it's not already installed):
Just to be safe, it is recommended that the 64-bit VC++ installer be run and the machine rebooted (even if you believe it's already installed).
---
DO NOT CONTINUE UNTIL YOU'VE COMPLETED PRE-REQUISITES.
DO NOT CONTINUE UNTIL YOU'VE COMPLETED PRE-REQUISITES.
DO NOT CONTINUE UNTIL YOU'VE COMPLETED PRE-REQUISITES.
---
If you've previously installed the 32-bit bit edition of Report Runner, please follow these steps:
1 - Uninstall the 32-bit Crystal runtime engine using Add/Remove Programs:
2 - Uninstall the 32-bit edition of Report Runner using Add/Remove Programs (see note below first):
When you uninstall, it does NOT do anything with your data (your reports or batches or schedules... nothing you've "created").
Note, before uninstalling, start Report Runner, go to Help, Debugging, and open/view the current log file, and do a find on "data directory". For most users, it will show "C:\Users\Public\Documents\Jeff-Net". Make note of this directory to make sure when you run the full 64-bit installer later, that's the same directory you're using.
Uninstall Report Runner:
4 - If it's easy to reboot, go ahead and reboot. This just makes things slightly "cleaner". If you can't though, you may continue to try to install the 64-bit edition.
5 - Download and run the FULL 64-bit installer (we will provide you a link to it, because the 64-bit installers are not posted publicly):
You'll know you have the correct installer when you see the x64 and 64-bit shown:
After passing a few other windows (by clicking Next), you'll come to the program files directory setting...
6 - Verify (and possibly change) the program files directory. This only matters if you're using Report Runner Batch. This is not critical if you are using other Report Runner products.
Note, the 32-bit version, by default, uses the x86 program files directory (C:\Program Files (x86)\Jeff-Net\Report Runner\). The 64-bit edition, but default, uses the non-x86 directory (C:\Program Files\Jeff-Net\Report Runner\).
IMPORTANT: You have a CRITICAL decision to make here if you use Report Runner Batch. Your previously scheduled batches, are ALL configured to look for the Report Runner Unified executable in the x86 directory. If you install the 64-bit to the non-x86 directory, you will have to manually update ALL of your batches to point to the non-x86 directory. Or, you can just install the 64-bit edition to the x86 directory. This does not meet best practices, but it will keep your batches and schedules working as-is.
This is YOUR CHOICE. We don't force it one way or the other. If you want to change it to the x86 directory, modify it below:
7 - Next, you'll come to the data directory setting.
Make sure this MATCHES the previous path from log file in Step #2. If it does not, you may continue with the install BUT YOU MUST CONTACT SUPPORT so we can correct your data directory settings after you complete the install. You will not be able to use Report Runner until we fix these settings.
8 - Complete the rest of the installation.
Please note, near the end of the installation, the installer will launch another installer to install the 64-bit edition of the Crystal runtime engine. Once all of that is complete, and assuming the data directories matched, you can start using Report Runner again.
The installation is not complete until you see the browser open with the 45 day license request AND the eventual "Woohoo - Install Complete" window.
9 - Last, but not least, for any of your reports that use DSNs, make sure you have created the 64-bit System DSNs to replace the 32-bit System DSNs used previously.
10 - When you start the new 64-bit edition, you will see x64 on the main window, and if you look at the log file you will see it's running the 64-bit edition:
