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
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.
To prepare for the transition from the old server to the new server, perform the following steps:
When prompted, please ensure you select the same Crystal runtimes version that is present on the old server.
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.
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.
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.
To fully move the software from the old server to the new, perform the following steps:
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).
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.
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.
Now it is time to officially make the switch from the old server to the new server. To do so, perform the following:
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.