3

It's been a whole saturday since I'm trying to install SQL Server 2016 without success.

My procedure has been the following (I always start by uninstalling all sql server instances before trying again):

  1. Download en_sql_server_2016_developer_x64_dvd_8777069.iso
  2. Run setup (it doesn't matter if I run it in administrator mode or not)
  3. On "SQL Server Installation Center" I click over "New SQL Server stand-alone installation"
  4. I select the free "Developer" edition
  5. I select all features ("select all")
  6. On "specify the name and instance ID" I select "Named Instance" and I name it "Test"
  7. I select "Use this SQL Server as standalone PolyBase-enabled instance"
  8. I select "Windows authentication mode"
  9. On "Specify SQL Server administrators" I simply press the button "Add Current User" which is automatically identified as "GFI\luis.gouveia"
  10. The install starts and apparently everything runs smoothly. However, at the end of the install, I get the following error: "SQL Server 2016: The specified user does not exist"

Important: I can achieve a successful install if I change my procedure on point 9: If I click 'Add' instead of clicking 'Add Current User', and then I check the name 'luis.gouveia' on the only location available (which is 'GFIPT0032' instead of 'GFI') I can do it. I don't understand exactly why, but I have 2 domain names installed (GFI and GFIPT0032). "GFIPT0032" is also my machine name:

enter image description here

This wouldn't bother me If I could set as SQL administrator the user defined in GFIPT0032, and not the one in GFI. Unfortunately, it seems SQL Server 2016 is unable to see the location 'GFI'. It only sees GFIPT0032. When I click Add, above the field 'check names', I would like to change the location from 'GFIPT0032' to 'GFI', but that is not possible.

Luis Gouveia
  • 211
  • 1
  • 3
  • 8
  • 2
    Luis - Without over thinking too much... Could you try mixed mode install and specify a password for SA and then once it installs just connect as SA. Afterwards, you can work on getting the AD or local security groups, user accounts, etc. setup? If you don't already have a default instance, you should consider installing as a default instance rather than a named instance if that's applicable in your case... so just those two ideas for you for potential options to assist... let me know how it goes. – Pimp Juice IT Oct 22 '16 at 22:21
  • Thank you a lot @ITSolutions, I just needed an update pack... ridiculous. Check my answer if you have the time. – Luis Gouveia Oct 23 '16 at 08:44

1 Answers1

1

I know it is beyond belief, but I've lost 14 hours of my life to find out that I just needed to install the "Cumulative Update Package 2 for SQL Server 2016" released on the 21/9/2016.

Here's the link: https://www.microsoft.com/en-us/download/details.aspx?id=53338

I hope that this might help somebody. I should say that above all I hope that someone from Microsoft realises how serious this is: Still today (23/10/2016) the "SQL Server 2016 Developer version" available to download at Microsoft's site, dates from 1/6/2016. Yes, this means they didn't change it after the update!!

Luis Gouveia
  • 211
  • 1
  • 3
  • 8