-
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: SSRS needs restart after reserving URLs #1331
Comments
I like the suggested solution. |
@johlju Do you think it's safe to assume once we're in |
You could call the Set-function with Invoke-DscResource so we should not assume it should always restart. I like the idea of setting a restart variable, if that is true then we restart. That why we could move the restart vi already have, so it uses the same variable. 🤔 So maybe the What do you think? |
I agree. If other resources use |
- Changes to SqlRS - Reporting Services are restarted after changing settings, unless `$SuppressRestart` parameter is set (issue #1331). `$SuppressRestart` will also prevent Reporting Services restart after initialization.
Details of the scenario you tried and the problem that is occurring
When changing (adding, removing) reserved URLs on SSRS, accessing
http://server/Reports
(the web application interface) will return a 503 until theSQL Server Reporting Services
Windows service is restarted.Suggested solution to the issue
Currently, SqlRS will restart the
SQL Server Reporting Services
Windows service only after initialising the configuration for the first time.I suggest we restart SSRS whenever
Set-TargetResource
makes a change.The DSC configuration that is used to reproduce the issue (as detailed as possible)
SQL Server edition and version the target node is running
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: