Wednesday, April 25, 2012 10:30 AM
We have a system in which there a SQL Server Express 2008 default instance called "SQLExpress".
Normally the SQL Server Express default instance is called "MSSQLSERVER".
Now we have an application installer with a SQL Server Express 2008 prerequisite.
This prerequisite tries to install a named instance called "SQLExpress".
This fails with the message:
Process exited with code -2068578304
The commandline arguments used by the installer are:
/q /hideconsole /action=Install /features=SQL /instancename=SQLEXPRESS /enableranu=1 /sqlsvcaccount="NT Authority\Network Service" /AddCurrentUserAsSqlAdmin /skiprules=RebootRequiredCheck
How can we handle this case?
- Edited by Ranjith Venkatesh - Private Wednesday, April 25, 2012 11:05 AM
Wednesday, April 25, 2012 12:27 PM
Wednesday, April 25, 2012 12:45 PM
Thanks for the lead. We are now looking into these logs to take it from here.
Will post back with more information.
Thursday, April 26, 2012 12:24 AMModerator
just a note... a "default instance" is always named "MSSQLSERVER"... but by default, SQLExpress installs as a named instance, named "SQLExpress"... so, if you already have a SQLExpress named instance (named "SQLExpress"), trying to install another one with the very same name always fails... is this the case?
http://www.asql.biz - DbaMgr2k - DbaMgr and further SQL Tools http://www.hotelsole.com/
Thursday, April 26, 2012 2:35 AMModerator
An instance is either the default instance or a named instance. The default instance name is MSSQLSERVER; SQLExpress for SQL Server Express. So if you need to install a named instance, you could not use “SQLExpress”. You need to change to another name.
If you specify MSSQLServer for the instance name, a default instance will be created. For SQL Server Express, if you specify SQLExpress for the instance name, a default instance will be created.
Reference: Instance Configure: http://msdn.microsoft.com/en-us/library/ms143531(v=sql.100).aspx.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.
Thursday, April 26, 2012 1:01 PMMy case was that the developer had installed a default instance with and instance id "SQLExpress" which caused the installer with SQL Server Express 2008 prerequisite to fail as it was trying to install a named instance with the instance id "SQLExpress"
Thursday, April 26, 2012 1:02 PMThanks for the link to Instance Configure. Helps understand the concepts around Instances - default and named better.
Thursday, April 26, 2012 1:05 PM
Thanks to Pradeep I was able to analyse the logs and find the issue.
The log entry said this:
The Instance ID 'SQLEXPRESS' is already in use by SQL Server instance 'MSSQLSERVER'. To continue, specify a unique Instance ID
It is a pity that the Installer breaks with no user friendly message and one has to dig deep in the log files to get this information.
Friday, May 04, 2012 12:10 PM
hi you can also ask the same problem on the below forum, it may help you.
Friday, May 04, 2012 12:14 PMModeratorwhat is the reason for using /SkipRules
SQL Server Setup Team
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you.
This can be beneficial to other community members reading the thread.