Monday, March 26, 2012

error during quiet installation of June CTP.

I am trying quiet installation of June CTP with the .ini file .

The installation is failing with Last Action :Install Finalize:
The sql server service failed to start.
Error number:29523
--
My ini file settings were as folllows
[snip]
SQLBROWSERACCOUNT= "NT AUTHORITY\LOCAL SERVICE"
SQLBROWSERPASSWORD=

SQLACCOUNT="NT AUTHORITY\LOCAL SERVICE"
SQLPASSWORD=

AGTACCOUNT="NT AUTHORITY\LOCAL SERVICE"
AGTPASSWORD=

ASACCOUNT=
ASPASSWORD=

RSACCOUNT=
RSPASSWORD=
[snip]
-
As mentioned in one of the mails in the group i changed the three accounts to
"NT AUTHORITY\LOCAL SYSTEM".

Now i get new errors as follows
Last Action : Validate_ServiceAccounts
Error String : SQL Server Setup was unable to validate the account or accounts you provided. To continue, verify that the user name, password, and domain name are correct, or provide another user account for SQL Server service login.
The logon account cannot be validated for the service SQL Browser.
Error Number : 29609
--

One observation is that the installation goes fine with <domain\user> and providing the password . But in my case i will have to ship the ini file with the product and dont the the settings on the customer system.
So i cannot use domain user.

Try removing the unused parameters (e.g. SQLBROWSERPASSWORD=, ASACCOUNT=, etc). When using a built-in account the password parameter is not necessary. Also, if you're installing on a localized OS (e.g. German or French) you need to pass the localized version of the built-in account. For example, Local System on a German OS is: NT-AUTORIT?T\SYSTEM

You can find the complete list in the setup help file, setupsql9.chm, under the topic Setting Up Windows Service Accounts.

If you still get errors please post your entire .ini file here.

Dan|||

Hello Dan,

Thanks for your reply.

I have made changes as per your suggestions , but still getting the validation error.

Last Action : Validate_ServiceAccounts
Error String : SQL Server Setup was unable to validate the account or accounts you provided. To continue, verify that the user name, password, and domain name are correct, or provide another user account for SQL Server service login.
The logon account cannot be validated for the service SQL Browser.
Error Number : 29609

Here is the test.ini file.

-
[Options]
;--
; If USERNAME or COMPANYNAME are not specified, the default operating system username and company name values for the server are used.
; Note: If names contain spaces, surround the names with quotes.

USERNAME=test
COMPANYNAME=test
;--
; Usage: PIDKEY=ABCDE12345FGHIJ67890KLMNO (This is not an actual key value.)

; NOTE: For the SQL Server 2005 CTP releases, the following PIDKEY command is not required
; because the PIDKEY parameter for the MSI file is preset. However, the final released version
; of SQL Server 2005 will require the PIDKEY parameter.
; NOTE: PIDKEY is not required for SQL Server Express Edition.
; NOTE: Do not include "-" in the PIDKEY.

;PIDKEY=
;--
; INSTALLSQLDIR specifies the location for the instance specific binary files.
; Default location is: %ProgramFiles%\Microsoft SQL Server\
; To use the default path, do not specify the following parameter.

; NOTE: INSTALLSQLDIR is REQUIRED for clustered installations and must point to a local
; drive for which the drive letter exists on all nodes in the cluster definition.
; NOTE: If there is a space in a specified path, surround the path with quotes
; and end every path with a '\'.

INSTALLSQLDIR="C:\Program Files\Microsoft SQL Server\"
;--
; INSTALLSQLSHAREDDIR specifies a custom location for Integration Services
; Notification Services, Client Components, SQL Server Books Online and Samples.
; To use the default path, do not specify the following parameter. Default path is %ProgramFiles%\Microsoft SQL Server\

; If Tools components are already installed on the computer, this parameter is ignored.
; NOTE: If there is a space in a specified path, surround the path with quotes
; and end every path with a '\'.

; The installation paths will be:
;<InstallDir>\90\DTS
;<InstallDir>\90\Notification
;<InstallDir>\90\Tools

INSTALLSQLSHAREDDIR=
;--
; INSTALLSQLDATADIR specifies the location for the SQL Server data files.
; Default: INSTALLSQLDIR\Data\
; To use the default path, do not specify the following parameter.

; NOTE: INSTALLSQLDATADIR is REQUIRED for clustered installations and must point to a
; shared drive which is a member of the cluster group specified for installation.
; NOTE: If there is a space in a specified path, surround the path with quotes
; and end every path with a '\'.

INSTALLSQLDATADIR=
;--
; INSTALLASDATADIR specifies the location for the Analysis Server Data Files.
; Default: INSTALLSQLDIR\Data\
; If Analysis Server is already installed on the computer, this parameter is ignored.
; To use the default path, do not specify the following parameter.

; NOTE: Do not use with a SQL Server Express installation.
; NOTE: If there is a space in a specified path, surround the path with quotes
; and end every path with a '\'.

INSTALLASDATADIR=
;--
; ADDLOCAL specifies which components to install. If ADDLOCAL is not
; specified, setup will fail.
; See SQL Server Books Online for more information on this topic.

ADDLOCAL=SQL_Engine,SQL_Data_Files,SQL_Replication,SQL_FullText,Client_Components,Connectivity,SQL_Tools90,SQL_Profiler90,SQLXML,SQL_Documentation,SQL_BooksOnline,SQL_SQLServerBooksOnline


INSTANCENAME=MSSQLSERVER
;--
; The UPGRADE property specifies which product to upgrade.
; The allowed values are SQL_Engine, RS_Server and AS_Server.
; If the UPGRADE option is specified, the INSTANCENAME parameter
; is REQUIRED to define which instance to upgrade.

;--
; The services for SQL Server and Analysis Server are set auto start. To use the *ACCOUNT settings
; make sure to specify the DOMAIN, e.g. SQLACCOUNT=DOMAINNAME\ACCOUNT
; NOTE: When installing SQL_Engine 3 accounts are REQUIRED: SQLACCOUNT, AGTACCOUNT and SQLBROWSERACCOUNT.
; SQLACCOUNT Examples:
; SQLACCOUNT=<domain\user>
; SQLACCOUNT="NT AUTHORITY\SYSTEM"
; SQLACCOUNT="NT AUTHORITY\NETWORK SERVICE"
; SQLACCOUNT="NT AUTHORITY\LOCAL SERVICE"

;Note that if SQLBrowser is already installed, SQLBROWSERACCOUNT and SQLBROWSERPASSWORD are ignored.
SQLBROWSERACCOUNT= "NT AUTHORITY\LOCAL SYSTEM"
;SQLBROWSERPASSWORD=

SQLACCOUNT="NT AUTHORITY\LOCAL SYSTEM"
;SQLPASSWORD=

AGTACCOUNT="NT AUTHORITY\LOCAL SYSTEM"
;AGTPASSWORD=

;ASACCOUNT=
;ASPASSWORD=

;RSACCOUNT=
;RSPASSWORD=
;--
; To use the *AUTOSTART features, specify 1 to start automatically or 0 to start manually.
; NOTE: If you decide to start SQL Agent automatically, then SQL is also started automatically.
; If *AUTOSTART is not specified on the command line, startup is set to manual.

SQLBROWSERAUTOSTART=1
SQLAUTOSTART=1
AGTAUTOSTART=1
ASAUTOSTART=0
RSAUTOSTART=0
;--
; To use Mixed mode authentication, use SECURITYMODE=SQL.
; If SECURITYMODE=SQL is not specified, then Windows Authentication only will be used by default.
; If you use SQL Authentication, you are REQUIRED to provide a strong system administrator (SA) password.
; If you use Windows Authentication, the SA account will be disabled.
; To set SA password specify SAPWD.

SECURITYMODE=SQL
SAPWD=Ericsson
;--
; SQLCOLLATION specifies the collation for Database Services.
; ASCOLLATION specifies the collation for Analysis Server.
; See SQL Server Books Online for more information on collation options.

SQLCOLLATION=SQL_Latin1_General_Cp1_CS_AS
ASCOLLATION=SQL_Latin1_General_Cp1_CS_AS
;--

I am not able to figure out what is wrong with this file.
However as specified in the setupsql9.chm file i am successfully installing from
command line using

Start /wait <DVD Drive>\setup.exe /qn INSTANCENAME=<InstanceName> ADDLOCAL=SQL_Engine,SQL_Replication SAPWD=<StrongPassword>

Here nothing is specified about the service accounts . It seems specifying them
i am gettting into trouble.

Regards
Ray

|||

I have tried removing all the accounts related information from the inin file . Then installation fails with


Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_DNASERVER3_SQL.log
Last Action : SetUnattendedSvcAccountProp
Error String : SQL Server Setup has determined that the following account properties are not specified: 'SQLBROWSERACCOUNT, AGTACCOUNT, SQLACCOUNT' . The properties specify the startup account for the services that are installed. To proceed, refer to the template.ini and set the properties to valid account names. If you are specifying a windows user account, you must also specify the password for the account.
Error Number : 28006


Ray

|||

Well the ini file should be like this ..
[snip]
SQLACCOUNT="NT AUTHORITY\SYSTEM"
;SQLPASSWORD=

AGTACCOUNT="NT AUTHORITY\SYSTEM"
;AGTPASSWORD=

SQLBROWSERACCOUNT= "NT AUTHORITY\SYSTEM"
;SQLBROWSERPASSWORD=

;ASACCOUNT=
;ASPASSWORD=

;RSACCOUNT=
;RSPASSWORD=
[snip]

I had put "NT AUTHORITY\LOCAL SYSTEM" instead.. A very painful oversight.

However there is a new problem . On 2003 server installation goes on just fine
but on 2000 server it fails with ->[Microsoft][SQL Native Client]Encryption not supported on the client. Refer to the blah blah blah.

On 2003 i have cryptography sercices running ...
Has neone faced this problem before

|||

Well the ini file should be like this ..
[snip]
SQLACCOUNT="NT AUTHORITY\SYSTEM"
;SQLPASSWORD=

AGTACCOUNT="NT AUTHORITY\SYSTEM"
;AGTPASSWORD=

SQLBROWSERACCOUNT= "NT AUTHORITY\SYSTEM"
;SQLBROWSERPASSWORD=

;ASACCOUNT=
;ASPASSWORD=

;RSACCOUNT=
;RSPASSWORD=
[snip]

I had put "NT AUTHORITY\LOCAL SYSTEM" instead.. A very painful oversight.

However there is a new problem . On 2003 server installation goes on just fine
but on 2000 server it fails with ->[Microsoft][SQL Native Client]Encryption not supported on the client. Refer to the blah blah blah.

On 2003 i have cryptography sercices running ...
Has neone faced this problem before?

Ray

No comments:

Post a Comment