8 replies to this topic

[jkames]

I have a product with several different installs. A customer ran the first install with no problems. When they tried to run the second install they just get the SetupCompleteError dialog. When I looked at the log file from this install, I found that the install is failing after it calls the first CA with a Return value of 3.
This CA is IS Script code that reads an environment variable ( ComputerName) and sets a property. This same code exists in the first install they successfully ran.

Does any one have any sugguestions on what to try to get this install to run. I've had them reboot and it didn't make a difference.

I have a machine here which I've been able to reproduce this problem. I ran the first install successfully, I ran the second install successfully. I then removed the second install. When I try and run the second install again I get the error. If I try and re-run the first install I get the problem.

Thanks,

John Ames
Clarus Corporation

[jkames]

Looking at the log file I came across this:

MSI © (88:8C): Doing action: EngineStartup
Action start 15:14:14: EngineStartup.
MSI © (88:8C): Creating MSIHANDLE (1) of type 790542 for thread 1676
1: extracting engine MSI file
1: Installing kernel files
1: scpthdlr.dll
1: After file installation, return code = 128
1: ikernel.exe
1: After file installation, return code = 0
1: iuser.dll
1: After file installation, return code = 0
1: knlwrap.exe
1: After file installation, return code = 128
1: msihook.dll
1: After file installation, return code = 0
1: objectps.dll
1: After file installation, return code = 0
1: Installing script engine
1: iscript.dll
1: After file installation, return code = 0
Action ended 15:14:15: EngineStartup. Return value 1.
MSI © (88:8C): Doing action: StartUp
Action start 15:14:15: StartUp.
MSI © (88:8C): Creating MSIHANDLE (37) of type 790542 for thread 1676
1: Extracting support files...
1: Checking product language...
1: Constructing string table...
1: Creating script engine
1: Starting script engine COM server...
1: Opening script file...
1: Starting Kernel wrapper...
1: Failed to create script engine...

Anyone know what the return code=128 means?
Is there anything I can do in the Install to ensure that the script engine is created successfully?

Thanks,

[Matt Hicks]

I have the same problem except some of the retrun codes are a little different.  If anyone knows a solution would you please post it and also notify Installshield then maybe we can get a work around for this issue
.
I talked to Installshield and they say that  "They have no issues in their records that are like the one I have experienced".  

If we were to make it known to them that this is indeed an issue and it's not just me that is having this problem then maybe they will look into it further.

Thanks,

--Matt

[jkames]

I have opened a support issue using my 30 days free support, and have not been able to get any resolution on this issue. I agree with Matt, if everyone experiencing this problem can let InstallShield know, by opening a support issue, maybe it will put more pressure on them to come up with a fix.

[SteveP]

Quick question:  Do you have the log from a successful install?  What is the value that appears on the same line as the 128 in the installation that failed?

The return value on the CA (3) is a fatal error.  Generally, if the Installer reports that the script engine can't be built, it means that the CA failed to compile.  You may want to see if you can grab the computer name in another way.  I don't use IS, but the following code in VB will return the computer name:

Dim wshnetwork
Dim Name
Set wshnetwork = CreateObject("WScript.Network")
Name = wshnetwork.ComputerName

[Stefan Krueger]

Note that there is a predefined property [ComputerName]

[jkames]

Thanks,

I've already started ripping the IS Script code out of my install and replacing it with the 'Windows Installer' equivalent method.

Unfortunately, since we shipped this as the "GA" release of the software, I can't go back and re-do what has been sent to our customers.

[Matt Hicks]

I have clients that are experiencing the same symptoms but my CA is not trying to get computer name.  Our problem is that when any custom action (on certain machines) gets called, setup goes directly to the SetupCompletError screen.  

I have sent the users ORCA in order to take out CA's and if they do so then they get one step further into the setup until the next CA is called then it fails again.  Custom Actions are a must in our setup.

As for SteveP's question the return code is usually "0" for those files when our install is a success.

--Matt

[Richard Eyre Todd]

(More evidence of something going wrong, no solution as yet sadly.)

I'm trying to create an installation package for Windows 95/98/NT/2000 using ISWI 2.03.

One of the many problems I've had includes the following:

I modify the installation package to detect a previous version of my product by using the Upgrade table, changing the product code/version number etc, and calling FindRelatedProducts. I need to move the RemoveExistingProducts action to lie between InstallValidate and InstallInitialise, so that my previous application files will be unregistered before they are deleted/overwritten by the new versions. Ah, now I've done it. The installation comes to a crunching halt after detecting the previous product and uninstalling it. "The wizard has been interrupted before the application was completely installed." But only under 95. Under NT, it works. Getting desperate, I install ISWI 2.03 under 95 and NT and difference the log files:

95 Log file:
<blah>
Action ended 10:01:48: RemoveExistingProducts. Return value 1.
MSI © (2D:05): Doing action: InstallInitialize
Action start 10:01:48: InstallInitialize.
MSI © (2D:05): BeginTransaction: Locking Server
MSI © (2D:05): Server not locked: locking for product {8760E910-9DA4-11D2-B6D2-00E029B09B27}
MSI © (2D:05): Searching for item Products\019E06784AD92D116B2D000E920BB972 in per-user non-managed key
MSI © (2D:05): Searching for item Products\019E06784AD92D116B2D000E920BB972 in per-machine key
MSI © (2D:05): Did not find item Products\019E06784AD92D116B2D000E920BB972
MSI © (2D:05): Searching for item Products\019E06784AD92D116B2D000E920BB972 in per-user non-managed key
MSI © (2D:05): Searching for item Products\019E06784AD92D116B2D000E920BB972 in per-machine key
MSI © (2D:05): Did not find item Products\019E06784AD92D116B2D000E920BB972
Action ended 10:01:49: InstallInitialize. Return value 1.
MSI © (2D:05): Doing action: Rollback_CleanUp
Action start 10:01:49: Rollback_CleanUp.
Action 10:01:49: GenerateScript. Generating script operations for action:
GenerateScript: Rollback_CleanUp
Action ended 10:01:49: Rollback_CleanUp. Return value 1.
MSI © (2D:05): Doing action: CheckForPreviousFiles
Action start 10:01:49: CheckForPreviousFiles.
MSI © (2D:05): Creating MSIHANDLE (152) of type 790542 for thread -815867
Action ended 10:01:49: CheckForPreviousFiles. Return value 3.
MSI © (2D:05): User policy value 'DisableRollback' is 0
MSI © (2D:05): Machine policy value 'DisableRollback' is 0
MSI © (2D:05): Note: 1: 1402 2: Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI © (2D:05): Note: 1: 1402 2: Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI © (2D:05): Unlocking Server
Action ended 10:01:49: INSTALL. Return value 3.
Action ended 10:01:49: ExecuteAction. Return value 3.
MSI © (2D:05): Doing action: SetupCompleteError
Action start 10:01:49: SetupCompleteError.
Action 10:01:49: SetupCompleteError. Dialog created
Action start 10:01:53: CleanUp.
Action ended 10:01:53: CleanUp. Return value 1.
Action ended 10:01:53: SetupCompleteError. Return value 2.
Action ended 10:01:53: INSTALL. Return value 3.
<setup terminates shortly thereafter>

NT log:
<blah>
Action ended 14:35:18: RemoveExistingProducts. Return value 1.
MSI (s) (0C:CE): Doing action: InstallInitialize
Action start 14:35:18: InstallInitialize.
MSI (s) (0C:CE): BeginTransaction: Locking Server
MSI (s) (0C:CE): Server not locked: locking for product {8760E910-9DA4-11D2-B6D2-00E029B09B27}
MSI (s) (0C:CE): Searching for item Products\019E06784AD92D116B2D000E920BB972 in per-user managed key
MSI (s) (0C:CE): Searching for item Products\019E06784AD92D116B2D000E920BB972 in per-user non-managed key
MSI (s) (0C:CE): Searching for item Products\019E06784AD92D116B2D000E920BB972 in per-machine key
MSI (s) (0C:CE): Did not find item Products\019E06784AD92D116B2D000E920BB972
MSI (s) (0C:CE): Searching for item Products\019E06784AD92D116B2D000E920BB972 in per-user managed key
MSI (s) (0C:CE): Searching for item Products\019E06784AD92D116B2D000E920BB972 in per-user non-managed key
MSI (s) (0C:CE): Searching for item Products\019E06784AD92D116B2D000E920BB972 in per-machine key
MSI (s) (0C:CE): Did not find item Products\019E06784AD92D116B2D000E920BB972
Action ended 14:35:18: InstallInitialize. Return value 1.
MSI (s) (0C:CE): Doing action: Rollback_CleanUp
Action start 14:35:19: Rollback_CleanUp.
Action 14:35:19: GenerateScript. Generating script operations for action:
GenerateScript: Rollback_CleanUp
Action ended 14:35:19: Rollback_CleanUp. Return value 1.
MSI (s) (0C:CE): Doing action: CheckForPreviousFiles
Action start 14:35:19: CheckForPreviousFiles.
MSI (s) (0C:CE): Creating MSIHANDLE (230) of type 790542 for thread 206
Action ended 14:35:48: CheckForPreviousFiles. Return value 1.
<setup continues nicely after this point and completes successfully>

So it looks like my custom action 'CheckForPreviousFiles' is failing under 95, but not NT. Sadly, it makes not a jot of difference what this custom action does. I've changed it to simply return ERROR_SUCCESS with the exact same result. When I run the installation package again, this time round there is no uninstallation of the previous product to be done and the process runs to completion. The act of running the Standard Action RemoveExistingProducts seems to cause the next Custom Action to fail with error code 3.