Post reply

SQL Server 2008 R2 Reporting Services Installation and Migration

  • September 21, 2011 at 2:39 pm

    #243438

    I'm not sure if this is should go in the SQL n00bs section or not, but here goes.

    I've been assigned a task of installing and migrating SQL Server Reporting Services using the following configuration.

    Node A: SQL 2005 Reporting Services (This will be retired)

    Node B: SQL 2005 -this contains the data Node A reports on.

    Node C: SQL 2008 R2 Service Pack 1 Reporting Services. This will also get the data from Node B.

    I am fairly confident with installing just 2008 Reporting Services on Node C.

    Although I have no experience with Reporting Services at all, it seems like I just need to configure it to look at Node B correctly and everything should fall in line.

    However, I have spent the greater part of today on the Googles and I can find scant information on the subject.

    For instance, I am unaware if using 2008 to look at 2005 is an issue.

    If anyone has any advice, or could point me in the direction of a good article on the matter I would appreciate it.

    Thank you in advance for any help.

  • September 29, 2011 at 8:36 am

    #1388406

    I started another thread on this with an error message that has apparently been deleted.

    Now that I have been trying to configure the two nodes I get the following message from the original node:

    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 '147'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)

    And then this from the new node:

    The report server installation is not initialized. (rsReportServerNotActivated)

    Any help here would be hot.

  • September 29, 2011 at 8:51 am

    #1388425

    you cant configure both SSRS instances to use the same database!!

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • September 29, 2011 at 9:14 am

    #1388440

    That would have been GREAT information to get eight days ago.

    Does anyone know how I can get the original node working again?

    Either node?

  • September 29, 2011 at 9:16 am

    #1388444

    Going along with Perry... When you say that Node B hs the reporting data, do you mean the ReportServer databases, or simply the data from some application or warehouse that is being returned for the results in the report? Based on your error messages, it seems that it is probably both, but I do not want to assume.

    Thanks,

    Jared

    Jared
    CE - Microsoft

  • September 29, 2011 at 9:21 am

    #1388448

    Node B contains both the ReportServer dbs, and the data warehouse.

  • September 29, 2011 at 9:24 am

    #1388452

    Hmm... You may have to create another instance on that server for the new report server databases and then you can migrate data.

    Thanks,

    Jared

    Jared
    CE - Microsoft

  • September 29, 2011 at 9:33 am

    #1388460

    I don't see how that's an option.

    I'm really just interested in getting the original Report Server working again.

    Would that really require a new instance?

  • September 29, 2011 at 9:44 am

    #1388466

    What did you do to the first one? I was under the impression that you were simply setting up a third server with a new version and that you did nothing to the first report server.

    Thanks,

    Jared

    Jared
    CE - Microsoft

  • September 29, 2011 at 9:46 am

    #1388468

    When I configured the new report server it borked the old one.

    It now says the database is unavailable or unreadable.

  • September 29, 2011 at 9:48 am

    #1388470

    Did you go into the ReportServer Configuration Manager to do this, or did you just try running a report?

    Thanks,

    Jared

    Jared
    CE - Microsoft

  • September 29, 2011 at 9:52 am

    #1388473

    jared-709193 (9/29/2011)

    Hmm... You may have to create another instance on that server for the new report server databases

    no, you do not have to do this. Configure the new SSRS instance to point to Node B and create a new Reportserver database with a different name to use the same instance on NodeB

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • September 29, 2011 at 11:53 am

    #1388554

    I didn't have to create a new DB or instance.

    I restored the backups of ReportServer and ReportServerTempDB back to their state before the new node touched them.

    That allowed me to rerun the configuration on the original node without errors.

    Then a friend helped me out with the IIS stuff as I am plenty ignorant about that.

  • October 26, 2011 at 3:04 pm

    #1399924

    I'm about to give this a go again.

    I'm going to try disabling Reporting Services on the 2005 machine, and then running the configuration on the 2008 machine.

    2008 Reporting Services should not have any issues getting the data from a 2005 SQL Server, correct?

    Any hornets' nests I may be running into?

    😀

Viewing 14 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply