Msi Custom Action Error 1721
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings error 1721 installshield and policies of this site About Us Learn more about Stack Overflow
Error 1721 Windows 7
the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation error 1721 windows 10 Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Wix error 1721 related to CustomAction up vote 3 down vote favorite 1 I have following CostomAction
SQL Server 2014 Express resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Samples Retired content We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Custom Action will not run & Error 1721 Windows Forms > ClickOnce and Setup & Deployment Projects Question 0 Sign in to http://stackoverflow.com/questions/11896681/wix-error-1721-related-to-customaction vote As the last step in a Major revions of an application, I moved the solution from VS2008 to VS2010. I also moved all projects from .Net 2 & 3.5 to .Net 4 (client) . This all seemed to work fine. However, the Setup Project is giving me fits. I did not have to make any changes ( except Version Numbers) to the setup https://social.msdn.microsoft.com/Forums/en-US/9bb3fe9d-fe82-4e16-8df3-2db0442d8734/custom-action-will-not-run-error-1721?forum=winformssetup project. I previously created a C# exectuable for a custom action and included it in my setup (MSI).The custom action in the commit step that was working is not working now. I try to execute it and it fails. A couple of observations: This only seems to happen if/when I am installing on a machine with a previous version installed. If I look at the TARGETDIR when the error happens, I noticed that most of the files from theMSI have not been installed yet there are enough ".tmp" files to account for all of the files. Here is the code: class Program { static int Main(string[] args) { //and if this is Vista (or Server 2008?) foreach (string dir in args) { if ((Directory.Exists(dir) == true) && (Environment.OSVersion.Version.Major >= 6)) { //Give Users full access to the dir folders string arguments = "\"" + dir.TrimEnd(new char[] { '\\' }) + "\" " + "/G Users:F /T /E"; Process caclsProcess = Process.Start( "CACLS", arguments); caclsProcess.WaitForExit(); } } return 0; } Here is the error (from the log): MSI (s) (34:18) [08:54:40:433]: Note: 1: 1721 2: _DA28B998_20A9_475A_BA65_A6AF0ADFFAE1 3: C:\Program Files\DIR1\APPDIR\PermissionChang
Windows Installer (MSI) Windows Installer (MSI) Error Messages Help with MSI (Microsoft Installer) error 1721: There is a problem with this Windows Installer package. http://www.itninja.com/question/help-with-msi-1721 A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: [2], location: [3], command: [4] 0 Comments [ + ] Show Comments Comments Please log in to comment Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable. Answers 0 Some have reported error 1721 that this error may be encountered if anti-virus software is running. It has also been reported to surface when repackaging an application for distribution that mistakenly contains items it sould not (see PackageCleaner). This can also be seen when the MSI installation attempts to execute a file located on the destination machine. If you are creating a package and choose to error 1721 windows have a custom action "Execute Program from Destination", you may avoid the problem by instead choosing to have the custom action "Execute Program From Installation". If the file to be called does not reside on the PC prior to the beginning of the installation, error 1721 will be seen if you choose "Execute Program from Destination". When the file you want to execute is being installed from the MSI, use "Execute Program from Installation". Answered 04/28/2004 by: AppDeploy.com Please log in to comment Please log in to comment 0 Unfortunately, there is no set reason why this error will arise. It could be that: you need to register and unregister Windows Installer; Windows Installer may contain corrupt / damaged files; a newer version of Windows Installer is needed or that the registry needs to be cleaned out with a registry cleaner. In order to resolve the error, you need to cover as many bases as possible and some such steps are provided here: http://www.personalcomputerfixes.com/general-errors/how-to-fix-installer-error-1721/ Answered 06/06/2012 by: bkelly Please log in to comment Please log in to comment 0 Hi there. First