locked
Office 2013 Packager failed: Office (32-bit) not packaging because of Office (64-bit) RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,


    I used ODT to download Office 2013 Pro 32-bit and now I am trying to create a package from those files. I use the command line:


    Setup.exe /packager configuration.xml "E:\Office 2013 Pro App-v"


    When I try to run this, I immidiatly get the following message:

    "We found a problem! We're sorry, Office (32-bit) couldn't be installed because you have these 64-bit Office programs installed on your computer. Microsoft Office 2013. 32-bit and 64-bit versions of Office programs don't get along, so you can only have one type installed at a time. Please try installing the 64-bit version of Office instead, or uninstall your other 64-bit Office programs and try this installation again."


    I checked my installed programs on the server, but I don't have Office 2013 64-bit installed. I did in the past create packages for Office 2013 64-bit , but it's currently not in published/installed on the server. I checked with revo uninstaller to be sure.


    Is there a registry setting, or something that is misleading App-V to believe I still have Office 2013 64-bit somewhere installed? I really need to stream MS Access 32-bit to users. But cannot solve this issue.


    Thanks in advance,

    Monday, September 22, 2014 9:11 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    Run the ODT on another VM then. Preferably one with nothing else installed on it.


    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or 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.


    This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.

    Twitter: @stealthpuppy | Blog: stealthpuppy.com | The Definitive Guide to Delivering Microsoft Office with App-V

    Tuesday, September 23, 2014 10:27 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Fixed this issue for now, by using another version of Office 2013 Pro. Using the .1002. 

    Thread can be closed.

    • Proposed as answer by znack Tuesday, September 30, 2014 6:56 PM
    • Marked as answer by Brandon RecordsModerator Tuesday, September 30, 2014 8:16 PM
    Sunday, September 28, 2014 8:41 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    The current configuration file I'm using to sequence:

    <Configuration>

      <Add SourcePath="E:\DGI Applicaties\DGI Office 2013 Pro" OfficeClientEdition="32" >
        <Product ID="ProPlusVolume">
           <Language ID="nl-nl" />
     <ExcludeApp ID="Excel" />
     <ExcludeApp ID="Groove" />
     <ExcludeApp ID="Infopath" />
     <ExcludeApp ID="Lync" />
     <ExcludeApp ID="OneNote" />
     <ExcludeApp ID="Outlook" />
     <ExcludeApp ID="Powerpoint" />
     <ExcludeApp ID="Project" />
     <ExcludeApp ID="Publisher" />
     <ExcludeApp ID="SharePointDesigner" />
     <ExcludeApp ID="Visio" />
     <ExcludeApp ID="Word" />
        </Product>
      </Add> 

         <Updates Enabled="False" />

         <Display Level="None" AcceptEULA="TRUE" /> 

       <Logging Name="Office2013_package.txt" Path="%temp%" />

      <Property Name="AUTOACTIVATE" Value="1" />

    </Configuration>

    Tuesday, September 23, 2014 7:23 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Run the ODT on another VM then. Preferably one with nothing else installed on it.


    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or 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.


    This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.

    Twitter: @stealthpuppy | Blog: stealthpuppy.com | The Definitive Guide to Delivering Microsoft Office with App-V

    Tuesday, September 23, 2014 10:27 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Thanks for replying. Your solution works, BUT I'm immidiatly running into a second problem. The .appv package that is created, cannot be published. The error I get is:

    An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.

    I think this has to do with issues in the september releases of Office 2013. I'm gonna try downloading a previous versin using ODT. Changing the configuration.xml file to:

    <Configuration>

      <Add SourcePath="E:\DGI Applicaties\DGI Office 2013 Pro" OfficeClientEdition="32" Version="15.0.4631.1002" >
        <Product ID="ProPlusVolume">
           <Language ID="nl-nl" />
     <ExcludeApp ID="Excel" />
     <ExcludeApp ID="Groove" />
     <ExcludeApp ID="Infopath" />
     <ExcludeApp ID="Lync" />
     <ExcludeApp ID="OneNote" />
     <ExcludeApp ID="Outlook" />
     <ExcludeApp ID="Powerpoint" />
     <ExcludeApp ID="Project" />
     <ExcludeApp ID="Publisher" />
     <ExcludeApp ID="SharePointDesigner" />
     <ExcludeApp ID="Visio" />
     <ExcludeApp ID="Word" />
        </Product>
      </Add> 

         <Updates Enabled="False" />

         <Display Level="None" AcceptEULA="TRUE" /> 

       <Logging Name="Office2013_package.txt" Path="%temp%" />

      <Property Name="AUTOACTIVATE" Value="1" />

    </Configuration>


    • Edited by Andee_1979 Wednesday, September 24, 2014 10:57 AM
    Tuesday, September 23, 2014 10:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Cannot solve the XML Parse errors.. Keep running into manifest error when trying to publish the package by console or powershell.
    Thursday, September 25, 2014 2:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Fixed this issue for now, by using another version of Office 2013 Pro. Using the .1002. 

    Thread can be closed.

    • Proposed as answer by znack Tuesday, September 30, 2014 6:56 PM
    • Marked as answer by Brandon RecordsModerator Tuesday, September 30, 2014 8:16 PM
    Sunday, September 28, 2014 8:41 PM