I have a similar issue. Reporting Services is installed on the failover node
and it points to the catalog database on the active node. However, when the
node is failed over, attempts to run reports produce this error page:
The report server is unable to access encrypted data. Apply a back-up key or
delete all encrypted content. (rsEncryptedDataUnavailble) (rsRPCError)
The encryption key appears to be configured on both nodes. Restarting the
SSRS service doesn't help.
Any ideas on how to fix this?
[quoted text, click to view] "isabelle" wrote:
> Hi,
> We have a 2 node cluster and realized when we were testing failover that
> reporting services was not installed on our 2nd node. So I tried to run the
> SQL 2005 install and got the message "Edition Change Check - Warning. To
> change an existing instance of SQL 2005 to a different edition, you must run
> SQL 2005 setup from the command propmt and include SKUUPGRADE=1 parameter."
> When I checked, Report Services was already installed and I went through the
> Reporting Services config tool and when I try to initialize it, I get the
> error: "The version of the Report Server database is either in a format that
> is not valid, or it cannot be read. The found version is 'C.0.8.54'. The
> expected version is 'C.0.8.40'.
>
> I have checked all the settings of the SQL Server configurations on both
> nodes 1 and 2 and they look identical. I've seen on forums that the solution
> is to create a new ReportServer database, but I already have the database on
> Node 1 that I do not want to overwrite and what I'm trying to do is setup
> Reporting Services on Node 2 so that when we failover, users can continue to
> access their reports.
>
> Any ideas or help anyone can give me is greatly appreciated!
> Thanks,
