Error 2721 Custom Action
Contents |
problem you cannot solve? Try here. Post Reply Print view Search Advanced search 12 posts • Page 1 of 1 AlexB Posts: 30 Joined: Tue Feb 19, 2008 8:03 pm Location: Sydney Error 2721: Custom action ACTAWE not found in
Error Code 2721
Binary table Quote Postby AlexB » Tue May 21, 2013 6:58 am Hi guys,I am internal error 2721 getting the following error in my installer:The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2721. Installer log contains few more details:Error 2721: Custom action ACTAWE not found in Binary table stream...Property(S): UNAUTHORIZEDEXEC_ERROR = Unauthorized to start the MSI installation/uninstallation!I can't figure out what actually causes it.Please http://www.symantec.com/connect/forums/error-2721-custom-action-action133137-not-found-binary-table-stream advise Top FrancescoT Site Admin Posts: 4438 Joined: Sun Aug 22, 2010 4:28 am Re: Error 2721: Custom action ACTAWE not found in Binary ta Quote Postby FrancescoT » Tue May 21, 2013 10:45 am Dear User,it is not so easy to find out what seems to happen with your package by the information provided. Error 2721 occurs if the installation is unable to find the file being launched by the custom action in the http://www.installaware.com/forums/viewtopic.php?t=9531 Binary table or within the project. and many several factors within the project can lead to this error. Is the error reproducible with any target OS or it can be verified with a specific target only? Do you call any EXE or DLL with the package?Regards Francesco ToscanoInstallAware Software SupportWhite Papers (HowTos) - http://www.installaware.com/publication ... papers.htmPublications - http://www.installaware.com/publications-review.htmInstallAware Help -F1 anywhere in the InstallAware IDE Top AlexB Posts: 30 Joined: Tue Feb 19, 2008 8:03 pm Location: Sydney Re: Error 2721: Custom action ACTAWE not found in Binary ta Quote Postby AlexB » Wed May 22, 2013 5:47 am Hi Francesco,Thank you for your reply. Yes, I had few calls of Run program (all after Apply Install command). I commented them out and problem was still there.However, after I restarted the build server (which is virtual Windows Server 2012) and re-made the build. Installer worked just fine.I use InstallAware 15. Now I have to re-boot that build server every time prior to making a build. Otherwise IA setup will fail with the error described in my original post.Please advise.Regards,Alex Top FrancescoT Site Admin Posts: 4438 Joined: Sun Aug 22, 2010 4:28 am Re: Error 2721: Custom action ACTAWE not found in Binary ta Quote Postby FrancescoT » Wed May 22, 2013 7:28 am Dear Alex,which is exactly the IA 15 version you are currentl
action -- file name and "Internal Error 2721" NewsArchive06-22-1999, 12:00 AMWhen I use the new beta version of InstallShield for Windows installer I got the following problem: I create a custom action by the custom http://community.flexerasoftware.com/archive/index.php?t-71307.html action wizard. When I fill the "Source" field by browse to get the binary file(e.g. mydll.dll) it showed as the actual file name(mydll.dll). But at the end it replaced the file name to another name as New_Binary1. Another custom action use the same binary file but call different function. As mentioned above the file name got replace to New_Binary2 at the end. During the installation it gave "Internal error 2721 Error 2721". After I found out the actual file name was got replace in the custom action wizard, I changed New_Binary2 to New_Binary1 instead of put the actual file name. Then it got rid of the Internal Error. Is the name replacement necessary? Why replace the same binary with different name and give Internal Error? How to avoid it? Since the file name replacement was done in the background error code 2721 without notice and it takes time to figure out the problem. This does not happen when use the old beta version of InstallShield for Windows installer. It keeps the original binary file name. Thanks! Sa NewsArchive06-23-1999, 12:00 AM<<..inline..>> >After I found out the actual file name was got replace in the custom >action wizard, I changed New_Binary2 to New_Binary1 instead of put >the actual file name. Then it got rid of the Internal Error. <<<