A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

MSIexec.exe



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old May 22nd 18, 02:01 AM posted to alt.windows7.general
Zaidy036[_5_]
external usenet poster
 
Posts: 379
Default MSIexec.exe

I am having an installer problem and would like to check if my version
5.0.7601.23446 for Win 7 SP1 64 bit is correct and the latest available.
--
Zaidy036
Ads
  #2  
Old May 22nd 18, 02:09 AM posted to alt.windows7.general
VanguardLH[_2_]
external usenet poster
 
Posts: 9,511
Default MSIexec.exe

Zaidy036 wrote:

I am having an installer problem and would like to check if my version
5.0.7601.23446 for Win 7 SP1 64 bit is correct and the latest available.


C:\Windows\system32\msiexec.exe

Right-clicked on it, looked at its Details tab, and it said the version
was:

5.0.7601.24052

That's so close differing only in the build number that mine is likely
the equivalent version to yours. I'm on Windows 7 Home x64 SP-1. Don't
know what edition (Home, Pro, Enterprise) of Win 7 that you have.

Both you and I have versions later than listed he
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
  #3  
Old May 22nd 18, 03:28 AM posted to alt.windows7.general
Zaidy036[_5_]
external usenet poster
 
Posts: 379
Default MSIexec.exe

On 5/21/2018 9:09 PM, VanguardLH wrote:
Zaidy036 wrote:

I am having an installer problem and would like to check if my version
5.0.7601.23446 for Win 7 SP1 64 bit is correct and the latest available.


C:\Windows\system32\msiexec.exe

Right-clicked on it, looked at its Details tab, and it said the version
was:

5.0.7601.24052

That's so close differing only in the build number that mine is likely
the equivalent version to yours. I'm on Windows 7 Home x64 SP-1. Don't
know what edition (Home, Pro, Enterprise) of Win 7 that you have.

Both you and I have versions later than listed he
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

Thanks for the reply. I am getting a "Missing Script" error in MS
installer when installing an X-Rite colorMunki device and asked since I
cannot find a way to "fix" it.

X-Rite is trying to help but I may have to contact MS.

--
Zaidy036
  #4  
Old May 22nd 18, 04:15 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 6,857
Default MSIexec.exe

Zaidy036 wrote:
On 5/21/2018 9:09 PM, VanguardLH wrote:
Zaidy036 wrote:

I am having an installer problem and would like to check if my version
5.0.7601.23446 for Win 7 SP1 64 bit is correct and the latest available.


C:\Windows\system32\msiexec.exe

Right-clicked on it, looked at its Details tab, and it said the version
was:

5.0.7601.24052

That's so close differing only in the build number that mine is likely
the equivalent version to yours. I'm on Windows 7 Home x64 SP-1. Don't
know what edition (Home, Pro, Enterprise) of Win 7 that you have.

Both you and I have versions later than listed he
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx


Thanks for the reply. I am getting a "Missing Script" error in MS
installer when installing an X-Rite colorMunki device and asked since I
cannot find a way to "fix" it.

X-Rite is trying to help but I may have to contact MS.


There are some tools here you can play with, to
determine if there is a "script" or not.

https://www.jsware.net/jsware/msicode.php5

Paul
  #5  
Old May 22nd 18, 10:18 AM posted to alt.windows7.general
VanguardLH[_2_]
external usenet poster
 
Posts: 9,511
Default MSIexec.exe

Zaidy036 wrote:

I am getting a "Missing Script" error in MS installer when installing
an X-Rite colorMunki device and asked since I cannot find a way to
"fix" it. X-Rite is trying to help but I may have to contact MS.


I don't believe you can do installs in Windows's safe mode, so much for
trying the install in safe mode. However, you can use msconfig.exe
(Sysinternals' Autoruns is more thorough) to disable all startup
programs. Then disable your anti-virus and other security software
(permanently until you later reenable it). Reboot Windows into normal
mode. Could be one of those programs interferes with the installer.

There should be an error code (number) besides just a "missing script"
error message. If the error dialog doesn't give a number, look in Event
Viewer for the error to see if an numeric error code is specified in the
description of the error.

Windows Installer Error Messages
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

As I recall, the installer author can have multiple scripts and decide
which to run. Looks like their installer hit a condition under Windows
7 (for your unidentified edition) where it calls a script but the author
forgot to include it. Microsoft cannot do anything about an author that
incorrectly codes the scripts within the .msi file. Only X-Rite can fix
their installer. That would be like complaining to the hardware store
that the nut you bought was the wrong size (they'll probably exchange
the nut for the correct one once you tell them but it wasn't their fault
for selling you the wrong nut size in the first place).

If their installer creates an install log file (not the one use for
later uninstallation but a log of the install), it should have a section
titled "rollback". I remember hunting for that string because that's
after the installer puked and reversed its changes made so far. I would
look backward from the rollback message to see on what the installer
reported as an error.

If their author decided not to have an option to save a debug log, you
might be able to create one by running:

msiexec.exe /i msipath /L*v debugfile

msipath is wherever you stored the .msi file. If the path to the file
or the filename has spaces, be sure to enclose it in double-quotes.
Same for the path and filename for the debugfile which will have the
verbose status messages. /i = add status messages, /v = verbose output.
Don't bother adding /x for extra debugging info unless /i wasn't enough.
I don't think /L needs to be uppercase but that's how I see it mentioned
in help articles. For info on using the program, run "msiexec /?".

Even if you cannot understand the debug file's content, X-Rite
programmers should. It would give them something more than your
description of the problem.
  #6  
Old May 22nd 18, 09:55 PM posted to alt.windows7.general
Zaidy036[_5_]
external usenet poster
 
Posts: 379
Default MSIexec.exe

On 5/22/2018 5:18 AM, VanguardLH wrote:
Zaidy036 wrote:

I am getting a "Missing Script" error in MS installer when installing
an X-Rite colorMunki device and asked since I cannot find a way to
"fix" it. X-Rite is trying to help but I may have to contact MS.


I don't believe you can do installs in Windows's safe mode, so much for
trying the install in safe mode. However, you can use msconfig.exe
(Sysinternals' Autoruns is more thorough) to disable all startup
programs. Then disable your anti-virus and other security software
(permanently until you later reenable it). Reboot Windows into normal
mode. Could be one of those programs interferes with the installer.

There should be an error code (number) besides just a "missing script"
error message. If the error dialog doesn't give a number, look in Event
Viewer for the error to see if an numeric error code is specified in the
description of the error.

Windows Installer Error Messages
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

As I recall, the installer author can have multiple scripts and decide
which to run. Looks like their installer hit a condition under Windows
7 (for your unidentified edition) where it calls a script but the author
forgot to include it. Microsoft cannot do anything about an author that
incorrectly codes the scripts within the .msi file. Only X-Rite can fix
their installer. That would be like complaining to the hardware store
that the nut you bought was the wrong size (they'll probably exchange
the nut for the correct one once you tell them but it wasn't their fault
for selling you the wrong nut size in the first place).

If their installer creates an install log file (not the one use for
later uninstallation but a log of the install), it should have a section
titled "rollback". I remember hunting for that string because that's
after the installer puked and reversed its changes made so far. I would
look backward from the rollback message to see on what the installer
reported as an error.

If their author decided not to have an option to save a debug log, you
might be able to create one by running:

msiexec.exe /i msipath /L*v debugfile

msipath is wherever you stored the .msi file. If the path to the file
or the filename has spaces, be sure to enclose it in double-quotes.
Same for the path and filename for the debugfile which will have the
verbose status messages. /i = add status messages, /v = verbose output.
Don't bother adding /x for extra debugging info unless /i wasn't enough.
I don't think /L needs to be uppercase but that's how I see it mentioned
in help articles. For info on using the program, run "msiexec /?".

Even if you cannot understand the debug file's content, X-Rite
programmers should. It would give them something more than your
description of the problem.

Win 7 Home SP-1

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

Same result with Immunet and MS Security Essentials both off and no
others on.

--
Zaidy036
  #7  
Old May 22nd 18, 10:15 PM posted to alt.windows7.general
Zaidy036[_5_]
external usenet poster
 
Posts: 379
Default MSIexec.exe

On 5/21/2018 11:15 PM, Paul wrote:
Zaidy036 wrote:
On 5/21/2018 9:09 PM, VanguardLH wrote:
Zaidy036 wrote:

I am having an installer problem and would like to check if my version
5.0.7601.23446 for Win 7 SP1 64 bit is correct and the latest
available.

C:\Windows\system32\msiexec.exe

Right-clicked on it, looked at its Details tab, and it said the version
was:

5.0.7601.24052

That's so close differing only in the build number that mine is likely
the equivalent version to yours.* I'm on Windows 7 Home x64 SP-1.* Don't
know what edition (Home, Pro, Enterprise) of Win 7 that you have.

Both you and I have versions later than listed he
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx


Thanks for the reply. I am getting a "Missing Script" error in MS
installer when installing an X-Rite colorMunki device and asked since
I cannot find a way to "fix" it.

X-Rite is trying to help but I may have to contact MS.


There are some tools here you can play with, to
determine if there is a "script" or not.

https://www.jsware.net/jsware/msicode.php5

** Paul

The X-Rite XRD_Manager is an "exe" which installs items and then asks to
do the "actual" installation which I assume is running the "MSI" which
is not separate. After failure it "backs out" any changes.

--
Zaidy036
  #8  
Old May 23rd 18, 04:29 AM posted to alt.windows7.general
VanguardLH[_2_]
external usenet poster
 
Posts: 9,511
Default MSIexec.exe

Zaidy036 wrote:

Win 7 Home SP-1

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


According to the web page mentioned in my prior reply, that error code
means:

There is a problem with this Windows Installer package. A program
required for this install to complete could not be run. Contact your
support personnel or package vendor.

Microsoft cannot fix logic errors in the script(s) the installer
programmer put into the MSI package. Only X-Rite can fix their own
screw up - if the installation is not getting interference from
something you are running on your computer.

Same result with Immunet and MS Security Essentials both off and no
others on.


Did you try my other suggestions? Else, you'll have to wait for X-Rite
to debug their own code in their scripts they put into the MSI package.
The debug log might afford them more specific information as to why
their installer aborts.
  #9  
Old May 23rd 18, 10:43 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 6,857
Default MSIexec.exe

Zaidy036 wrote:
On 5/22/2018 5:18 AM, VanguardLH wrote:
Zaidy036 wrote:

I am getting a "Missing Script" error in MS installer when installing
an X-Rite colorMunki device and asked since I cannot find a way to
"fix" it. X-Rite is trying to help but I may have to contact MS.


I don't believe you can do installs in Windows's safe mode, so much for
trying the install in safe mode. However, you can use msconfig.exe
(Sysinternals' Autoruns is more thorough) to disable all startup
programs. Then disable your anti-virus and other security software
(permanently until you later reenable it). Reboot Windows into normal
mode. Could be one of those programs interferes with the installer.

There should be an error code (number) besides just a "missing script"
error message. If the error dialog doesn't give a number, look in Event
Viewer for the error to see if an numeric error code is specified in the
description of the error.

Windows Installer Error Messages
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx


As I recall, the installer author can have multiple scripts and decide
which to run. Looks like their installer hit a condition under Windows
7 (for your unidentified edition) where it calls a script but the author
forgot to include it. Microsoft cannot do anything about an author that
incorrectly codes the scripts within the .msi file. Only X-Rite can fix
their installer. That would be like complaining to the hardware store
that the nut you bought was the wrong size (they'll probably exchange
the nut for the correct one once you tell them but it wasn't their fault
for selling you the wrong nut size in the first place).

If their installer creates an install log file (not the one use for
later uninstallation but a log of the install), it should have a section
titled "rollback". I remember hunting for that string because that's
after the installer puked and reversed its changes made so far. I would
look backward from the rollback message to see on what the installer
reported as an error.

If their author decided not to have an option to save a debug log, you
might be able to create one by running:

msiexec.exe /i msipath /L*v debugfile

msipath is wherever you stored the .msi file. If the path to the file
or the filename has spaces, be sure to enclose it in double-quotes.
Same for the path and filename for the debugfile which will have the
verbose status messages. /i = add status messages, /v = verbose output.
Don't bother adding /x for extra debugging info unless /i wasn't enough.
I don't think /L needs to be uppercase but that's how I see it mentioned
in help articles. For info on using the program, run "msiexec /?".

Even if you cannot understand the debug file's content, X-Rite
programmers should. It would give them something more than your
description of the problem.

Win 7 Home SP-1

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

Same result with Immunet and MS Security Essentials both off and no
others on.


I tried this one.

http://downloads.xrite.com/downloads...nager_v240.exe

It failed to run under WINE, and it could be a similar problem
to what you were seeing.

I ran it in Windows 10, and the process moved forward until
it actually tried to install drivers. At that point, it asks
for permission, and I stopped at that point to see what
materials it had decompressed. This is what I found in
my %temp% folder while it was prompting me for permission
to install the drivers, in a sub-folder in there that had the
current date and time (just freshly unpacked). There
was a single file "drivers32.msi". I opened that file
with 7ZIP for a look, and this is what i got. You can see
it also includes 64-bit files.

https://s7.postimg.cc/j71t84j3f/drivers32.gif

Paul
  #10  
Old May 27th 18, 02:58 PM posted to alt.windows7.general
Mayayana
external usenet poster
 
Posts: 4,641
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.



 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 10:08 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Copyright 2004-2018 PCbanter.
The comments are property of their posters.