Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-6356

sqlserver : Fails to install sql server when SQLSYSADMINACCOUNTS contains multiple accounts or whitespace

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: sqlserver
    • Labels:
      None
    • Template:
      MODULES Bug Template
    • Team:
      Windows
    • Sprint:
      Windows Kanban
    • Method Found:
      Customer Feedback
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      Module Version: 2.1.0
      Puppet Version: 5.3.3
      OS Name/Version:
      Server 2012 R2 and Server 2016

      Describe your issue in as much detail as possible...
      When passing in accounts for the SQLSYSADMINACCOUNTS parameter the only setting that appears to work is Administrators and local user accounts with no spaces in their name. In particular:

      • SQL 2016 on Win2016 with 1 local group specified for SQLSYSADMINACCOUNTS
      • SQL 2016 on Win2016 with 1 domain group specified for SQLSYSADMINACCOUNTS
      • SQL 2016 on Win2016 with 3 groups (1 local, 1 domain and BUILTIN\Administrators) specified for SQLSYSADMINACCOUNTS

      This was also repro'd on SQL 2012 and SQL 2014

      Desired Behavior:
      Should add accounts as admins during installation

      Actual Behavior:
      Errors that account "xxxx\xxxx" is not able to be found

      Note - This is due to the quotes being taken literally instead of being used to surround text with whitespace.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              glenn.sarti Glenn Sarti
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support