locked
Installing software with the MSI file. RRS feed

  • Question

  • I ran a test for a package using it's MSI installer in Interactive mode, it worked fine. when trying silen mode, nothing happens. I used the
    file.msi /qn as the setup line, assuming that would be enough.
    what AM i doing wrong?
    Wednesday, November 18, 2009 3:01 PM

Answers

  • 1603 is a generic error code from Windows Installer. 

    The error will be in that full msi installation log... but yeah, I know it's a big pain to read.  If you haven't ever looked at Windows Installer tables, properties, actions, sequences... it can be hard to even find where the error is listed.  As a huge generalization, the real error will be about 2/3rds of the way down in the log file.  I usually work my way backwards in the log.
    Standardize. Simplify. Automate.
    Wednesday, November 18, 2009 11:49 PM

All replies

  • Have the installation drop a log file locally, and see what the MSI itself has to say about what the problem is, like this:

    file.msi /qn /l*v c:\File.log

    c:\file.log will say exactly what it's whining about--it might be buried--sometimes those MSI log files aren't the easiest things to interpret because you have to know a little bit about Windows Installer sequences, actions, etc., but it will be in the log.


    Standardize. Simplify. Automate.
    Wednesday, November 18, 2009 4:02 PM
  • OK, I have added the log file and will wait for results.
    Sort of a dumb question, when you install using the MSI, is it still necessary to to add the MSI again into the windows installer tab?
    Wednesday, November 18, 2009 4:07 PM
  • By adding the MSI file again in the Windows installer tab, you 'give' the package an unique identifier. This identifier is used when distributing the package to distribution points. When a client requests the package, it uses the Windows Installer product code to check which distribution points have the correct package. At least, this is one of the features, so it's always good to set it!
    Wednesday, November 18, 2009 4:55 PM
  • Thanks for the clarification, so I am glad I added it!
    Here is the log so far, the actual package number is TOS0001A.
    I still cannot see the advertisement on the client. This goes through a protected branch distribution point, to a client in the boundary assigned, and the package was successfully copied.

    The logged on user is TOS\Shraq    execmgr    11/18/2009 5:57:37 AM    1456 (0x05B0)
    The user has logged off.    execmgr    11/18/2009 5:59:40 AM    1996 (0x07CC)
    Execution Manager timer has been fired.    execmgr    11/18/2009 6:00:40 AM    1996 (0x07CC)
    ContentAvailable ignoring update with no DPs for content request ID {B34B4DA2-58D9-4D03-B457-C33C32D05E39}    execmgr    11/18/2009 7:11:19 AM    3536 (0x0DD0)
    Policy deleted for advertisement TOS20015 package TOS00018 program Office Communicator 2007    execmgr    11/18/2009 7:20:24 AM    1196 (0x04AC)
    Policy was deleted or expired for program Office Communicator 2007. Remove the execution request.    execmgr    11/18/2009 7:20:24 AM    1196 (0x04AC)
    Policy arrived for parent package TOS0001A program Communicator 07R2    execmgr    11/18/2009 6:18:30 AM    3104 (0x0C20)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramOfferReceivedEvent
    {
        AdvertisementId = "TOS20016";
        ClientID = "GUID:FB9FA98F-BC00-49A9-A877-2C2296F815F8";
        DateTime = "20091118161830.606000+000";
        MachineName = "ADMIN01";
        ProcessID = 320;
        SiteCode = "TOS";
        ThreadID = 3104;
    };
        execmgr    11/18/2009 6:18:30 AM    3104 (0x0C20)
    A user has logged on.    execmgr    11/18/2009 8:41:21 AM    1968 (0x07B0)
    The logged on user is TOS\Shraq    execmgr    11/18/2009 8:41:21 AM    1968 (0x07B0)
    The user has logged off.    execmgr    11/18/2009 8:42:48 AM    1968 (0x07B0)
    A user has logged on.    execmgr    11/18/2009 8:47:35 AM    2568 (0x0A08)
    The logged on user is TOS\Shraq    execmgr    11/18/2009 8:47:36 AM    2568 (0x0A08)
    The user has logged off.    execmgr    11/18/2009 8:50:13 AM    2796 (0x0AEC)
    Execution Manager timer has been fired.    execmgr    11/18/2009 8:51:13 AM    3248 (0x0CB0)

    Wednesday, November 18, 2009 5:01 PM
  • oh, I think I gave you bad information then.  I thought that the MSI package wasn't installing correctly, but the advertisement itself was running.

    So, question: Advertisement ID TOS200016: has this client run this advertisement before? in your previous, not-the-silent program settings?  If so, you may need to use one of the multiple tools out there to tell a client to "rerun this mandatory advertisement just this once more".  I use Roger Zanders Client Center to do that, although there are multiple methods to get this done.
    Standardize. Simplify. Automate.
    Wednesday, November 18, 2009 8:52 PM
  • i ran the advertisement on machines that did not have it before, and this is the error i got:
    Script for Package:TOS0001A, Program: Communicator 07R2 failed with exit code 1603    execmgr    11/18/2009 12:46:48 PM    3140 (0x0C44)
    I have the full MSI install log, but cannot find any errors. I looked at http://support.microsoft.com/default.aspx/kb/834484 , but I do not think they apply. The only thing might be permission, but the install runs with a domain admin credentials.
    Will this be the right place to post it?
    I just found something very odd. Both my branch servers have disappered from the package advertisement after the failure, and their SMSPKG$ directory is gone. I am speechless. is it a software error??
    Wednesday, November 18, 2009 9:46 PM
  • 1603 is a generic error code from Windows Installer. 

    The error will be in that full msi installation log... but yeah, I know it's a big pain to read.  If you haven't ever looked at Windows Installer tables, properties, actions, sequences... it can be hard to even find where the error is listed.  As a huge generalization, the real error will be about 2/3rds of the way down in the log file.  I usually work my way backwards in the log.
    Standardize. Simplify. Automate.
    Wednesday, November 18, 2009 11:49 PM
  • The error was right where you said it was. Turns out the MSP integration to the MSI did not succeed despite saying it did... all fixed now.
    Thursday, November 19, 2009 7:17 AM