0

Most of the question is in the title. My case concerns MS SQL Server 2017 - Developer Edition.

The error happens during SQL Server 2017 installation process.

While searching for answer online I noticed, the majority of the cases when this error emerges, is while migrating existing db into newer version of MS SQL Server but I get it during MS SQL Server 2017 installation process.

Before posting this question I've read this and this and many sites like these, https://social.msdn.microsoft.com/Forums/sqlserver/en-US/05d4bdb7-9585-4d8c-9f35-2fb9d4355ccc/error-0x84bb0001-installing-sql-server-2017-express-on-windows-10-pro?forum=sqlgetstarted , that always say about "migrating some existing database" or "associated Databases" and setting privileges in SQL Management Studio.

Well I get it during SQL Server 2017 installation.

It's the first time I install any version of SQL Server in my life. I don't even have SQL Management Studio installed yet.

I've read this as well but I'm not mapping no users to any existing DBases. I'm just trying to install this s*** for the first time in my life.

As tutorial I'm using this youtube video.

Well, during installation on the "feature selection" screen I ticked everything - not only "Database Engine Selection".

enter image description here

The whole message of the error I receive is as follows:

Error installing SQL Server Database Engine Services Instance Features
User, group, or role 'ZARZĄDZANIE NT\USŁUGA SIECIOWA' already exists in the current database.
Changed database context to 'DWConfiguration'.
Error code: 0x84BB0001
Visithttps://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x7590AFD6%400x9A41B222&EvtType=0x7590AFD6%400x9A41B222 to get help on troubleshooting.

I'm installing this MS SQL Server on Windows 10 Home Edition x64.

Another thing I've done different than on the youtube tutorial is here, https://youtu.be/sgMCfX2zmOc?t=589 on this very "Database Engine Configuration" screen I left tick at "Windows Authentication Mode" where as in the Tutorial it is changed to the Mixed Mode - but can this setting be the reason of User, group, or role 'ZARZĄDZANIE NT\USŁUGA SIECIOWA' already exists in the current database. Changed database context to 'DWConfiguration'.

In case it's necessary I'm uploading the complete error log to OneDrive and I'm sharing the link with you.

I don't know what else could I write here. Give me a hint in the comments, if the link to the log files works.

UPDATE IS FROM HERE

After few hours of rest I've made another attempt to instal MS SQL SERVER 2017 with Polybase Query Service which in my opinion is a feature responsible for the previous crashes of earlier installation attempts.

This time I made sure to add myself as the sys admin in every stage of the installation.

Moreover, I changed the Authentication Mode to "Mixed Mode" just as it's shown in all tutorials I've been following. The password chosen was a strong one, so no mistake here.

The result is similar as before (failure of all SQL features installation) but the error is different now. It's even less descriptive this time.

TITLE: Microsoft SQL Server 2017 Setup

The following error has occurred:

The handle is invalid

For help, click: https://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.2027.2&EvtType=0x69CEA745%25400xDC80C325

enter image description here

enter image description here

One thing got cleared out 4 sure. The authentication method is irrelevant, because the SQL Server 2017 instance won't install no matter if the authentication Method chosen is "Windows Authentication Mode" or "Mixed Mode".

Here is a screen shot from the very first installation attempt. Just have a look underneath the green progress bar. It's always PolyBase Query Service feature that crashes whole SQL Server 2017 installation and its main component: Database Engine Services.

enter image description here

No Hadoop queries for me :-)

  • Michal - DWConfiguration is a database which gets created when you install PolyBase which is one off the options you selected. Looking through the log you shared, did you add yourself as the sys admin? "ADDCURRENTUSERASSQLADMIN:false". Maybe try re-running the install and add yourself as sys admin. – Adrian Sugden Jun 22 at 14:12
  • ... but sys admin of my Windows operating system?? Or what kind of sys Admin. The installation is lunched from Windows Admin account. – michal roesler Jun 22 at 14:19
  • Do you mean to re-nun installation as a new instance of SQL SERVER or how? Sorry if the questions are rudimentary. I've just never done this before and it seems quite obscure for me. – michal roesler Jun 22 at 14:34
  • When you go through the install Wizard there is an option to add the current users as sys admin within SQL Server (this is separate from sys admin in Windows OS.) Try re-running the installation as a new instance and choose to add the current users (or even your user) as sys admin within SQL Server. – Adrian Sugden Jun 22 at 14:52
  • Yes there is this option as you say but the Installation Wizard will not let me through without adding myself as SQL Server sys admin. The one thing I'm wondering is why in every tutorial the default: Windows Authentication Mode (password blanks greyed out) is changed to Mixed Mode, where you have to specify the password? Well, the bottom line is that Installation Wizard won't let you further without specifying at least one admin. Like here: link – michal roesler Jun 22 at 15:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.