Hi All,

The product Autosys is a vendor MSI which contains
2 custom actions employed in it.

It shows description as below When you open vendor MSI with wise package studio:

1.WiseScript.EXE detected in Binary table row 'WiseCustomCalla'. Binary row updated.
2.WiseScript.EXE detected in Binary table row 'setSybaseEnv'. Binary row date updated

I came to know that It is adding 2 files in the binary table so that is creating a problem.


Basically the problem is that we're able to create a transform for this vendor MSI with wise package studio but when you run vendor MSI with the MST. It is failing with the below error.

Please find following exerpts from the LIME verbose log pertaining to the error:

MSI (s) (74!34) [12:08:59:317]: Product: AutoSys Remote Agent v4.5.1D for 64-bit Windows -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: , location: WiseCustomCall, command: g2

Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: , location: WiseCustomCall, command: g2
CustomAction setSybaseEnv returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 12:08:59: InstallFinalize. Return value 3.
Action ended 12:09:04: INSTALL. Return value 3.
MSI (s) (74:04) [12:09:04:351]: Product: AutoSys Remote Agent v4.5.1D for 64-bit Windows -- Installation operation failed.

MSI (s) (74:04) [12:09:04:352]: Windows Installer installed the product. Product Name: AutoSys Remote Agent v4.5.1D for 64-bit Windows. Product Version: 1.4. Product Language: 1033. Manufacturer: CA, Inc.; package produced by AMRS Distributed Job Scheduling. Installation success or error status: 1603.

Can anyone give a hand in resolving this issue?


 

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

Are you saying that running the vendor MSI silent results in a successful installation?

If so, it sounds like opening the MSI in Wise is causing the issue as it's attenpting to update the items in the Binary table.

How about using Orca to create an MST with whatever options you need setting (you've used the InstallTailor to identify what those are already), taking Wise totally out of the equation?

 

Hope that helps,

Dunnpy

Answered 11/26/2012 by: dunnpy
Red Belt

Please log in to comment
1

Day one of the Wise Package Studio course..."When creating transforms for vendor-supplied MSIs, it's best to apply the read-only file attribute to the MSI."

Answered 11/26/2012 by: VBScab
Red Belt

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