locked
System account installation of SQL Server 2016 fails if PolyBase Query feature is enabled. RRS feed

  • Question

  • Hello folks,

    Requirement : Install SQL server enterprise edition 2016 in System context

    Issue : When tried installing SQl Server Enterprise Edition 2016 in System context with configuration File where SQLSYSADMINACCOUNTS=NT AUTHORITY\SYSTEM, it fails saying that "Cannot find the principal '<<%USERDOMAIN%>>\SYSTEM', because it does not exist or you do not have permission.  Changed database context to 'DWQueue' " with exit code = ( -2068119551 ). This issue appears only when "PolyBase Query Service for External Data" Feature tries to get installed in System Context.

    In Detail.txt it shows below error:

    (01) 2018-01-17 11:43:19 SQLPolyBase: --PolybaseDatabaseConfig: Replacing $(Admin) with <<%USERDOMAIN%>>\SYSTEM...

    ALTER AUTHORIZATION ON DATABASE::DWQueue TO [<<%USERDOMAIN%>>\SYSTEM]

    (01) 2018-01-17 11:43:19 SQLPolyBase: --SqlScriptExecutionWrapper: Connection to SQL Server Engine succeeded, but script statement execution failed. Exception: 'Microsoft.SqlServer.Configuration.Sco.ScoException: Cannot find the principal '<<%USERDOMAIN%>>\SYSTEM', because it does not exist or you do not have permission.

    The problem is it takes admin account as <<%USERDOMAIN%>>\SYSTEM instead of NT AUTHORITY\SYSTEM.

    Please Help me out !!!!

    Regards,

    Hema


    Thursday, January 18, 2018 10:29 AM

Answers

  • Hi HemanandhiniPandian,

    Installing "PolyBase Query Service for External Data" Feature requires using this SQL Server as a part of PolyBase scale-out group. In a PolyBase scale-out group, PolyBase engine and PolyBase data movement service on all nodes must run under the same domain account.

    As a result, it will take admin account as <<%USERDOMAIN%>>\SYSTEM instead of NT AUTHORITY\SYSTEM as you seen. Please use a domain account for the PolyBase engine.

    Best Regards,

    Teige


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, January 19, 2018 5:57 AM