"Scale-out deployment" error while migrating Reporting Services from SQL 2005 to SQL 2008

  • Marios Philippopoulos

    SSC Guru

    Points: 57030

    I'm in the process of migrating our SSRS installation from SQL 2005 to SQL 2008.

    I'm doing a side-by-side migration on the same machine from a SQL 2005 to a SQL 2008 instance, following the procedure outlined in this link:

    How to: Migrate a Reporting Services Installation

    http://msdn.microsoft.com/en-us/library/ms143724.aspx

    When I'm about to test the new report server and enter the url, I get this error:

    The feature: "Scale-out deployment" is not supported in this edition of Reporting Services. (rsOperationNotSupported)

    Anyone know how to fix this?

    Many thanks for any input.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Marios Philippopoulos

    SSC Guru

    Points: 57030

    I should point out that I am migrating from SQL-2005 Enterprise Edition to SQL-2008 Standard Edition.

    In the Reporting Services Configuration Manager for SQL 2008 I have removed the entries in the Scale-out deployment node, and now I am getting the following error:

    The report server installation is not initialized. (rsReportServerNotActivated)

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Gift Peddie

    SSC Guru

    Points: 73570

    Scale out error means you are running either SQL Server Express or Standard and is trying to deploy reports created in either Enterprise or Developer edition.

    The short answer is you cannot do that you have to remove features related to Enterprise edition before you can run it. There is a support article I will look for it.

    Kind regards,
    Gift Peddie

  • Marios Philippopoulos

    SSC Guru

    Points: 57030

    Gift Peddie (2/6/2009)


    Scale out error means you are running either SQL Server Express or Standard and is trying to deploy reports created in either Enterprise or Developer edition.

    The short answer is you cannot do that you have to remove features related to Enterprise edition before you can run it. There is a support article I will look for it.

    Thank you so much for the quick response, yes, any links on this would be appreciated.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • denglishbi

    SSCrazy Eights

    Points: 8831

    From the documentation on Configuring a Report Server Scale-Out Deployment:

    "The Reporting Services edition must be Enterprise, Developer, or Evaluation. Standard edition does not support a scale-out deployment. You can create a scale-out deployment using a combination of editions as long as the edition supports the scale-out feature."

    ----------------------------------------------------------------------------------------
    Dan English - http://denglishbi.wordpress.com

  • Gift Peddie

    SSC Guru

    Points: 73570

    Your error is specific to 2008 migration which gives the scale out error based on how the migration was performed. There is an edit in the page that shows how to fix it and there are things you need to do when you move reporting services DB from one server to the other it also gives the Scale out error if you move code from developer to enterprise. Check below for some solutions.

    http://msdn.microsoft.com/en-us/library/ms156421.aspx

    http://support.microsoft.com/?kbid=842425

    http://blogs.msdn.com/bimusings/archive/2006/03/03/543088.aspx

    Kind regards,
    Gift Peddie

  • Marios Philippopoulos

    SSC Guru

    Points: 57030

    Dan English (2/6/2009)


    From the documentation on Configuring a Report Server Scale-Out Deployment:

    "The Reporting Services edition must be Enterprise, Developer, or Evaluation. Standard edition does not support a scale-out deployment. You can create a scale-out deployment using a combination of editions as long as the edition supports the scale-out feature."

    Thank you, I actually don't want to use the scale-out feature. I only want to migrate to sql 2008.

    The problem, I think, is that my SQL 2005 installation is on Enterprise Ed., whereas my SQL 2008 installation is on Standard Ed.

    There is a scale-out deployment node in the Reporting Services Config tool for SQL 2008. I went there and removed the SQL-2005 and SQL-2008 nodes, thinking that this would fix the error, but then I got the 2nd error I have posted above.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Marios Philippopoulos

    SSC Guru

    Points: 57030

    Gift Peddie (2/6/2009)


    Your error is specific to 2008 migration which gives the scale out error based on how the migration was performed. There is an edit in the page that shows how to fix it and there are things you need to do when you move reporting services DB from one server to the other it also gives the Scale out error if you move code from developer to enterprise. Check below for some solutions.

    http://msdn.microsoft.com/en-us/library/bb522762.aspx

    http://support.microsoft.com/?kbid=842425

    http://blogs.msdn.com/bimusings/archive/2006/03/03/543088.aspx

    Thanks!

    I will have a look at this info.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Marios Philippopoulos

    SSC Guru

    Points: 57030

    Marios Philippopoulos (2/6/2009)


    I should point out that I am migrating from SQL-2005 Enterprise Edition to SQL-2008 Standard Edition.

    In the Reporting Services Configuration Manager for SQL 2008 I have removed the entries in the Scale-out deployment node, and now I am getting the following error:

    The report server installation is not initialized. (rsReportServerNotActivated)

    Now, I'm getting this error (above). There is no initialization node on the Reporting Services Config tool for SQL 2008.

    Any suggestions how to fix this?

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Gift Peddie

    SSC Guru

    Points: 73570

    It is not related to that the answer is in the support article I posted some of the reasons I submitted many bugs to Microsoft.

    Here is what is happening you have restored your ReportServerDB and TempReportServerDB but the Master Database of the SQL Server 2008 does not know you have added the databases so the relational engine does not know about the databases that contain your RDL files. Here is the link for how to move those databases from one server to another use that with the support article and that error will be fixed because when you create Backup devices your database is restored through the Master of the new server.

    http://technet.microsoft.com/en-us/library/ms156421.aspx

    Kind regards,
    Gift Peddie

  • Marios Philippopoulos

    SSC Guru

    Points: 57030

    Gift Peddie (2/6/2009)


    It is not related to that the answer is in the support article I posted some of the reasons I submitted many bugs to Microsoft.

    Here is what is happening you have restored your ReportServerDB and TempReportServerDB but the Master Database of the SQL Server 2008 does not know you have added the databases so the relational engine does not know about the databases that contain your RDL files. Here is the link for how to move those databases from one server to another use that with the support article and that error will be fixed because when you create Backup devices your database is restored through the Master of the new server.

    http://technet.microsoft.com/en-us/library/ms156421.aspx

    Thanks for the link.

    The problem seems to be with the encryption key of the "old" SQL 2005 install.

    I just went and deleted the encryption key from the sql-2008 install (I had restored the sql-2005 key on it) and I can now view all my reports listed no problem - the error has disappeared.

    I have probably lost all my datasource info though. I will need to recreate it...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Gift Peddie

    SSC Guru

    Points: 73570

    SQL Server Reporting Services dropping the DataSource permission is also a known issue you could open your RDL files in the designer and check the connection property it is usualy empty so you have to add the permissions back again.

    I am assuming this is your problem if not you could run test runs before fixing your problems in production.

    Kind regards,
    Gift Peddie

  • Marios Philippopoulos

    SSC Guru

    Points: 57030

    Gift Peddie (2/6/2009)


    SQL Server Reporting Services dropping the DataSource permission is also a known issue you could open your RDL files in the designer and check the connection property it is usualy empty so you have to add the permissions back again.

    I am assuming this is your problem if not you could run test runs before fixing your problems in production.

    Yes, I have to go to every data source and pick the radio button named "Windows Integrated Security".

    It's a workaround, but not a great one.

    The big question is, why the SQL-2005 encryption key does not work with the SQL-2008 install.

    I have not used any Enterprise-ed. features in the sql-2005 installation, so the encryption key should have been acceptable to the sql-2008 installation.

    I wonder if this is a bug I should open with MS.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Gift Peddie

    SSC Guru

    Points: 73570

    Goodluck with posting bugs because you may find your answer in the link below and most of what Microsoft says are depreciated are bugs I gave to the Reporting Services team in person.

    The changes relevant to upgrade from 2005 are in the link below.

    http://msdn.microsoft.com/en-us/library/ms143380.aspx

    Kind regards,
    Gift Peddie

  • Marios Philippopoulos

    SSC Guru

    Points: 57030

    Gift Peddie (2/6/2009)


    Goodluck with posting bugs because you may find your answer in the link below and most of what Microsoft says are depreciated are bugs I gave to the Reporting Services team in person.

    The changes relevant to upgrade from 2005 are in the link below.

    http://msdn.microsoft.com/en-us/library/ms143380.aspx

    OK, thank you for all the help, much appreciated.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

Viewing 15 posts - 1 through 15 (of 23 total)

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