dsccommunity / dsccommunity/SqlServerDsc

SqlSetup: RS feature can't be installed using SqlSetup for SQL Server 2017

Open
#1,109 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
PowerShell
Stars
385
Forks
224
PR merge metrics
No merged PRs in 30d

Description

Details of the scenario you tried and the problem that is occurring

In SQL Server 2017 the reporting services can no longer be installed using the feature 'RS'. It is now a separate download, see What's new in SQL Server 2017

The resource will try to install RS and setup.exe will fail, resulting in an error that says Test-TargetResource returned false after calling Set-TargetResource.. I suggest we add a warning message if major version 14 is detected and RS feature is present.

The DSC configuration that is using the resource (as detailed as possible)
SqlSetup 'InstallReportingServicesInstance'
{
    InstanceName          = $Node.InstanceName
    Features              = 'RS'
    SourcePath            = 'D:\'
    BrowserSvcStartupType = 'Automatic'
    RSSvcAccount          = $ReportingServicesServiceCredential
    InstallSharedDir      = $Node.InstallSharedDir
    InstallSharedWOWDir   = $Node.InstallSharedWOWDir
    UpdateEnabled         = $Node.UpdateEnabled
    SuppressReboot        = $Node.SuppressReboot
    ForceReboot           = $Node.ForceReboot

    PsDscRunAsCredential  = $SqlInstallCredential
}
Version of the operating system and PowerShell the target node is running

Windows Server 2016

SQL Server edition and version the target node is running

SQL Server 2017

What SQL Server PowerShell modules, and which version, are present on the target node.

n/a

Version of the DSC module you're using, or write 'dev' if you're using current dev branch

Dev

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the SqlSetup resource and the supplied configuration, using SQL Server 2017 on Windows Server 2016 to reproduce the failed RS installation. Check how the resource handles the RS feature and SQL Server major version 14; done means the unsupported combination produces a warning instead of attempting the failing installation.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
databases, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.