dsccommunity / dsccommunity/SqlServerDsc

SqlSetup: Missing Configuration Feature/Options Telemetry

Open
#1,431 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue 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

We are trying to install anew SQL 2017 SERVER with the SqlSetup dsc resource.

Verbose logs showing the problem
+             SQLTELSVCACCT  = "NT Service\SQLTELEMETRY$SQLTEST05"
+             ~~~~~~~~~~~~~
The member 'SQLTELSVCACCT' is not valid. Valid members are
'Action', 'AgtSvcAccount', 'AgtSvcStartupType', 'ASBackupDir', 'ASCollation', 'ASConfigDir', 'ASDataDir', 'ASLogDir', 'ASServerMode', 'ASSvcAccount', 'AsSvcStartupType', 'ASSysAdminAccounts', 'ASTempDir', 'BrowserSvcStartupType', 'DependsOn', 
'ErrorReporting', 'FailoverClusterGroupName', 'FailoverClusterIPAddress', 'FailoverClusterNetworkName', 'FeatureFlag', 'Features', 'ForceReboot', 'FTSvcAccount', 'InstallSharedDir', 'InstallSharedWOWDir', 'InstallSQLDataDir', 'InstanceDir', 'InstanceID', 
'InstanceName', 'ISSvcAccount', 'IsSvcStartupType', 'ProductKey', 'PsDscRunAsCredential', 'RSSvcAccount', 'RSSVCStartupType', 'SAPwd', 'SecurityMode', 'SetupProcessTimeout', 'SourceCredential', 'SourcePath', 'SQLBackupDir', 'SQLCollation', 'SQLSvcAccount', 
'SqlSvcStartupType', 'SQLSysAdminAccounts', 'SQLTempDBDir', 'SqlTempdbFileCount', 'SqlTempdbFileGrowth', 'SqlTempdbFileSize', 'SQLTempDBLogDir', 'SqlTempdbLogFileGrowth', 'SqlTempdbLogFileSize', 'SQLUserDBDir', 'SQLUserDBLogDir', 'SQMReporting', 
'SuppressReboot', 'UpdateEnabled', 'UpdateSource'.
At C:\Users\operator-attaleb\Documents\PowScripts\06_InstallSqlServer.ps1:82 char:13
+             SQLTELSVCSTARTUPTYPE = "Disabled"
+             ~~~~~~~~~~~~~~~~~~~~
The member 'SQLTELSVCSTARTUPTYPE' is not valid. Valid members are
'Action', 'AgtSvcAccount', 'AgtSvcStartupType', 'ASBackupDir', 'ASCollation', 'ASConfigDir', 'ASDataDir', 'ASLogDir', 'ASServerMode', 'ASSvcAccount', 'AsSvcStartupType', 'ASSysAdminAccounts', 'ASTempDir', 'BrowserSvcStartupType', 'DependsOn', 
'ErrorReporting', 'FailoverClusterGroupName', 'FailoverClusterIPAddress', 'FailoverClusterNetworkName', 'FeatureFlag', 'Features', 'ForceReboot', 'FTSvcAccount', 'InstallSharedDir', 'InstallSharedWOWDir', 'InstallSQLDataDir', 'InstanceDir', 'InstanceID', 
'InstanceName', 'ISSvcAccount', 'IsSvcStartupType', 'ProductKey', 'PsDscRunAsCredential', 'RSSvcAccount', 'RSSVCStartupType', 'SAPwd', 'SecurityMode', 'SetupProcessTimeout', 'SourceCredential', 'SourcePath', 'SQLBackupDir', 'SQLCollation', 'SQLSvcAccount', 
'SqlSvcStartupType', 'SQLSysAdminAccounts', 'SQLTempDBDir', 'SqlTempdbFileCount', 'SqlTempdbFileGrowth', 'SqlTempdbFileSize', 'SQLTempDBLogDir', 'SqlTempdbLogFileGrowth', 'SqlTempdbLogFileSize', 'SQLUserDBDir', 'SQLUserDBLogDir', 'SQMReporting', 
'SuppressReboot', 'UpdateEnabled', 'UpdateSource'.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : InvalidInstanceProperty
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
        SqlSetup InstallSql {
            InstanceName        =  $InstanceName
            InstanceDir         = 'E:\Microsoft SQL Server' 
            INSTALLSHAREDDIR    = 'E:\Program Files\Microsoft SQL Server'
            INSTALLSHAREDWOWDIR = 'E:\Program Files (x86)\Microsoft SQL Server'
            SourcePath          = '\\fs-sunarchive\dbasoftware$\SQL2017\SQL 2017 Standard Edition'
            SourceCredential    = $Cred
            Features            = 'SQLENGINE,REPLICATION,FULLTEXT'
            SQLSysAdminAccounts = 'AVI-DC\GN-BRU-DatabaseAdministrators'
            BROWSERSVCSTARTUPTYPE='Automatic'
            SQLUserDBDir        = $ConfigurationData.NonNodeData.DataDir
            SQLUserDBLogDir     = $ConfigurationData.NonNodeData.LogDir
            SQLTempDBDir        = $ConfigurationData.NonNodeData.TempDataDir
            SQLBackupDir        = $ConfigurationData.NonNodeData.BackupDir
            SqlTempdbFileCount  = 4
            SqlTempdbFileGrowth = 1024
            SqlTempdbFileSize   = 1024
            SQLTempDBLogDir     = $ConfigurationData.NonNodeData.TempLogDir 
            SqlTempdbLogFileGrowth = 1024 
            SqlTempdbLogFileSize   = 1024
            SQLCollation           = 'SQL_Latin1_General_CP1_CI_AS'
            SecurityMode           = 'SQL'
            SAPwd                  = $saCred#(Get-Credential -Credential sa)
            UpdateEnabled          = 'True'
            UpdateSource           = '.\Updates'
            PsDscRunAsCredential   = $Cred#(Get-Credential -Credential avi-dc\operator-attaleb)
            SuppressReboot = $True
            SQLTELSVCACCT  = "NT Service\SQLTELEMETRY$SQLTEST05"
            SQLTELSVCSTARTUPTYPE = "Disabled"
            FTSvcAccount ="NT Service\MSSQLFDLauncher$SQLTEST05"

        }

SQL Server edition and version the target node is running

Microsoft SQL Server 2017 (RTM-CU16) (KB4508218) - 14.0.3223.3 (X64) Jul 12 2019 17:43:08 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Standard 10.0 (Build 14393: ) (Hypervisor)

SQL Server PowerShell modules present on the target node

Name Version Path


SQLPS 1.0 E:\Program Files (x86)\Microsoft SQL Server\130\Tools\PowerShell\Modules\SQLPS\SQLPS.psd1

The operating system the target node is running

OsName : Microsoft Windows Server 2016 Standard
OsOperatingSystemSKU : StandardServerEdition
OsArchitecture : 64-bit
WindowsBuildLabEx : 14393.3143.amd64fre.rs1_release.190725-1725
OsLanguage : en-US
OsMuiLanguages : {en-US}

Version and build of PowerShell the target node is running

Name Value


PSVersion 5.1.14393.3053
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.3053
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Version of the DSC module that was used ('dev' if using current dev branch)

Name Version Path


SqlServerDsc 12.5.0.0 C:\Program Files\WindowsPowerShell\Modules\SqlServerDsc\SqlServerDsc.psd1

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 at the SqlSetup resource definition and its declared configuration options; compare SQLTELSVCACCT and SQLTELSVCSTARTUPTYPE with the supported members shown in the error. Reproduce the supplied SQL Server 2017 configuration with SqlServerDsc 12.5.0.0 and verify the options are accepted without InvalidInstanceProperty.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.