Error 2711 Msi
Contents |
AMI have this interesting problem: I need an installer that can create 3 different installations depending on the user selection, but want to error 2711 the specified feature name not found in feature table use only one install msi file. So we discovered the ADDLOCAL error 2711 office 2013 keyword that can be passed on by the msiexec command parameters. Just one small problem: I get
Windows Installer Cleanup Utility
a “Internal Error 2711” when I execute the msiexec. Tracing the problem I discovered that it is caused by not finding the feature, to install. Further testing I discovered that it appears to be a bug in the InstallShield since the feature is indeed defined but for some unknown reason it does not know about the new names but keeps insisting on using the first created feature name. When I try this: · Create a completely new project. · Add the feature “NewFeature1” · Build · Execute: msiexec /i test.msi ADDLOCAL=NewFeature1 It works perfect. Now I rename the feature “NewFeature1” to something else like “VisioWave30” And build the command “msiexec /i test.msi ADDLOCAL= VisioWave30” fails with the “Internal Error 2711” error! Now is the interesting part, If I execute that same msi file with “msiexec /i test.msi ADDLOCAL=NewFeature1” then it succeeds!!! It is clearly that it keeps on remembering the older feature while that one has been omitted in the installshield project! Do we have a fix for that? Or a workaround? Many thanks TsungH07-24-2006, 11:50 PMWhere and how did you change the feature name? Did you change in ISM project and rebuild the project? Can you open up MSI file (.msi) in InstallShield X IDE and verify the feature name is not changed? Now I rename the feature “NewFeature1” to something else like “VisioWave30” And build the command “msiexec /i test.msi ADDLOCAL= VisioWave30” fails with the “Internal Error 2711” error! Powered by vBulletin Version 4.2.2 Copyright © 2016 vBulletin Solutions, Inc. All rights reserved.
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs http://community.flexerasoftware.com/archive/index.php?t-161064.html Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec https://support.symantec.com/en_US/article.TECH31550.html Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' KNOWN ISSUE: Receive error 2711 when applying a universal transform TECH31550 June 27th, 2007 http://www.symantec.com/docs/TECH31550 Support / KNOWN ISSUE: Receive error 2711 when applying a universal transform Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation Steps to reproduce: Create a new Universal Transform. Add a registry key. Compile. Create a new .msi. Run the .msi with the .mst applied. You will receive Internal error 2711. Complete.Error 2711 is "The specified Feature name ('[2]') not found in Feature table." Cause If you open the .msi and apply the .mst in Orca, you will see that in the .mst the Complete feature is marked as being deleted. This causes Windows Installer to believe that there is not a Complete feature even though other tables reference a feature named Complete. Addit
not load file or assembly “System.Runtime.Serialization.Formatters.Soap”, =2.0.0.0, Culture = neutral, or one of its dependencies. → Error 2711: The installer has encountered an unexpected http://relyonsoft.com/techsupportTest/?p=278 error installing this package. This may indicate a problem with this package. The error code is 2711. Posted on August 23, 2012 by Naveen Shivkumar Error: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2711. Error Message: error 2711 Causes: It is may be problem with corrupted .Net Framework. Application might be corrupted. Improper uninstallation of Dotnet framework, your registry is not clean and might be corrupted. Clean the temp and %temp% folder. For Windows Vista\7\8 .NET Framework comes with the operating systems. So need not install it again. You just error 2711 msi need to configure it from control panel. Solution 1: Clean system "temp" folder Start > Run > type temp Click enter and try to remove all the files and folders from the temp folder. Start > Run > type %temp% Click enter and try to remove all the files and folders from the %temp% folder Solution 2: Configure Microsoft .NET framework [Applicable only for Windows Vista\7\8\Server 2003\Server 2008 operatings systems] Click Start ->Control Panel ->Programs and Features Turn Windows features on or off -> Select "Microsoft .NET framework 3.5.1" Click OK and restart the system. Solution 3: Open control panel, click Add\Remove Programs and uninstall the .NET Framework. Re-Install the .NET Framework. Solution 4: Run .NET Framework cleanup Utility to clean the .NET Framework components completely. Download: .NET Framework Cleanup tool Navigate to [C:\Windows] folder Rename folder assembly & Microsoft.NET to assemblyOld, Microsoft.NETOld Later Install Microsoft .Net Framework 2.0 SP1. or Latest version. Solution 5: Re-install the applic