Select the product you need help with
FIX: Component installation process freezes after you install SQL Server 2012 SP1Article ID: 2800050 - View products that this article applies to. On This PageSymptoms
Note Specifically, the Windows Installer process (Msiexec.exe) freezes and consumes excessive CPU resources after you install SQL Server 2012 SP1. CauseThis issue occurs because the microsoft.analysisservices.wizard.v1.dll assemblies in SQL Server 2012 and in SQL Server 2012 SP1 target different versions of the Microsoft .NET Framework. Therefore, the installation of SQL Server 2012 SP1 leaves Windows Installer in an inconsistent state. Windows Installer tries to repair the installation and then blocks the next installation. ResolutionCumulative update informationCumulative Update 2 for SQL Server 2012 SP1The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:2790947 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 2012 SP1 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:
(http://support.microsoft.com/kb/2790947/
)
Cumulative update package 2 for SQL Server 2012
Service Pack 12772858
(http://support.microsoft.com/kb/2772858/
)
The SQL
Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was
releasedHotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, you must have SQL Server 2012 SP1 installed on the computer.Restart requirementYou do not have to restart the computer after you apply this hotfix.File informationThe global hotfix version of this has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Collapse this image  Collapse this table
Collapse this table
Collapse this image  WorkaroundTo work around this issue, restart the computer after you install SQL Server 2012 SP1. StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Properties | Article Translations
 |
Back to the top
