Installer Status 1602
Attention, Internet Explorer User Announcement: VMware Communities has discontinued support for Internet Explorer 7 and below. In order to provide the best platform for continued innovation, VMware Communities no longer supports Internet Explorer 7. VMware Communities will not function with this version of Internet Explorer. Please consider upgrading to Internet Explorer 8, 9, or 10, or trying another browser such as Firefox, Safari, or Google Chrome. (Please remember to honor your company's IT policies before installing new software!).
Symantec helps consumers and organizations secure and manage their information-driven world. Our software and services protect against more risks. Nov 25, 2012 SCCM client push CCMsetup error 1602. Windows Installer (MSI) error code 1602 indicates that the user canceled the installation.
Recently we’ve got error installing driver on our Windows 2008 R2 server. It does not provide any specific error dialog, just constantly showing “Please wait while the application is preparing for the first use”. After you press Cancel, it gives you error message saying that installation could not be completed because other installation is in progress. The only diagnostic message in the Application log was EventID 1033 form MsiInstaller with message “Installation success or error status: 1602” or “Installation success or error status: 1618”.
Which obviously not helpful. Internet search revealed, that this message is quite common and can be caused by many things. Also I have found that installer created MSI.log which contained the same diagnostic message about status 1602 or 1618, but it also contained another message “Failed to grab execution mutex. System error 258” which also does not look helpful, but quick search for this string found. The problem is that our server has Remote Desktop Session Host (Terminal services), which by default forbids chained installations.
Installer Status 0
Windows Installer Status 1602
Chained installation is the method of installation when one msi file calls another one to install some prerequisites. Remote Desktop Session Host can be used by many users so, which can try to install many MSI files simultaneously, which potentially can cause some conflicts and broken installations, so Remote Desktop Session Host by default permits only one installation at a time, all other installations are queued for sequential installations. Of cause it is not possible for chained installation, when you first MSI is running and is waiting subsequent msi file to complete, to queue subsequent installations. To fix this issue you need to use Group Policy, either local or domain. The required setting is: Computer Configuration-Administrative Templates-Windows Components-Remote Desktop Services-Remote Desktop Session Host-Application Compatibility-Turn off Windows Installer RDS Compatibility Just set it to “Enabled” and run gpupdate /force, and rerun your installation.