After you install SQL Server 2012 SP1 on a computer, the Windows Installer (Msiexec.exe) process is repeatedly started to repair certain assemblies. Additionally, the following events are logged in the Application log:
EventId: 1004 Source: MsiInstaller Description: Detection of product '{A7037EB2-F953-4B12-B843-195F4D988DA1}', feature 'SQL_Tools_Ans', Component '{0CECE655-2A0F-4593-AF4B-EFC31D622982}' failed. The resource''does not exist.
EventId: 1001 Source: MsiInstaller Description: Detection of product '{A7037EB2-F953-4B12-B843-195F4D988DA1}', feature 'SQL_Tools_Ans’ failed during request for component '{6E985C15-8B6D-413D-B456-4F624D9C11C2}'
When this issue occurs, you experience high CPU usage.
Cause
This issue occurs because the SQL Server 2012 components reference mismatched assemblies. This behavior causes native image generation to fail repeatedly on certain assemblies. Therefore, a repair operation is initiated on the installer package.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Scenario 2: You installed either a hotfix or Cumulative Update 1 after installing Service Pack 1 for SQL Server 2012.
In this scenario, we recommend that you install Cumulative Update 2 for SQL Server 2012 SP1.
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:
Cumulative update package 2 for SQL Server 2012 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 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:
The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Information about the Non Security Update for SQL Server 2012 SP1
Prerequisites
To apply this update, you must have SQL Server 2012 SP1 installed.
Restart requirement
You do not have to restart the computer after you apply this update.
File information
Collapse this imageExpand this image
The global version of this update 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.
For all supported x86-based versions of SQL Server 2012 Database Services Core Instance
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Sql_engine_core_inst_keyfile.dll
2011.110.3128.0
24,064
29-Dec-2012
05:21
Sqlaccess.dll
2011.110.3128.0
442,344
29-Dec-2012
05:24
Sqlagent.exe
2011.110.3128.0
448,488
29-Dec-2012
05:10
Sqldk.dll
2011.110.3128.0
1,649,640
29-Dec-2012
05:23
Sqllang.dll
2011.110.3128.0
26,404,352
29-Dec-2012
05:23
Sqlmin.dll
2011.110.3128.0
26,692,584
29-Dec-2012
05:23
Sqlos.dll
2011.110.3128.0
25,088
29-Dec-2012
05:22
Sqlservr.exe
2011.110.3128.0
160,768
29-Dec-2012
05:10
Sqltses.dll
2011.110.3128.0
8,162,792
29-Dec-2012
05:23
For all supported x86-based versions of SQL Server 2012 Database Services Common Core
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Microsoft.datawarehouse.interfaces.dll
11.0.3128.0
37,888
29-Dec-2012
05:18
Sql_common_core_keyfile.dll
2011.110.3128.0
24,064
29-Dec-2012
05:21
For all supported x86-based versions of SQL Server 2012 Business Intelligence Development Studio
To work around this issue, manually pause the NGEN service manually if you have installed SQL Server 2012 SP1. However, we do not recommend that you apply this workaround because the NGEN service resumes as soon as you restart SQL Server or install other SQL Server updates.