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
- :
- Re: Help! Enable environment variable during installation
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
Aug 18, 2020
04:40 AM
Help! Enable environment variable during installation
Somebody can help the problem that I met.
I use installshield to install the ActiveMQ. At first, I create a system variables(JAVA_HOME) , then I invoked lauchAppAndWait launching a cmd.exe to create a mq broker.
But the windows don't allow same installation program to use new created variable JAVA_HOME .
I have to install it twice to enable this key.
Do you have any ideas to solve the problem ?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 18, 2020
11:48 AM
Hi @derek_shen ,
- Hope you have followed settings given here as per installation(On Install-set/create) requirement:
- What is the sequence of function you are calling lauchAppAndWait from Install-Execute,which you might see under Custom Actions->Sequence->Execution
- There is a custom action called "WriteEnvironmentStrings" which might be dealing with all the environment variable related settings
- You can keep the custom action you call cmd.exe after WriteEnvironmentStrings action.
Thanks,
Jenifer
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 20, 2020
06:21 AM
@Jenifer wrote:Hi @derek_shen ,
- Hope you have followed settings given here as per installation(On Install-set/create) requirement:
- What is the sequence of function you are calling lauchAppAndWait from Install-Execute,which you might see under Custom Actions->Sequence->Execution granny
- There is a custom action called "WriteEnvironmentStrings" which might be dealing with all the environment variable related settings
- You can keep the custom action you call cmd.exe after WriteEnvironmentStrings action.
Thanks,
Jenifer
Thank you so much for your help.