Compartir a través de

App-V Support Tip: Publishing Server URL is unreachable after upgrade to 5.1

  • Artículo

~ John Behneman | Senior Support Escalation Engineer

imageHello everyone, John Behneman here again with a quick note on a Microsoft Application Virtualization 5.1 issue you may see after doing an upgrade from 5.0.

After upgrading App-V 5.0 Management and Publishing servers to App-V 5.1, you may encounter a problem where publishing no longer function properly and the following issues appear:

- Accessing the Publishing URL in Internet Explorer from directly on the Publishing Server (e.g. https://localhost:82 , where 82 is the port assigned to the Publishing Server Service) generates the following error message:

The website cannot display the page

- The event below is seen in Event Viewer\Applications and Servers logs\App-V\Server-Publishing-Private\Debug:

Failed to pre-load publishing metadata.
Message: Object reference not set to an instance of an object.
Details:
Stack Trace:
at Microsoft.AppV.Server.Publishing.PublishingMetadataSerializer.PackageSerializer.Load(XElement pkgElement, PublishingMetadata& data)
at Microsoft.AppV.Server.Publishing.PublishingMetadataSerializer.RootSerializer.Load(XmlReader reader)
at Microsoft.AppV.Server.Publishing.PublishingMetadataSerializer.LoadFromFile(String filePath)
at Microsoft.AppV.Server.Publishing.DataManager.ProcessRawMetadata()
at Microsoft.AppV.Server.Publishing.DataManager.PreLoadPublishingMetadata()
at Microsoft.AppV.Server.Publishing.DataManager..ctor()

Cause

This can occur if the PublishingMetaData.xml file on the App-V Management Server was not regenerated after the App-V 5.1 upgrade. The default location of this file is C:\programdata\microsoft\appv\server\Management\PublishingMetadata.xml.

Resolution

To resolve this issue, rename or deletethe PublishingMetadata.xml file on the App-V Management Server and run an IISREST from an elevated command prompt. An IISRESET may be required on each of the Publishing Servers as well.

John Behneman | Senior Support Escalation Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter :

clip_image001 clip_image002

System Center All Up: https://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: https://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: https://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: https://blogs.technet.com/momteam/ 
Service Manager Team blog: https://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: https://blogs.technet.com/scvmm

Microsoft Intune: https://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: https://blogs.technet.com/sus/
The RMS blog: https://blogs.technet.com/b/rms/
App-V Team blog: https://blogs.technet.com/appv/
MED-V Team blog: https://blogs.technet.com/medv/
Server App-V Team blog: https://blogs.technet.com/b/serverappv
The Surface Team blog: https://blogs.technet.com/b/surface/
The Application Proxy blog: https://blogs.technet.com/b/applicationproxyblog/

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

Comments

  • Anonymous
    October 22, 2015
    ~ Paul Westervelt | Support Escalation Engineer The purpose of this article is to demonstrate how you
  • Anonymous
    November 22, 2015
    Hi John, Do you mean IIRESET? no command IISREST is available
  • Anonymous
    February 13, 2016
    You are correct. it is IISRESET.