Databases
StackOverflow2013
Postsdbo
PONSIS - msiexec /i fails with code 1619 if I call SetOutPath
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONSIS - msiexec /i fails with code 1619 if I call SetOutPath
    primarykey
    data
    text
    <p><code>ExecWait "msiexec /i myinstaller.msi /qn" $0</code></p> <p>That's all I'm calling in my script. (The <code>/qn</code> is for silent installation without popping up any progress window, I've also tested without it).</p> <p>It fails with an <a href="http://support.microsoft.com/kb/229683" rel="nofollow">msiexec error code</a> of 1619-<code>This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.</code></p> <p>The same msiexec call works fine on the commandline, or if I write a basic NSIS script that does nothing else- which means it's <strong>not</strong> because of <a href="http://support.microsoft.com/kb/316309" rel="nofollow">NTFS permissions</a> that a Google search throws up.</p> <p>Therefore, it must be something else in my main installer script. After commenting out nearly everything in my script to isolate the cause:</p> <p><code>SetOutPath "$INSTDIR\Some directory"</code></p> <p>If I comment this section out and don't set an output path, everything works fine. What on earth is going on? Why should this interfere with the msiexec call? </p> <p><strong>Update</strong> - Here's the <code>tl;dr</code> version of the problem - the following snippet doesn't work when run as an independent script unless I comment out the <code>SetOutPath</code> call. WHY? It does not matter whether the output directory has any files in it or not(it doesn't), or whether I call it immediately before or several lines before.</p> <pre><code>showinstdetails show OutFile test.exe section setoutpath "D:\back" ExecWait "msiexec /i MyInstaller.msi /qr" $0 MessageBox MB_OK $0 sectionend </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRex
    1. USRex
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONSIS - msiexec /i fails with code 1619 if I call SetOutPath
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONSIS - msiexec /i fails with code 1619 if I call SetOutPath
      1. USRex
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload