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
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Strange issue on Japanese OS
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
‎Jul 28, 2010
11:18 AM
Strange issue on Japanese OS
Hello,
I am using InstallAnywhere 8 enterprise edition to install one of our products on a windows server 2003 Japanese OS.
There is a utilit which is packaged in one of the merge modules and is included in our installer. The utility is extracted during the install time and copied to Program Files directory. Upon copying, it is executed from Program Files directory. However what is strange is that the utility execution operation from InstallAnywhere is failing. The logs suggest that Program is not recognized, which indicates that the execution is failing as a result of spaces with the path(Program Files). However if i execute the same manualy from the command line without enclosing the path in double quotes, the utility executes sucessfully.
What could be wrong here? I am stuck. Please help.
I have inspected teh server and the server is configured to use short path names(8.3 registry setting).
What are the next steps i could try? Any help would be very much appreciated.
Regards,
Kiran Hegde
I am using InstallAnywhere 8 enterprise edition to install one of our products on a windows server 2003 Japanese OS.
There is a utilit which is packaged in one of the merge modules and is included in our installer. The utility is extracted during the install time and copied to Program Files directory. Upon copying, it is executed from Program Files directory. However what is strange is that the utility execution operation from InstallAnywhere is failing. The logs suggest that Program is not recognized, which indicates that the execution is failing as a result of spaces with the path(Program Files). However if i execute the same manualy from the command line without enclosing the path in double quotes, the utility executes sucessfully.
What could be wrong here? I am stuck. Please help.
I have inspected teh server and the server is configured to use short path names(8.3 registry setting).
What are the next steps i could try? Any help would be very much appreciated.
Regards,
Kiran Hegde
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 29, 2010
01:35 AM
If I'm not mistaken, historically, IA had troubles installing in path that contain non-alphanumeric characters (I think it choked on a ! in the path, let alone Japanese characters).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 29, 2010
11:47 PM
Thanks for the response.
However this is happening on only 2 Japanese OS, not everywhere.
What could be wrong?
How do i generate a verbose log?
How do i debug problems with InstallAnywhere?
What are the next debugging steps i could use?
Any help would be very much appreciated.
Also if someone is aware as to what windows API is called during launching an executable operation, could you please let me know?
I want to use the same API using a test program and see if it is working.
Regards,
Kiran Hegde
However this is happening on only 2 Japanese OS, not everywhere.
What could be wrong?
How do i generate a verbose log?
How do i debug problems with InstallAnywhere?
What are the next debugging steps i could use?
Any help would be very much appreciated.
Also if someone is aware as to what windows API is called during launching an executable operation, could you please let me know?
I want to use the same API using a test program and see if it is working.
Regards,
Kiran Hegde
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 03, 2010
05:10 PM
So you mean it happens only on 2 machines with Japanese OSes, but not on all machines? Are the installation steps exactly the same as for the rest of the machines for which it works? Maybe there's something wrong with these two machines?
There aren't too many ways to debug an IA installation: you've got a Debug Output action which writes information in a log file.
You mentioned an API but I'm not sure I understood in what way it is related to your issue.
There aren't too many ways to debug an IA installation: you've got a Debug Output action which writes information in a log file.
You mentioned an API but I'm not sure I understood in what way it is related to your issue.