Hello Raj,
To see why the installation fails you need to check the log file.
In order to generate an installation log, you can check the
Enable Verbose Logging option from the
Install Parameters page. By enabling this option, a log file will be generated each time the install package runs. This option sets the Windows Installer
MsiLogging property to
v value. Windows Installer will automatically set the
MsiLogFileLocation property to the full path of the log file.
Then, you can create your custom action as
a custom action written in C# or
a custom action written in C++ which will parse the installation log file and search through the log to see where the installation fails or gather useful information about the installation process. The Installer writes values into the log when an action returns any error code. For details, please check the
Logging of Action Return Values article.
You can also take a look on the
Send (or prepare) an email during installation forum thread that debates a similar subject and on the
Options to integrate and debug custom actions article which may be useful to you.
Let us know if that helped, otherwise give us more details about your specific scenario.
Best regards,
Dan
FOLLOW US
Get the latest news in Application Packaging