msiexec.exe processes keep running after installation of SQL Server 2012 SP1 by Bart Kuppens

Hi Microsoft. When you say the issue has been "fixed", do you mean:

    A. The bug has been patched
    B. Microsoft has released a tool to remediate the damage caused by the bug.
    C. All of the above.

Thanks.

Hi Bart -- As this issue has been fixed in SQL Server 2012 SP1 CU2, I am closing this issue.

Thanks to all of you for showing how much this issue means to you!

Luckily, SQL Server 2012 SP1 CU2 is now available, which contains the fix from KB2793634.
http://support.microsoft.com/kb/2790947

@MS: Is the fix included in the current downloadable SP1?

I did not experience the registry bloat problem, but I did experience the recurring Application Event Log messages every 10 minutes saying that components were being re-compiled and re-installed.

KB2800050 helped fix the problem for me.    After applying KB2800050 my servers are at version 11.0.3335.0 and I am no longer experiencing the recurring application event log messages.

@DizzyBadger. You put me on the right track, and I've solved the problem. Thanks!

Here are the steps.
-2) Read and understand http://support.microsoft.com/kb/2498915
-1) Make sure you've cleaned out the junk keys from the registry.
0) Boot into Windows PE
1) copy the huge SOFTWARE hive file to a backup file for safekeeping
2) load the bloated software hive in regedit
3) export the Microsoft/Windows and the Microsoft/.net framework/2.0xx/Ngen/Roots keys into new files as hive files.
4) Delete the two keys exported above. The point here is to reduce the size of the remaining keys in the software hive. Exporting these two keys worked for me, you may have to experiment.
5) export the bloated software hive as a hive file. If you've deleted enough in steps 3 and 4, this will work.
6) Exit regedit, load regedit, and unload the bloated hive.
7) Load the newly saved hive that you saved in step 5.
8) Create the Microsoft/Windows key and import the exported Windows hive file into it.
9) Create the Microsoft/.net framework/..../Roots key and import the exported Roots hive into it.
10) Exit regedit, load regedit, and unload the hive we are working with.
11) Copy the newly fixed up hive overtop of SOFTWARE
12) Reboot into Windows
13) run sfc /scannow

You are done. Hurray!

@nibbler2: http://support.microsoft.com/kb/2498915 only Works if the actual data contained in the registry hive file is less than about 100MB. I am not sure exactly what the limit is, but export from regedit to a hive file will fail on large hives, and the only ones I have been able to successfully export have been smaller than 100MB.

If the HKLM\software registry hive is bloated up to 2GB, chances are that something else on the server will get messed up as well and you should reinstall. If the hive isn't that far gone, say 1800MB, you can apply the patch and live happily ever after for a while. I am currently testing whether or not the patch will remove the extra registry keys. Be aware though that even if that works, the software hive file itself won't get any smaller.

I am experiencing this issue as well. It seems to be happening wherever Analysis Services is installed. I have tried to install the fix mentioned below but it fails. If the Registry is bloated is there any way to go forward without starting all over (new OS, New SQL 2012, New SharePoint)

Hi!
I have a similar problem, the production SQL 2012 cluster is not stable. The reason, bloated registry file - Software. Has anyone been able to optimize and compress? Applied the patch, which is laid out below - the file remained abnormally high (Thanks for the help!

In case any one was able to recreate this on a fresh setup, please let me know the steps you followed.

They have but they also posted a comment below

Please Note: The patch should only be applied if you're on SQL 2102 SP1. If you have already applied a Cumulative update or an "On Demand" fix on top of SP1, please wait for the associated hotfix update to be made available.

I am trying to find out when the patches are coming if you have installed CU1 on top of SP1. Also it does explain exactly if it will fix the registry bloat.

Microsoft has posted a description of the bug plus a link to the patch (KB2793634) here: https://support.microsoft.com/kb/2793634.

I found many many more of the root subkeys had the thousands of duplicate entries not just the dst ones. When is MS going to be releasing a patch for cu1 and cu2 on SP1?? will the patch just stop the issue or will it fix the now bloated registry as well or will they provide details of a fix. I might have to use a premium support call to find out.

Ooops. URL in my previous post is wrong. It is: http://support.microsoft.com/kb/2498915

Well. I didn't catch this problem until my registry hit 2GB, and I couldn't log in anymore. I managed to stop the NGEN and remove the bloated keys, but the SOFTWARE registry file is still 2GB and I can no longer apply windows updates.

I tried the instructions here: http://support.microsoft.com/kb/249891 , but step 3 fails with an error.

Does anybody have any ideas? I would just reinstall the OS and SQL Server, but this server also runs an Exchange instance (this is a small business). So, it would be a huge pain. Help!

New install of SQL 2012 Std and Management Studio on Server 2012... after applying SP1 I got the same behavior. The patch referred to by Shamik (KB2793634) fixed it there.

Just applied same fix to a production server on Server 2008 R2. Took a while, but it worked and it didn't require a server reboot. Didn't even realize this was happening on the production server.

FYI, after installing KB2793634 the reported versions have been incremented...

From SSMS:
Microsoft SQL Server Management Studio 11.0.3128.0 {was 11.0.3000.0}

From the setup tools:
Microsoft SQL Server 2012 Service Pack 1 Setup Discovery Report

Product Instance Instance ID Feature Language Edition Version Clustered
Microsoft SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS Database Engine Services 1033 Express Edition 11.1.3128.0 No
Microsoft SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS SQL Server Replication 1033 Express Edition 11.1.3128.0 No
Microsoft SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS Full-Text and Semantic Extractions for Search 1033 Express Edition 11.1.3000.0 No
Microsoft SQL Server 2012 Management Tools - Basic 1033 Express Edition 11.1.3128.0 No
Microsoft SQL Server 2012 LocalDB 1033 Express Edition 11.1.3128.0 No
{all were 11.1.3000.0}

Microsoft, thank you for the fix. Are you going to post any information about what it does/what it fixes? At this point the link is to a web page to download a patch, it says its a patch for the problem that is the title of this Connect article, and there is no other info. On my installations, I am having some of the symptoms (recurring MisInstaller and Restart Manager messages in the event logs, etc., maintenance jobs failing intermittently due to failure to obtain a connection, and server dropping from the network) but not others (I don't see the msiexec.exe process running).

This update seems to be working correctly.
After the update installed, msiexec.exe continued to run while mscorsvw.exe took a chunk of CPU and RAM while the ngen process finished. Now that is complete and I don't see any of the Event Log entires, Registry bloat, or msiexec.exe coming back.

I'll keep an eye on it for a few hours to be sure.

A fix for this issue is now available for download from http://www.microsoft.com/en-us/download/details.aspx?id=36215.

Please Note: The patch should only be applied if you're on SQL 2102 SP1. If you have already applied a Cumulative update or an "On Demand" fix on top of SP1, please wait for the associated hotfix update to be made available.


Thanks and regards
Shamik Ghosh
[SQL Server Team]

The SQL Server team will be releasing a fix to address this issue early next week.
I will post the download location immediately once it is available for public consumption.


Thanks and regards
Shamik Ghosh
[Sql Server Team]

The SharePoint guys are harassing me for SP1 but there's no way I'm installing it on a SQL 2012 cluster. I'm not experiencing the high CPU on my test server but still am not willing to risk it even with these workarounds. Hurry up!

If there is still somebody who hasn't hit this issue, here's something to try (but NOTE that this is ABSOLUTELY UNTESTED, since I'm not in a position to sacrifice any more machines to this issue):

* before running the SP1 installation, do the "ngen queue pause" thing as described in MS's stopgap post below
* install SP1
* let the machine sit for a while without doing anything at all -- this is to let ngen's automatic stuff kick in. It probably won't but it certainly wont hurt to wait
* reboot -- this is to make sure nothing is holding any locks on any files, etc.
* let the automatic ngen kick in, i.e. dont touch the machine for a while. you can just RDP into it (or sit it front of it if you can), start process explorer, disable screensaver & disable screen from turning off, and just watch it if you can. you'll eventually see ngen's automatic service start doing its thing. just make sure not to touch the mouse, keyboard, etc.
* a couple hours later, or whenever ngen stops doing its stuff, you should be all done. reboot once more for good measure, and check your eventlog periodically to see if symptoms appear.

I've been seeing the Event Log entries as well as repeated (approx every 5 minutes) TEMP files (filling up my system drive) but luckily not the CPU utilization. I've paused the NGEN queue and hope it'll help.

From SSMS:
Microsoft SQL Server Management Studio 11.0.3000.0
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML 3.0 4.0 6.0
Microsoft Internet Explorer 9.0.8112.16421
Microsoft .NET Framework 4.0.30319.17929
Operating System 6.1.7601

From the setup tools:
Microsoft SQL Server 2012 Service Pack 1 Setup Discovery Report

Product Instance Instance ID Feature Language Edition Version Clustered
Microsoft SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS Database Engine Services 1033 Express Edition 11.1.3000.0 No
Microsoft SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS SQL Server Replication 1033 Express Edition 11.1.3000.0 No
Microsoft SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS Full-Text and Semantic Extractions for Search 1033 Express Edition 11.1.3000.0 No
Microsoft SQL Server 2012 Management Tools - Basic 1033 Express Edition 11.1.3000.0 No
Microsoft SQL Server 2012 LocalDB 1033 Express Edition 11.1.3000.0 No

Is the registry bloat bug related to SQL clusters only, or to all installations of SQL server?

Same exact issues here. For me, the command lines to pause the 32-bit ngen service failed with an 0x80004005 (access denied) error, while the 64-bit was successful. So, I wound up just stopping the ngen service entirely and then disabling it for the time being.

As for the registry bloat that Peter De Tender mentioned, my SOFTWARE hive file was up to 1.4 GB. To combat this, I exported all of the keys that contained Microsoft.DataTransformationServices and then deleted them from the Registry. I then edited the .reg files to remove all of the subkeys. I left the subkeys that were 0 or 1 as the "nearby" (non-problematic) keys only had those - the ones related to DTS had literally hundreds. After that I reimported the keys from the now modified .reg files.

Before modifying them, the .reg files were all over 200 MB each and there were 5 subkeys, so about 1.0 GB of files total. After modifying the files, all of them were in the range of no more than 1 MB.

The system is stable now. I'm assuming that all of the space used by the now-deleted Registry keys have been returned to the Registry database as usable whitespace. It's been years since I even tried a Registry defrag/compact utility and am hesitant to do so as long as the space in the SOFTWARE hive is now indeed free for use.

I'm eager to see an official fix or at least some kind of update from Microsoft regarding this issue.

Experiencing the same issue on a production machine after applying SP1. Microsoft should really handle this with a higher priority.

I wrote an article about my troubleshooting and workaround regarding this issue here: http://lokna.no/?p=1251
Noticed the original issue mentions Hyper-V. I have seen this on both virtual and physical servers.

Update.. i removed SQLMS off my reporting server... and was working for wile, now i have started report issue...

THIS NEVER HAPPEND PRE SP1... IS THERE A FIX...YOUR WORKAROUNDS DONT WORK!!!

MS, the workaround you supplied doesn't work.

Like Nick0, the same for me, I've no Sharepoint installation. I've Windows 7 x64 PS1 with Visual Studio 2012 and SQL Server 2012. Also, my issue since the SQL Service Pack 1 installation on 28/11 is that on my D: drive are created many temporary MSIxxx.tmp folders and on my Event Viewer I see many errors of MsiInstaller with event ID of 1001 and 1004.
The message is:
"Detection of product "{A7037EB2-F953-4B12-B843-195F4D988DA1}", feature "SQL_Tools_ANS", component "{6E985C15-8B6D-413D-B456-4F624D9C11C2}" failed."

I've the italian version, so the original message is:
"Errore durante il rilevamento della caratteristica "" di "{A7037EB2-F953-4B12-B843-195F4D988DA1}". L'errore si è verificato durante una richiesta per il componente "{6E985C15-8B6D-413D-B456-4F624D9C11C2}"."

The situation has nothing to do with SharePoint - on my Windows 7 64-bit I never installed it. After several days of being practically unable to work, I removed the Management Studio and now the computer is alive again, but this is NOT a solution.
Isn't it high time for a useful step from Microsoft?
At least there should be a warning for anyone who tries to download or install the near 1-GB SP !

I had the same issues. A shared features repair of SQL 2012 fixed the issues even though the actual repair failed!

We also have similar issues with our always-on mirrored cluster (SQL2012 SP1).
As a result, our SOFTWARE registry hive has grown to exactly 2048MB.
( see http://blogs.msdn.com/b/sqljourney/archive/2012/10/25/why-the-registry-size-can-cause-problems-with-your-sql-2012-alwayson-setup.aspx ). Luckily we're not yet experiencing issues with the SQL services!
Because of this, we are having issues with -among others- our user profile service, and we can no longer log on to the server.

Upon investigating the issue, we found the following regkeys to be bloated:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727\NGENService\Roots\C:/Program Files (x86)/Microsoft SQL Server/110/Tools/Binn/ManagementStudio/Microsoft.DataTransformationServices**
Note that these keys are related to our dear friend, the NGEN service!
There are probably other keys that are too large also....
Because of these issues, the normal procedure to unbloat the registry doesnt work (http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/aae7fbf9-79c0-4053-8b8f-e70c1372e62f/)

We will keep track of this thread and are anxiously awaiting a real fix from Microsoft!

Same problem but without high CPU Usage, tons of warnings in event log.

Same problem running on Server 2008 R2 with IIS installed. Not using Sharepoint though.

We have the same problem on both Windows 2008 R2 and Windows 2012 servers.

This kind of killed my Windows Server 2008 R2 machine. (Server 2012 Management Tools only)

We noticed problem only after 3 days, coult not log in. (RDP or locally) Nothing seems work correclty, cant uninstalla any updates or so. (After 2 boots we can log in.. but registry is full or someting is wrong)

Guys… just an update… I was getting the same issue with the MSI process, but also the bonus issue of …..

Report Server has encountered a SharePoint error. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error. ---> System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {BDEADF26-C265-11D0-BCED-00A0C90AB50F} failed due to the following error: 800703fa.

….as we have a BI environment.

Removing SQL M Studio off the server running SSRS 2012 (with SSRS 2012 SharePoint integrated, you don’t really need MS on your server anyhow) seems to of solved the issue. I logged in this morning, ran a report with no issue. I will test again during the day and confirm tomorrow.

For the backend SQL DB’s, I will try the work around posted by the MS guys… But let’s hope there is a fix soon…

Hello all, we have identified a temporary workaround for this issue. We will continue to work on a permanent fix and will communicate more information as it becomes available.

If you are currently experiencing this issue, perform the following steps appropriate for you CPU architecture:
- Open an elevated cmd.exe
- If you are on a 64-bit architecture machine, run both of the following commands in the cmd.exe window:
     - %windir%\Microsoft.NET\Framework\v4.0.30319\ngen.exe queue pause
     - %windir%\Microsoft.NET\Framework64\v4.0.30319\ngen.exe queue pause
- If you are on a 32-bit architecture machine, run only the following command in the cmd.exe window:
     - %windir%\Microsoft.NET\Framework\v4.0.30319\ngen.exe queue pause

After running these command(s) CPU consumption should return to normal and the 1004/1001 events should cease being published to the event log.

More information on ngen.exe can be found here: http://msdn.microsoft.com/en-us/library/vstudio/6t9t5wcf(v=vs.100).aspx

Note - after a machine reboot, the workaround will need to be re-applied

thanks,
[SQL Server Team]

We can't deploy the BI features of SharePoint 2013 because of this issue. They depend on SQL 2012 SP1.

I can reproduce this on a Windows 7 SP1 (as well as Svr 2012) computer with just the Management Tools installed.

Hi all, thanks for your patience on this issue. We are actively investigating this issue and have identified potential workaround that we are in the process of validating. We will provide an update shortly when this is available.

thanks,
[SQL Server Team]

***Wow, I need to stand back and give MS a well-deserved clap on this one…”that noise you hear, is me CLAPPING”***

One work around is to uninstall SQL MS... good luck for that one... 3 hours, and its stuck on Undo_NativeImage_64 ... ngen.exe *32 and ScenarioEngine.exe just sits consuming 2 gig of mem each.

SP1 is affecting our SP integrated SSRS as well. Every morning, you are presented with a glorious

Report Server has encountered a SharePoint error. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error. ---> System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {BDEADF26-C265-11D0-BCED-00A0C90AB50F} failed due to the following error: 800703fa.

Do an IIS reset and hey presto… it all works…only to fall over some time later... this started to happen post SP1!!!

I will be reinstalling, after trying to remove SQL MS, the RS SharePoint plugin to see if this sorts out the issue as its now @ 11.1.3000.0, I will post ay findings.

MS - UPDATE? ...

MS - Any updates? This issue brought down both nodes of a production cluster. We are having to recover from backups. This should be a high priority issue.

I'm seeing this on a fresh Windows Server 2012 installation, as well. No SharePoint features are installed, but Database, Analysis, Reporting, and Integration Services are all installed, as are Data Tools and Management Studio.

I don't have sharepoint stuff on my laptop either, but most everything else. Win7x64. My error log is flooded with this message ever since updating to 2012 SP1 (CU1 didn't stop messages). Thankfully I am not getting the 100% msiexec thrashing!

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1001</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-11-21T22:16:22.000000000Z" />
<EventRecordID>449371</EventRecordID>
<Channel>Application</Channel>
<Computer>machinenamehere</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data>{A7037EB2-F953-4B12-B843-195F4D988DA1}</Data>
<Data>SQL_Tools_ANS</Data>
<Data>{6E985C15-8B6D-413D-B456-4F624D9C11C2}</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data />
</EventData>
</Event>

Got this as well on two Windows 2012 servers that only have SSDT and SSMS installed no database engine (TFS build servers). Fine after 2012 install, failed when we put SP1 on them.

Hi all, we are currently in the process of actively investigating this issue. We will provide an update as soon as we have more information to share.

thanks,
[SQL Server Team]

I suspect anyone who installs SP1 has this problem but may not realize it yet. In our case we are running Windows 2008 R2 and only have SQL Server installed.

Fortunately we didn't didn't experience 100 percent CPU utilization but msi installer errors kept appearing in application event log. Thats when we noticed msiexec.exe was running. Killing the process works for awhile but the process returns minutes later.

We resolved by uninstalling SQL Server Management Tools and SQL Data Tools. Also did a repair with original setup.exe but that may not have been necessary. A reboot is suggested after uninstalling features mentioned.

I have this problem too - Windows 7 Pro x64

Just tried installing CU1 for SP1 (http://support.microsoft.com/kb/2765331)

==> Issue is NOT fixed in this update.

My experience with SQL 2012:

1 - SSDT - Have you seen the chain of installs required to get all the desired bits in place for VS 2010/2012? Automatic SSDT conversion of VS 2010 SQL projects all failed with nothing complicated or unusual in their makeup. After a couple of hours of tinkering, finally rolled back the changes and upgraded the projects manually - finally got it all working. Some lost/changed functionality but also some gained. VS sure does run a lot slower - especially when using schema compare.

2 - SP1 - MS releases the slipstream ISO which really isn't. Upgrade a SQL 2008R2 installation and lose a day and a half trying to figure out what is going on because none of the SP1 changes appear to be present. Start investigating and then, whadda ya know, the ISO disappears from MSDN. No explination - just caught wind of it through the online grapevine. Finally install from standalone MSI and things start moving along.

3 - SP1 - CHecking on things after install and all of a sudden an otherwise empty/"clean" event log is filling with warnings. Moving on week number four and still no resolution or acceptable (to me) workaround.


Not the best showing. I echo the sentiment below: "Really Microsoft? Really?".

I rarely complain (and never have publicly) and can even deal with the bugs - but the lack of response on this given the amount of time that has elapsed is stunning...and I am not even suffering from the 100% CPU issue. It is just the principle of the thing. I know I would not be surprised to lose my job if I performed at the same level.

I would like ~three days of my life back.

Same issue here on three servers:

Protokollname: Application
Quelle:        Microsoft-Windows-RestartManager
Datum:         30.11.2012 03:43:10
Ereignis-ID: 10000
Aufgabenkategorie:Keine
Ebene:         Informationen
Schlüsselwörter:
Benutzer:     SYSTEM
Computer:     TONNO.mydomain.local
Beschreibung:
Sitzung wird gestartet: 0 - ?2012?-?11?-?30T02:43:10.155305400Z.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-RestartManager" Guid="{0888E5EF-9B98-4695-979D-E92CE4247224}" />
    <EventID>10000</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2012-11-30T02:43:10.155305400Z" />
    <EventRecordID>278496</EventRecordID>
    <Correlation />
    <Execution ProcessID="1384" ThreadID="3520" />
    <Channel>Application</Channel>
    <Computer>TONNO.mydomain.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <RmSessionEvent xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/2005/08/Windows/Reliability/RestartManager/">
     <RmSessionId>0</RmSessionId>
     <UTCStartTime>2012-11-30T02:43:10.155305400Z</UTCStartTime>
    </RmSessionEvent>
</UserData>
</Event>

Protokollname: Application
Quelle:        MsiInstaller
Datum:         30.11.2012 03:43:10
Ereignis-ID: 11724
Aufgabenkategorie:Keine
Ebene:         Informationen
Schlüsselwörter:Klassisch
Benutzer:     Nicht zutreffend
Computer:     TONNO.mydomain.local
Beschreibung:
Product: SQL Server 2012 Management Studio -- Install started.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">11724</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-11-30T02:43:10.000000000Z" />
    <EventRecordID>278495</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TONNO.mydomain.local</Computer>
    <Security />
</System>
<EventData>
    <Data>Product: SQL Server 2012 Management Studio -- Install started.</Data>
</EventData>
</Event>

Protokollname: Application
Quelle:        MsiInstaller
Datum:         30.11.2012 03:43:10
Ereignis-ID: 1040
Aufgabenkategorie:Keine
Ebene:         Informationen
Schlüsselwörter:Klassisch
Benutzer:     SYSTEM
Computer:     TONNO.mydomain.local
Beschreibung:
Eine Windows Installer-Transaktion wird gestartet: {A7037EB2-F953-4B12-B843-195F4D988DA1}. Clientprozess-ID: 2792.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">1040</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-11-30T02:43:10.000000000Z" />
    <EventRecordID>278494</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TONNO.mydomain.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data>{A7037EB2-F953-4B12-B843-195F4D988DA1}</Data>
    <Data>2792</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>
    </Data>
</EventData>
</Event>

Protokollname: Application
Quelle:        MsiInstaller
Datum:         30.11.2012 03:43:10
Ereignis-ID: 1001
Aufgabenkategorie:Keine
Ebene:         Warnung
Schlüsselwörter:Klassisch
Benutzer:     SYSTEM
Computer:     TONNO.mydomain.local
Beschreibung:
Erkennung von Produkt "{A7037EB2-F953-4B12-B843-195F4D988DA1}" und Funktion "SQL_Tools_ANS" fehlgeschlagen beim Anfordern von Komponente "{6E985C15-8B6D-413D-B456-4F624D9C11C2}".
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-11-30T02:43:10.000000000Z" />
    <EventRecordID>278493</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TONNO.mydomain.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data>{A7037EB2-F953-4B12-B843-195F4D988DA1}</Data>
    <Data>SQL_Tools_ANS</Data>
    <Data>{6E985C15-8B6D-413D-B456-4F624D9C11C2}</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>
    </Data>
</EventData>
</Event>

Protokollname: Application
Quelle:        MsiInstaller
Datum:         30.11.2012 03:43:10
Ereignis-ID: 1004
Aufgabenkategorie:Keine
Ebene:         Warnung
Schlüsselwörter:Klassisch
Benutzer:     SYSTEM
Computer:     TONNO.mydomain.local
Beschreibung:
Erkennung von Produkt "{A7037EB2-F953-4B12-B843-195F4D988DA1}", Funktion "SQL_Tools_ANS" und Komponente "{0CECE655-2A0F-4593-AF4B-EFC31D622982}" fehlgeschlagen. Die Ressource "" ist nicht vorhanden.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">1004</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-11-30T02:43:10.000000000Z" />
    <EventRecordID>278492</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TONNO.mydomain.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data>{A7037EB2-F953-4B12-B843-195F4D988DA1}</Data>
    <Data>SQL_Tools_ANS</Data>
    <Data>{0CECE655-2A0F-4593-AF4B-EFC31D622982}</Data>
    <Data>
    </Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>
    </Data>
</EventData>
</Event>

You don't need SharePoint to reproduce this error either. All I have on this 2012 Server box is:

Database Engine Services
Full-Text and Semantic Extractions for Search
Management Tools - Basic
Management Tools - Complete

...and the workaround to unstall the Management Tools is absurd. The service pack was pushed out by Windows Update and now the solution is to uninstall the Management Tools? Really Microsoft? Really? An why push out a broken Service Pack when this issue, which clearly affects many people given searches on Bing, is still there?! I'm truly baffled as to how this could make it out the door. Please give us a better workaround, or perhaps a fix.

This is an easy one to reproduce.

i am also..