This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Knowledge Base
- :
- InstallShield 2014 Known Issues
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
InstallShield 2014 Known Issues
InstallShield 2014 Known Issues
Summary
This article documents known issues for InstallShield 2014.Synopsis
This article contains a list of hyperlinks to articles about known issues, workarounds, hotfixes, and related information for InstallShield 2014. The article will be updated as new information becomes available.Discussion
Issue Number | Description | Fix (if available) |
---|---|---|
IOJ-1660031 | "Unspecified Error" displayed in Visual Studio Japanese accessing InstallScript view | HOTFIX: "Unspecified Error" Displayed in InstallScript View When InstallShield Japanese is Integrated With Visual Studio |
IOJ-1661158 | Distributing Releases to a Virtual Machine that InstallShield Provisions at Build Time or on Demand does not work - Error 28: Out of stack space | |
IOJ-1663885 | Patch update.exe is not signed when specified to do so | As a workaround, find the appropriate ISPatchConfigurationProperty - SignaturePassword field in the direct editor and replace its value with the raw password. |
IOJ-1663062 | Major upgrade of an InstallScript/MSI project terminates unexpectedly | Run the major upgrade in compatibility mode. |
IOJ-1664081 | InstallScript system variables FOLDER_APPLICATIONS64 and PROGRAMFILES64 do not resolve correctly during uninstallation | |
IOJ-1665767 |
XML File Changes configured not to format target file leave target file formatted after uninstallation | |
IOC-000061592 | Setting a Component's .NET Precompile Assembly property to Yes uses .NET 1.1 command line values when project is configued to use later versions of the .NET framework | As a workaround, use a custom action to call ngen.exe with command line values appropriate for the targeted version of the .NET framework. |
IOJ-1667248 | CopyFile on locked file causes installation to hang | HOTFIX: CopyFile on Locked File Results in Installation Hanging |
IOJ-1720774 | Unable To Obtain New License From Trialware View | HOTFIX: Unable To Obtain New License From Trialware View |
IOJ-1721225 | InstallScript Project package fails during Suite installation | HOTFIX: Suite Fails with an InstallScript Project (.ism) Package |
IOJ-1726120 | The computer image on the left side of the InstallScript skinned dialog does not appear on the progress dialog | HOTFIX: No Image on the Left Side of the STATUSEX Dialog |
IOJ-1727555 | 64 bit system variables resolve to their respective 32 bit paths on an upgrade install where the base was created with an older version of InstallShield | HOTFIX: 64 bit System Variables Resolves to 32 bit Path During an Upgrade |
IOJ-1719756 | Properties contained in ISHiddenProperties and passed as arguments to the Suite launcher or to any packages are logged in plain text | HOTFIX: Properties contained in ISHiddenProperties and passed as arguments to the Suite launcher or to any packages are logged in plain text |
IOJ-1721173 | When attempting to use the "Distribute to VM" feature using InstallShield 2014 SP1 and supplying an invalid path, InstallShield will become unresponsive | HOTFIX: Distribute to VM with Invalid Path Results in InstallShield Becoming Unresponsive |
IOJ-1723088 | The install log is not getting created when the installation log location is set to a UNC path |
Additional Information
HOTFIX: "Unspecified Error" Displayed in Japanese Visual Studio InstallScript ViewHOTFIX: No Image on the Left Side of the STATUSEX Dialog
HOTFIX: CopyFile on Locked File Results in Installation Hanging
HOTFIX: Suite Fails with an InstallScript Project (.ism) Package
HOTFIX: Properties contained in ISHiddenProperties and passed as arguments to the Suite launcher or to any packages are logged in plain text
HOTFIX: Distribute to VM with Invalid Path Results in InstallShield Becoming Unresponsive
No ratings