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: $ not accepted as part of a password
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Jun 12, 2012
12:52 PM
$ not accepted as part of a password
Hi,
I have a problem using $ as part of a password during "get user input".
For example, when I enter Pa$$word123 as the password and immediately display the password, the InstallAnywhere displays Paword123, so it removes 2 $$ in the input.
Is there a way to let InstallAnywhere accept $ in the password?
Thanks a lot for your help.
I have a problem using $ as part of a password during "get user input".
For example, when I enter Pa$$word123 as the password and immediately display the password, the InstallAnywhere displays Paword123, so it removes 2 $$ in the input.
Is there a way to let InstallAnywhere accept $ in the password?
Thanks a lot for your help.
(7) Replies
Jun 12, 2012
06:26 PM
I did more testing. If there is 1 $ in the password, it worked, but if I have 2 $ together, it didn't work.
It seems to me that this is a bug in InstallAnywhere. It should definitely be fixed.
Let me know if I am wrong.
Thanks for your help in advance.
It seems to me that this is a bug in InstallAnywhere. It should definitely be fixed.
Let me know if I am wrong.
Thanks for your help in advance.
Jun 13, 2012
01:39 PM
Hi,
My case is that during "Get User Input", the password was entered as Pa$$word123, then I will use it in a text file.
Thanks Jerome for the hint. I tried to use "Modify Text File" with “Substitute InstallAnywhere variables in file” unchecked, but that seemed not doing the trick.
Is it too late to modify the variable in a text file after "Get User Input" since both $ was already removed.
Thanks.
My case is that during "Get User Input", the password was entered as Pa$$word123, then I will use it in a text file.
Thanks Jerome for the hint. I tried to use "Modify Text File" with “Substitute InstallAnywhere variables in file” unchecked, but that seemed not doing the trick.
Is it too late to modify the variable in a text file after "Get User Input" since both $ was already removed.
Thanks.
Jun 13, 2012
03:32 PM
Hi,
As I mentioned in my own reply below, it seemed that it is too late to modify the variable in a text file after "Get User Input" since both $ was already removed during "Get User Input" time.
So it seems to me that my only option is to go with 2011 version.
Jerome, can you help confirm this before I escalate this issue?
Thank you very much.
As I mentioned in my own reply below, it seemed that it is too late to modify the variable in a text file after "Get User Input" since both $ was already removed during "Get User Input" time.
So it seems to me that my only option is to go with 2011 version.
Jerome, can you help confirm this before I escalate this issue?
Thank you very much.
Jun 14, 2012
03:20 AM
Yes, I think you really need to upgrade to version 2011.
http://kb.flexerasoftware.com/doc/Helpnet/IA2011/Content/helplibrary/ia_setting_vars.htm#advanced_solutions_3164012938_1167674
--Jerome
http://kb.flexerasoftware.com/doc/Helpnet/IA2011/Content/helplibrary/ia_setting_vars.htm#advanced_solutions_3164012938_1167674
--Jerome
Jun 14, 2012
12:49 PM
Thanks, Jerome.
I downloaded 2011 version yesterday and did some testing through a simple project. It worked. 🙂
I am escalating the issue and hopefully I can get the upgrade.
BTW, I am so surprised that the issue wasn't fixed until 2011 version. It's hard to believe nobody else had the same issue long before.
Thanks again for your help.
I downloaded 2011 version yesterday and did some testing through a simple project. It worked. 🙂
I am escalating the issue and hopefully I can get the upgrade.
BTW, I am so surprised that the issue wasn't fixed until 2011 version. It's hard to believe nobody else had the same issue long before.
Thanks again for your help.