About varul

varul · ‎Oct 12, 2021

Hi, This issue has been fixed in IS2020R3SP1, please check the release notes for master issue number: IOJ-2179070 https://docs.revenera.com/installshield26helplib/rn/Content/helplibrary/InstallShield_2020_R3_SP1_1.htm You can upgrade to R3 SP1, If you want to use 2020R3, then use batch_install to true as a work around , please refer below community discussion. https://community.flexera.com/t5/InstallShield-Forum/InstallShield-2020-automatically-activates-maintenance-mode/td-p/184948 Hope it helps Regards, Vijay.A

varul · ‎Oct 11, 2021

Running an Automation Script via the InstallShield SAB on Windows Server Core Docker Image Summary: How to run an InstallShield automation script (VBScript or PowerShell) inside a Windows Server Core Docker image. Build a Docker image that has the InstallShield Standalone Build installed by following the steps in the following Knowledge Base article: InstallShield Standalone Build with Docker Synopsis This information applies to the following InstallShield project types: Basic MSI InstallScript MSI Cause When we run an automation script on a Windows Server Core Docker image, it fails with the error "The specified module could not be found." or the project will not build. Solution The issue of the build failure on a Windows Server Core Docker image is due to the following missing Microsoft Windows libraries: oledlg.dll, msvbvm60.dll, glu32.dll, opengl32.dll, srpapi.dll. Windows Server Core provides you with a minimal installation of Windows Server with minimal features and supports only certain server roles. Oledlg.dll, msvbvm60.dll, glu32.dll, opengl32.dll, srpapi.dll are not included with the Windows Server Core installation. Hence, the Automation Interface is failing to build the project for a Basic MSI project or a InstallScript MSI project. Since all of these DLLs are from Microsoft and we do not have the redistribution rights, we need to copy all of these 5 DLLs from a Windows Server 2019 GUI > SysWow64 folder to the Windows Server 2019 Core Docker image > SysWow64 folder, and then execute the automation script. The automation script will then execute without any errors. Reference Creating a PowerShell automation script: PowerShell Automation Script Creating a Python automation script: Python Automation Script

varul · ‎Oct 08, 2021

Could you please check the component3 is not linked to feature1 and the same file in component 3 is not shared or added to other component like comp1 and comp2, How you are validating the files from comp3 are getting installed by checking the presence of files or log Could you please the project ism file, or a sample ism to replicate the issue, so we can check the ism file correctly configured or not.

varul · ‎Oct 07, 2021

It looks like more of windows machine issue, Please try the suggestions provided in below link https://www.drivereasy.com/knowledge/how-to-fix-the-application-is-unable-to-start-correctly-0xc00007b-error/ https://geeksadvice.com/fix-the-application-was-unable-to-start-correctly-0xc000007b-error/

varul · ‎Oct 07, 2021

Please reach out to the support team who will be able to help you with this activation issue - you can contact them directly via phone using number provided at this link: they will help you to solve this quickly. https://community.flexera.com/t5/Support-Information/Support-Contacts/ta-p/94720 Alternatively there is an online chat available (Need to activate Let's chat) which you can find in a clickable box image on the right hand side here https://community.flexera.com/t5/InstallShield/ct-p/InstallShield

varul · ‎Oct 07, 2021

Did you install hotfix patch for IS2019R2 to fix digital signature issue. https://community.flexera.com/t5/InstallShield-Knowledge-Base/Digital-Signing-Patch-for-InstallShield-2015-SP2-and-above/ta-p/121641 We dont have any issue with respect with digital signature , so please check the certificate details entered are correct and make sure the pfx file used to sign is not expired.

varul · ‎Oct 07, 2021

You can also refer the kb article to write registry on 64 bit location https://community.flexera.com/t5/InstallShield-Knowledge-Base/Create-a-64-bit-Windows-Registry-Entry-via-an-InstallScript/ta-p/193440/jump-to/first-unread-message

varul · ‎Oct 07, 2021

Since its a upgrade license, you cant you use in IS2019, you can check the license available in your account in product license center, You can also reach out to the support team who will be able to help you with this activation issue and queries - you can contact them directly via phone using number provided at this link: they will help you to answer this quickly. https://community.flexera.com/t5/Support-Information/Support-Contacts/ta-p/94720 Alternatively there is an online chat available (Need to activate Let's chat) which you can find in a clickable box image on the right hand side here https://community.flexera.com/t5/InstallShield/ct-p/InstallShield

varul · ‎Oct 05, 2021

Could you please provide steps to reproduce this issue. so that we can check it from our end, and screenshot of the msi folder structure from where you adding the file, Why you are changing the target msi location under operation -->install--> filed. by default this value will be selected when you are adding the msi. (what is the value of this field when you add the msi package)

varul · ‎Oct 05, 2021

Sample code to update version in ism file using vbs: 'Path to ism file sPath = "C:\InstallShield 2021 Projects\Test.ism" 'creating object Set pProject = createObject("ISWiAuto27.ISWiProject") 'Set m_ISWiProject = CreateObject() 'Opening the ism file pProject.OpenProject sPath, True 'set project version to ism pProject.ProductVersion = "1.0.1" pProject.ProductCode="{AA6E6AAB-32DB-4CD6-B256-B46D0DDB1C51}" 'set project Cmpany name(Publisher) to ism pProject.CompanyName="VJFlexera" 'set the prod configuration which exists Set prodconf = pProject.ISWiProductConfigs("Product Configuration 1") 'set the Release which exists Set rel = prodconf.ISWIReleases.Item("Release 1") 'rel.SignatureDescription = "test" pProject.SaveProject 'Building the specific release rel.Build()

varul · ‎Oct 05, 2021

Hi, Try to pass the version using - y switch, at build time if you want to update the ism file, then try using our automation layer support to update the version https://docs.revenera.com/installshield26helplib/helplibrary/ISCmdBldParam.htm -y <product version> Advanced UI, Basic MSI, InstallScript MSI, Merge Module, Suite/Advanced UI This parameter enables you to specify a product version from the command line. This is especially helpful if you want to increment the build version (the third field) of the product version. For example, to set the product version to 1.0.5: ISCmdBld.exe -y "1.0.5" For information on valid product version numbers, see Specifying the Product Version . This parameter is optional.

varul · ‎Oct 05, 2021

You need to find the specific file which is holding the process, until the files process is stopped we wont be able to copy the files.

varul · ‎Oct 05, 2021

Could you please explain your use case, why you are moving this file from one folder to other? when you are doing this at the time of upgrading (like from upgrading from version1 to version2 time)

varul · ‎Oct 05, 2021

Hi, You have script to copy the folder before uninstall to new path? like C:\test to C:\test1 and on uninstalling the project custom created folder C:\test1 is getting deleted, is my understanding correct? If yes, could you please check is C:\test1 folder created is part of the ism, if yes, then its expected the folder will be deleted on uninstallation, if the folder is created by customaction then it wont uninstall, Could you please try the xcopy file function to copy the file to back up folder and see it works for you https://docs.revenera.com/installshield22helplib/Subsystems/installshield22langref/installshield22langref.htm#CSHID=helplibrary%2FLangrefXCopyFile_Example.htm|StartTopic=helplibrary%2FLangrefXCopyFile_Example.htm https://docs.revenera.com/installshield22helplib/Subsystems/installshield22langref/helplibrary/LangrefCreateDir_Example.htm? Hope it helps

varul · ‎Oct 05, 2021

What is your project type? Are you doing upgrade like when version1 is installed before installing verison2 you are creating backup of version1 is my understanding correct? If you are using the script as a customaction then you need to sequence it at app search of installexec sequence or any anything before uinstalling older version or updating older version. If you are using install script function , try on firstuibefore https://docs.revenera.com/installshield21helplib/Subsystems/installshield21langref/helplibrary/LangrefBeforeDataMoveHandlers.htm https://docs.revenera.com/installshield22helplib/Subsystems/installshield22langref/helplibrary/LangrefOnFirstUIBefore.htm

Online Status	Offline
Date Last Visited	‎Oct 21, 2021 08:37 AM

Re: RebootDialog launching setup in maintenance mode after system reboot

Running an Automation Script via the InstallShield SAB on a Windows Server Core Docker Image

Re: Installshield component getting installed even when feature is not selected

Re: libiomp5md.dll & The Application was Unable to Start Correctly (0xc000007b)

Re: Installshield 2021 concurrent license server

Re: 2019R3 - MSI - error -1027 signing SWIDTAG (signing OK with tag disabled)

Re: Installscript project: How to force registry to write to x64 section

Re: Can I use several single user upgrade licenses at same time on different machines?

Re: Target Package not found in project - Installshield Suite

Re: integrate InstallShield into teamcity build server.

Re: integrate InstallShield into teamcity build server.

Re: using XCopyFiles with open processes

Re: using XCopyFiles with open processes

Re: Disable logging to prevent files being removed during uninstallation

Re: Installshield unable to backup a folder before installing new files

Re: RebootDialog launching setup in maintenance mode after system reboot

Running an Automation Script via the InstallShield SAB on a Windows Server Core Docker Image

Re: Installshield component getting installed even when feature is not selected

Re: libiomp5md.dll & The Application was Unable to Start Correctly (0xc000007b)

Re: Installshield 2021 concurrent license server

Re: 2019R3 - MSI - error -1027 signing SWIDTAG (signing OK with tag disabled)

Re: Installscript project: How to force registry to write to x64 section

Re: Can I use several single user upgrade licenses at same time on different machines?

Re: Target Package not found in project - Installshield Suite

Re: integrate InstallShield into teamcity build server.