About banna_k

banna_k · ‎Mar 10, 2021

Hi @Lirantev , Please check the below thread for the solution for the restart. https://community.flexera.com/t5/InstallShield-Forum/Visual-C-2019-x64-Prerequisite-fails-when-Visual-C-2017-x64-is/td-p/115589

banna_k · ‎Mar 02, 2021

Hi @nileshmunnur, See what value configured for the windows installer (msi) "Minor Upgrade handling" setting in the packages view: Minor Upgrade Handling .msi, Basic MSI project Indicate the appropriate behavior that should occur when an earlier version of the package is present on the target system. Available options are: • None —The Advanced UI or Suite/Advanced UI installation launches the package without running it in minor upgrade mode. That is, the Advanced UI or Suite/Advanced UI installation does not set the REINSTALL or REINSTALLMODE properties for the package. • Automatic —The Advanced UI or Suite/Advanced UI installation launches the package in upgrade mode by setting the REINSTALL property to ALL and the REINSTALLMODE property to vomus . It does not inform the end user that the product will be upgraded. • Ask the User —The Advanced UI or Suite/Advanced UI installation displays a secondary window that asks the end user whether they want to continue. If the end user chooses to continue, the Advanced UI or Suite/Advanced UI installation launches the package in upgrade mode. If the end user chooses to not continue, the package does not run. Try configuring " Automatic" —The Advanced UI or Suite/Advanced UI installation launches the package in upgrade mode by setting the REINSTALL property to ALL and the REINSTALLMODE property to vomus . It does not inform the end user that the product will be upgraded.

banna_k · ‎Feb 26, 2021

Hi @chrisfox2385 , It may be due to the difference in the COM extraction settings. Firstly, I am suggesting you to upgrade InstallShield to the latest version (InstallShield 2020). We made some improvement in COM extraction in the latest versions. InstallShield provides three different methods to extract the COM information, but at a time InstallShield extract the information based on the method configured in the registry. UseAPIRegistryHooks registry value located in HKEY_LOCAL_MACHINE\Software\InstallShield\RegSpy key (on 32-bit machines) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\InstallShield\RegSpy key(on 64-bit machines) holds the method configured to extract the COM information. Value Description 0 COM information captured by hooking Windows Registry API, old method. 1 COM information captured through Registry redirection API 2 COM information captured through Kernel mode registry filtering; latest method introduced in InstallShield 2012. Value "2" is the latest method, which is more efficient than all others. But, in some cases value can be changed to the suitable method if the default one(value "2") is not working. InstallShield provides a utility tool named RegSpyUI to cross check the values extracted from COM component, extracted by the method specified in the registry. RegSpyUI tool is available in the InstallShield support folder(C:\Program Files (x86)\InstallShield\2019\Support), this tool can be used to verify the COM extraction done by InstallShield. See, RegSpyUI able to extract the COM information with the registry value 2 and then see with value "1". RegSpyUI is a COM extraction utility available in InstallShield, located under the <InstallShield Programs File Folder>\Support folder. More information on RegSpyUI can be found at the below link: https://community.flexera.com/t5/InstallShield-Knowledge-Base/Extracting-COM-Information-with-RegSpy...

banna_k · ‎Feb 11, 2021

Hi @ssglogic, Can you configure the timestamp server in settings.xml as mentioned in the below KB article, as well install the patch. https://community.flexera.com/t5/InstallShield-Knowledge-Base/Digital-Signing-Patch-for-InstallShield-2015-SP2-and-above/ta-p/121641

banna_k · ‎Jan 17, 2021

Hi @skummara, Yes, its possible to automate using the automation interfaces. More information on the automation interfaces can be found : https://docs.revenera.com/installshield26helplib/helplibrary/IHelpAutoISWiProject.htm#ref-automationinterface_3198501150_1161875 Sample VB script code to add new release: Set oISM = CreateObject("ISWiAuto23.ISWiProject") ' this time, open project as read-write oISM.OpenProject "D:\MySetups\BuildMe.ism", False ' get existing configuration Set oMyConfig = oISM.ISWiProductConfigs("DemoVersion1") ' add new release to existing configuration Set oNewRelease = oMyConfig.AddRelease("new") ' set release properties oNewRelease.Compressed = True oNewRelease.SetupEXE = True oNewRelease.TargetOS = 3 ' i.e., os9xNT: include both engines ' ...set other properties... ' if you want, build the new release oNewRelease.Build( ) ' for testing MsgBox "Done!" ' this time, save the project before closing it oISM.SaveProject oISM.CloseProject

banna_k · ‎Jan 15, 2021

Hi @rguggisberg , Please follow below InstallShield KB article to fix the signing related issues: https://community.flexera.com/t5/InstallShield-Knowledge-Base/Digital-Signing-Patch-for-InstallShield-2015-SP2-and-above/ta-p/121641

banna_k · ‎Jan 15, 2021

Hi @jkcraig , Hope you have executed the " TSConfig.exe /registerVSIP" in an administrator command prompt from InstallShield 2018 R2 system folder. If InstallShield 2018 R2 failed to integrate with VS2019 after executing above command, then please reach out to Revenera support to analyze this further. https://www.revenera.com/about-us/contact-us.html https://community.flexera.com/t5/InstallShield-Knowledge-Base/How-to-Use-Revenera-Support-Chat-to-He... https://community.flexera.com/t5/Support-Information/Support-Contacts/ta-p/94720

banna_k · ‎Jan 06, 2021

Hi @JSBurton, Can you share more info on this, such as which automation interface is throwing error or it will be great if you could share a sample script file.

banna_k · ‎Jan 06, 2021

Hi @jmaHexagon, .ise files are not supported in InstallShield limited edition for Visual studio, .ise file are supported in InstallShield Express and higher version. Hope you are activating InstallShield 2020 with InstallShield 2020 express activation key. You can contact Revenera support to get faster help on activation related issues https://www.revenera.com/about-us/contact-us.html https://community.flexera.com/t5/InstallShield-Knowledge-Base/How-to-Use-Revenera-Support-Chat-to-He... https://community.flexera.com/t5/Support-Information/Support-Contacts/ta-p/94720

banna_k · ‎Jan 06, 2021

Hi @theone_sumit, Check your time stamp URL configured in the settings.xml, if you are using old symantec or verisign then you need to update Settings.xml file in <InstallShield_InstallPath>/Support/0409 with new URLs Before: <DigitalSignature Timestamp="http://timestamp.verisign.com/scripts/timstamp.dll"/><DigitalSignature TimestampRFC3161="http://sha256timestamp.ws.symantec.com/sha256/timestamp"/> After: <DigitalSignature Timestamp="http://timestamp.digicert.com"/><DigitalSignature TimestampRFC3161="http://timestamp.digicert.com"/> Also install the digital signing patch if you are configured to sign using Digicert server and using older version of InstallShield: More information on this patch can be found at the below link: https://community.flexera.com/t5/InstallShield-Knowledge-Base/Digital-Signing-Patch-for-InstallShiel...

banna_k · ‎Jan 05, 2021

Hi @Professor, It looks like the response XML is not proper, my suggestion here is to repeat the process again. 1- Try to activate again with the activation code, 2- if its asking for the offline activation, generate the activation xml and upload to the URL given last time and generate the response XML again. 3- Load the new response XML in the activation wizard again. If the problem is not resolved, then Please contact Revenera support to get faster help on this. https://www.revenera.com/about-us/contact-us.html https://community.flexera.com/t5/InstallShield-Knowledge-Base/How-to-Use-Revenera-Support-Chat-to-He... https://community.flexera.com/t5/Support-Information/Support-Contacts/ta-p/94720

banna_k · ‎Jan 05, 2021

Hi @MattTrinder , As suggested by @shunt , can you change the values from "2" to "3". I think, you have changed in the wrong column. So can you update again as in the below screenshot: change the values just before the "http://www.installengine.com/cert05/dotnetfx" string ( <td>3</td><td>http://www.installengine.com/cert05/dotnetfx). OR There is a setting configuration in "C:\Program Files (x86)\InstallShield\2020\Support\0409\settings.xml", which help you to change these values through the IDE. 1- Search for the string "<DotNetTabReleases Hide="1"/>" in the settings.xml, and then change the value to "<DotNetTabReleases Hide="0"/>. Save the settings.xml. 2- Close and reopen all the application(InstallShield and Visual studio IDE) and InstallShield projects. 3- Navigate to Releases view, change the value to "Do Not Include" for the ".NET Framework Location" for all the releases in the "Releases" view, as shown in the below screenshot image. Hope this help you to proceed the evaluation.

banna_k · ‎Jan 03, 2021

Hi @MattTrinder , If you are evaluating InstallShield and have any questions or issues, for faster response, please raise a support ticket. Please contact Revenera support: https://www.revenera.com/about-us/contact-us.html https://community.flexera.com/t5/InstallShield-Knowledge-Base/How-to-Use-Revenera-Support-Chat-to-He... https://community.flexera.com/t5/Support-Information/Support-Contacts/ta-p/94720

banna_k · ‎Jan 03, 2021

Hi @adurai21 , Yes, its possible to do with Basic MSI, InstallScript MSI, or using InstallScript project to deploy the web application.

banna_k · ‎Jan 03, 2021

Hi @tech_it , Usually, there will be an option in the PLC (Product Licensing center) to return the license and generate one for the new machine. If not, can you check with Revenera support: https://www.revenera.com/about-us/contact-us.html https://community.flexera.com/t5/InstallShield-Knowledge-Base/How-to-Use-Revenera-Support-Chat-to-He... https://community.flexera.com/t5/Support-Information/Support-Contacts/ta-p/94720

Online Status	Offline
Date Last Visited	‎Mar 10, 2021 01:13 PM

Re: C++ 2019 Redistributable restart required via InstallShield

Re: offline msi package upgrade via suite installer

Re: Building same patch on a different machine

Re: Invalid Timestamp http address

Re: Automating ism in Install shield

Re: SigningHelper: error 0x80072efe while attempting to sign file

Re: InstalllShield 2018 R2 installer won't register Visual Studio 2019 extension

Re: Error -2147319765: Automation error - Element not found

Re: Couldn't open ise file with Installshield Visual Studio

Re: SigningHelper: error 0x80072efe while attempting to sign file

Re: Installshield Internet Activation Failed

Re: Brand new installation fails with 1603 error trying to install .NET 1.0

Re: Brand new installation fails with 1603 error trying to install .NET 1.0

Re: Install shield for web application

Re: how to cancel a generated "Standalone Build License"

Re: C++ 2019 Redistributable restart required via InstallShield

Re: offline msi package upgrade via suite installer

Re: Building same patch on a different machine

Re: Invalid Timestamp http address

Re: Automating ism in Install shield

Re: SigningHelper: error 0x80072efe while attempting to sign file

Re: InstalllShield 2018 R2 installer won't register Visual Studio 2019 extension

Re: Error -2147319765: Automation error - Element not found

Re: Couldn't open ise file with Installshield Visual Studio

Re: SigningHelper: error 0x80072efe while attempting to sign file

Suggested Actions

Suggest an improvement

Open a support case