WFWI.exe command line build problems
Using WFWI.EXE (Build 6.20.0.281) to attempt to automate or build process (VB6 applications..) doesn't work as expected.
Using a command line without the /S runs correctly, and creates the correct MSI & WSI files as if created manually.. Using the /S it builds the output, then hangs indefinitely. We have 3 packages we'd like to automate the build process for, and can't..
I can supply the exact build options command line if needed for troubleshooting... for instance here's one now...:
"C:\Program Files\Wise for Windows Installer\wfwi.exe" "\\Server\SetupPrograms\Scripts\Client.wsi" /c="Client" /o "D:\Ptest\Version %1\Client\Client.msi"
- works perfectly with no issues...
"C:\Program Files\Wise for Windows Installer\wfwi.exe" "\\Server\SetupPrograms\Scripts\Client.wsi" /c="Client" /o "D:\Ptest\Version %1\Client\Client.msi" /s
- creates output but hangs indifinitely... I have 3 more I need to run after this one..
Any help? -- Oh yeah, locating the /S i different places in the command line has the same effect.. ie between /C & /O parms, or as the first parm or as the last parms.. all have the same effect...
Thanks in advance for helping me to solve this issue..
Comments
Things to try
1. Turn on logging with the /l option. The log may give you a hint as to what is hanging the process.
2. Are there any dialogs being produced during a command line compile without /s ?
3. Try changing the "Version %1" string to something without a % in it, as this may be misinterpreted by the Wise code.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Thanks for the response
Thanks for the response Ed...
Sorry.. the %1 is a parameter used in the batch file.. It is replaced by Version Number Parameter passed to the bat file..
As for running without the /S there is a DB login prompt at the start of the process, and a prompt for "Express Build is not valid with a single cab file" (or something similar to that..)
I'll try the /L (i'm guessing it's an "L"..)
Try it on some other machine/location
I tried to reproduce the error on my test build, however it is working fine. Below command I used to for creation of MSI
"C:\Program Files\Altiris\Wise Package Studio\Windows Installer Editor\WfWI.exe" "C:\Test\Test.wsi" /c /o "C:\Test\Test % 1\Test.msi" /s
Try to build MSIs on some other machine Or test build creation by copying WSIs on local machine.
Run without the /S to get a
Run without the /S to get a logfile with a working compile. Then try with the /S to see where it stalls. However, if the compile without /s requires user input, then it will inevitably stall if you use /s to suppress error messages, as the underlying error is still there.
Yankiar's test used direct drive mapping rather than a UNC address - perhaps this is something you should also try.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Can you gentlemen tell me if
Can you gentlemen tell me if we have a support contract or agreement of any kind?
I've identified the problem, but my attempts at resolution have been un-successful so far.
We have the packager intalled on a stand-alone machine not part of our domain. (I'm not sure why, it's what I inherited...)
We're trying to automate our build process to a nightly one line command which calls the compiler, then the packager...
I can use the command line now, specifying the password parameter (/p password=********) Not really documented anywhere I could find, just an educated guess, and the command line works fine.
However because it's on a different domain, our machine which runs the script being on the domain can't run a script on a remote machine not in the domain.
So, I've un-installed & re-installed on a machine which IS on the domain. However I can't get the packager to funciton normally now.
2 issues. I need to specify the DSN name about 6 or 7 during the package process. When the package process completes(?), there's an error message displayed:
-----------------------------------------------------------------------------------------------------
Error while opening database for merge module VB_Control_msmask32.BFA50E2B_4434_11D3_A51D_00A0C9231BA1 at C:\Program Files\Common Files\merge modules\msmask32_X86.msm.
-----------------------------------------------------------------------------------------------------
This message is displayd for each merge module used in the build.
Thanks in advance
Mike Dickerson
This is a user forum and we are not Symantec employees
As we are not associated with Symantec we are unable to determine whether you have any sort of maintenance or support agreement. If you cannot determine this internally, then you would need to contact Symantec and ask them, but as a support agreement is quite expensive I would have thought there would be some sort of approval process in your company that you could look for.
What actual Wise product do you have? It is Wise Package Studio 6? Your reference to entering a DSN 6 or 7 is missing something - do you mean you have to enter it 6 or 7 times ??
As you have already remarked about issues arising from being in different domains, and now have problems with DSNs, if you do have WPS6 then I would recommend you have a look at the Getting Started Guide to understand how the relationships between the WPS installation, the SQL server, and the Wise Share Point must be set up for correct operation. Having any of these resources in different domains is not a good idea. Finally, the Wise client must be installed with the same admin account as it will be used with, as the licensing information is held in the installing user profile.
Apologies if I am covering ground that you have already negotiated, but it is important to ensure that the basics are correct before we go any further.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Would you like to reply?
Login or Register to post your comment.