This error message is displayed by the Microsoft Windows Installer Engine (Wondering whats this? Read here) and is a general error code that indicates a problem occurred during the installation. Read on this article to learn how to sidestep this speed bump. The following is the probable list of known causes for this error to occur: Short… Continue reading Troubleshoot the error 1603 “Fatal Error During Installation”
Hi Folks, Its time for yet another Guest Post; and we have Bhuvana writing for us. In this article she focuses on the command line arguments and the silent switches that can be used for msi and msp (un-installable patches). Bhuvana specializes in InstallShield & MSI Installers and her primary responsibility at work is “Build &… Continue reading Command Line Switches for MSI and MSP Installations
As you guys are aware, I am writing a series of posts which covers some key discussions, topics and FAQs in the stream of application packaging. In this third post, we will look at some questions on key OS components and Installation sequences. Q11. What is the difference between a Task, Process and a Service… Continue reading Windows Installer FAQ – Part 3
Deferred custom actions have limited access to the installation session. If your deferred custom action requires information about the installation that it cannot obtain through its limited access, then you can provide that information to the deferred custom action through the CustomActionData property. This method is only available to script and DLL deferred custom actions.… Continue reading Access MSI Database in Deffered Context through Custom Actions
The ADDLOCAL, ADDSOURCE, and ADVERTISE properties can be used to install only a certain number of known features. The following command-line script would be used to install the “Word” and “Excel” features of the example.msi package locally on the machine. Feature names are case-sensitive. msiexec /i example.msi ADDLOCAL=Word,Excel /qb The following command-line script would advertise… Continue reading Installing Specific Features in a MSI Package
The following registry key gives information about the sourcelist for a msi. (Source Resilency) HKCR\Installer\Products\convertedGUID\Sourcelist We can also check for the transforms which were installed along with msi in HKCR\Installer\Products\convertedGUID\TRANSFORMS
When an installation fails, it may be because of the Custom Action(s) it contains. Here’s how to examine the MSI logs to troubleshoot the problem. Generate the MSI log and search for RETURN VALUE 3. This will help you identify and solve the problem in some cases. Further, the possible Return Values for CAs are:… Continue reading How to Fix Custom Action Issues in MSI Installation?
Validation is performed by one or more Internal Consistency Evaluators, that are organized into CUB files. Several standard validators and CUB files are provided as part of the Platform SDK. ORCA can also use custom validators and CUB files.