The service name is invalid. More help is available by typing NET HELPMSG 2185. - Macbook Pro M2 about mssqlexpress-m1-install HOT 11 CLOSED

I have the same problem on M2 MacBook Air

from mssqlexpress-m1-install.

same here
MacBook Air M2

Any chance to fix this?
Thanks

from mssqlexpress-m1-install.

Make sure your windows user has password

from mssqlexpress-m1-install.

As a german user it helped me to change the following line from the .ps1.

$sqlInstallArgs = "/qs /ACTION=Install /FEATURES=SQLEngine /INSTANCENAME=$instanceName /ENU /IACCEPTSQLSERVERLICENSETERMS /UPDATEENABLED=false /USEMICROSOFTUPDATE=false"
to
$sqlInstallArgs = "/qs /ACTION=Install /FEATURES=SQLEngine /INSTANCENAME=$instanceName /IACCEPTSQLSERVERLICENSETERMS /UPDATEENABLED=false /USEMICROSOFTUPDATE=false"

from mssqlexpress-m1-install.

Please note after some digging around and running the SETUP.exe directly, path length is a factor in the success. SQL Setup will fail silently if the path is long than 260 characters

from mssqlexpress-m1-install.

I have been trying for the last day to get SQL 2019 running on Windows 11 (Parallels) on my M2 Max. Getting the same error that @rngallen posted above. Any ideas?

from mssqlexpress-m1-install.

Make sure your windows user has password as by default it install MSSQL with windows authentication. @twaibs23

from mssqlexpress-m1-install.

@rngallen Script seemed to complete this time, however now I'm getting the same Windows Update error message that I've gotten all along when trying to install 2019 or 2022 SQL on my machine. Anyone able to give me a hand and take a look? Trying to get 2019 installed to work with Webgility.

from mssqlexpress-m1-install.

Just a few notes. I got it working but didn't use a Microsoft account when setting up Windows 11. I created a standard local account setup as a member of the local administrators group with a password assigned to it and got all versions of the script to install their respective SQL editions without any issues under that usage scenario. If you're using a Microsoft account to sign in I'd ditch that and go with a local admin account with a password instead to get things going. For security purposes you shouldn't use an account with local admin privileges as your daily driver account unless you are security conscious and know what you're doing. Use a non-admin account for that but don't use a Microsoft account with Windows 10 or 11 either way if you want to avoid a bunch of headaches....

from mssqlexpress-m1-install.

Judging by the error it looks like an issue with getting the user - what is the output of "whoami" in PowerShell on the affected machine? Are you using Active Directory account? The scripts were tested with a personal Microsoft account. Also as @rngallen mentioned, the user account under which you are installing should probably have a password set.

from mssqlexpress-m1-install.