Application event log error code 1642 even though the SQL Server update was applied successfully

This article provides more information about the 1642 error message that is reported in the application event log though the SQL Server update is applied successfully.

Original product version:   SQL Server 2016, SQL Server 2014, SQL Server 2012 Developer, SQL Server 2012
Original KB number:   4230836


When you install a cumulative update to Microsoft SQL Server, setup may complete successfully. However, you may find the following error logged in the system's Application event log:

Log Name:      Application  
Source:        MsiInstaller  
Date:         date time  
Event ID:      1024  
Task Category: None  
Level:         Error  
Keywords:      Classic  
User:          SYSTEM  
Computer:     host_name  
Product: SQL Server 2016 Database Engine Services - Update '  {DDCDC225-F14E-411F-925A-7CF68238240F}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support:  
Event Xml:  
<Event xmlns="">  
        <Provider Name="MsiInstaller" />
        <EventID Qualifiers="0">1024</EventID>
        <TimeCreated SystemTime="date time" />
        < EventRecordID>463708</EventRecordID>
        < Channel>Application</Channel>
        <Security UserID="user_id" />
        <Data>SQL Server 2016 Database Engine Services</Data>
        < Data>{DDCDC225-F14E-411F-925A-7CF68238240F}</Data>


This issue occurs in several scenarios in which an MSI installer package failure is logged in the Application event log because the setup call to the MsiGetPatchFileList API does not get a list of files from the MSP (Windows Installer patch file).


You can safely ignore this message in the Application event log when the following conditions are true:

  • Setup of the SQL Server cumulative update completed successfully.

  • No error messages are recorded in the Summary.txt file.

For more information, see View and Read SQL Server Setup Log Files.