3 replies to this topic

[sklett]

Hi-

I attempted to install some symantec software yesterday and I received an error: 1607: Unable to install InstallShield Scripting Runtime.

SO I started with that error, found the many posts on the web about checking C:\WINNT\Installer permission. Both Administrators group as well as System have FULL control.

SO I moved on, trying other things. I tried to re-install the MSI service, but after downloading the file: InstMsiW.exe and trying to install it, I get the error: "The specified service already exists"

OK, moving right along I do more searches and find a tool from MS called the "Cleanup Tool" or something( InstMsiW.exe ) - now when I try to run this file I get the error: "This installation package could not be opened. Verify that the package exists and that can access it......blah blah blah"

I've rebotted
I've checked for new SPs
I've read all I can find on these specific errors....

I'm stuck. Does anyone know what in the world is happenign on this machine? It's a win2k Server machine, sp4.
I'm attempting all these installs, etc from a remote machine. I'm logged in as administrator. Everything should be fine.

Looking forward to any help or tips you might have!!

Thanks,
Steve Klett

[Glytzhkof]

Unfortunately I am all too familiar with this error message. It actually has nothing to do with the windows installer engine itself. As the error message states it is the Installshield scripting engine that cannot be correctly installed. This is Installshield's own API. It must be installed to run any Installscript custom actions.

The problem is that it is installed using a modified MSI database that installs files without component GUID's. This MSI is run in silent mode from the setup.exe bootstrapper, and whenever it returns some sort of error message this error message you mention seems to show up. As such the error message tends to occur for more than one type of errors. In my world the error message now means "something is wrong in the user profile for the user installing, and it could be just about anything".

There are several things you can try. Installshield has a knowledge base article that describes a pletora of options. However, what normally works for me is to create a local admin user on the problem system and then run the installation using this account. Since this user account has just been created there is less of a chance that it has a messed up registry, and hence the installation tends to work correctly. Still, there could be many other reasons for the problem, and if it doesn't work with the new user look up the Installshield KDB article I mentioned above.

[mishka]

I'm seeng this message too, a lot of times.. How can I understand from log file what actually wrong with user's profile ?

[Glytzhkof]

Given that you have a verbose log file there is a tool called WILogUtl.exe in the windows installer SDK that you can use to analyze it.

Look for the section "How can I figure out why my package fails to install?" on this page: http://www.microsoft...122123121120120

Edited by Glytzhkof, 19 May 2004 - 11:52.