Re: execmgr.log Error 1619 when distributing MSI's



1619... "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."

I've seen that before; both for legitimate reasons (like the package
you are installing is an agent that integrates with network protocols,
or is a NIC driver update, so *of course* it has to disconnect network
connectivity), and for bogus reasons (whoever packaged that MSI didn't
know what they were doing, and have custom actions or something else
inside which looks for drive letters, and fails on UNC paths).

If what you are installing may be (by design) hooking into network
protocols or network drivers, etc; your only choice may be Download &
Execute. If it's possible it's bogus reason (bad packaging), a
possible trick to try is within the Program Properties, Environment
Tab, Drive mode, instead of "Runs with UNC name", try "Requires drive
letter". SMS will map a drive letter to your DP's UNC path, install
the app, and then unmap it when done.

As to modifying the MSIs--you don't have to directly modify the MSI,
if you have the tools available to you, you could create an .MST, (a
Transform), to customize the install. That way you are not modifying
their original installation, just customizing it for your environment.


On Jul 13, 8:56 am, Mike A <Mi...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hey,

I'm having an issue distributing MSI's to some of my clients. The msi
executes, and is getting a 1619 error. I've enabled logging in the msi,
but don't get any error messages.

Here's all I get in the msi logging. for my msiexec command line I used
msiexec.exe /i (name of msi) /q /norestart /L*v
m:\windows\system32\ccm\logs\Msilog.txt.

I can use download and execute via sms, and it will run perfectly fine.

How can I get it to run from my dp, so I don't have to download the entire
package to get it to run.

The only KB I found washttp://support.microsoft.com/default.aspx/kb/271602.

But these are msi's that come from software vendors, so I am unable to
modify them. If I modify their MSI's I'll lose support.

Thanks,


.



Relevant Pages

  • Re: dist-upgrade problem (was Re: /etc/modutils/0keep: line 9: keep: command not found)
    ... Reading package fields... ... i t does not have execute permission ... installation script returned error exit status 100. ...
    (Debian-User)
  • Re: Finding installed package files
    ... >, and who is going to supply this documentation. ... > is a package with the common man pages for the thousand odd common commands ... tell me, as an installation option for some large packages, what was ... >>a set of commands and 'man' pages, could produce such a directory to make it ...
    (alt.os.linux.redhat)
  • Security Update for Microsoft Data Access Components (KB832483)
    ... : An error occurred while setup was trying to ... verify the version of Microsoft Data Access Components ... package returned FALSE, or there was a fatal error while ... installation. ...
    (microsoft.public.windowsupdate)
  • Security Update for Microsoft Data Access Components (KB832483)
    ... : An error occurred while setup was trying to ... verify the version of Microsoft Data Access Components ... package returned FALSE, or there was a fatal error while ... installation. ...
    (microsoft.public.windowsupdate)
  • Re: bits/news from the users of Debian?
    ... "Le bottin des jeux Linux" speaks about 800 Linux games and i hope that's growing. ... I start with Debian, then test Mandrake because it seem's at this time very complicated. ... I think graphics interface for installation is a good thing: you have make a good job! ... I use Debian Sid and I have experiment a lot of problem some years ago because i install too recent package on Sid which are not well tested. ...
    (Debian-User)

Quantcast