Quantcast
Channel: SQL Server Setup & Upgrade forum
Viewing all articles
Browse latest Browse all 5760

SQL Server 2008 R2 Express with SP2: 'SQLEXPRESS'-instance installation fails while any other instance name installation succeeds.

$
0
0

We supply our software package that also includes the unattended installation (with /QS and so on) of SQL Server R2 Express (with SP2).
The setup works good in about 99.9% cases, but one customer complained that after the "successful SQL Sever installation (at least, it looked so!) he could not open the supplied database getting some strange error messages...

After some months of trial-n-error attempts we are now able to reproduce the problems this custumer had. But we cannot find the reason of the problem.

So the test computer is a virtual machine with Windows 7 + sp1 32-bit.
Among the programs/tools installed on this machine there were (in the following order):
SQL Server 2008 Express - the default SQLEXPRESS instance
SSMS
VS 2010 Pro (German)
SQL Server 2008 Express R2 (with SP 1 or SP2 - ?) - the default SQLEXPRESS instance
Then some of them were uninstalled in the following order:
SQL Server 2008 Express
SSMS
SQL Server 2008 Express R2 

Now we tried to install (in normal mode with UI) the SQL Server 2008 Express R2 with SP2.
When we chose the default SQLEXPRESS instance - it failed with the following info:

Configuration status: Failed: see details below
Configuration error code: 0x7FCCE689
Configuration error description: External component has thrown an exception.

and the Detail.txt file contained the following:

2015-01-20 10:44:09 Slp: External component has thrown an exception.
2015-01-20 10:44:09 Slp: The configuration failure category of current exception is	ConfigurationValidationFailure
2015-01-20 10:44:09 Slp: Configuration action failed for feature	SQL_Engine_Core_Inst during timing Validation and scenario Validation.
2015-01-20 10:44:09 Slp: System.Runtime.InteropServices.SEHException	(0x80004005): External component has thrown an exception.
2015-01-20 10:44:09 Slp: at SSisDefaultInstance(UInt16* , Int32* )
2015-01-20 10:44:09 Slp: at	Microsoft.SqlServer.Configuration.SniServer.NLRegSWrapper.NLregSNativeMethod	Wrapper.SSIsDefaultInstanceName(String sInstanceName, Boolean&	pfIsDefaultInstance)
....
2015-01-20 10:44:09 Slp: Exception:	System.Runtime.InteropServices.SEHException.
2015-01-20 10:44:09 Slp: Source:	Microsoft.SqlServer.Configuration.SniServerConfigExt.
2015-01-20 10:44:09 Slp: Message: External component has thrown an exception..
2015-01-20 10:44:09 Slp: Watson Bucket 1	Original Parameter Values
2015-01-20 10:44:09 Slp: Parameter 0 : SQL Server 2008 R2@RTM@
2015-01-20 10:44:09 Slp: Parameter 1 : SSisDefaultInstance
2015-01-20 10:44:09 Slp: Parameter 2 : SSisDefaultInstance
2015-01-20 10:44:09 Slp: Parameter 3 :	System.Runtime.InteropServices.SEHException@-2147467259
2015-01-20 10:44:09 Slp: Parameter 4 :	System.Runtime.InteropServices.SEHException@-2147467259
2015-01-20 10:44:09 Slp: Parameter 5 : SniServerConfigAction_Install_atValidation
2015-01-20 10:44:09 Slp: Parameter 6 :	INSTALL@VALIDATION@SQL_ENGINE_CORE_INST

When we chose some other instance name then the installation has completed successfully.

So the questions are:

  1. What could be the reason of the problem (and only for SQLEXPRESS instance that was earlier installed and then uninstalled)? I will provide the complete Detail.txt file if needed. 
  2. How could we check (if we could) the conditions so some name would be allowed as an instance name for SQL Server installer to success?

With the best regards,

Victor


Victor Nijegorodov


Viewing all articles
Browse latest Browse all 5760

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>