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 Forum
- :
- I'm glad to found this problem by your side.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 15, 2016
08:31 PM
Bug Japanese resources
Hi,
I tried to use InstallShield 2016 in my environment.
I'm just upgrade my setup from 2015 to 2016.
But that setup does not work correctly. The setup will terminate with error message "Error -1639 Invalid command argument."
The kind of project type is "InstallScript MSI project".
I tried a couple of things to find out the condition to happened this problem,
When I set the Build parameter at Media-Releases menu, that combination are below.
Compression - Compressed
UI Languages - English (United States), Japanese
When I add Japanese UI Languages, the error will happen every time.
If I remove the Japanese UI Language from this parameter, that will complete installation normally.
When I use 2015 version, it is not occurred.
Is it bug for 2016 version?
Thank you,
Mitch
I tried to use InstallShield 2016 in my environment.
I'm just upgrade my setup from 2015 to 2016.
But that setup does not work correctly. The setup will terminate with error message "Error -1639 Invalid command argument."
The kind of project type is "InstallScript MSI project".
I tried a couple of things to find out the condition to happened this problem,
When I set the Build parameter at Media-Releases menu, that combination are below.
Compression - Compressed
UI Languages - English (United States), Japanese
When I add Japanese UI Languages, the error will happen every time.
If I remove the Japanese UI Language from this parameter, that will complete installation normally.
When I use 2015 version, it is not occurred.
Is it bug for 2016 version?
Thank you,
Mitch
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 16, 2016
09:47 AM
It's not reproducible on my end. I created a very simple InstallShield 2015 SP1 project with the English and Japanese support that installs a single executable file, and then migrated into InstallShield 2016. The compressed setup installed successfully without any errors. Did you make any modifications to your project after upgrading to InstallShield 2016?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 16, 2016
04:35 PM
We found reproduction steps and are working on creating a fix for it. I will post more information when the fix is ready to go.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 28, 2016
02:13 AM
Hi Hidenori,
Thank you for your reply and for you found out this problem.
I didn't change the project after converting from IS2015 SP1 to IS2016.
Anyway, I stop the upgrade for all of my project right now, and I will be waiting until fix this problem.
Thanks again,
Mitch
Thank you for your reply and for you found out this problem.
I didn't change the project after converting from IS2015 SP1 to IS2016.
Anyway, I stop the upgrade for all of my project right now, and I will be waiting until fix this problem.
Thanks again,
Mitch
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 23, 2017
02:57 PM
I'm pleased to announce that InstallShield 2016 SP1 is released today. This issue has been tracked under IOJ-1741435 and fixed in the service pack.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 31, 2017
11:51 PM
I am installing the Sp1 on my environment and I confirmed it. It problem is gone.
Thanks a lot.
Mitch
Thanks a lot.
Mitch
hidenori wrote:
I'm pleased to announce that InstallShield 2016 SP1 is released today. This issue has been tracked under IOJ-1741435 and fixed in the service pack.