January 13, 2023 at 10:30 am
Please be gentle.. newbie here !
I'm creating an install program (Using Advanced Installer, but I don't think that's relevant) to install SQL Express. I'm trying to do this as a quiet install with no user intervention.
It's failing with a request for a password on the SQL Server Browser. I cant see how to overcome this with a switch.
This is my current command line :
/IACCEPTSQLSERVERLICENSETERMS
/ACTION=Install
/FEATURES=SQL
/INSTANCENAME=SQLEXPRESS99
/SQLSVCACCOUNT="NT AUTHORITY\Network Service"
/SQLSVCPASSWORD='thepassword'
/TCPENABLED=1
I have to say that I don't understand the "/SQLSVCACCOUNT" switch or why its needed, but that seems to work.
Where it's failing is on the Server Configuration screen with :
SQL Server Browser "NT AUTHORITY\LOCAL SERVICE" , with no password.
Can anyone please point me in the right direction (and hopefully explain so that I can learn more!)
Thank you
January 13, 2023 at 1:52 pm
Just a quick thought, change the SQLSVCACCOUNT to an account you create before the installation.
😎
January 14, 2023 at 6:56 am
Good answer: Eirikur
You may review this Web site. It has all options explained well.
Here is a sample from the web site:
setup.exe /q /ACTION=Install /FEATURES=SQL /INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="<StrongPassword>" /SQLSYSADMINACCOUNTS="<DomainName\UserName>" /AGTSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /SQLSVCINSTANTFILEINIT="True" /IACCEPTSQLSERVERLICENSETERMS
I would practice on a test platform before trying on the live server.
DBASupport
January 16, 2023 at 9:23 am
Thank you both for your input.
I had already researched the Microsoft article, but - and that was the reason for the posting - it expects a level of network knowledge that I don't have.
Although I have 20 years experience of using MS SQL within a programming environment, I have never needed to install a version of SQL and my networking knowledge is very limited.
My proposed installations are aimed entirely at local machines without domains.- probably the most basic of installs possible.
So Eiriker's posting regarding SQLSVCACCOUNT hasn't helped (although I'm obviously grateful for the response), hence in my original post I wrote :
"I have to say that I don't understand the "/SQLSVCACCOUNT" switch or why its needed, but that seems to work."
So.. if I may rephrase my original question..
How can I bypass (or set defaults) into the list of switches to prevent the installation from stopping.
January 16, 2023 at 12:58 pm
IIRC, there is a startup parameter for the Express version to enable networking, otherwise, it will only enable shared memory!
😎
January 16, 2023 at 11:45 pm
"I have to say that I don't understand the "/SQLSVCACCOUNT" switch or why its needed, but that seems to work."
SQL Express does not run as a program like the application for which you are creating an installer. Windows runs SQLExpress in the background as a Service. Windows will start that service when it is needed. The service does not run in your user session - it runs in its own session. The /SQLSVCACCOUNT switch sets the local User Login account that will, in the background, log in and run the SQL Server service. That account must have the "log on as a service" permission added to it in order for it to work.
This account must exist, and you must provide the installer with the necessary credentials for it to log in as that account and do work. Same for the /AGTSVCACCOUNT parameter, which sets the account under which the SQL Server Agent (automation engine of SQL Server) runs.
Eddie Wuerch
MCM: SQL
January 17, 2023 at 2:28 pm
Thank you Eddie - that gives me a direction for further research.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply