Migrate Prolaw SSRS to a New Server

Thursday, July 9th, 2015 | ProLaw Case Management, Technical | Mike Smith

This guide is migrate a Prolaw SSRS instance from one server to another.  This guide does not cover migrating Prolaw from one server to another, and many steps assume that this has already been done.  This guide is aimed at a firm that has many customizations to their built-in reports, or has many custom reports in Prolaw.  If you are simply using the default reports, there is no real need to move the whole SSRS instance, since the ReportInstaller.exe can easily redeploy the reports to the new server for you in their default setting.



Server1 (old) and Server2 (new) both have SQL installed and configured

Server1 and Server2 Have SSRS installed and configured

Server1 and Server2 both have Prolaw installed and accessible (database is the same)

Always keep one-off backups of each program piece when doing a migration!


Steps 1-10 are basically the same as the Microsoft articles for moving an SSRS database (https://msdn.microsoft.com/en-us/library/ms156421.aspx).  Steps 11+ are Prolaw specific.


Step1 – Log onto Server1 and backup the ReportServer database to a shared location.


Step2 – Open SSRS Configuration manager on Server1, backup encryption keys to the same location as above.


Step3 – Copy Server1 report database and Encryption key backup file (snk) to Server2.


Step4 – Stop SSRS Services on Server2


Step5 – Restore Server1’s Report server database to Server2, overwriting the database.


Step6 – Ensure the account you have SSRS running under on Server2 has the proper roles on the ReportServer database you just restored (RSExecRole / db_owner)


Step7 – Start SSRS Services on Server2


Step8 – Open SSRS Configuration Manager, under database, change database to the new database you just restored (even if same name).  Then restore the encryption keys from Server1.


Step9 – On Server2, review the “KEYS” table in the “ReportServer” database you just restored. Delete the entry pointing to the old server (machinename column).  If this is omitted, there could be a “scale-out deployment” error.


Step10 – Test the SSRS access.


Step11 – Now that SSRS is working, we need to update Prolaw to point to the new instance. Setup your Prolaw Agent account (that will run SSRS) in SQL, give them Sysadmin and ServerAdmin roles.  Map them to the correct databases (Prolaw and Reporting)


Step12 – Browse to the Prolaw folder on Server2’s SSRS instance, open the “Datasources” folder.  Modify the connection string of the datasource to your new server/database.



Step13 – run “reportinstaller.exe” in the Prolaw application directory on Server2, and update to new values (required for new service account password as its encrypted, new URL, etc).


Step14 – Test standard and custom reports in Prolaw.

Tags: , , , , ,

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Page 1 of 11

Leave a Reply