Hi,

Months ago I tried making a new software package (Mathcad 14). Unfortunately the MSI can’t run without setup.exe because it requires the ISSCRIPT9.msi installation.

I left the installation alone for some while, but now I read some information AngelD provided: http://itninja.com/question/msi-corporate-standardiser6&mpage=1&key=&#19850

I included the isscript9 merge module in the MSI and added the VBS script as custom action right before ISMsiServerStartup.

The first time installing the software the MSI completes successfully. Uninstalling the software is no problem.

When I try to install the software again, the installation screen freezes at: “Please wait while Windows configures Mathcad 14”

When accessing the log file, it returns the following:

Action ended 10:54:23: ISStartup. Return value 1.
Action start 10:54:23: AppSearch.
Action ended 10:54:23: AppSearch. Return value 1.
Action start 10:54:23: InstallCreateLog.
1: RPC runtime reported exception 0x6b5
Action ended 10:54:23: InstallCreateLog. Return value 1.
Action start 10:54:23: SetIsHelpInstalled.
1: RPC runtime reported exception 0x6b5
Action ended 10:54:23: SetIsHelpInstalled. Return value 3.
Action start 10:54:23: ISCleanUpFatalExit.
1: Shutting down the PRC server...
1: RPC runtime reported exception 0x6b5
Action ended 10:54:23: ISCleanUpFatalExit. Return value 3.

Anyone an idea?

It seems the ISSCRIPT is corrupt on the system.
I can install the ISSCRIPT9.msi manually, but installing the Mathcad MSI with the ISSETUPDRIVE=1 property gives the same result (hang).
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
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.
Answered 02/27/2008 by: VBScab
Red Belt

Please log in to comment
0
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.
Answered 02/27/2008 by: MARIN
Orange Senior Belt

Please log in to comment
0
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?
Answered 02/27/2008 by: VBScab
Red Belt

Please log in to comment
0
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."
Answered 02/28/2008 by: MARIN
Orange Senior Belt

Please log in to comment
0
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.
Answered 02/29/2008 by: VBScab
Red Belt

Please log in to comment
0
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.
Answered 02/29/2008 by: MARIN
Orange Senior Belt

Please log in to comment
0
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...)
Answered 02/29/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity