Software Deployment

I can't be certain in this case but, in my experience, almost *all* IS issues are caused by the now well-documented issue with the driver's COM Identity. Being v9 is even more of a clue.

Use AppDeploy's search facility and search for 'InstallShield DCOM'. Basically, the driver's identity needs to be set as 'Launching User' rather than 'Interactive User'. Luckily, this is normally as simply as removing a 'RunAs' entry from the registry. IIRC, there's a script available (here on AppDeply? I cann't remember...) that walks the GUIDs of all the known offenders and removes the entry from them.

Worth a try, anyway.

I used the VBS script from AngelD post and created a custom action for it.

It seems to work for the first time installing the software, but installing right after the uninstall results in a installation hang.

ORIGINAL: MARIN
I used the VBS script from AngelD post and created a custom action for it.

It seems to work for the first time installing the software, but installing right after the uninstall results in a installation hang. - Did the script run?
- Did it do any work (running and working being two separate things!) i.e. remove any RunAs entries?
- It may be that there is an additional entry which the script doesn't address. Have you looked into that possibility? Use DCOMCNFG to check whether the IS driver's Identity has changed.
- What errors do you see in the log?

My VMWare machine was a mess so I had to clean up.

I tried again and this is the result.

- The installation starts
- The MSI does not complain about any ISSETUP.msi missing
- The application itself installs succesfully

Before completing the installation the screen freezes. The added the command /l* log.txt with the following output.

Action ended 8:34:21: RenameTemplateFiles. Return value 1.
Action start 8:34:21: OnMoved.
Action ended 8:34:21: OnMoved. Return value 1.
Action start 8:34:21: InstallFinalize.
Action ended 8:35:12: InstallFinalize. Return value 1.
Action start 8:35:12: ISSelfRegisterFinalize.
Action ended 8:35:12: ISSelfRegisterFinalize. Return value 3.
Action start 8:35:12: ISCleanUpFatalExit.
Action ended 8:35:12: ISCleanUpFatalExit. Return value 3.

The VBS script to set the DCOM permissions seems to run succesfully:Action start 8:33:58: DCOM_PERM.
Action ended 8:33:59: DCOM_PERM. Return value 0.

I checked for the DCOM permissions in Component Services and all InstallShield InstallDriver are set on "The launching user."

Action ended 8:35:12: ISSelfRegisterFinalize. Return value 3 [shudder...] Man, I could strangle people who persist in this practise...

- Make a note of the entries in the ISSelfRegister table (or whatever it's called)
- Extract the COM information from those DLLs using the utility provided by your authoring tool (WiseComCapture for Wise, I've forgotten what the IS one is called)
- Import the resulting .REGs into your transform, electing to use the advertising tables if prompted
- Either remove the entries from that table or comment-out (or add an impossible-to-meet condition) for the ISSelfRegisterFinalize Custom Action.

Or, you could find out why the self-registration is failing (almost certainly a missing dependency) and fix that. A registry monitor will show you why the self-reg is failing.

Thank you for your reply. You pointed me in the right direction.

There where some entrees in the ISSelfReg table. I deleted these entrees in now the installation works fine. I can try to find the ID's of these COM objects and do the same thing as I did for the InstallShield installation.

It seems the application itself also registers com objects.

ORIGINAL: MARIN

Thank you for your reply. You pointed me in the right direction.

There where some entrees in the ISSelfReg table. I deleted these entrees in now the installation works fine. I can try to find the ID's of these COM objects and do the same thing as I did for the InstallShield installation.

It seems the application itself also registers com objects. The install works fine but what about the app? You still need to add the COM information from those DLLs, as you've removed the self-registration activity. The app will almost certainly try to create objects and fail without that information.

I'm pretty sure the app will only register the EXE (as any good COM server EXE should...)