March 14, 2009 at 1:11 pm
Hi,
We have a production default sql server 2000 instance database engine along with reporting services installed on the same same server.The reort server and reportservertempDb also on the same default instance.Now, we need to move this entire database engine and reporting services to ServerB(SQL server 2000).To achive this, we installed New sql server 2000 default instance on serverB and moved all the databases,logins,jobs.Now How to move the reporting services to serverB from production server?
I did not find any document for this task to achive. Could you please put steps together to do this task?
thanks
March 14, 2009 at 7:00 pm
Can we move the reporting services from one sql server 2000 instance to other sql server 2000 instance OR NOT?If yes please explain me the steps.
March 16, 2009 at 5:27 pm
hi,
http://msdn.microsoft.com/en-us/library/ms143724.aspx
http://msdn.microsoft.com/en-us/library/ms156421.aspx
http://www.developmentnow.com/g/115_2004_10_0_0_452440/Moving-RS-To-A-New-Web-Server-Problems.htm
followed the above links and I did the following
1.Install reporting services in New server.
2.Delete the ReportServer n ReportServerTempDb and restored the ReportServer n ReportServerTempDb from Old Server.
3.run the following command at a command prompt on the computer that is configured as the report server:
RSConfig -c -s Server name -d Reporting Services database name -a Sql|Windows -u User name -p User password
4.Backup the encryption key in old server using
RSKeyMgmt.exe -e -f Path of file name -p Strong password
5.Stop the IIS in new server
6.Restore the encryption key in new server that we have backed up in old server
7.Start the IIS
8.Then i went to the IIS->default website->reports->browse, I got the below error
This edition of Reporting Services does not support web farm deployment. (rsInvalidRSEditionConfiguration
We are using Reporting services 2000 standard edition.
what are the steps do I need follow to accomplish this?
March 17, 2009 at 12:02 pm
1.Install reporting services in New server.
2.Delete the ReportServer n ReportServerTempDb and restored the ReportServer n ReportServerTempDb from Old Server.
3.run the following command at a command prompt on the computer that is configured as the report server:
RSConfig -c -s Server name -d Reporting Services database name -a Sql|Windows -u User name -p User password
In step 3:
In the new server,the report server service running as network service what should I give the authentication and password in below statement
RSConfig -c -s Server name -d Reporting Services database name -a Sql|Windows -u User name -p User password
When I brose the reports in IIS IAm getting The error that The report server installation is not initialized. Check the documentation for more information. (rsReportServerNotActivated) Get Online Help -2147159550
Please advice me
Thanks
March 17, 2009 at 12:20 pm
When you get SSRS not initialized it means the Master database in the new server does not know your ReportServerDB and ReportServerTempDB so you need to make the changes so the relational engine in the new server will know your moved databases. Check the thread below for how another person fixed it and check the second link which is the migration doc to see what changes you need.
http://www.sqlservercentral.com/Forums/Topic651732-147-2.aspx#bm651915
http://technet.microsoft.com/en-us/library/ms156421.aspx
Kind regards,
Gift Peddie
March 17, 2009 at 3:23 pm
Hi,
Could you plz tell me the srteps to move sql server 2000 reporting services standard edition from one server to other(SQL server 2000 standard edtion).
I tried all the option in links you provided but none of them helped me.If possible please provide me the steps
March 17, 2009 at 3:30 pm
The first question did you create backup devices when you moved the two databases because that is how the Master of the new server gets to know your databases. The instructions are fixed you cannot do what you like you need to print it out and take one step at a time. I have even helped 2008 in Windows 2008 migration so you need to print out the how to move reporting services from one server to another and do exactly.
Kind regards,
Gift Peddie
March 17, 2009 at 3:56 pm
thanks peddie,
Here all the links explaining about how to migrate reporting services from sql server 2000 to 2005. But I need to migrate reporting services from one sql server 2000 to other sql server 2000.
there is no proper document to do this task. So It would be GREAT help for me if you put some steps together.
Thanks in advance
March 17, 2009 at 4:08 pm
Yes the link opened to 2008 that was my over site but that is the document you need to print out, use that with the support article which covered configuration. I tried to help you but you decided to do what you want, most things with SSRS did not leave room for that so I left you alone. So print out these two pages read them in a quiet place.
Moving a Report Server Database to Another Computer
http://msdn.microsoft.com/en-us/library/ms156421(SQL.90).aspx
http://support.microsoft.com/kb/842425
Kind regards,
Gift Peddie
March 17, 2009 at 5:51 pm
I followed the below steps:
To move a SQL Server 2000 Reporting Services database to another computer and to make Reporting Services point to that database, follow these steps:
Back up the Reporting Services database and the Reporting Services temporary database on the source computer.
Note By default, the name of the Reporting Services database is ReportServer, and the name of the Reporting Services temporary database is ReportServerTempDB.
Restore the databases that you backed up in step 1 on the appropriate instance of SQL Server on the destination computer.
To make Reporting Services point to the database that you restored in step 2, run the following command at a command prompt on the computer that is configured as the report server:
RSConfig -c -s Server name -d Reporting Services database name -a Sql|Windows -u User name -p User password
Note For more information about the Rsconfig.exe command-line utility, run the following command at a command prompt:
RSConfig /?
To move the Reporting Services database together with the Reporting Services Windows service, and Reporting Services Web service from one computer to another computer, you must first back up the encryption keys on the source computer. You can then move the Reporting Services database from the source computer to the destination computer and then restore the encryption keys on the destination computer. To do this, follow these steps:
On the source computer, use the Rskeymgmt.exe command-line utility to back up the symmetric encryption keys. To do this, run the following command at a command prompt:
RSKeyMgmt.exe -e -f Path of file name -p Strong password
Note For more information about the Rskeymgmt.exe command-line utility, run the following command at a command prompt:
RSKeyMgmt /?
On the destination computer, follow these steps:
Install Reporting Services.
Stop the Report Server Windows service.
Stop Microsoft Internet Information Services (IIS).
Move the Reporting Services database and the Reporting Services temporary database from the source computer to the appropriate instance of SQL Server on the destination computer.
Note By default, the name of the Reporting Services database is ReportServer, and the name of the Reporting Services temporary database is ReportServerTempDB.
For more information about how to move databases between computers that are running SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
314546 (http://support.microsoft.com/kb/314546/ ) How to move databases between computers that are running SQL Server
On the destination computer, follow these steps:
Start the Report Server Windows service.
Start IIS.
Use the Rsconfig.exe command-line utility to configure the report server instance to use the Reporting Services database that you moved to the destination computer in step 3. To do this, run the following command at a command prompt:
RSConfig -c -s Server name -d Reporting Services database name -a Sql|Windows -u User name -p User password
Note For more information about the Rsconfig.exe command-line utility, run the following command at a command prompt:
RSConfig /?
Use the Rskeymgmt.exe command-line utility to apply the symmetric encryption keys that you backed up in step 1. To do this, run the following command at a command prompt
Note Path of file name is the path of the file name and Strong password is the password that you used in step 1):
RSKeyMgmt -a -f Path of file name -p Strong password
Note The solutions in this article do not account for problems that will occur if you are restoring a standard edition report server. The problem is that the row for the old instance will still be in the database after you follow the instructions. Standard edition will not start because it will think that the source computer and the destination computer have joined a Web farm.
To resolve this problem, manually run Delete from keys where client > -1 before you apply a backup key. Manually run Delete from keys where client > -1 only for Standard edition. If you have a Web farm, you must disable all the other nodes in the Web farm that are presumably still working.
Could you please explain me how and where to perform the above quoted lines
March 17, 2009 at 6:17 pm
I may have found what you need find out about your setup that makes SSRS thinks you are in a web farm. Check below for the type of places you cannot run SSRS 2000 standard.
http://msdn.microsoft.com/en-us/library/cc966443.aspx
Kind regards,
Gift Peddie
March 19, 2009 at 1:00 am
Yeah....I have succesfully Moved reporing services from one sql server 2000 to other sql server 2000 and also upgraded to 2005 succesfully.
I will put together steps and post here soon.
Many thanks to peddie......
March 19, 2009 at 7:07 am
I am so glad to know you have finished the migration please post what was making it complain about web farm in SSRS 2000 and other things so others can use it.
🙂
Kind regards,
Gift Peddie
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply