Installation Studio - Command line build is not outputting .msi
Updated: 21 May 2010 | 11 comments
This issue has been solved. See solution.
Hi guys.. forgive me for my noob-ish question but I'm having some difficulty performing a compile and deploy of .msi for my application and would appreciate it if anyone has any words of advice. I'm using an evaluation version if that makes any difference.
From an elevated command prompt:
WFWI.exe C:\LabWorksInstallFiles\Labworks.wsi /c/pUSER_COUNT="5" /pAPP_VERSION="915" /o C:\Labworks_915.msi /l c:\prepsetup.log
The Labworks.wsi file successfully compiles, the log file is created.. but nothing is deployed. Log file reports of files that were compressed which are part of my app, but it just stops there.
The .wsi file successfully compiles and I can deploy with no issues to an .MSI file. This is when using the studio express GUI.
Thanks much!!
Brian
discussion Filed Under:
Comments
What do you mean by deploy?
What do you mean by deploy?
Confused
What product are you evaluating?
Wise Installation Studio and Wise Installation Express are two different products so your reference to Studio Express GUI is not helpful in this respect.
In addition, this is a packaging tool and not a deployment tool. It is perhaps possible that you are using the term "deploy" incorrectly, but if you could clarify exactly what your expectations are, we will try and answer your questions once we understand them!!
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Reply to questions
Hey guys..
Product is Installation Express. Currently running Trial version, but my company is purchasing today and will try with non-trial version to see if it makes a difference.
By DEPLOY, I apologize I meant "Distribute" from the file menu in the GUI. I create the actual .msi this way.. I'm not aware if a simple compile will create the .msi but as far as I can tell I must go to the distribute step to get it.
My expectations.. I have a preexisting batch file that I use to get all the source files together. I would like to run WFWI.exe from the batch file as well so I can have it spit out an .MSI automatically. Just trying to eliminate steps and stumbling points here.
My issue is that even from elevated command prompt, the command will run and successfully compile, but there is no output as I expected from using the switch: /o C:\Labworks_915.msi
I thought this would create my .MSI file.
I'm guessing at these possible reasons:
1. Trial version doesn't allow command line builds
2. There is an unreported error during the process (again, I'm creating the log file, but it doesn't report anything)
3. I'm a moron and am missing something.
Thanks guys!
Brian
Trial version is not restricted
The trial version is not restricted in any way. However, it does create packages with a message saying that they are compiled with a trial version, but that's the only difference to a licensed version.
Do you have write access to C:\ ?
Are you able to compile the same WSI to the same target location using the GUI instead of the command line?
Have you tried with UAC turned off ?
How about giving us the entire command line you are using?
There are three possibilities at the moment:
1. There is a problem with the WSI or with permissions where you are trying to create the MSI
2. There is a problem with the command line.
3. You are a moron and are missing something.
However, we never jump to any conclusions regarding reason 3 until all other avenues have been exhausted, so we will try and work with you and get this one sorted out. Just remember to give us as much information as possible, including what operating system you are developing on.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Tried with UAC on full version
SO, the company bought Wise Installation Studio, the full version
Same issue! (As you suspected =)
Tried with UAC off, no change there.
By hand, in the GUI the WSI compiles completely with no messages. I'm also able to Distribute to MSI with no issues or warnings either.
The command line:
WFWI.exe C:\LabWorksInstallFiles\Labworks.wsi /c/pUSER_COUNT="5" /pAPP_VERSION="915" /o C:\Labworks_915.msi /l c:\prepsetup.log
Output from prepsetup.log:
...<a few hundred similar lines snipped>...
That's it. no MSI is generated.
Next attempt will be to make a new simple .WSI and see if I can get that to completion.
Thanks for your help so far!
Brian
Simplify the command line
When things go wrong, I find it often helps to simplify the command line to the point where things work as expected, then add stuff back in until you identify what breaks the install.
The first thing that I would take out are the property settings and the logfile and see if that gets it working.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Simplified.. still no workey
Simplified to WFWI labworks.wsi /c/o"c:\lw.msi"
I'm doing a simple .wsi next to see if it lets that work at least!!
Brian
Check syntax
Sometimes the absence of spaces and full paths in a command line can cause problems.
Try <path>\ WFWI.exe <path>\labworks.wsi /c /o"c:\lw.msi"
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
SOLVED ? Bug in WFWI?
Hi all,
Thanks so much for your generous help over the past few weeks.
I seemed to have missed something that was right under my nose the entire time. When running the command as originally described it was outputting an .msi file the entire time. Strange though, it was creating a like-named msi to the wsi file and path.
SO:
From an elevated command prompt
The output from this command is:
c:\LabWorksInstallFiles\Labworks.MSI <-- NOT c:\Labworks_915.msi as requested.
c:\prepsetup.log <-- as expected.
Although this is unexpected behavior, I can work with it in the batch file I created to compile my app. I'll just use the created .msi file as a temp file, copying to a location that I specify with a name change in the process.
If WFWI is still an actively developed product, the team might consider looking into this as a possible bug and necessary patch.
My environment is Vista Ultimate 32bit and all commands are elevated, for what it's worth.
Thanks so much guys! I'll leave the thread open for a bit in case anyone wants to add anything.
End of Installation Studio?
Did anyone got this email as well?
"End of Availability for Wise Installation Studio and Wise Installation Express.
Dear Valued Customer,
This letter is to notify you that Symantec is announcing the end-of-availability of Wise Installation Studio and Wise Installation Express.
Effective April 19, 2010, Symantec will no longer be accepting orders for new licenses of Wise Installation Studio or Wise Installation Express. In addition, Symantec will no longer be accepting renewals for maintenance agreements related to Wise Installation Studio effective April 19, 2010.
Sincerely,
Symantec Corporation"
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Nope, did not get it
Nope, did not get it
Would you like to reply?
Login or Register to post your comment.