-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SqlRs: SQL Server 2016 SSRS init fails on AWS #1258
Comments
I've now tested with two different AWS AMIs, with our production configuration, which uses The production configuration succeeds on both AMIs and the test configuration fails on both with the above error. Is the CIM class used in |
I wonder if it fails on this - it would suggest that. So it can never get to the point that it restarts the service We should really add more verbose messages in this resource so it's easier to track how far it gets. Can you please provide the parts of configuration script that configures the Reporting Services? So it's is possible to reproduce this. |
Hi, I've managed to replicate the problem with absolutely minimal configuration. I tested with the following AWS AMI (eu-west-01 region, the ID will be different in different regions):
On a clean install, first install
Then, save this to a
You'll get the same error:
|
It also looks that all that is needed after the initialisation fails is to restart SSRS service. I have a few custom SSRS resources (setting policies and roles). They keep failing until I restart SSRS service. |
@bozho Wonder if they way it configures it is the same way to configure a scale out deployment, and since the Standard version does not support it (see Scale out deployment (Web farms) under Reporting Services Features Supported by the Editions of SQL Server , then it fails. This probably works if you use Enterprise edition of SQL 2016. So the problem is that this should be able to correctly initialize SSRS 2016 Standard as well. |
The strange thing is that if I use the And why would Are there two different versions of |
@johlju Ok, found out why the The code in You write better code and you're worse off... :-) |
@johlju I can confirm this is still happening. Would it make sense to treat this as a warning? I see no way to control the "scale-out deployment" option on SSRS... |
But if you get this error, aren’t the wrong edition used if you get this error? 🤔 Or is this just a warning reported back from the CIM call, but we treat it as an error? If so we can just output a warning for this, but an error in all other cases. The integration test for SqlRS does not report this error, at least the tests doesn’t fail. Is it because we use the Evaluation (equals the Enterprise) version for the tests? |
No idea, we use SQL Standard on AWS (this is SQL 2016), so SSRS is bundled with it. AWS image contains a default install of SQL Server, with SSRS just installed, not configured/initialised (there's an option in SQL Setup for that).
|
I’m good with outputting a warning for now, when this error is reported, until we know if this is a bug in the CIM method, or any other reason it is reporting this error. :) |
Ok, I'll work on the patch |
@johlju Heh, I had a hunch and did a bit more testing by executing It seems that executing CIM method I suppose by executing So, the suggested patch here would be not to execute |
Awesome detective work on this one too! 😃 |
…L Standard and lower editions
…r CIM method is never called
…L Standard and lower editions
…r CIM method is never called
…L Standard and lower editions
…r CIM method is never called
…L Standard and lower editions
…r CIM method is never called
…L Standard and lower editions
…r CIM method is never called
…L Standard and lower editions
…r CIM method is never called
- Changes to SqlRS - When initializing Reporting Services, there is no need to execute `InitializeReportServer` CIM method, since executing `SetDatabaseConnection` CIM method initializes Reporting Services Fixed (issue #1258)
Details of the scenario you tried and the problem that is occurring
We have a configuration that we run against a provisioned AWS VM Windows Server 2016 + SQL Server 2016 SP1 Standard. (We use the latest AMI that matches the name pattern Windows_Server-2016-English-Full-SQL_2016_SP1_Standard*)
Our set of partial configurations is not trivial - we have a workflow that compiles and pushes these configurations to the target server. One of the first things it does is set the machine name, which causes a reboot. Our workflow then waits for the machine to boot back up and then waits for the configuration run to finish.
Recently, we noticed that after a while the workflow starts reporting that DSC has encountered an error, but there's nothing in the Event Log. However, there is an entry in the log file:
Verbose logs showing the problem
It looks like the initialisation only partially fails - after this has run, Reporting Services Configuration Manager looks fine, but logging into the web GUI gets you a 503, until we manually restart the SSRS service.
After the restart, SSRS seems to be working fine, our custom roles/policies resources to their job, we can deploy reports, etc.
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
I'll see if I can produce a minimal configuration to replicate this problem.
SQL Server edition and version the target node is running
I'll see if I can find a Win2016+SQL2016 AMI that doesn't exhibit this problem.
SQL Server PowerShell modules present on the target node
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
The text was updated successfully, but these errors were encountered: