Support Tip: Adding a virtual Office package in Microsoft Application Virtualization 5.0 fails with Error Code 1400000007


Tools

UPDATED 11/11/2014: This issue has been resolved in the latest Office packages that were released in October 2014. Please upgrade to build 15.0.4659.1001 or higher.

=====

Hi everyone, I just wanted to take a moment to let you know about an issue we recently discovered in App-V 5.0 when using the latest Office packages that were released in September.

The issue is that when adding a virtual Office package to Microsoft Application Virtualization 5.0, the action will fail if you are using the Office builds 15.0.4649.1001 or 15.0.4649.1003. The error you receive is:

Add-AppvClientPackage : Package manifest is invalid. Validation of elements in AppV namespace failed.
Operation attempted: Retrieve Package and Version IDs From Package URL.
AppV Error Code: 1400000007.
Please consult AppV Client Event Log for more details.

clip_image002

There are two options available to work around this issue:

1. Uninstall the September updates. Note that there were no security bulletins for Office in September.

2. Specify the older build version in the config.xml file so that the package uses that version. This can be done by updating the version field in the config.xmlfile as shown in the example below.

BEFORE

<Configuration>
  <Add SourcePath="…" OfficeClientEdition="…" Version="15.0.4649.1001">
  …
< /Configuration>

AFTER

<Configuration>
  <Add SourcePath="…" OfficeClientEdition="…" Version="15.0.4631.1002 ">
  …
< /Configuration>

Note that this issue will be fixed in the next Office update due in October.

Priya Raghavan | Senior Test Lead | Microsoft

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/


Comments (4)

  1. J.C. Hornbeck [MSFT] says:

    Thanks, fixed now.

  2. Ian says:

    Your version number has an extra 15.0 in it.

  3. Anonymous says:

    Here is a list of the top Microsoft Support solutions for the most common issues experienced when you

  4. Anonymous says:

    Here is a list of the top Microsoft Support solutions for the most common issues experienced when you

Skip to main content