FIX: A slipstream installation of SQL Server 2008 fails intermittently

Article translations Article translations
Article ID: 976899 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.
Expand all | Collapse all

SYMPTOMS

You try to perform a slipstream installation of Microsoft SQL Server 2008. However, the installation process fails intermittently. Additionally, the following combination of error messages may be logged in the SQL Server 2008 setup log file and in the SQL Server 2008 error log file.

Error message in the SQL Server 2008 setup log file (Detail.txt)
<Date Time> SQLEngine: --SqlDatabaseServiceConfig: Connecting to SQL....
<Date Time> Slp: Sco: Attempting to connect script
<Date Time> Slp: Connection string: Data Source=\\.\pipe\SQLLocal\SQLEXPRESS;Initial Catalog=master;Integrated
Security=True;Pooling=False;Network Library=dbnmpntw;Application Name=SqlSetup
<Date Time> Slp: Sco: Connection error code from SqlException is : -2
<Date Time> Slp: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Error message in the SQL Server 2008 error log file
<Date Time> spid6s Database 'master' is upgrading script 'msdb_upgrade_discovery.sql' from level 167773760 to level 167774691.
Alternatively, the following combination of error messages may be logged in the SQL Server 2008 setup log file and in the SQL Server 2008 error log file.

Error message in the SQL Server 2008 setup log file (Detail.txt)
<date time>SQLEngine: --SqlServerServiceSCM: Starting SQL via SCM (-mSqlSetup ………)
Error message in the SQL Server 2008 error log file
<date time>spid7s Populate syssubsystem table...
<date time>spid7s Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
<date time>spid7s Using 'xplog70.dll' version '2007.100.1600' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
<date time>spid7s Error: 15151, Severity: 16, State: 1.
<date time>spid7s Cannot find the object 'fulltext_stopwords', because it does not exist or you do not have permission.
<date time>spid7s Error: 15151, Severity: 16, State: 1.
<date time>spid7s Cannot find the object 'fulltext_stoplists', because it does not exist or you do not have permission.
<date time>spid7s Error: 15151, Severity: 16, State: 1.
Note These error messages also exist in the SQL Server error log file when a slipstream installation succeeds. You can safely ignore these reported error messages if the installation succeeds. Cumulative Update 6 (CU6) for SQL Server 2008 Service Pack 1 (SP1) also resolves this issue.

CAUSE

This problem occurs while a slipstream package is being installed. This problem occurs because certain upgrade scripts are executed before the base installation is fully configured.

RESOLUTION

The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
977443 Cumulative update package 6 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

To resolve this problem, follow these steps:
  1. Uninstall the failed slipstream installation.
  2. Run the SQL Server 2008 SP1 CU6 package to install or upgrade the setup support files before you run the slipstream installation package.
  3. Install the slipstream package again. Alternatively, you can build a new slipstream package that includes SQL Server 2008 SP1 CU6 and then install the package.

WORKAROUND

To work around this problem, use one of the following methods.

Method 1

Because this problem does not always occur, you can try to install the slipstream package again.

Method 2

If you use a remote installation, copy the package to the local computer, and then perform the installation process locally.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

The database engine should run upgrade scripts after the database engine runs installation scripts. For example, the installation sequence of a SQL Server 2008 slipstream installation should resemble the installation sequence of a non-slipstream installation of SQL Server 2008 and of SQL Server 2008 SP1.

To check whether your installation package is a slipstream package, check the Summary.txt setup log file for the following package property:
Package properties:
  Slipstream:                    True

REFERENCES

For information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems


For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 976899 - Last Review: January 21, 2010 - Revision: 1.0
APPLIES TO
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 Express
Keywords: 
kbexpertiseadvanced kbsurveynew kbqfe kbfix KB976899

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com