This guide will walk you through transferring/migrating the software to another server.
This guide will walk you through transferring/migrating the software to another server. It is imperative that you follow the steps below carefully. Do not simply uninstall the software from your old server. This will result in an unsuccessful migration.
This guide assumes that the installation is on a Local SQL Server instance located on the server that has the software installed on. This is the default database setup at time of initial installation.
Any problems that arise from a migration are outside the scope of regular technical support. Therefore, it is highly recommended that you book one of our Professional Services consultants to perform the migration for you. This will ensure
- a smoother transition,
- minimal to no downtime,
- minimal resources & time spent completing the migration.
If you would like to inquire about Professional Services, please contact our Customer Relations department at +1-888-781-8966 Option 2, or submit this form.
- Maintenance must be current with your license. Attempting to transfer the software without active maintenance will cause the migration & activation process to fail.
- All the installation Prerequisites must be met on the new server you are migrating the software to. To review Prerequisites, select your software from this list:
- Make sure that you are a local administrator with full administrative rights for both the old and new servers. This is necessary to ensure the software installs and runs successfully.
- In order to perform the transfer/migration on your own, you must be running the latest release of the software. If you are currently running an older version of the software, please update to the most current build. If you cannot update to the current build, you will need to phone Customer Relations at 1-888-781-8966, Option 2 or log a support ticket (select Professional Services Request for the ticket type) to have Professional Services assist in the transfer/migration.
Preparing for the transition
To prepare for the transition from the old server to the new server, perform the following steps:
- You will need to download and install the latest version on the new server in order to proceed with the transfer/migration. To get the latest version, please visit our Product Info & Updates blog and click the most recent blog post relating to CRD. The link will be at the bottom of the article. Follow the installation instructions for your software here:
When prompted, please ensure you select the same Crystal runtimes version that is present on the old server.
- On the old server, ensure that all report locations (Schedule Properties > Report Location) and disk destinations (Schedule Properties > Destination) point to a full UNC path.
If report locations and disk destinations are pointing to a mapped drive or a path other than a full UNC path, the reports will not be found and/or will not export to the correct disk destination when schedules are executed on the new server.
- On the new server, recreate the 32-bit DSNs that the reports on the old server use. These will be needed in order for the new installation to successfully access your data sources.
Please ensure that the DSNs are set up exactly as they are on the old server. Failure to do so will result in errors when the schedules run on the new server.
- For CRD Migrations: On the old server, navigate to C:\Program Files (x86)\ChristianSteven\CRD and copy the Cache folder and all its contents. Move the copy over to the new server.
If you do not move the cache folder from the old server to the new server, all schedules will show the error "Load Report Failed" when opened for the first time on the new server. If you do not want to move the cache folder, you can resolve this issue. Simply run a full system refresh (Right click Home folder > All Contents > Refresh) on the new server once you have completed the rest of this process.
Transition to the New Server
To fully move the software from the old server to the new, perform the following steps:
- Open the software on the old server and create a system backup. Follow the instructions for your software here:
It is recommended that you save the backup in a location where it is easily accessed by the new server (such as a network drive).
- On the new server, restore the backup you created in the previous step. Follow the instructions for your software here:
- Turn off scheduling on the new server by performing the following:
- Open the software on the new server. Navigate to Options > Scheduler and click the box next to No Scheduling Required.
- Click Apply Setting in the upper right. Then, close the window.
Until you turn scheduling off, you may receive a pop-up window with an error stating that the new server is not the primary scheduler. This will pop up continuously until scheduling is turned off on the new server.
- Once you have successfully turned off the scheduler, verify the following:
- All of your settings listed on the Options tab are correct
- All schedules are pointing to the correct directory for your reports
- Mail, database, and system path settings are correct
- Test, Test & Test again.
It is highly recommended that you take the time to verify that all of your schedules on the new server are running properly. Essentially, you will want the new server to operate the same as the old server before proceeding to the activation/deactivation portion of the migration. You have 30 days from the date that you install the software on the new server to activate it. Please allow enough time in that 30-day window to ensure your schedules are running as expected before going live.
Going Live with the New Server
Now it is time to officially make the switch from the old server to the new server. To do so, perform the following:
- Stop the scheduler on the old server
- Deactivate the old server
- Activate the new server
- Start the scheduler on the new server
At this time, your software should be completely transferred to the new server. You can go ahead and uninstall the software from the old server.