Software Deployment

The MapInfo installation is an InstallScript "enhanced" MSI and so requires the InstallShield Scripting Engine to be present on the target machine for it to work correctly.

As shipped, I think I am right in saying that there is a wrapper setup executable that the installing user normally runs to install MapInfo. This executable will first check that the correct version of the InstallShield Scripting Engine is installed in order to support the bulk of the installation. If there is no InstallShield Scripting Engine present, the executable will install the correct version for you (version 8, I think in this case).

If you have separated the wrapper executable from the main MapInfo MSI and are trying to install just from the MSI itself, you need to make some sort of alternative provision for the scripting engine to be installed / incorporated

Possible options are :

1) Install the Scripting Engine separately as a prerequisite - it is, itself, an MSI named ISSCRIPT8.MSI (for version 8) and should be somewhere on the installation CD for MapInfo.

or

2) Use the InstallShield Scripting Engine Merge Module available as a download from

http://saturn.installshield.com/isd/mergemodules/801/installshieldscriptingengine.msm

in conjunction with the MapInfo MSI

Assuming you are seeing the problems despite the engine being available then you are absolutely right in saying that there have been problems reported with DCOM permissions and the scripting engine. They seem to centre around the file IDRIVER.EXE and there are a number of discussions on the InstallShield forums about this.

One good link you could try is

http://community.installshield.com/showthread.php?t=117720&page=1&pp=5

It concerns problems with SMS rather than GPO deployment, but it will hopefully put you on the right track.

Regards,

Spartacus

Nice answer Spartacus I'm going to rate that a 2.

Thanx for your reply. I have made a few adjusments in the isscriptx.msi:

1) open isscript.msi, then navigate to registry table, remove the Registry601 entry (which is a RunAs InteractiveUser).

2) navigate to the RemoveRegistry table and add Registry601 entry, so that if there was already a key like that in the current registry it will get deleted.


I going to test some more...
thanx for your help

Nope didn´t work. I hate installshield.´s isscript....[:@][:@][:@]

The apps still freezes at install. Isscript is being installed before mapinfo. Does anybody else have these problems

This error looks like a dcom permission error - are you sure you've set the DCOM permissions for isscript? If you need some pointers, have a look at http://itninja.com/question/how-do-you-roll-out-new-machines?911&mpage=1&key=୯ - note that the GUID changes for different versions of isscript, you can check that out using dcomcnfg

Hope that helps

Rgds

Paul

Hi,

I have is Installation stuck problem some time back which has ISScript1050.
Please check eventlog, you should have a error with IDriver with out any reason.
This could be a problem with some custom action.

Thanks

Does it install correctly when you install it manually as a local administrator?

The DCOM issue is usually recognisable by the fact that the install works manually, but doesn't work using group policy or certain other deployment tools.

Sejacru, have you created an administrative install point?
I know not all InstallShield programs allow it, but running 'setup.exe /a' might create an administrative install point containing an MSI file that can be run without running setup.exe.

Yes manually it installs just fine. I have now created an administrative install point just as DR. Soup [:D] mensioned. So i will let you guys know if it is working now.

thanx for your reply

Nope didn't work either.....
next week must this go in produktion so....i think manually

Nope in the eventlog are no messages about idriver.exe
but when turning logging on in the msi i got the above error messges (see earlier post)

The first thing you should do is confirm whether it's a DCOM issue or not.

So try this:

1) Install the application.
2) Run "%SystemRoot%\system32\dcomcnfg.exe"
3) Browse to "Component Services\Computers\My Computer\DCOM Config\Installshield Driver" and check it's properties. What can you see under the identity tab? "Interactive User" or "Launching User"?
4) Check the properties of "InstallShield InstallDriver String Table" in the same why as above.

I have allready checked this.
Its a dcom permission problem.

But in my isscript1050.msi i have made a few adjustments:

1) open isscript.msi, then navigate to registry table, remove the Registry601 entry (which is a RunAs InteractiveUser).

2) navigate to the RemoveRegistry table and add Registry601 entry, so that if there was already a key like that in the current registry it will get deleted.

but the application still freezes on install.

ORIGINAL: sejacru

I have allready checked this.
Its a dcom permission problem.

But in my isscript1050.msi i have made a few adjustments:

1) open isscript.msi, then navigate to registry table, remove the Registry601 entry (which is a RunAs InteractiveUser).

2) navigate to the RemoveRegistry table and add Registry601 entry, so that if there was already a key like that in the current registry it will get deleted.

but the application still freezes on install.



The question is whether your changes are working?

What do the DCOM settings look like after installing your new MSI?

I embedded the following VBScript in my "Isscript.msi" just after "InstallFinalize" (immediate):

On Error Resume Next
Set oWsh = CreateObject("Wscript.Shell")
oWsh.RegDelete "HKCR\AppID\{E4A51076-BCD3-11D4-AB7D-00B0D02332EB}\RunAs"
oWsh.RegDelete "HKCR\AppID\{99BDE2B6-D79E-11D4-AB87-00B0D02332EB}\RunAs"
Set oWsh = Nothing

It did the trick for me... but it has to be said that my error was slightly different from yours.

I think the problem here is that the custom action ismsiserverstartup or isstartup in the MapInfo MSI may be reverting the DCOM registry settings back to their defaults despite all the efforts to get around this with the previous customised isscript8.msi running first.

Try running Regmon (available at http://www.sysinternals.com/Utilities/Regmon.html) and monitor the DCOM registry keys during execution of your main MapInfo.msi and see if they do get changed.

This will at least confirm whether the above is true.

Spartacus

thanx for your reply, i appriciate it.
Next week i have a day off, so i will check it.