Software Deployment

Secondlaw,

I'm not sure if you and I are having the same problem but the results are the same and I'm puzzled. Our XP SP2 core build contains both ISScript 10 (actually 10.1.0.238) and 10.5 (I think that 10.5 was put down by Roxio CD Creator). I have an app, SmartView 11 that uses ISScript 10. The SV11 install fails and my log file looks almost like yours, but farther up in the log there is a CA that looks to see if ISScript is installed and it reports "InstallShield Script Engine version is adequate". Then it continues and fails the install just like yours.

I'm trying to figure out how to get rid of the 10.1 ISScript as I think it's corrupted in the image (I can't uninstall it - it says it's not installed but the Service is running). Maybe your problem and mine have the same root maybe?

If someone has a suggestion, that would be nice. [;)] As it is, I'm thinking about creating a wrapper that uninstalls 10.5, then, somehow, stops the service, then removes all the associated files and keys for 10, then installs ISScript 10 and then I can call the install of SV11. Doesn't sound very pretty...

I'll wager that, before that error, you've got an error 'Cannot find InstallDriver in ROT table'. If so, you have the old IS chestnut, LaunchingUser versus InteractiveUser. This is a subject which has been dealt with extensively here and elsewhere. Use the 'Search' facility for details.

ORIGINAL: VBScab

This is a subject which has been dealt with extensively here and elsewhere. Use the 'Search' facility for details.


Is this what you were referring to:
http://www.appdeploy.com/messageboards/printable.asp?m=31300

ORIGINAL: VBScab

I'll wager that, before that error, you've got an error 'Cannot find InstallDriver in ROT table'. If so, you have the old IS chestnut, LaunchingUser versus InteractiveUser. This is a subject which has been dealt with extensively here and elsewhere. Use the 'Search' facility for details.


ooooh k. and what exactly am I searching for? I've had this issue with many installshield (sucks) apps. I've yet to find a solution that actually works! I've tried the vbscripts for Dcom permissioning, I've tried the vbscripts for killing idriver, etc... I'm really at a loss here. I thought this was an issue with just 1 app but now I'm running into it again within 2 weeks. This isscript thing is BS.

@bearden3: Yes, exactly right.

@Secondlaw: and what exactly am I searching for?In any log, you want to find the FIRST instance of the text 'Return value 3'. The dozen or so lines above and below that text will point to the main cause of the failure.

Have you ensured that the IS-fixing script includes the GUIDs for ALL the IS versions? IIRC, the version which is most widely available only goes as far as v8 and IIRCA, there was a slip-up in one flavour of v10 which repeated the error. Thus, you need to find the AppIDs for each version that you want to fix and add it to the fix-up script.

FWIW, at my last client, we gave up including the script in IS-driven packages and just created a separate package with the fix in and distributed it globally (after having fixed the rogue MSIs, of course).

Can you point me in the direction for the IS Fixing script? I searched but could not locate it.

See the link in post #4. Part of the thread it links to contains the script. Or you could search for "Interactive User" on AppDeploy.

Can you point me in the direction for the IS Fixing script? I searched but could not locate it.

I'm afraid SecondLaw that Ian was talking about a custom made company-specific package for IS. So there's no ready-made package floating around there.

That being said however, I'm pretty sure the Installshield Engine gets distributed in MSI-form (isscript11.msi, isscript12.msi). These files should be readily downloadable and can form the basis for a standalone InstallShield Engine package.

Rgds,

PJ

pj,

isscript10.msi was supplied with the vendor package. This is one of those "issetupdriven" packages. I am installing isscript first via altiris, then installing the main package. In a previous package, isscript 10 was mandatory as the main .msi had a CA which specifically looked for v10. So if v11 was on the machine, it would not work. You had to install 10 and kill all idriver processes, then launch idriver.exe (v10).

So, I used a vbscript found on this site which actually took care of killing all instances of the idriver processes, then used the Dcom permission vbscript just for extra credit. :) This worked but only on some machines.

I don't understand why people use installshield in this line of work. I've used it before and thought it was pretty good but seeing how this isscript thing has become such an issue, I would not recommend using it. Wise is the way to go (IMHO).

Wise is the way to go if you want to be tied in to a supplier whose committment to the product is (being kind) patchy. I prefer WPS by a long way but can no longer recommend it because of that lack of committment. v8? Do me a favour...we all know it's v7 SP4.

IS is a "problem" only for packages which use IS-specific functionality. It's no different to using, say, the Web site stuff in Wise. That produces CAs which call functions in custom DLLs.

I don't understand why people use installshield in this line of work. I've used it before and thought it was pretty good but seeing how this isscript thing has become such an issue, I would not recommend using it. Wise is the way to go (IMHO).

I agree that ISScript is an absolute pain in the ass when you run into it in an MSI. I wouldn't link the use of InstallShield to InstallScript though. nothing says because you use Installshield you have to use InstallScript. Personally I prefer InstallShield Adminstudio over WPS for day to day use, but that in no way implies I use ISScript (in fact I'll shoot myself before ever creating a package that uses it)

pjgeutjens
Personally I prefer InstallShield Adminstudio over WPS for day to day use, but that in no way implies I use ISScript (in fact I'll shoot myself before ever creating a package that uses it)

I use both WPS 7 and AS 9.5 in my job and while I prefer using WPS, I don't have a problem using AS. I agree with you that I would shoot myself before using ISScript; I'll use VBScript and put it into the package. I don't think that ISScripts are portable but VBScripts are - another good reason for using VBScript instead of ISScript.

Sounds like there really is no solution to many of the problems people have been experiencing. This is too bad. The worse part about my issue is that it's intermittent. It works on some systems but doesn't work on others.

You haven't yet confirmed whether or not you're seeing the 'Cannot find InstallDriver in ROT table' error, so the whole script thing could be a red herring. We're also in the dark as to whether or not you added all the AppIDs for the different versions.

Yep... Sorry about that, I am in fact receiving that error.

...in which case, you're definitely on the trail of fixing the DCOM identity.