Select the product you need help with

Setup stops responding when you try to upgrade to SQL Server 2012

Article ID: 2712929 - View products that this article applies to.

Symptoms

Consider the following scenario. A computer is running Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2, or Microsoft SQL Server 2012 Release Candidate 0 (RC0). You try to upgrade to Microsoft SQL Server 2012.

In this scenario, the Setup program seems to stop responding during the SQLEngineConfigAction_upgrade step.

When this issue occurs, setup information that resembles the following is logged at the end of the Detail.txt file:

(01) 2012-04-01 12:12:12 SQLEngine: : Checking Engine checkpoint 'SetSecurityDataDir_1'
(01) 2012-04-01 12:12:12 SQLEngine: --SqlEngineSetupPrivate: Setting Security Descriptor D:(A;OICI;FA;;;S-1-5-80-1-2-3-4-5...) on Directory H:\MSSQL\DATA_FS
(01) 2012-04-01 12:12:12 Slp: Sco: Attempting to set security descriptor for directory H:\MSSQL\DATA_FS, security descriptor D:(A;OICI;FA;;;S-1-5-80-1-2-3-4-5...)
(01) 2012-04-01 12:12:12 Slp: Sco: Attempting to normalize security descriptor D:(A;OICI;FA;;;S-1-5-80-1-2-3-4-5...)
(01) 2012-04-01 12:12:12 Slp: Sco: Attempting to replace account with sid in security descriptor D:(A;OICI;FA;;;S-1-5-80-1-2-3-4-5...)
(01) 2012-04-01 12:12:12 Slp: ReplaceAccountWithSidInSddl -- SDDL to be processed: D:(A;OICI;FA;;;S-1-5-80-1-2-3-4-5...)
(01) 2012-04-01 12:12:12 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned: D:(A;OICI;FA;;;S-1-5-80-1-2-3-4-5...)
(01) 2012-04-01 12:12:12 Slp: Sco: Directory H:\MSSQL\DATA_FS\ is a volume mount point. VolumeName is \\?\Volume{abc-123-456-789-123abc}\

Note The Detail.txt file is located in the following folder:

\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\timestamp

Back to the top | Give Feedback

Cause

This issue can occur if there are many subfolders and files that contain SQL Server data.

Note This issue is more likely to occur if the database is integrated into the NTFS file system by using the FILESTREAM feature or the FILETABLE feature.

Back to the top | Give Feedback

Resolution

No action is required to resolve this issue. To complete the upgrade, let the SQL Server 2012 Setup program finish.

Back to the top | Give Feedback

More information

The issue that is described in the "Symptoms" section occurs because the SQL Server 2012 Setup program calls the SetSecurityInfo Windows API. The SetSecurityInfo API applies a discretionary access control list (DACL) to subfolders and files that contain SQL Server data. This process can take a long time to finish.

Back to the top | Give Feedback