Hi @Kemshamj ,
Usually the file is determined from the path you have added the files
For EX: if you have added files from C:\test\data path, the file will be available in the ism with proper size,
If the path C:\test\data is not exists or the files inside the data folder doesnt exists then it will show as a 0 size
So please check the path <path_to_3.7_Files> have file exists or not,
You can check path of path_to_3.7_Files under path variable, Please refer attached screenshot.
Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO".
... View more
Hi @Sattibabu ,
If you upgrade to IS2023R1 or R2 you are still seeing this issue? since this issue is fixed in our IS2023R1, Please upgrade and then try once.
Are you able to see the setup installation error on test project as well, meaning if you create a test project with "No" option on installing you are seeing the error
ERROR: error reading setup initialization file
If yes, I suggest you to please raise a case and add your issue description and our support engineering will be able to assist further on this issue,
... View more
Hi @Sattibabu
What is your project type? Basic MSI?
Is your project release --> setup.exe tab --> include msi engine set to YES.
If it set to YES change it to NO and then try again,
And we have this issue fixed in our IS2023R1, You can refer below release notes for issue number "ISDEV-42950"
https://docs.revenera.com/installshield/rn/Content/helplibrary/InstallShield_2023_R1_1.htm#isreleasenotes_4268113285_1264397
... View more
You can add supporting OS using our project assistant tab, and the condition will added automatically, May i know what is your project type, i have explained below for Basic MSI project type
First select view tab and enable project assistant tab,
Then select the project assistant tab, and select installation requirement tab at the bottom row,
Then you will see supported OS, options you can select the OS you are supported,
Then go to Installation designer tab, you can see the installation condition added.
please refer screenshot attached.
... View more
Thanks for explaining the issue,
I have investigated and found the issue is due to the registry value changes in 8.0.32 version
The registry for 8.027 the registry path has / added after MySQL Connector/NET
However in 8.0.32 the / option is removed and the registry has path MySQL Connector NET
which causes this issue, so you need to check for any other registry which is unique for both 8.0.27 and 8.0.32, or try with file exits with version option.
Refer the screenshot attached for your reference.
... View more
What do you mean by 8.0.32 png,
Could you please explain your scenario,
Is your machine is installed with 8.0.32 and your prq is different version included,
Did you tried with the prq i have shared? if not please try with the prq i have shared
... View more
Hi @rmcgee @vinhpx
We have created the requested prq files, and attached here, please download and extract it to your installshield install directory SetupPrerequisites folder
Did my reply solve the issue? Please Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something?
And please Click "KUDO".
... View more
Hi @najnug_inias ,
Please try the attached prq file and verify it works or not, we have tested locally, it working as expected, make sure you copy the mysql msi file under setupprerequisites folder under installshield directory, refer screenshot.
Did my reply solve the issue? Please Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something?
And please Click "KUDO".
... View more
Introduction
This article discusses how to successfully activate the InstallShield Standalone Build (SAB) inside a Docker Container with a Cloud License Server (CLS) ID license.
Instructions
To enable the CLS ID within a Docker container, it's necessary to generate a registry and include the CLS ID by creating a registry key.
Once Docker Images are created, log in with the docker run command. Please refer to the Knowledge Base (KB) article in the More Information Section of this article.
Once logged into Docker, run the following command: reg add "HKCU\SOFTWARE\InstallShield\29.0\Professional" /v LicenseServerCLS /t REG_SZ /d "https://flexerasoftware.compliance.flexnetoperations.com/instances/CLSID"
Replace CLSID with your CLSID (For example: QXXIAE24EIPJ) and then press enter. Please refer below screenshot.
Try to build the project using IsCmdBld.exe and verify that the build is successful.
If the build still fails, please create the following Windows Registry entry to create a Installshield.log: reg add "HKCU\SOFTWARE\InstallShield\29.0\Professional" /v DoVerboseLogging /t REG_DWORD /d 1
Please change the number (see above) 29.0 to match your InstallShield version installed in Docker (For example, for InstallShield 2022, the version is 28.0 and, for InstallShield 2023, the version is 29.0)
Build the project again and a log file will be created under the <InstallShield_Home>\System folder where <InstallShield_Home> is where InstallShield is installed (For example: C:\Program Files (x86)\InstallShield\2023 SAB\System).
A log file named "InstallShield.log" will be created under System folder.
Check the failure log details and try the KB article suggestions below if the failure is for an SSH certificate.
More Information
Click here for more information about installing the InstallShield SAB inside a Docker Container.
Click here for more information about running an automation script inside a Docker Container.
Click here for error on CLS - Failed to connect the CLS server - SSL peer certificate or SSH remote key was not OK
... View more
Hi @ClarksonsCmail ,
Good to hear it worked,
Did you mean to say you are seeing a license error now, like SDEV : fatal error -7159:
How you have activated your SAB, using license file? or connected to license server?
As per the error, its not activated, You can confirm by doing a command line build by following below steps,
Open cmdlet in administrator mode, navigate to system path and try to build a sample ism file and verify it builds without any error or not,
C:\Program Files (x86)\InstallShield\2023 SAB\System\IsCmdBld.exe" -p "<path to ism>"
If you see the same error, then SAB2023 is not activated, Please try to activate again and then verify build again.
If you still face same error, even after successfully activation,
Please reach out to the support team who will be able to help you with this activation or license 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
... View more
Hi @ClarksonsCmail ,
You need to change the automation layer dll version,
Try to change your automation object from ISWiAuto21 to ISWiAuto29
From:
$comProjectObject = New-object –com ISWiAuto21.ISWiProject
To
$comProjectObject = New-object –com ISWiAuto29.ISWiProject
You need to change this dll version as per the installshield version you are using.
https://community.flexera.com/t5/InstallShield-Knowledge-Base/Build-a-Project-Using-the-Automation-Interface/ta-p/3545
Please try it and let us know it works or still you are facing an issue.
... View more
Introduction
This article discusses how to successfully build in a Docker Container with a Cloud LIcense Server (CLS), especially in a Windows servercore:ltsc2019 image:
The build fails due to an SSL certificate not being available or not having been updated inside the Docker Container.
9-28-2023[11:38:12 AM]: CLS - Failed to connect the CLS server - https://flexerasoftware.compliance.flexnetoperations.com/instances/[CLSID]/request: [[1,7e4,7,0[75000001,60,3001025c]] General data transfer failure. SSL peer certificate or SSH remote key was not OK
Instructions
To address this problem, the solution involves exporting certificates from the local machine, saving them as an SST file, then importing them into the Docker Container.
Export the certificate from your local machine using following PowerShell command in an opened instance of PowerShell ISE: Get-ChildItem -Path cert:\LocalMachine\Root | Export-Certificate -FilePath c:\Test\TrustedRootCertBackup.sst -Type SST
Copy the backup .sst file to folder shared with the Docker Container.
Log into the Docker Container with an active session.
Launch the Docker Container in PowerShell Mode using the following command: docker run -it -v "C:\ISDockerBuild:C:\Test" installshield-sab2023r1 powershell
Once the Docker Container is started, run the following command and make sure the .sst file is available in the shared folder.
Import the certificate using the following command: Import-Certificate -FilePath C:\test\TrustedRootCertBackup.sst -CertStoreLocation Cert:\LocalMachine\Root
Try to build the project with the build command (ISCmdBld.exe).
The build will succeed.
More Information
Click here for more information about using Dockerfiles on Windows.
... View more
Introduction
This article details the process of generating desktop shortcuts within an MSIX project using the Package Support Framework (PSF).
By default, MSIX packages don't inherently support the installation of a desktop shortcut due to Microsoft's limitation on user-driven preferences. Therefore, actions such as creating a Desktop shortcut or pinning it to the Taskbar or Start Menu are beyond the user's direct control.
However, if you still need to deploy an application shortcut on a user's Desktop through an MSIX package, there is a option available. In this article, we'll explore that option to accomplish this task.
Instructions
Configure the MSIX package to support "Application alias" package. To do that, follow the steps below:
Create a MSIX project.
Add your .exe file under the Files and Folder View > INSTALLDIR.
Go to the Applications View and create a shortcut for the newly added .exe file.
Select the Key Name field on righthand pane.
Rename it to the same name as the shortcut name:
Go to Declarations.
Right-click then add "New Declaration set."
"Declaration Set 1" will be added.
Right-click on "Declaration Set 1."
Add a "New Custom Declaration."
On the righthand pane, select the Namespace field dropdown menu then select "Xmlns:uap3= , and xmlns:desktop=" as shown below:
12. Select the XML content field then enter the code below and rename the Executable name and Executable alias name:
<uap3:Extension
Category="windows.appExecutionAlias"
Executable="[ExecutableName]"
EntryPoint="Windows.FullTrustApplication">
<uap3:AppExecutionAlias>
<desktop:ExecutionAlias Alias="[AliasName]" />
</uap3:AppExecutionAlias>
</uap3:Extension>
13. Go to the Application View and select the Declaration field and select the newly added Declaration above: 14. Save then build the project and install the MSIX package that gets created. 15. Make sure the shortcut is created in the Start Menu. 16. Press Win+R then type the application name and check that your application launches successfully, which means the alias exe shortcut was created successfully:
17. Go to the user's Desktop then right-click and select New --> Shortcut and enter your exe name and click Finish: 18. A new shortcut with the name, provided in the dialog above, will be created on the user's Desktop. 19. Right-click the Desktop shortcut then select Properties --> and select the shortcut tab. 20. Change the target path field and start in field to the LocalAppData path as shown below: 21. Copy your icon file to folder path under LocalAppData --> package --> Roaming where our application folder is created with the product name and random ID. For example: C:\Users\Administrator\AppData\Local\Packages\MSIXTestShortcut_d14rjvjqp047y\LocalCache\Roaming:
22. Click the change icon button and change the icon from above copied to the LocalAppData Roaming folder path:
23. Click OK then Finish and close all dialogs. Now, we have a new Desktop shortcut with an icon created. 24. Now, we have to automate this process using PowerShell in the Package Support Framework (PSF). 25. Copy the icon file and the newly created shortcut in to our test data folder as shown below: 26. Add the value copied from above to the project .ism file > INSTALLDIR: 27. Download the attached ZIP files then extract them and paste them into the same test data folder (the .json file, createshortcut.ps1 file, and the StartingScriptWrapper.ps1 file). 28. Edit the .json file and change the executable name to your exe name and edit the id and change the shortcut to the "Key Name" field value. 29. Save then close the jason file. 30. Now, open our MSIX package's project .ism file then go to the Application View --> Select the shortcut created and select Fixup Type under "Package Support Framework." 31. Click on the + icon then select Custom Fix Up:
32. Set Architecture to x86 and the .json path to the test data folder where the .json file was copied to:
33. Now edit the createshortcut.ps1 file then change the path and name of the file, per the shortcut and .ico file that was created. Save and close the powershell script file:
34. Go to the Files and Folders View and add both StartingScriptWrapper.ps1 and createshortcut.ps1 in to our project's INSTALLDIR 35. Select the Root Node (the Destination computer node) then add the JSON file config.json and save the project .ism file:
36. Save and Build the project. 37. Install the newly built MSIX package. 38. Observe a desktop shortcut is created when launching your application, which runs the PowerShell script to create the Desktop shortcut.
NOTE:
Make sure all machines have the remote execution policy enabled to run a PowerShell script without any issues.
The workaround installs a conventional .lnk desktop shortcut rather than a contemporary application entry.
The script is triggered only after the application is initiated, allowing the Desktop shortcut to be copied.
The MSIX uninstallation process does not include the removal of Desktop shortcuts, necessitating a separate action to address this, which is currently not supported using script as well.
Inadvertently deleting the Desktop shortcut won't be resolved by repairing the MSIX package, as it won't automatically restore the shortcut. Reinstallation after uninstallation of the MSIX package is necessary to recover the Desktop shortcut.
More Information
Click here for Microsoft PSF help link.
Click here for Microsoft documentation on how to create a desktop shortcut.
... View more
Introduction
This article explains the process of deleting or disabling a scheduled task before installing with a new installer using a Custom Action in an InstallScript project.
Instructions
When installing with a new installer, if an existing scheduled task is running, the installer will fail to created a new task. In order to create a scheduled task without any issues, first, we should disable or delete the existing scheduled task running on the target machine.
Please follow the steps below to delete or disable an existing scheduled task.
Create an Installscript project.
Add files under the Files and Folders View.
Go to the InstallScript View under Behavior and Logic.
Select the setup.rul.
Select the righthand pane.
Add the following InstallScript code:
function OnBegin()
STRING szMyPath, szCmdPath, szMyCmd, svProgramData, szMyPath2, szCmdPath2, szMyCmd2;
NUMBER nvBufferSize;
begin
szMyPath2 = "\"" + "for /f %x in ('schtasks /query ^| findstr test') do schtasks /Delete /TN %x /F" + "\"";
szCmdPath2 = WINSYSDIR ^ "cmd.exe";
szMyCmd2 = "/c " + szMyPath2;
MessageBox("szMyPath2=" + szMyPath2, INFORMATION);
MessageBox("szCmdPath2=" + szCmdPath2, INFORMATION);
MessageBox("szMyCmd2=" + szMyCmd2, INFORMATION);
LAAW_SHELLEXECUTEVERB="runas";
LaunchApplication(szCmdPath2, szMyCmd2, "", SW_HIDE, INFINITE, LAAW_OPTION_USE_SHELLEXECUTE | LAAW_OPTION_WAIT);
end;
A working sample project that demonstrates this functionality is attached to this article.
More Information
Click here to access the InstallScript Language Reference.
... View more
