Summary Error 1315: Unable to write to the specified folder (shared folder) error is observed when performing a major upgrade or removing an installed target application from a shared location. Project Types Basic MSI InstallScript MSI Symptoms Error 1315: Unable to write to the specified folder (shared folder) is observed when performing a major upgrade or removing a setup that is already installed at a shared location. Cause Error 1315 is observed on Windows 10 machines where Windows Update KB4551762 is installed. Resolution: To avoid Error 1315, make sure that the latest Windows updates are installed, specifically Windows updates released after Windows update KB4551762. Reference: A forum post that discusses this issue. ... View more

Summary Error 7354 occurs when building a project with a shortcut or feature or string name with more than 8 characters. -7354: The English (United States) value for string 'ID_STRING2' does not contain a legitimate value for table Directory column DefaultDir   -7354: The English (United States) value for string 'ID_STRING3' does not contain a legitimate value for table Shortcut column Name Project Types Basic MSI InstallScript MSI Express Project Cause Error 7354 was added to InstallShield 2016 and higher builds due to Microsoft string validations that were previously missing. Error 7354 occurs when InstallShield attempts to create any string with more than 8 characters on a machine where NtfsDisable8dot3NameCreation is not enabled. Resolution: The user needs to enable the NtfsDisable8dot3NameCreation option on the machine. A Windows short name has 8 characters for the name and 3 characters for the file extension. Windows long names exceed 8 characters for the name. The suggested resolution works by enabling Windows short names. Follow these steps: Click Start > Run. Enter regedit and click OK. In the Windows Registry Editor, go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem Right-click the NtfsDisable8dot3NameCreation entry. Select Modify from the drop-down menu. The Edit DWORD Value dialog opens. In the Value data textfield, enter: 2 Click OK to close the dialog. You should see a message as follows: The registry state of NtfsDisable8dot3NameCreation is X... State Values: 0 = 8.3 file creation is enabled on all volumes on the system 1 = 8.3 file creation is disabled on all volumes on the system 2 = 8.3 file creation is enabled per volume on the system (default) 3 = 8.3 file creation is DISABLED on all volumes except the system volume Reference: A blog post about NtfsDisable8dot3NameCreation. A StackOverflow post about Windows short names. Microsoft documentation about Windows short versus long names. Microsoft documentation about Windows long names. ... View more

Summary When installing suite setup.exe, the suite installation fails with Error 8002000a. This error usually happens during an upgrade. Project Type Suite/Advanced UI Cause The Error 8002000a indicates an out of present range error. This means the version used in a package included in the suite installer is not correct and the version exceeds the allowed version range set by Microsoft. Resolution To fix this issue, use a valid version which is within the range specified by Microsoft rules. Valid version numbers cannot exceed the following values: File version: 65535.65535.65535.65535 Product version: 255.255.65535 Reference VERSIONINFO Resource ProductVersion Property ... View more

Summary Set All Component 64bit option to “YES “using Installshield Automation Interface script   Symptoms In a project which contains a large amount of components changing  64bit option to YES manually is time consuming. Resolution It is possible to use Installshields Automation Interface functionality to automate this process.  The example below uses  vbscript code to set all the component 64 bit option to YES. You can run the script using vbs editor or you can run the script using “wscript.exe” in cmdlet. Path to wscript.exe “C:\Windows\System32>wscript.exe”   'Create project object for InstallShield 2019 Set pProject = CreateObject("ISWiAuto25.ISWiProject") 'Open project your project ism file pProject.OpenProject "<Path to ISM File>" 'set 64 bit option to YES for single component Set pComponent = pProject.ISWiComponents.Item("<Your Component name>") pComponent.Attrib64BitComponent = "True" 'Set 64 bit option to YES for all component in ISM Set pComponent = pProject.ISWiComponents ‘Msgbox pComponent.Count For Each pComponent in pProject.ISWiComponents 'Setting Component to 64bit pComponent.Attrib64BitComponent = "True" 'Setting Dot Scan option to None pComponent.DotNetScanAtBuild = 0 Next 'Adding a Product Config and Release pProject.AddProductConfig("Prod config").AddRelease("Release") 'Set an existing product configuration Set productconfig = pProject.ISWiProductConfigs.Item("Prod config") 'Set and existing release Set Release = productconfig.ISWiReleases("Release") 'Build the release Release.Build() 'Save and close pProject.SaveProject pProject.CloseProject   Reference Link: https://docs.flexera.com/installshield24helplib/installshield24helplib.htm#helplibrary/IHelpAutoISWIComponents.htm ... View more

Symptoms:           “Feature Transfer Error:142” Observed on installing Installscript created setup.exe Diagnosis:   This information applies to the following InstallShield project types: InstallScript  When we set a password for setup.exe from release view but not setting the dialog “Show password Dialog” to NO and creating the setup.exe. on installing the setup.exe user will see an error “Feature Transfer Error:142”   Solution:  To avoid error “Feature Transfer Error:142”, make sure you remove the password from the setup.exe à password filed on releases view. Else if you want to continue using password then make sure you set the field “Show password Dialog” to YES Then you will get a dialog to enter the password   Reference: https://community.flexera.com/t5/InstallShield-Knowledge-Base/How-Do-I-Password-Protect-My-Setup/ta-p/4110/jump-to/first-unread-message ... View more

Description   Error 6118 occurs while building a InstallScript MSI project with custom action added for DetectIIS6Interfaces Replication Scenario   The InstallscriptMSI project migrated from IS2016 has “IISbrowsecertificate” dialog gets added on migration, and along with that user adds Cutomaction for DetectIIS6Interfaces which is causing the error 6118   Workaround   Go to Dialogs  and Check for Presence of IISBrowsecertificate dialog and delete the dialog, then rebuild the project. Version Fix Target   Work order has been raised and accepted by engineering. The master issue number is  IOJ-2112218 Resolution Manually deleting "IISBrowsecertificate" dialog from the dialog view will help in avoid the error 6118. ... View more