isscript.msi issue - can't install
Jim
selected it. It said the message was no longer available on the server which
I don't understand because it was only 3 minutes old. So, I am reposting.
---------------------------------------------------------------------------
I downloaded the trial version of VPC2004 and had an issue installing that
kept me from trying it. I figured its just a bug in the trial version so I
went out and bought a copy from CompUSA. I still get the same error with the
purchased version. I am presented, via dialog box, with the error:
"1: The InstallScript engine on this machine is older than the version
required to run this setup. If available, please install the latest version
of ISScript.msi, or contact your support personnel for further assistance."
Also, the following 2 errors are put into the Application log in the Event
Viewer:
Information --- MsiInstaller --- 11707
Error --------- MsiInstaller --- 1013
Using the sites listed below for help, I have installed the re-distributable
Windows Installer version 2.0. It did not install as it prompted that the
service was already installed. Checked the properties of Setup.exe and the
version is 8.1.160.0. Deleted the \.....\CommonFiles\InstallShield\Driver
directory and reinstalled isscrip8.msi (tried the same with isscript7 &
9.msi). Deleted the \.....\CommonFiles\InstallShield\Engine directory and
ran the engine update from the lkernelupdate.exe from the InstallShield
website. Downloaded and installed the whole Microsoft Windows Installer 2.0
SDK, hoping it would install or correct something. Downloaded, installed and
ran the Microsoft Installer cleanup utility; there were no instances of VPC
listed for cleanup. Rebooted machine between many install attempts to insure
that the msiexec service was not running as the InstallShield site listed
multiple instances of certain processes as a possible culprit. I cannot stop
the msiexec service via task manager, I am denied. However, I am an
Administrator on my machine. As I understand it, this is normal. Ending a
service is a request and can be denied. It depends how the service is
written. Also, I have not been able to find a correlation between the error
message in the dialog box and event code 1013 anywhere. Event code 1607 is
commonly associated with InstallShield issues, but I am not getting this
error. Another attempt I made, was to delete the
\.....\CommonFiles\InstallShield\Driver directory completely and replace it
with nothing. This way, there would be no conflict with something that
Setup.exe was trying to install. Just for grins, I removed some applications
to make more room on the C: drive although the installation never actually
gets that far. Also, I defragged the drive; again this should have no
affect.
I deleted the \....\Local Settings\Temp directory to see what files were
created by Setup.exe. Before the error message dialog is closed via the OK
button, the following files are created in the temp directory:
(Note: the log file, tmp file and subdirectory names will modify if
subsequent installs are done without flushing the tempdirectory)
MSIB0.tmp
MSIB1.tmp
57434b.msi
MSI7434c.log (this was not readable in an editor)
There is also a directory named _isAD. Inside that directory are:
ISScript8.msi (this is probably the intended isscipt update that I have
already tried manually)
0x0409.ini
Setup.ini
_ISMSIDEL.INI
All of the above files and subdirectory are deleted when the incomplete
install is finished via the dialog box OK buttons. The only exception is the
log files which are left behind.
Also, I have contacted InstallShield and they will not help because they did
not package the product. This is rightfully so, but I thought I'd give it a
try because getting help from Microsoft is difficult at best. I went to the
Microsoft support site and they want to FORCE me create a passport account
just for customer service which is bull. Anyway, VPC was not even listed as
one of the products.
My system is Dell Precision 210 Mini Tower, 550Mhz P3, 512MB RAM, 25GB HD
(6GB free), corporate environment (networked with domain server), AGP dual
monitor card using ATI Desktop manager.
I am out of ideas!!! Does anyone have the solution?
Regards,
Jim
P.S.: Below are a listing of useful websites:
I have found the following sites with information about ISScript install
issues:
http://www.robertmoir.co.uk/win/vpcfaq/VPCFAQ7-KnownIssueswithVP.html
http://consumer.installshield.com/kb.asp?id=Q108322
http://consumer.installshield.com/utilities.asp
http://www.installsite.org/pages/en/msifaq/a/1027.htm
http://www.appdeploy.com/tips/detail.asp?id=54
http://www.appdeploy.com/messageboards/tm.asp?m=64&mpage=1&key=&anchor#120\
http://asp.appdeploy.com/messageboards/tm.asp?m=599
http://www.installshield.com/news/books/windows-installer-setup/Chapter%2004.pdf
http://www.castlepersonnel.com.au/Gemma/Downloads/installshield1607.htm
http://support.installshield.com/kb/view.asp?articleid=Q108515
http://consumer.installshield.com/kb.asp?id=Q108158
David Wang [Msft]
was focus on getting ISScript.msi to install and not fail. The error code
that is returned is not from MSI, so it is some custom value from
InstallShield.
Can you clarify what version of Windows you are running.
You have a way to get that ISScript.msi out of the installer, so I would
focus on getting that msi to install. Run it with
msiexec /I ISScript.msi /L*v ISInstall.log
And after the install finishes/fails, look in ISInstall.log for this string
"error " (the space is useful to zoom in on any failures logged in the log
file. If it succeeds, I suspect that Virtual PC installation would succeed.
Finally, I'm sorry to hear that you expect getting help from Microsoft to be
"difficult at best". I know that there are so many ways to get quality time
of really helpful people, including Microsoft employees and users that it
really matters which channel you pick as well as the topic and how you
phrase it.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Jim" <cook...@aol.com> wrote in message
news:eYkyF1No...@TK2MSFTNGP10.phx.gbl...
Jim
How about that, ALL that info and I didn't mention my OS?!? I am running
Windows 2000. The manual install of isscript8.msi does not error. It
installs cleanly.
I was also able to produce a readable logfile by invoking msiexec manually.
It's fairly long so I will attach it instead of embedding it in the text of
this mail.
Also, I found out how to check the version of msiexec. The version on my
machine is 2.00.2600.1183. I found another person here at work that has
version 3.00.3790.2180. I installed the latest of everything that I could
find from Microsoft and InstallShield.
Jim
"David Wang [Msft]" <som...@online.microsoft.com> wrote in message
news:eiKqVlOo...@TK2MSFTNGP15.phx.gbl...
Scott Baker
Virtual PC installation.
Scott
Jim wrote:
> > l http://consumer.installshield.com/kb.asp?id=Q108322
David Wang [Msft]
I went and found a Windows 2000 machine, checked that msiexec.exe returned
the same version (2.00.2600.1183), and I installed Virtual PC successfully.
In my case, I had the following InstallShield versions:
W32i APP ENU 7.4.0.377 shp c:\program files\common
files\installshield\driver\7\intel 32\iscript7.dll
W32i APP ENU 8.1.0.304 shp c:\program files\common
files\installshield\driver\8\intel 32\iscript8.dll
W32i APP ENU 6.30.100.1255 shp c:\program files\common
files\installshield\engine\6\intel 32\ctor.dll
W32i APP ENU 6.30.100.1255 shp c:\program files\common
files\installshield\engine\6\intel 32\ikernel.exe
W32i APP ENU 6.10.100.1257 shp c:\program files\common
files\installshield\engine\6\intel 32\ilog.dll
W32i APP ENU 6.30.100.1255 shp c:\program files\common
files\installshield\engine\6\intel 32\iuser.dll
W32i APP ENU 3.1.0.392 shp c:\program files\common
files\installshield\engine\6\intel 32\knlwrap.exe
W32i DLL ENU 3.1.392.0 shp c:\program files\common
files\installshield\engine\6\intel 32\msihook.dll
W32i APP ENU 6.30.100.1255 shp c:\program files\common
files\installshield\iscript\iscript.dll
Which ISScript.msi said was new enough.
I suspect InstallShield isn't working on your machine right now due to the
fact that you went and just deleted InstallShield files without uninstalling
them... because due to how MSI works, if you install files using an MSI
(which is what InstallShield is using) and afterwards went and DELETED those
files, even if you later install that MSI again, those files will not be
restored. This is because the MSI engine will detect that you are simply
trying to install an MSI with the same Product ID as something else that was
already installed -- and it will simply skip the installation -- thus
nothing is restored.
Thus, it is a bad idea for you to just delete files and reinstall with an
MSI because it won't work. In your case, you need to uninstall the MSI
files for InstallShield OR run the MSI in repair mode (there are commandline
parameters to do this), where the MSI engine will actually detect whether
files all exist and re-run the installation..
Your log file indicates it is InstallShield's ISScript.msi which is failing
to install... which even though redistributed by Virtual PC, it is still a
part of the InstallShield product that they should support. It's like if
you write a Windows application and redistribute MSVCRT.DLL with your
applications -- you are not obligated to support MSVCRT.DLL just because you
repackaged it -- Microsoft publishes and supports those DLLs for
redistribution.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Jim" <cook...@aol.com> wrote in message
news:%23jrJ20O...@TK2MSFTNGP11.phx.gbl...
Forgot to attach logfile.txt that I mentioned in my previous post! Dam* It!
Jim
"Jim" <cook...@aol.com> wrote in message
news:u%23SxPyOo...@tk2msftngp13.phx.gbl...