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
- :
- executing visual basic script
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
Dec 31, 2007
02:48 PM
executing visual basic script
I'm not sure what I'm doing wrong. I have a post-install action defined that is intended to create a user. I wrote a vb script that takes care of creating the user (and works fine when I run it from the command line outside of IA2008).
I'm trying to launch "cscript $USER_INSTALL_DIR$\config\createuser.vbs username userpassword". I'm not sure what is happening - but when the install completes, I do not have my user created. I don't think the vbscript is ever executed (I added trace message to output to a text file if it's hit - never see this).
My other post install tasks execute correctly. However, they are all calling executables and not a vbscript.
Any ideas on this? I also tried sticking the commands in a bat file and calling it. It is not working for me either.
I'm trying to launch "cscript $USER_INSTALL_DIR$\config\createuser.vbs username userpassword". I'm not sure what is happening - but when the install completes, I do not have my user created. I don't think the vbscript is ever executed (I added trace message to output to a text file if it's hit - never see this).
My other post install tasks execute correctly. However, they are all calling executables and not a vbscript.
Any ideas on this? I also tried sticking the commands in a bat file and calling it. It is not working for me either.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 04, 2008
12:21 PM
I figured this out. The directory my vb script existed in had embedded spaces. I had to quote $USER_INSTALL_DIR$ before calling it.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)