I cannot call a long msiexec /i command line from a wise package studio 7 wrapper (ipf file)
Updated: 21 May 2010 | 4 comments
How can I call this command line from a batch file and make sure that the exitcode is communicated back to the wrapper ?
If you have any other suggestions to solve this issue, please let me know.
discussion Filed Under:
Comments
>If you have any other
>If you have any other suggestions
Oh...I don't know...use the 'Search' facility first? :)
If your command line is long, my guess would be that you're passing a whole bunch of properties. Use a transform instead.
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Do you actually know what you are using?
An IPF file is generated by SMS Installer, the version of the wisescript editor that was licensed by Microsoft over 10 years ago. Wise Package Studio does not generate IPF files, although you could rename an IPF file to WSE and try and import it as the code base is pretty similar.
IPF is not a batch file either.
So can you clarify what you are working with, as a Wisescript wrapper is capable of handling strings of 32 K in length.
The more information you supply us, the less time we have to waste trying to figure out what you are asking.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Set a Variable
If I understand the question correctly, you're saying that you are limited to the length to in the command line on the wrapper?
You might try setting your command line arguments into a variable then using that variable in the execute statement or use mulitiple variables if necessary.
thanks
Hi thanks for the tips !.
Eventually, I ended up calling a vbs by the wrapper and passing a variable from the ipf to vbscript.
Would you like to reply?
Login or Register to post your comment.