Error: Detection of product ‘{}’, feature ‘SQL_Tools_Ans’ failed during request for component


The problem started when new instance of SQL Server 2012 is installed to the existing data platform stack that supports multiple application databases having SQL Server 2008 and 2008 R2 version on existing Windows Server 2008 R2.

 

During this error there is an unusual behavior of  HIGH CPU spikes on the server causing issues to the other instances on this physical server. However this behavior was not observed on the similar server where we had multiple versions of SQL Server versions as Virtual Machines (mixture of VMWare & Hyper-V)!

The initial tests were conducted to see what kind of queries that are running on all of those SQL instances for this HIGH CPU spikes, noting was obvious to pin point the root cause.

Further down the line the Systems Center monitoring alerted about a warning from Event log. The message was as follows:

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}’

It caught my eye about the feature ‘SQL_Tools‘ which is pointing out about SQL Server tools on this server. Having a search on net about these messages revealed nothing to resolve.

Back to old drawing board and to see why & when this message is generated in the Application log. It happens whenever the newly installed SQL Server 2012 instance.

BINGO! We got the root cause for this issue and high CPU usage, also the KBA2793634 highlights the symptoms and hotfix to download that will cure the problem.

Cause:

After you install SQL Server 2012 SP1 on a computer, the Windows Installer (Msiexec.exe) process is repeatedly started to repair certain assemblies.

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.

 

This is where we get to see the advantage of Cumulative Update package releases. The KBA clearly highlights the resolution as follows:

Scenario 1: You did not install any hotfixes or Cumulative updates after installing Service Pack 1 for SQL Server 2012.

In this scenario, we recommend that you install the Non Security Update for SQL Server 2012 SP1.

The following files are available for download from the Microsoft Download Center:

 
 

Download

Download the package now.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 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:

2790947 Cumulative update package 2 for SQL Server 2012 Service Pack 1

FYI