Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

James Serra's Blog

James is currently a Senior Business Intelligence Architect/Developer and has over 20 years of IT experience. James started his career as a software developer, then became a DBA 12 years ago, and for the last five years he has been working extensively with Business Intelligence using the SQL Server BI stack (SSAS, SSRS, and SSIS). James has been at times a permanent employee, consultant, contractor, and owner of his own business. All these experiences along with continuous learning has helped James to develop many successful data warehouse and BI projects. James has earned the MCITP Business Developer 2008, MCITP Database Administrator 2008, and MCITP Database Developer 2008, and has a Bachelor of Science degree in Computer Engineering. His blog is at .

SQL Server 2012 SP1 Causes MsiInstaller Application Log Entries

After installing SP1 to SQL Server 2012 (11.0.3000) on one of our servers, I noticed higher than normal CPU loads due to msiexec.exe running non-stop.  The cpu percentage would bounce from 0% to 13%, and the application log would have five new entries about MsiInstaller and RestartManager about every 30 seconds.  There is a Connect bug about it at msiexec.exe processes keep running after installation of SQL Server 2012 SP1, and a fix has just been released at Non Security Update for SQL Server 2012 SP1 (KB2793634).

After installing the fix, SQL Server will be at version 11.0.3128, you will no longer see msiexec.exe running, those log entries will stop, and your CPU usage will drop.

More info:

SQL Server 2012 SP1 – Endless MsiInstaller Application Log Entries

Comments

Leave a comment on the original post [www.jamesserra.com, opens in a new window]

Loading comments...