I did a little digging but didn't find anything so I hope I am not asking a multi-repeated question.

I am working with Marimba and I am doing a windows installer package.
Unfortunatly my MSI is not kicking off. I think I build the package right but I must be missing something if the MSI is getting delivered but Marimba isn't kicking it off.

Do you need a kick off script for windows installer packages?

thanks in advance for the help. It's my first day here. I hope to be helpful eventually.
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
There can be a few issues here.

*Are you positive the MSI is getting delivered?
*Does the MSI run manually on the target machine?
*Does the application show up as being installed in Channel Manager?

Check the latest history log file in the channel, should give you some insight on the issue.

Hope this helps!
Answered 10/17/2007 by: vjt914
Senior Yellow Belt

Please log in to comment
0
the MSI is getting delivered.
Marimba should run the MSI once it is delivered, thats where I hit my snag.
it varies depending on settings, once it showed successful but wasnt and another was pure failure.
Answered 10/17/2007 by: JSALSB
Senior Yellow Belt

Please log in to comment
0
Interesting. There is nothing that you have to set in the Windows Installer package (Marimba) that would initiate the MSI. It's really just as simple as importing your MSI and regardless of any customization to the MSI or package, it should run.

If you can, post the latest history log file from the channel in this forum. Browse to the Marimba workspace on the target machine, located wherever Marimaba is installed, and check the map.txt and find out which channel is for your MSI install. This will definately tell you why it's failing.

What MSI are you working with?
Answered 10/17/2007 by: vjt914
Senior Yellow Belt

Please log in to comment
0
what is your coomand for running the MSI? Are you running it silently? If not it will prompt for user imput.

Type msiexec at a command prompt for switches. Common install switches are:

msiexec /i <path to MSI> /qb

Check that and get back.
Answered 10/17/2007 by: Coriolus
Orange Belt

Please log in to comment
0
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): TTCSupport = 1
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): Time = 12:46:21
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): Date = 10/17/2007
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): MsiNetAssemblySupport = 1.1.4322.2032
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): MsiWin32AssemblySupport = 5.1.2600.3019
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): RedirectedDllSupport = 2
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): Privileged = 1
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): OriginalDatabase = C:\marimba\tuner\.marimba\Pepsi_Agent\ch.25173\data\msi\FMS.msi
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): UILevel = 3
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): MsiUIProgressOnly = 1
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): ACTION = INSTALL
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): ROOTDRIVE = D:\
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): CostingComplete = 0
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): OutOfDiskSpace = 0
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): OutOfNoRbDiskSpace = 0
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): PrimaryVolumeSpaceAvailable = 0
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): PrimaryVolumeSpaceRequired = 0
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: Property(S): PrimaryVolumeSpaceRemaining = 0
[17/Oct/2007:12:46:21 -0500] - audit jsalsb 9056 Adapter info: Windows Installer info: === Logging stopped: 10/17/2007 12:46:21 ===
[17/Oct/2007:12:46:21 -0500] - major jsalsb 9058 Adapter error: MSI installation failed: 1603
[17/Oct/2007:12:46:21 -0500] - critical jsalsb 9041 Install Failed
[17/Oct/2007:12:46:22 -0500] - audit jsalsb 1120 File map updated
[17/Oct/2007:12:46:22 -0500] - audit jsalsb 9510 Install Mode failed:
[17/Oct/2007:12:46:22 -0500] - major jsalsb 9001 Operation failed: , mode: 0, INSTALL
[17/Oct/2007:12:46:22 -0500] - audit jsalsb 9030 Adapter finished:
[17/Oct/2007:12:46:22 -0500] - audit jsalsb 1152 Channel instance stopped
Answered 10/17/2007 by: JSALSB
Senior Yellow Belt

Please log in to comment
0
I am using and MSI I created for an inhouse application.

the msi has been tested on several machines so I know that works ok.
just getting marimba to explode it.
Answered 10/17/2007 by: JSALSB
Senior Yellow Belt

Please log in to comment
0
I am sure I am just missing something.
I thought it might be user context but I am not selecting thato n my prescript and the windows installer isnt giving me that option like a standard file packager.
Answered 10/17/2007 by: JSALSB
Senior Yellow Belt

Please log in to comment
0
[17/Oct/2007:12:46:21 -0500] - major jsalsb 9058 Adapter error: MSI installation failed: 1603
See here http://support.installshield.com/kb/view.asp?articleid=q107182 for some help with 1603 errors
Answered 10/17/2007 by: VBScab
Red Belt

Please log in to comment
0
Google the error "msi error 1603"
And the first return is from appdeploy with: "In order to see just what the problem actually is you should enable Windows Installer logging which will allow you to view a log of all attempts and failures related to your installation. Generally this problem revolves around SYSTEM account permissions on the target system, free disk space on the target system, or bad file download or locked/inaccessable file."

Also http://support.installshield.com/kb/view.asp?articleid=Q107182 shows:
Symptoms
When running an InstallShield installation, the following error occurs at run time:
[blockquote]Error -1603: Fatal error during installation.[/blockquote]
[hr]

Cause
This error message is displayed by the Microsoft Windows Installer (MSI) engine and is a generic error code that indicates a problem occurred during the installation. The following is a non-exhaustive list of known causes for this error:

  • Short file name creation is disabled on the target machine.


  • An InstallScript custom action is prototyped incorrectly.


  • A file is locked and cannot be overwritten.


  • The Microsoft Windows Installer service is not installed correctly.


  • The Windows Temp folders are full.


  • The setup was corrupted after installation and, therefore, fails with this error during uninstallation.


  • An older version of InstallShield is being used.


  • A general error occurred during the installation.


  • File and Printer sharing is not enabled or was not installed when installing Windows
    Maybe the above could help?
  • Answered 10/17/2007 by: dnipe
    Yellow Belt

    Please log in to comment
    0
    ok
    I decided to give up on using the windows installed and just threw everything together into a file packager. I have run into another issue.
    once the MSI kicks off I keep running into an invalid S drive. I have a prescrpt mapped to that drive before the install and technically the people that are installing this MSI will already have it mapped but even with all of those things I am still getting this error.

    Has anyone ever run into a issue where mapped drives for an installing application doesnt work?
    Answered 10/23/2007 by: JSALSB
    Senior Yellow Belt

    Please log in to comment
    0
    Most deployment systems use the local System account to do their thing so I'd imagine Marima is no different. This account has no network access.
    Answered 10/23/2007 by: VBScab
    Red Belt

    Please log in to comment
    0
    The S: drive was probably your problem in the beginning - usually but not always that is what the 1603 eror is.

    NT runs as NT System authority which will not have the S: drive mapped.
    If you do not need the S: drive then you can do a pre-script (batch file) and run:
    subst s: c:\temp
    That should work. On the MSI isues you were having, if you run them noisy (Full GUI in the MSI) then you will see the error that is stopping the installation.
    Alternately you can always kick off verbose logging in the MSI install and see the errors there also.
    Answered 10/28/2007 by: nick3635
    Yellow Belt

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

    Share