Office 2013 with Visio and Project Error - Package manifest is invalid

Question

In July I successfully created an App-V install of Office 2013 VL using the ODT. This week I decided to try just doing Visio as we don't install it or Project on all systems. I used my same customconfig.xml and just changed the ProPlusVolume to VisioProVolume
and changed the source path. Everything downloaded and packaged fine. I was able to import into SCCM just fine and create a deployment to my test collection. However when I run the install out of Software Center I get (as part of a much longer error) the message
in AppEnforce.log that the package manifest is invalid. Thinking that maybe I had to include Office as long with Visio I tried packaing all three items but still get the same error. Has anyone else seen this behavior and/or ideas how to fix it? Can I sequence
just Visio or just Project? I'm including my config.xml just in case I've got something wrong with it that I haven't caught. Thanks
 <Configuration>
  <Add SourcePath="<networkpath>\Microsoft\AppVOffice2013\Sept\" OfficeClientEdition="32" >
    <Product ID="ProPlusVolume">
    <Language ID="en-us" />
    </Product>
    <Product ID="VisioProVolume">
    <Language ID="en-us" />
    </Product>
    <Product ID="ProjectProVolume">
    <Language ID="en-us" />
    </Product>
  </Add>
  <Display Level="None" AcceptEULA="TRUE" />
  <Logging Name="OfficeSetup.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Answer 1

Hy. I'm having the same problema.
I'm trying to create na app-v package (v.5 SP2) of Office 2013.
I downloaded the Office Deployment Tool for Click-to-Run from here:
http://www.microsoft.com/en-us/download/details.aspx?id=36778
I installed it into C:\Office2013pck shared that folder as 
\\APPVMANAGER\Office2013 and mapped as Z:\.
I changed the configuration.xml file to:
<Configuration>
<Add OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
Then I ran in na elevated cmd:
>Z:
>\\APPV-CL-WIN7DEF\Office2013\setup.exe /download
\\APPV-CL-WIN7DEF\Office2013\configuration.xml
and
>\\APPV-CL-WIN7DEF\Office2013\setup.exe /packager
\\APPV-CL-WIN7DEF\Office2013\configuration.xml
\\APPV-CL-WIN7DEF\Office2013\Appv
Everything seemed to work fine.
The creted folder had Office\Data\15.0.4649.1001 folder (I guessed this is a version number)
When I tried to add the package to App-V Server (in the Console) I get the following error:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I tryied to publish it from powershell, getting the same error message agalluci image post shows.
From the Event Log I got this additional information:
There was a problem retrieving the requested package \\APPVMANAGER\AppVpck\Office\VisioProVolume_ProPlusVolume_en-us_x86.appv for import. Error message: Unspecified error
Element '{http://schemas.microsoft.com/appv/2010/manifest}UsedKnownFolders' is unexpected according to content model of parent element '{http://schemas.microsoft.com/appx/2010/manifest}Package'.
I haven't found any indication of which file is the manifest app-v file.
I also haven't found any .xml with the "UsedKnownFolders" tag (I changed the .appv package extension to .zip and explored some of the files).
I tryied creating a package for 32 and 64 bits, only office, office and visio, and office visio and project running Windos 7 and Windows 2012.
Thanks in advance for any help.