none
Unable to connect to Azure SQL server when installing HPC from domain joined machines

    Question

  • I am trying to use Azure SQL server as the SQL server database for the HPC 2016 update 1, but
     am getting the error when trying to connect to the DB, but  issue is not happeningwith the non-domain joined machines.
    
    Let me know if you have any suggestion.

    Getting the following error:

    To use the remote instance for the HPC databases, you must assign the db_datareader, db_datawriter and db_ddladmin database roles to the current user, and grant to that user the ALTER, CONNECT, EXECUTE and VIEW DEFINITION database permissions




    Monday, February 26, 2018 2:04 PM

Answers

  • As per MS team,

    What they explain to me is that the HPC 2012 had a requirement that the head node must be installed as a domain user, and it is required that the domain user and the head node machine account have the DB permissions even when the database username/password is given, because some operations on DB are done as the setup domain user/machine account, but not as the DB username.

    In HPC Pack 2016, we removed the limitation that head node must be domain joined, but some legacy DB permission checking is not removed <g class="gr_ gr_35 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar multiReplace" data-gr-id="35" id="35">for</g> the scenario head node is domain joined.

     

    If the head node is domain joined and the setup user is a domain user, the setup wizard with check the DB permissions for the current domain user, we can try to install the head node as a local administrator which is not a domain user.

    As the Azure SQL database is not having the AD permission it is not able to authenticate the DB.

    Thursday, March 15, 2018 1:12 PM

All replies

  • Seems you didn't configure the database permissions for the user properly. In the setup folder, there is a sql script file AddDbUserForHpcSetupUser.sql where you can find the minimum DB permissions required, or you can just set the user as DB_Owner.

    Friday, March 02, 2018 6:21 AM
  • As per MS team,

    What they explain to me is that the HPC 2012 had a requirement that the head node must be installed as a domain user, and it is required that the domain user and the head node machine account have the DB permissions even when the database username/password is given, because some operations on DB are done as the setup domain user/machine account, but not as the DB username.

    In HPC Pack 2016, we removed the limitation that head node must be domain joined, but some legacy DB permission checking is not removed <g class="gr_ gr_35 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar multiReplace" data-gr-id="35" id="35">for</g> the scenario head node is domain joined.

     

    If the head node is domain joined and the setup user is a domain user, the setup wizard with check the DB permissions for the current domain user, we can try to install the head node as a local administrator which is not a domain user.

    As the Azure SQL database is not having the AD permission it is not able to authenticate the DB.

    Thursday, March 15, 2018 1:12 PM