November 22, 2017 at 9:25 am
Hello, i´m new woriking with SQL reporting services,
This is the issue:
Every time i restore the report server database works fine but
a couple of hours is corrupted by an error of versioning,
maybe something is upgrading the report server data base.
I don´t work with scale-out deployment, .
How do I disable the automatic update?
Error log.
-----------------------------------------------------------------------------------------------------------------------
Process monitoring started.
library!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Catalog SQL Server Edition = Standard
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Exporting public key
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Performing sku validation : Scale-Out
library!DefaultDomain!4084!11/21/2017-16:33:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Scale-out deployment" is not supported in this edition of Reporting Services.;
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Exporting public key
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Performing sku validation : Scale-Out
library!DefaultDomain!b8fc!11/21/2017-16:33:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Scale-out deployment" is not supported in this edition of Reporting Services.;
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Exporting public key
---------------------------------------------------------------------------------------------------------------
November 22, 2017 at 11:38 am
guerrerocz87 - Wednesday, November 22, 2017 9:25 AMHello, i´m new woriking with SQL reporting services,
This is the issue:Every time i restore the report server database works fine but
a couple of hours is corrupted by an error of versioning,
maybe something is upgrading the report server data base.
I don´t work with scale-out deployment, .How do I disable the automatic update?
Error log.
-----------------------------------------------------------------------------------------------------------------------
Process monitoring started.
library!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Catalog SQL Server Edition = Standard
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Exporting public key
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Performing sku validation : Scale-Out
library!DefaultDomain!4084!11/21/2017-16:33:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Scale-out deployment" is not supported in this edition of Reporting Services.;
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Exporting public key
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Performing sku validation : Scale-Out
library!DefaultDomain!b8fc!11/21/2017-16:33:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Scale-out deployment" is not supported in this edition of Reporting Services.;
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Exporting public key
---------------------------------------------------------------------------------------------------------------
It sees it as a scale out due to the references in the Keys table in the ReportServer database. Remove the one pointing to the other/original server.
Sue
November 22, 2017 at 11:45 am
Sue_H - Wednesday, November 22, 2017 11:38 AMguerrerocz87 - Wednesday, November 22, 2017 9:25 AMHello, i´m new woriking with SQL reporting services,
This is the issue:Every time i restore the report server database works fine but
a couple of hours is corrupted by an error of versioning,
maybe something is upgrading the report server data base.
I don´t work with scale-out deployment, .How do I disable the automatic update?
Error log.
-----------------------------------------------------------------------------------------------------------------------
Process monitoring started.
library!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Catalog SQL Server Edition = Standard
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Exporting public key
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Performing sku validation : Scale-Out
library!DefaultDomain!4084!11/21/2017-16:33:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Scale-out deployment" is not supported in this edition of Reporting Services.;
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Exporting public key
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Performing sku validation : Scale-Out
library!DefaultDomain!b8fc!11/21/2017-16:33:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Scale-out deployment" is not supported in this edition of Reporting Services.;
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Exporting public key
---------------------------------------------------------------------------------------------------------------It sees it as a scale out due to the references in the Keys table in the ReportServer database. Remove the one pointing to the other/original server.
Sue
Hi Sue.
Thanks for the response.
I do that but when i restore the reporting database, the encription key for the old server appears on the table dbo.keys.
regards!
November 22, 2017 at 1:02 pm
guerrerocz87 - Wednesday, November 22, 2017 11:45 AMSue_H - Wednesday, November 22, 2017 11:38 AMguerrerocz87 - Wednesday, November 22, 2017 9:25 AMHello, i´m new woriking with SQL reporting services,
This is the issue:Every time i restore the report server database works fine but
a couple of hours is corrupted by an error of versioning,
maybe something is upgrading the report server data base.
I don´t work with scale-out deployment, .How do I disable the automatic update?
Error log.
-----------------------------------------------------------------------------------------------------------------------
Process monitoring started.
library!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Catalog SQL Server Edition = Standard
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Exporting public key
crypto!DefaultDomain!4084!11/21/2017-16:33:45:: i INFO: Performing sku validation : Scale-Out
library!DefaultDomain!4084!11/21/2017-16:33:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Scale-out deployment" is not supported in this edition of Reporting Services.;
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Exporting public key
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Performing sku validation : Scale-Out
library!DefaultDomain!b8fc!11/21/2017-16:33:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Scale-out deployment" is not supported in this edition of Reporting Services.;
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Initializing crypto as user: NT Service\ReportServer
crypto!DefaultDomain!b8fc!11/21/2017-16:33:45:: i INFO: Exporting public key
---------------------------------------------------------------------------------------------------------------It sees it as a scale out due to the references in the Keys table in the ReportServer database. Remove the one pointing to the other/original server.
Sue
Hi Sue.
Thanks for the response.I do that but when i restore the reporting database, the encription key for the old server appears on the table dbo.keys.
regards!
The scale out errors are from the other server in the keys table - it's based on machine name and instance name. Leave the one with NULL for machine name and -1 for client.
You also do need the encryption key from the old server and need to restore that. So after you restore and delete the key of the old server, you need to use Reporting Services Configuration Manager to verify the settings and then import the encryption key.
Moving SSRS databases are a bit different than other databases. You also need the config files if you are using any custom extensions but that's a different error that should just be in the reporting services logs. The jobs and schedules will be recreated which can cause problems as well. If you just do a restore, you will also have the data sources pointing to whatever is being used in production.
Sue
November 22, 2017 at 1:55 pm
Thanks in advance!
November 22, 2017 at 2:01 pm
guerrerocz87 - Wednesday, November 22, 2017 1:55 PMThank you Sue.
I appreciate your response
I will apply this solution and tomorrow I share the resultThanks in advance!
Thanks for the feedback. Please do let us know how it turns out. If you get any errors, capture the specific errors and let us know what those are. The errors would most likely be in the Reporting Services log.
Sue
November 28, 2017 at 10:00 am
Sue_H - Wednesday, November 22, 2017 2:01 PMguerrerocz87 - Wednesday, November 22, 2017 1:55 PMThank you Sue.
I appreciate your response
I will apply this solution and tomorrow I share the resultThanks in advance!
Thanks for the feedback. Please do let us know how it turns out. If you get any errors, capture the specific errors and let us know what those are. The errors would most likely be in the Reporting Services log.
Sue
Hi Sue.
This issue was resolved...
That answer you give me was correct!
but my main issue was that in the backup SQL server someone installed SSRS and redirect for that server works like scale-out deployment, but after some test he unninstall the feature and the reporting services on that server will not stopped.
After stop the sql report service on the sql bakcup server the table dbo.keys on production environment not register any key from the sql backup server, and consequently the schema from the report database was not upgrated automatically.
Thank you for the support to all!
regards!
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply