I have an msi, Accesspro Redaction, that installs normally when launched manually but does not install when using command line switches for silent installs.

Installing on windows 7

I have tried /qb /qr /qn /quiet /passive   nothing works

any ideas??

Thanks

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2

Does the install do anything when you launch it silently, like showing a dialogue box or having a couple of msi processes appear in the task manager? If it does nothing, I'd try turning on logging and see what you get.

"msiexec.exe /i filename.msi /qn /L*v c:\accesspro_msiinstall.log"
Answered 12/11/2012 by: Ben M
Ninth Degree Black Belt

Please log in to comment

Answers

0

Hey Ben

I have tried logging but only lists all the actions that have started and and ended

It looks like it installs whne i use some of the switches ( seeing the GUI ) and the log states that the installation was successful      very starnge

but I get errors when I launch the program but when I install manually it works fine

here is the command line %SYSTEMROOT%\system32\MSIEXEC.EXE /i "%SOURCE%\Privasoft_AccessPro_Redaction_US.msi" /liwear "c:\LOGS\AccessPro\AccessPro_EN.LOG" ALLUSERS=1 /passive

Thanks

Answered 12/11/2012 by: jensv
Senior Yellow Belt

  • Does the log contain any error codes or completion messages? What error do you get when you launch the program after the passive install? Also, I assume /liwear is a typo, can you confirm that?
    • No errors
    • no /liwear is what I have in the line ????
    • Ditto to what Dunnpy said. I'd never heard of the /liwear switch before. You learn something new everyday :)
  • Logging Options
    /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
    i - Status messages
    w - Nonfatal warnings
    e - All error messages
    a - Start up of actions
    r - Action-specific records
    u - User requests
    c - Initial UI parameters
    m - Out-of-memory or fatal exit information
    o - Out-of-disk-space messages
    p - Terminal properties
    v - Verbose output
    x - Extra debugging information
    + - Append to existing log file
    ! - Flush each line to the log
    * - Log all information, except for v and x options
    /log <LogFile>
    Equivalent of /l* <LogFile>

    /liwear = Log Status messages, Nonfatal warnings, All error messages, Start up of actions, and Action-specific records.

    Personally, I just use /lvx*
    • The only reason I'm doing a command line is because I don't have access to any packaging software and nothing is setup here yet for packaging I've been packaging for over 7 years and have not come across any msi that wouldn't accept any switches

      Thanks for all the input
Please log in to comment
0

Try the command line with logging specified by 'Ben M' - you're not getting everything in your log with your log switch.

When you install manually, are you having to input some information for it to install correctly? Create a log of the manual install and see what items are being written to Properties, create those populated properties in an MST to see if that allows a silent install.

 

Hope that helps,

Dunnpy

Answered 12/11/2012 by: dunnpy
Red Belt

Please log in to comment
0

In general, MSI logging can be enabled globally but it can write quite a lot of data, just good for troubleshooting MSI installs temporarily. I have not seen "liewear" either, I am used to "voicewarmup" :) perhaps the registry key helps to produce the logfile in %TEMP% which would may give you an idea if anything starts at all. Btw, Windows Installer service was started at the time you tested those packages? Just to make sure..

How to enabled MSI logging in Windows XP/Vista/7
http://support.microsoft.com/kb/314852

Answered 12/12/2012 by: RaSko
Purple Belt

Please log in to comment
0
 here is the command line %SYSTEMROOT%\system32\MSIEXEC.EXE /i "%SOURCE%\Privasoft_AccessPro_Redaction_US.msi" /liwear "c:\LOGS\AccessPro\AccessPro_EN.LOG" ALLUSERS=1 /passive

Is there any reason your using such a long command path? If you upload the MSI and attach it to the software inventory, you can just set the msi name directly without a path.

Here is our acrobat one for example.

msiexec /i acropro.msi TRANSFORMS=AcroPro.mst /qb

 

 

Answered 12/12/2012 by: MoranTug
Senior Purple Belt

Please log in to comment
0

 

The only reason I'm doing a command line is because I don't have access to any packaging software and nothing is setup here yet for packaging ( waiting approval)    I've been packaging for over 7 years and have not come across any msi that wouldn't accept any switches


Thanks for all the input

Answered 12/14/2012 by: jensv
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity