How to troubleshoot publishing server refresh failures in App-V v5

Article ID: 2778168 - View products that this article applies to.
Expand all | Collapse all

Summary

This article discusses how to troubleshoot publishing server refresh failures on Microsoft Application Virtualization (App-V) v5 clients. Perform the steps listed in the More Information section to troubleshoot this issue.

More information

Step 1: Verify the Publishing Server URL configured on the client

To verify the Publishing Server URL, perform the following steps:

1. On the App-V Client, open an elevated PowerShell command prompt.

2. Type Get-AppvPublishingServer and hit enter.

3. Verify the URL listed in the output is correct.
If the Publishing Server name is PubSvr and the publishing server port is 82, the URL listed in the Get-AppvPublishingServer output should be: http://PubSvr:82 or https://PubSvr:82

If the Publishing Server URL is incorrect, use the Remove-AppvPublishingServer cmdlet to remove the Publishing Server. Then use the Add-AppvPublishingServer cmdlet to add the Publishing Sever with the correct URL.

Sample commands to remove and re-add the Publishing Server:

Remove-AppvPublishingServer -ServerId 1
Add-AppvPublishingServer -Name PublishingSever -URL http://PubSvr:82

Common errors that are logged on the App-V client if the Publishing Server URL is incorrect:
  • Powershell

Sync-AppvPublishingServer : Application Virtualization Service failed to complete requested operation.
Operation attempted: RefreshPublishingServer.
Internet Error: 0x80072EE7 - The server name or address could not be resolved
Error module: Publishing. Internal error detail: 45500D2780072EE7.
Please consult AppV Client Event Log for more details.

Sync-AppvPublishingServer : Application Virtualization Service failed to complete requested operation.
Operation attempted: RefreshPublishingServer.
AppV Error Code: 0500090001.
Error module: Shared Component. Internal error detail: 3E50110500090001.
Please consult AppV Client Event Log for more details.
  • APP-V Event Log

Log Name:      Microsoft-AppV-Client/Admin
Source:        Microsoft-AppV-Client
Event ID:      19102
Task Category: Publishing Refresh
Level:         Error
Description:
Getting server publishing data failed.
 URL: http://PubSvr:82/
 Error code: 0x45500D27 - 0x80072EE7

Log Name:      Microsoft-AppV-Client/Admin
Source:        Microsoft-AppV-Client
Event ID:      19203
Task Category: Publishing Refresh
Level:         Error
Description:
HttpRequest sendRequest failed.
 URL: http://PubSvr:82/
 Error code: 0x45500D27 - 0x80072EE7

Log Name:      Microsoft-AppV-Client/Admin
Source:        Microsoft-AppV-Client
Event ID:      19205
Task Category: Publishing Refresh
Level:         Error
Description:
The content from server is not valid XML for publishing.
 URL: http://PubSvr:82/
 Error code: 0x3E501105 - 0x90001

Log Name:      Microsoft-AppV-Client/Admin
Source:        Microsoft-AppV-Client
Event ID:      19102
Task Category: Publishing Refresh
Level:         Error
Description:
Getting server publishing data failed.
 URL: http://PubSvr:82/
 Error code: 0x3E501105 - 0x90001

Step 2: Add Windows Firewall exception on the Publishing Server

If the Windows Firewall is enabled on the Publishing Server, an Inbound Rule must be added to allow inbound connections on the port used by the Publishing Server.

To add an Inbound Rule, perform the following steps:

1. On the Publishing Server, open the Windows Firewall.

2. Click Advanced Settings.

3. Right-click on Inbound Rules and select New Rule.

4. Select Port and click Next.

5. Select TCP, specify the port used by the Publishing Server and click Next.

6. Select the appropriate connection condition for your environment and click Next.

7. Select the appropriate profile and click Next.

8. Provide a name for the Inbound Rule and click Finish.

Common errors that are logged on the App-V client if the firewall port is blocked:

  • Powershell
Sync-AppvPublishingServer : Application Virtualization Service failed to complete requested operation.
Operation attempted: RefreshPublishingServer.
Internet Error: 0x80072EE2 - The operation timed out
Error module: Publishing. Internal error detail: 45500D2780072EE2.
Please consult AppV Client Event Log for more details.

  • App-V Event Logs

Log Name:      Microsoft-AppV-Client/Admin
Source:        Microsoft-AppV-Client
Event ID:      19102
Task Category: Publishing Refresh
Description:
Getting server publishing data failed.
 URL: http://PubSvr:82/
 Error code: 0x45500D27 - 0x80072EE2

Log Name:      Microsoft-AppV-Client/Admin
Source:        Microsoft-AppV-Client
Event ID:      19203
Task Category: Publishing Refresh
Description:
HttpRequest sendRequest failed.
 URL: http://PubSvr:82/
 Error code: 0x45500D27 - 0x80072EE2

Step 3: Verify the Publishing Server site is started on the Publishing Server

To verify the Publishing Server site is started, perform the following steps:

1. On the Publishing Server, open the IIS Manager console.

2. Click Sites.

3. Verify the Microsoft App-V Publishing Service site is Started.

Common errors that are logged on the App-V client if the Publishing Server site is not started:
  • Powershell

Sync-AppvPublishingServer : Application Virtualization Service failed to complete requested operation.
Operation attempted: RefreshPublishingServer.
Internet Error: 0x80072EE2 - The operation timed out
Error module: Publishing. Internal error detail: 45500D2780072EE2.
Please consult AppV Client Event Log for more details.

  • App-V Event Logs

Log Name:      Microsoft-AppV-Client/Admin
Source:        Microsoft-AppV-Client
Event ID:      19102
Task Category: Publishing Refresh
Level:         Error
Description:
Getting server publishing data failed.
 URL: http://PubSvr:82/
 Error code: 0x45500D27 - 0x80072EE2

Log Name:      Microsoft-AppV-Client/Admin
Source:        Microsoft-AppV-Client
Event ID:      19203
Task Category: Publishing Refresh
Level:         Error
Description:
HttpRequest sendRequest failed.
 URL: http://PubSvr:82/
 Error code: 0x45500D27 - 0x80072EE2

Step 4: Verify the Publishing Server application pool is started on the Publishing Server


To verify the Publishing Server application pool is started, perform the following steps:

1. On the Publishing Server, open the IIS Manager console.

2. Click Application Pools.

3. Verify the AppVPublishing application pool is Started.

Common errors that are logged on the App-V client if the AppVPublishing application pool is not started:
  • Powershell
Sync-AppvPublishingServer : Application Virtualization Service failed to complete requested operation.
Operation attempted: RefreshPublishingServer.
Windows Error: 0x801901F7 -
Error module: Publishing. Internal error detail: 45500D27801901F7.
Please consult AppV Client Event Log for more details.

  • App-VEvent Logs

Log Name:      Microsoft-AppV-Client/Admin
Source:        Microsoft-AppV-Client
Event ID:      19102
Task Category: Publishing Refresh
Level:         Error
Description:
Getting server publishing data failed.
 URL: http://PubSvr:82/
 Error code: 0x45500D27 - 0x801901F7

Log Name:      Microsoft-AppV-Client/Admin
Source:        Microsoft-AppV-Client
Event ID:      19203
Task Category: Publishing Refresh
Level:         Error
Description:
HttpRequest sendRequest failed.
 URL: http://PubSvr:82/
 Error code: 0x45500D27 - 0x801901F7

Step 5: Verify the Publishing Server URL is accessible using a web browser

On the App-V client, access the publishing server URL (e.g., http://PubSvr:82/) using a web browser. If the publishing server is working properly and is accessible, an XML output will be displayed which lists the applications published on the Publishing Server:

- <Publishing Protocol="1.0">
- <Packages>
  <Package PackageId="639138dd-a4f5-4846-bab2-02e94a87c8a6" VersionId="b29da9c2-07d1-4fac-97ca-4f081c487c79" PackageUrl="\\pubsvr\content\Office 2013 AppV Package\ProPlusVolume_VisioProVolume_ProjectProVolume_en-us_x86.appv" /> 
  </Packages>
- <NoGroup>
  <Package PackageId="639138dd-a4f5-4846-bab2-02e94a87c8a6" />
  </NoGroup>
  </Publishing>

In the example above, Office 2013 is the only package currently published on the Publishing Server.

Step 6: Perform a publishing server refresh

After performing the steps above, perform a manual publishing refresh to verify no errors are logged.

There are two methods to manually perform a publishing refresh:
  • In Powershell, use the Sync-AppvPublishingServer cmdlet.
  • In the App-V client console, click Update
Note: The Update box will be greyed out if a publishing server hasn’t been configured on the client machine.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2778168 - Last Review: November 1, 2012 - Revision: 1.0
Applies to
  • Microsoft Application Virtualization 5.0 for Terminal Services
  • Microsoft Application Virtualization 5.0 for Windows Desktops
  • Microsoft Application Virtualization Hosting 5.0 for Windows Desktops
Keywords: 
KB2778168

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com