none
Live Meeting 2007 Install Fails

    Question

  • I'm trying to install the Office Live Meeting 2007 Client (not the Outlook Add-In) on a Windows 7 (Enterprise) machine with Office 2010 Professional Plus.  Half way through I get "The installer was interrupted before Microsoft Office Live Meeting 2007 could be installed. You need to restart the installer to try again."

    Naturally, if I try again I get the same error.

    I have enabled installer logging and found this line in the log file.

    MSI (s) (2C:74) [12:46:40:142]: Doing action: MsiProcessDrivers
    Action 12:46:40: MsiProcessDrivers.
    Action start 12:46:40: MsiProcessDrivers.
    MSI (s) (2C:74) [12:46:40:143]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'MsiProcessDrivers'
    MSI (s) (2C:10) [12:46:40:146]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI2E07.tmp, Entrypoint: ProcessDriverPackages
    DIFXAPP: ERROR - The operating system you are running on is not supported. Only Windows 2000, Windows XP, Windows Server 2003 and Windows codenamed Longhorn are supported.
    CustomAction MsiProcessDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    Action ended 12:46:40: MsiProcessDrivers. Return value 3.
    MSI (s) (2C:74) [12:46:40:181]: Machine policy value 'DisableRollback' is 0
    MSI (s) (2C:74) [12:46:40:181]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (2C:74) [12:46:40:183]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (2C:74) [12:46:40:184]: Calling SRSetRestorePoint API. dwRestorePtType: 13, dwEventType: 103, llSequenceNumber: 133, szDescription: "".
    MSI (s) (2C:74) [12:46:40:184]: The call to SRSetRestorePoint API succeeded. Returned status: 0.
    MSI (s) (2C:74) [12:46:40:184]: Unlocking Server
    Action ended 12:46:40: INSTALL. Return value 3.

    Thoughts?  I downloaded the most recent version of the client from the Live Meeting support site (believe it is the Jan 2011 update).

    Tuesday, February 08, 2011 5:43 PM

All replies

  • Hi, would you please install LiveMeeting on other computers try again, if works fine on other computers, then this is a problem related to computer rather than LiveMeeting software. If the LiveMeeting software doesn't work on all computers, please let me know. thanks.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, February 09, 2011 6:52 AM
  • I've seen this multiple times myself.  If I install Live Meeting right after and initial Windows 7 install, no problem.  But, if I try after I apply all patches, and have installed Office 2010, this is what I get.  Extremely annoying, and it's not related to the computer, as I can reproduce this rather easily on different physical and virtual machines - I ran into it yet again tonight, and came across this post while searching for an answer. This is a major pain, as I am building a base corporate image and don't want to have to start over just to get Live Meeting installed.  Yes, I should have remebered to install it earlier, but I shouldn't HAVE to worry about it at all.

    Sunday, February 20, 2011 5:18 AM
  • Hi  , I have the same problem with me , I suppose there's no solutions for this matter still.
    Thursday, May 19, 2011 2:32 AM
  • Hi, I've experienced the same issue and after digging through the MSI and looking at some posts - I was able to modify the MSI so that it would process the "customaction.dll".

    The following two links pointed me in the direction of examining the UAC as a source of the issue and modifying the action so it ran in the system context.

    http://blogs.msdn.com/b/cjacks/archive/2006/10/30/deferred-custom-actions-and-permissions-on-windows-vista-with-uac-enabled.aspx

    http://ezhnotes.blogspot.com/2008/09/change-msi-to-run-under-custom-actions.html

    The modifications that I performed on the MSI were to modify the custom action table.  For the SetInstallCookie action I changed the Type to 3073.  This is 1025 plus the 0x800 bitmask that changes this action to run in the context of system rather than user.

    <snip>

    However, you can specify that the custom acton will not use impersonation. By including in the bitmask msidbCustomActionNoImpersonate == 0x800, you will no longer be impersonating the currently logged in user (with their non-elevated token), and instead be running with system privileges just like the rest of the MSI installation. This avoids the issue of an access denied message being triggered by some action in the MSI (at the expense of removing the user impersonation). In the above example, we would use msidbCustomActionTypeInScript | msidbCustomActionTypeDll | msidbCustomActionNoImpersonate == 0x400 | 0x1 | 0x800 == 0xC01 == 3073

    <snip>

    This, I believe, is what is causing the MSI to error out.  SCCM trying to deploy this, running under the SYSTEM account and not being able to run this action.

    I modified the values and saved the MSI under another file name - with the included streams. It would probably also work with a transform, but I have not fully tested that.

    I deployed the newly created MSI with SCCM 2012 in the lab environment to multiple VM Windows 7 guests, and then performed a deployment to a test collection in the production SCCM environment. MSI log files show success on the custom actions.

    This may not represent the best way to workaround the 1603 errors I have been seeing, but it was one method that worked for me. Your mileage may vary, but I would appreciate any detailed follow-up that anyone has the chance to document.

    thx,


    Thursday, October 10, 2013 7:22 PM
  • I cracked open the Live Meeting msi with Installshield, navigated Direct Editor, selected the CustomAction Table, changed the Type to 3073 for SetInstallCookie action, and saved the msi.  When I deploy the application through SCCM 2012 the installer log gives the following error:

    CustomAction SetInstallCookie returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    Is there anything else I'm missing to get this to install?

    Wednesday, January 22, 2014 10:12 PM
  • I know this thread is old, but did you get an answer DirectorZ?  I'm having this issue as well.  Interesting that this msi deployed fine with SCCM 2007, but does not work with SCCM 2012.  I always get the 1603 error. I've tried, newer, older msi's.  Tried transforming and directly editing the msi.  Always the 1603.
    Tuesday, July 15, 2014 3:31 PM
  • I was able to get this working today in ConfigMgr 2012R2.  Had the exact same issues as noted above.
    I used Orca to create a Transform File with this Modification:
    Table = CustomAction
    Action: SetInstallCookie - Right Click -> Drop Row
    Save Transform as LMConsole.mst

    I then Run a script for the install

    copy LMConsole.mst c:\cabs\LMConsole.mst /Y
    msiexec.exe /i "LMConsole.msi" /qn /log "C:\cabs\installlogs\LiveMeeting.log" TRANSFORMS=c:\cabs\LMConsole.mst
    del c:\cabs\LMConsole.mst /F /S /Q

    Hope that Helps


    • Edited by blokg Monday, May 04, 2015 7:31 PM
    Monday, May 04, 2015 7:16 PM
  • Instead of changing the SetInstallCookie custom action type value to 3073, set it to 1089. That takes the original value of 1025 and changes it from the default of Synchronous Fail with Non-0 return to Synchronous Ignore Exit Code.

    https://msdn.microsoft.com/en-us/library/aa368071(v=vs.85).aspx

    • Proposed as answer by PwrshllJerry Wednesday, September 02, 2015 10:14 PM
    Wednesday, August 26, 2015 4:16 PM
  • Instead of changing the SetInstallCookie custom action type value to 3073, set it to 1089. That takes the original value of 1025 and changes it from the default of Synchronous Fail with Non-0 return to Synchronous Ignore Exit Code.

    https://msdn.microsoft.com/en-us/library/aa368071(v=vs.85).aspx

    This is correct.  Installing Live Meeting to 40 computers through AD machine policy.  5 failed over and over.  JeremyJackson FTW!
    Thursday, May 12, 2016 6:36 PM
  • Sadly the standalone release from September 2017 does not correct this defect so many thanks to those who shared their solution!

    Microsoft allegedly patched Live Meeting 2007 and so far despite the doco posted at https://support.microsoft.com/en-us/help/4025868/descriptionofthesecurityupdateforofficelivemeetingconsoleseptember12-2 the update has not been released to Windows update as of last Thursday. 

    Sunday, October 08, 2017 1:49 PM