jimm98y / MSSQLEXPRESS-M1-Install

Installers and installation scripts for Microsoft SQL Server Express on ARM64.
MIT License
288 stars 63 forks source link

The service name is invalid. More help is available by typing NET HELPMSG 2185. - Macbook Pro M2 #19

Closed rngallen closed 7 months ago

rngallen commented 1 year ago

` Exception calling "SetAccessRule" with "1" argument(s): "Some or all identity references could not be translated." At C:\Users\ngallen\AppData\Local\Temp\Temp1_MSSQLEXPRESS-M1-Install-main.zip\MSSQLEXPRESS-M1-Install-main\src\install2 022Developer.ps1:98 char:1

Exception calling "SetAccessRule" with "1" argument(s): "Some or all identity references could not be translated." At C:\Users\ngallen\AppData\Local\Temp\Temp1_MSSQLEXPRESS-M1-Install-main.zip\MSSQLEXPRESS-M1-Install-main\src\install2 022Developer.ps1:103 char:1

Copy-Item : Cannot find path 'C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Binn\Templates\master.mdf' because it does not exist. At C:\Users\ngallen\AppData\Local\Temp\Temp1_MSSQLEXPRESS-M1-Install-main.zip\MSSQLEXPRESS-M1-Install-main\src\install2 022Developer.ps1:120 char:1

New-ItemProperty : Cannot find path 'HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQLServer\Parameters' because it does not exist. At C:\Users\ngallen\AppData\Local\Temp\Temp1_MSSQLEXPRESS-M1-Install-main.zip\MSSQLEXPRESS-M1-Install-main\src\install2 022Developer.ps1:126 char:1

New-ItemProperty : Cannot find path 'HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQLServer\Parameters' because it does not exist. At C:\Users\ngallen\AppData\Local\Temp\Temp1_MSSQLEXPRESS-M1-Install-main.zip\MSSQLEXPRESS-M1-Install-main\src\install2 022Developer.ps1:129 char:1

New-ItemProperty : Cannot find path 'HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQLServer\Parameters' because it does not exist. At C:\Users\ngallen\AppData\Local\Temp\Temp1_MSSQLEXPRESS-M1-Install-main.zip\MSSQLEXPRESS-M1-Install-main\src\install2 022Developer.ps1:132 char:1

Corneliuus commented 1 year ago

I have the same problem on M2 MacBook Air

ginolabit commented 1 year ago

same here MacBook Air M2

Any chance to fix this? Thanks

rngallen commented 1 year ago

Make sure your windows user has password

HMside commented 1 year ago

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"

newky2k commented 1 year ago

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

twaibs23 commented 1 year ago

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?

rngallen commented 1 year ago

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

twaibs23 commented 1 year ago

@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.

TroyT868 commented 11 months ago

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....

jimm98y commented 11 months ago

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.

jimm98y commented 7 months ago

Should be fixed using the new installers or scripts.