Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Importing a deployment configuration file on App-V v5 fails with "The configuration file does not contain well formed AppV configuration XML"


View products that this article applies to.

Symptoms

When importing UserConfiguration.xml or DeploymentConfiguration.xml files on a Microsoft Application Virtualization (App-V) v5 Management Server you receive the following error:  

The configuration file does not contain well formed AppV configuration XML


On the App-V v5 Client, the following error occurs:

Add-AppvClientPackage : XML document could not be loaded because it is invalid. Please supply a valid XML document.
Please consult AppV Client Event Log for more details.
Operation attempted: Configure AppV Package.
AppV Error Code: 050009000A.
Please consult AppV Client Event Log for more details.
At line:1 char:1
+ Add-AppvClientPackage $P -DynamicDeploymentConfiguration $D
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
    + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage

Publish-AppvClientPackage : XML document could not be loaded because it is invalid. Please supply a valid XML
document. Please consult AppV Client Event Log for more details.
Operation attempted: Publish AppV Package.
AppV Error Code: 050009000A.
Please consult AppV Client Event Log for more details.
At line:1 char:1
+ Publish-AppvClientPackage PowerPointViewer2007 -DynamicUserConfigurationPath $U
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidResult: (:) [Publish-AppvClientPackage], ClientException
+ FullyQualifiedErrorId : PublishPackageError,Microsoft.AppV.AppvClientPowerShell.PublishAppvPackage

↑ Back to the top


Cause

This issue occurs because the TakeoverExtensionPointsFrom46 attribute in the deployment configuration file is case sensitive. 

Supported values: TakeoverExtensionPointsFrom46="true" or TakeoverExtensionPointsFrom46="false"

Unsupported values: TakeoverExtensionPointsFrom46="True" or TakeoverExtensionPointsFrom46="False"

↑ Back to the top


Resolution

Update the TakeoverExtensionPointsFrom46 attribute in the deployment configuration file to one of the following values:

TakeoverExtensionPointsFrom46="true" or TakeoverExtensionPointsFrom46="false"

↑ Back to the top


Keywords: kb

↑ Back to the top

Article Info
Article ID : 2778945
Revision : 2
Created on : 3/27/2020
Published on : 3/27/2020
Exists online : False
Views : 140