Geek Answers Handbook

MSI 1721 Custom Action Error on Windows 8 Using InstallShield 2010

I get error 1721 on Windows 8 when my basic MSI installation tries to run a custom executable, while on Windows XP and Windows 7 it starts because I installed it with InstallShield . The executable file is stored in a binary table. Why is this happening?

Screenshot with the error message containing error 1721: "DJPro Automations Installer Information. Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action : Initializer, location: C: \ Windows ... \ MSID974.tmp, command: "

+4
source share
3 answers

Run as administrator. It will do. I had the same problem and it was solved by doing the same.

+1
source

Change In-Script Execution to "Delayed Execution in the System Context" in your custom action

+1
source

This was originally associated with architecture. Make sure that all parts of user actions, programs, paths and file names, etc. Are valid. Also, as already mentioned, always use installers through an administrator account.

If you call an EXE stored in a binary table, make sure you specify it correctly. Often, Windows Installer decompresses the MSI into the "% temp%" folder, so confirm the access and the correct path. MSIEXEC extracts temporary files, for example, "MSID974.tmp", which then performs a pre-configured MSI function, but crashes.

Finally, try creating a verbose MSI log file. This will help you more clearly identify the problem.

0
source

More articles:


All Articles