Thread: MSIexec.exe
View Single Post
  #10  
Old May 27th 18, 02:58 PM posted to alt.windows7.general
Mayayana
external usenet poster
 
Posts: 6,438
Default MSIexec.exe

"Zaidy036" wrote

| Event Log and Error page give same result #1720 Script could not be run.
|

As Paul noted, you can usually fish the MSI
out of TEMP if need be.

----------------
Error 1720:

There is a problem with this Windows Installer package. A script required
for this install to complete could not be run. Contact your support
personnel or package vendor. Custom action [2] script error [3], [4]: [5]
Line [6], Column [7], [8]
-------------------

The numbers in braces point to info that can only
be obtained by acessing the LastErrorRecord object
of WindowsInstaller. I don't know if there's a way
to do that. It's possible that there's a debug option
of some kind, but I don't know of any. The installer
is supposed to handle that. In other words, the error
message should just say error 1720. It should say
something like:

"Error 1720. Custom Action SnazzyEffects.vbs
script error Access Denied, line 103, column 8"

If it does that you could actually extract the script
and figure out exactly what it was trying to do. On
the other hand, that might be more than you really
want to know.

My best guess would be permissions problems,
an open file that can't be accessed... something like
that. You could try running Process Monitor to see
where it gets hung up.

If you can't figure it out and the error is not telling
you anything useful, you can call the company
and curse at them for not writing their error handlers
properly. If you *are* getting all that error info you
could post it, along with a link to the installer, and
one of us may be able to tell you the problem.

The whole thing would be a little easier if companies
didn't try to be clever by putting MSIs inside of EXEs.
That just adds unnecessary complications. But usually
the MSI can be accessed and the EXE is typically
just a wrapper to look official and "kick off" the install.



Ads