msiexec --help output in the middle of wine install log

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
Forester
Level 2
Level 2
Posts: 35
Joined: Sun Jun 22, 2008 2:39 pm

msiexec --help output in the middle of wine install log

Post by Forester »

I've installed an application from the command line with:

wine 'F:\Setup.exe' 2>&1 | tee wine.log

In the log, somewhere towards the end of the install, appears the same output as you get with the command line:

msiexec --help

which suggests to me that my application's installer or Wine has messed up an invocation of msiexec and as a consequence the installation may be incomplete or even broken.

What kind of WINEDEBUG trace can I use to find out more ?
vitamin
Moderator
Moderator
Posts: 6605
Joined: Sat Feb 23, 2008 2:29 pm

Re: msiexec --help output in the middle of wine install log

Post by vitamin »

Forester wrote:I've installed an application from the command line with:

wine 'F:\Setup.exe' 2>&1 | tee wine.log

In the log, somewhere towards the end of the install, appears the same output as you get with the command line:

msiexec --help

which suggests to me that my application's installer or Wine has messed up an invocation of msiexec and as a consequence the installation may be incomplete or even broken.

What kind of WINEDEBUG trace can I use to find out more ?
WINEDEBUG=+exec would probably be enough. However it sounds like a known problem with command line parsing - http://bugs.winehq.org/show_bug.cgi?id=9628
Forester
Level 2
Level 2
Posts: 35
Joined: Sun Jun 22, 2008 2:39 pm

Post by Forester »

Many thanks vitamin for your reply.

The trace you suggested didn't do the trick but the bug link you gave led me to try WINEDEBUG=trace+msiexec and that did do the trick.

My case is not bug 9628 as I get:

trace:msiexec:main argvW[1] = L"F:\\WPOX3\\ISUS.msi"
trace:msiexec:main argvW[2] = L"APP_PRODUCTCODE={83FBD495-DDF6-4C8D-92D6-10261DD6F6A3}"
trace:msiexec:main argvW[3] = L"APP_DWUSLANG=1033"
trace:msiexec:main argvW[4] = L"APP_DWUSINTERVAL=30"
trace:msiexec:main argvW[5] = L"APP_VERSION=13.0"
trace:msiexec:main argvW[6] = L"NESTED=1"
trace:msiexec:main argvW[7] = L"/qn"

which I believe is a case of:
NOTE: Product code on commandline unimplemented as of yet
This is serendipitous as the installer that won't install is Install Shield Update Service, which you really really don't want as anyone who has ever had anything to do with this in the real Windows world will confirm.
Locked