bikeoid asked a question.
It appears that it cannot contact servers online because of TLS protocol changes.
I have tried the de-register and register offline, but the results are rejected. Is it possible to activate the license on a new computer after deactivating on the old one?
h.jansen@anva.nl asked a question.
Hello, suddenly InstallShield started to generate more than 1 cab file for my MSI project (data1.cab and data11.cab), although it only has less than 3k files, none of the files are anywhere near 2GB and the CAB size should not be larger than 636MB. So, why is that?
Next, when running the installer, it doesn't seem to switch cab files, after the last file from the first cab has been deployed, I get the following:
...
MSI (s) (80:7C) [16:43:38:156]: Executing op: ChangeMedia(MediaVolumeLabel=DISK1,MediaPrompt=Please insert the disk: 1,MediaCabinet=Data11.cab,BytesPerTick=65536,CopierType=2,ModuleFileName=C:\WINDOWS\Installer\217a17.msi,,,,,IsFirstPhysicalMedia=1)
Action ended 16:43:38: InstallFinalize. Return value 3.
MSI (s) (80:7C) [16:43:38:234]: Note: 1: 2265 2: 3: -2147287035
...
And the install rolls back, ultimately ending with:
...
MSI (c) (58:6C) [16:43:48:549]: Note: 1: 1708
MSI (c) (58:6C) [16:43:48:549]: Product: ONYX -- Installation operation failed.
MSI (c) (58:6C) [16:43:48:549]: Windows Installer installed the product. Product Name: .... Product Version: .... Product Language: 1033. Manufacturer: .... Installation success or error status: 1603.
...
Suggestions welcome
Meanwhile I found the CompressedNetworkCABSize setting (which appears to default to 600MB): I turned off the splitting, so I can continue.
But in case of future need, I wonder why the installer didn't continue with the other CAB file. I confirmed it to be part of the MSI and I wonder whether InstallShield generated faulty data in the Media table (not sure whether it matters, but could duplicate DiskPrompt and/or VolumeLabel entries confuse the installer service?):
DiskId LastSequence DiskPrompt Cabinet VolumeLabel Source
1 2941 1 #Data1.cab DISK1
2 2953 1 #Data11.cab DISK1
misterjo asked a question.
Hello,
I have installed InstallShield 2026R1 on a Windows Server 2016 with VisualStudio 2015. There is already an InstallShield 2015 LE installed with a broken license. If I start the application it happens nothing. There is only an application log in Windows Event-Log:
Faulting application name: isdev.exe, version: 32.0.0.68, time stamp: 0x6a486a53
Faulting module name: KERNELBASE.dll, version: 10.0.14393.9140, time stamp: 0x69fb5476
Exception code: 0x80000003
Fault offset: 0x001548c2
Faulting process id: 0x1e8
Faulting application start time: 0x01dd41e55e3226c4
Faulting application path: C:\Program Files (x86)\InstallShield\2026\system\isdev.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 324d2af8-a048-4390-acae-8c928a43b830
Faulting package full name:
Faulting package-relative application ID:
As long it is the very first start-up after the installation, I would expect that a dialog would popup to ask for the license. But nothing happens.
It would be nice if someone could help me with that problem.
Br,
misterjo
Hi Joachim,
Thank you for your response.
We have raised a support request for your requirement and the case number for your reference is 05097001.
We will be assisting you further through the case. Please respond back to the case email with requested details.
Regards,
Sunil.
kusakata@fsi.co.jp asked a question.
We are using InstallShield 2025 R2 to create a Basic MSI project.
We created a custom action by selecting the following option in the Custom Action Wizard:
Call a public method in a managed assembly
The managed assembly is stored in the Binary table.
We expected this custom action to use the .NET Framework CLR. However, a crash dump captured during execution indicates that the InstallShield-generated custom action wrapper is attempting to start the .NET 8 CoreCLR runtime.
The relevant call stack is as follows:
Ijwhost!start_runtime_and_get_target_address Ijwhost!start_runtime_thunk_stub CoreClrNativeHelper!CallCoreMethod MSI278F+0x3018 msi!CallCustomDllEntrypoint
The dump also contains the following module information:
IMAGE_NAME: Ijwhost.dll IMAGE_VERSION: 8.0.1825.31117 OSPLATFORM_TYPE: x86
Based on this information, it appears that the InstallShield-generated wrapper is using the 32-bit .NET 8 CoreCLR runtime rather than the .NET Framework 4.x CLR.
We would like to execute the custom action assembly using .NET Framework 4.8 instead of .NET 8.
Does anyone know whether this is the expected behavior in InstallShield 2025 R2?
We would also appreciate any information regarding the following questions:
For reference, the custom action assembly is intended to target .NET Framework 4.8.
If anyone has encountered the same behavior or knows the supported method for executing a .NET Framework 4.8 assembly as a managed custom action in InstallShield 2025 R2, any advice would be greatly appreciated.
Screenshots of the custom action configuration and the crash dump analysis results are attached.
Superfreak3 asked a question.
Currently, we use a small utility that makes use of Windows scripts to embed language transforms into our .msi package. The scripts are wilanguid and wisubstg.vbs. So, once embeded, the install can be called like this to show the different languages....
msiexec .i path\to\installer.msi TRANSFORMS=:languageId
The colon indicates that the transform is embedded I believe.
My question is, is there a release option in the InstallShield IDE to automatically embed the transforms as opposed to the need to maintain the external utility?
If not, that would be a fairly nifty option to have I think.
Any help or guidance appreciated.
Thanks in advance!!
AgostinoSturaro asked a question.
ISDEV-45022 --> CVE-2026-4869--> Fixed in IS2026R1,
This CVE is initally reported for IS2023R2, with CVE-2024-7562
we have another sceurity issue(ISDEV-44981) reported over the same IS2023R2 hotfix with same CVE which is fixed over the same CVE-2024-7562, It's fixed in IS2026R1.
Please test it, if you still face any issue with related to the work order and CVE, you can raise a support ticket.
ayKoike asked a question.
@AgostinoSturaro : You can find the details of the cve in below KB article
You can find the hotfix for 2025R2 for this specific CVE in our product and license center
Are you sure you want to cancel the case creation?
Activity: Status change: 2 hours ago
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Hi Mike,
Thank you for contacting us.
InstallShield 2012 has reached end-of-life and there is no activation / technical support available for this product.
The InstallShield Activation Service has been discontinued, and this was announced back on February 2, 2022.
We recommend you try our latest version of InstallShield, which is version 2026 and check if it meets your requirement. You can download our trial software from below link:
https://info.revenera.com/IS-EVAL-InstallShield-Premier
Please go through the attached document for more information on upgrade and sales contact.
Regards,
Sunil.
Revenera Support.