Article ID: 2712929 - View products that this article applies to.
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'
Note The Detail.txt file is located in the following folder:
\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\timestamp
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.
No action is required to resolve this issue. To complete the upgrade, let the SQL Server 2012 Setup program finish.
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.
For more information about the SetSecurityInfo Windows API, visit the following MSDN website:
Article ID: 2712929 - Last Review: November 19, 2012 - Revision: 3.0