Error Code 2721 Wix
Contents |
to you? Average Rating 0 7646 views 06/21/2009 Software Deployment Windows Installer (MSI) Windows Installer (MSI) Error Messages Hi I'm doing a transform for error 2721 custom action not found in binary table stream an application which basically applies some security settings to the local C:
Msi Installer Error 2721
drive. The application installs ok, however during the testing of the un-install option i receive
Internal Error 2721
the mst. I'm a little bit lost as to what is causing this issue. [font="times new roman"]
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://stackoverflow.com/questions/16415985/what-causes-a-1723-dll-not-found-error-in-a-wix-installer of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a error 2721 minute: Sign up What causes a 1723 DLL not found error in a WIX installer up vote 5 down vote favorite 2 I'm working with a WIX installer and keep getting this error message: WIX Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Are there any other installer error 2721 issues that would cause the 1723 error which are not related to the DLL not being found? I can say with 100% certainty that the DLL has to be found because previous custom actions in the same installer work and they all use the same DLL. I had this error before and solved it by renaming the custom action so I assumed it was related to the length of the name allowed for the custom action. This time I have tried both a shorter name and a name the exact length of other working custom actions and still get this error. I have investigated causes of 1723 and the most common one seems to be that the installer fails to unpack the DLL due to access rights. Although this is very unlikely as other custom actions in the same file referencing the same DLL work fine I have ensured that the folder the installer is trying to access has full access for this user, also I am running the installer from a command prompt in administrator mode so we should have no issues there.