sql server reporting services: RS2005 front-end disaster-how to assoc ReportServer db to new fron -- sql server reporting services

RS2005 front-end disaster-how to assoc ReportServer db to new fron

Dana Forsberg
12/28/2005 1:31:03 PM

sql server reporting services:

Search phrases:
encyrption key
symmetric keys
Scale-out deployment... not supported
Sql Server 2005 Standard Edition
Reporting Services 2005
The report server installation is not initialized.
(rsReportServerNotActivated) (rsRPCError)
Reporting Services Configuration Manager

====================
Question:
What exactly is a working procedure for dis-associating a ReportServer
database from one Report Server installed on Server "A", and re-associating
it successfully with a ReportServer installed on Server "B"?
In particular, how is this done in Standard Edition, and without having to
delete encrypted information in the Report Server database? (Of course
deleting the encyrption key *only* is OK, if in the end there's a step to
restore it.)
====================

The particular difficulty I've run into has to do with encryption keys.
On the one hand, messages during install emphasize backing up the encryption
keys, plus there is an entire screen in "Reporting Services Configuration
Manager" devoted to doing-things with these keys.
On the other hand, when simply trying to configure a new-install of
Reporting Services by giving it an *existing* ReportServer database to use,
an error appears saying "Scale-out Deployment, that feature is not supported
by this edition ... remove existing keys first" (full error listed below).

If recovery of a front-end to a different server isn't supported -- what the
heck is the backup of the encryption keys for?!

Now 'remove existing keys first' sounds like a good suggestion. And I did
find that the RsKeyMgmt.exe program has a "-r" option which will remove
existing keys without removing the encrypted data (at least that's my
impression). The trouble is it doesn't work! Here's the symptom:

-------------- Begin ---------
These are commands run on Server "A"
[quoted text, click to view]
SERVER-A\MSSQLSERVER - a13fc790-41dd-43e2-aca7-6bb503cd1bf7

[quoted text, click to view]
Are you sure you want to delete this key? Yes (y)/ No (n): y
The command completed successfully

[quoted text, click to view]
SERVER-A\MSSQLSERVER - a13fc790-41dd-43e2-aca7-6bb503cd1bf7
-------------- End ---------
Notice that the "-l" option shows no change after the command presumably
completed successfully.

Trying to run this on Server "B", I first install and get the error
mentioned above (scale-out... not supported). Now my RsKeyMgmt.exe will
operate on the ReportServer database I'm trying to dis-associate/re-associate
-- at least it now knows what database I'm trying to affect.

When I run RsKeyMgmt, I can now see two Reporting Servers listed, according
to the ReportServer database.
-------------- Begin ---------
These are commands run on Server "B"
[quoted text, click to view]
SERVER-B\MSSQLSERVER - 99b64336-d87f-4085-8288-467631befecd
SERVER-A\MSSQLSERVER - a13fc790-41dd-43e2-aca7-6bb503cd1bf7
The command completed successfully
-------------- End ---------

However, I have run through this scenario several times, sometimes trying to
remove the key by running the command on Server "A", sometimes running it on
Server "B". I try to remove Server "B", and that does work, confirmed by the
listing from "RSKeyMgmt.exe -l" -- but that only puts me back to a working
installation with Server "A" as the front end. Attempts to remove Server "B"
do not succeed. I've tried "iisreset" and stopping and starting the Reporting
Services service. The most affect I've had is to render both Server "A" and
Server "B" inoperable, unless I completely delete the encrypted information.

Dear Microsoft, a confirmed and complete step-by-step procedure is really
what is needed here. If I've overlooked it in the manual or help, please tell
me exactly where it is. If not, please fill this gap in a core administrative
aspect and disaster-recovery aspect of Reporting Services 2005.

Thanks!

Complete Error Text:
(Warning icon) Setting Connection Info for Reporting Server
You specified a connection to a report server database that contains
encryption keys for another report
server. If you are configuring a scale-out deployment, that feature is not
supported by this edition of
Reporting Services. If you want to use this report server database with the
current report server instance,
remove the existing encryption keys first.

RE: RS2005 front-end disaster-how to assoc ReportServer db to new fron

Dana Forsberg
12/28/2005 1:58:02 PM

In the second-to-last paragraph, it should read "Attempts to remove Server "A"
do not succeed."

[quoted text, click to view]

RE: RS2005 front-end disaster-how to assoc ReportServer db to new

Fabian
2/16/2006 8:28:20 AM

Dana, have you heard anything from Microsoft regarding this issue?
I'm running into the exact same issues. The only way I can get the new
server to work is to manually recreate the encrypted content.
Let me know if you hear anything.
Thank you.
Fabian

[quoted text, click to view]

RE: RS2005 front-end disaster-how to assoc ReportServer db to new

Dana Forsberg
2/16/2006 9:39:28 AM

Nope, not a thing.
In fact, I appreciate your question as it confirms that I *am* getting email
if a reply is posted.

I will let you know, and likewise, I hope, if you get any good information
on this.
--Dana

[quoted text, click to view]

Re: RS2005 front-end disaster-how to assoc ReportServer db to new

DWallace
3/1/2006 10:56:24 AM

We ran into this same issue, and also found it odd that we could not
effectively deploy a workable recovery process using reporting
services. The help that IS available applies only to scale-out
deployments, which are not supported in standard edition.

Here's how we beat it though.

In your production instance, backup your encryption key. This is
easily done in the reporting services configuration utility for SQL
Server 2005.

Backup your reportserver database on both the production and the backup
instance.

Shut down reporting services on the backup instance.

Detach the reportserver database on the backup instance.

Rename the reportserver.mdf datafile, and corresponding .ldf file on
the backup instance.

Restore the production backup into the backup instance.

Start reporting services on the backup instance
You should notice that the report server fails to initialize...no
big deal
At this point, query reportserver database as follows:
select * from reportserver.dbo.keys
You will see two records, one for your current server, and one that
shows null

Navigate to the encryption keys area of Report Server Configuration
select 'restore' under the encryption key maintenance heading
run the above select again and notice that you now have three
keys, the two
you had before, and now one that has information from your
production reportserver

Delete the single record in the backup instance reportserver.dbo.keys
which corresponds to your production server.

DELETE FROM REPORTSERVER.DBO.KEYS WHERE MACHINENAME =
'YourProductionServerNameHere'

Stop and start reporting services again and all should be working fine.

The other thing we found that works also, is to restore the
reportserver production backup, then start reporting services, then
select 'delete' under delete encrypted content..the only difference is
that with this method we had to reset all of our data sources in the
reporting service web interface.

Hope this helps.

D

Re: RS2005 front-end disaster-how to assoc ReportServer db to new

suslikovich
3/14/2006 11:16:25 AM

Hi,
I have the same problem. I was developing reports on my local machine
(A) which was a report server too. I am getting data from a remote
server (B). Everything was working properly locally. Now I need to move
all this stuff to another server within my domain (C). I am still
developing reports on my local machine.
I installed SQL Server 2005 on C and followed instructions on this
post. I attached my machine's A "ReportServer" db on macnine C. By the
way, when I selected keys for the first time I saw three keys, my A
key, C key and NULL so I just deleted the A key. When I try to browse
report server I get this error:

The report server installation is not initialized.
(rsReportServerNotActivated)

I stopped and restarted service a few times. Did not help. Now I am
totaly confused about Reporting Services Configuration on both
machines. It is pretty strait forward for machine C. I made all
settings to that machine, dbs, accounts etc. But what about
configuration on my local machine now? Especially for "Database Setup"
part.

I appreciate any help!

Thanks,
Stan

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server reporting services group.