After SQL Fails Over to New Node Reports No Longer Work In ProjectDox

After SQL Fails Over to New Node Reports No Longer Work In ProjectDox

ISSUE:  After SQL Fails Over to New Node Reports No Longer Work In ProjectDox.  When a fail-over occurs to another SQL Server node, the Report Server database gets a new encryption key assigned to it which is different from the one stored in the connection string used by ProjectDox when it was connected to the initial node from when the reports were configured in ProjectDox.

SOLUTION:  In order to resolve you need to either delete the encrypted content on the Report Server side or run the ProjectDox Reports Migration Utility again to allow it to write a new connection string to the web.config file for connecting to the new SQL node. 

Deleting the encrypted content is the easiest method and the steps to complete are as follows:  Open the Report Manager Configuration screen on the SQL Server and then go to the section for Encrypted Content and select the option to Delete the Encrypted Content in the database. After performing this step, log into ProjectDox and try to access the reports and verify that you can view the report with the returned content from the SQL Server.