Using the Refresh Server option to refresh a Publishing Server from the Microsoft Application Virtualization Client MMC snap-in results in error code 2A-0000274D

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

SYMPTOMS

When you use the Refresh Server option to refresh a Publishing Server from the Microsoft Application Virtualization (App-V) Client MMC snap-in, you may receive the following error message: 

The Application Virtualization Client could not update publishing information from the server ServerName.
No connection could be made because the target machine actively refused it.
Error code: xxxxxxx-xxxxxx2A-0000274D

CAUSE

This issue can occur if the App-V client cannot communicate with the Publishing Server. 

RESOLUTION

Verify the Publishing Server settings are correct.

To verify this, perform the following steps on the App-V client:

1. In Administrative Tools, open the Application Virtualization Client MMC snap-in. 

2. Click Publishing Servers.

3. Right-click the server reporting the error code and then click Properties.

4. Verify the publishing server Type.

5. Verify the server name that is specified in the Host Name box.

6. Verify the port that is specified in the Port box.
 
If the Publishing Sever settings are correct, verify that the Application Virtualization Management Server service is started on the App-V server.

 To verify this, perform the following steps on the App-V Management Server: 

1. In Administrative Tools, open the Services MMC snap-in. 

2. Locate the Application Virtualization Management Server service.

3. Verify that the service is Started.

4. If the service is not started, right-click Application Virtualization Management Server, and then click Start.

5. If the service fails to start, search the Microsoft Knowledge Base for the error message that is reported. 

 If the Application Virtualization Management Server service is started, verify the App-V client can telnet to the server name and to the server port. 

To verify this, perform the following steps on the App-V client: 

1. At a command prompt, type telnet ServerName Port, and then press ENTER.

For example, type the following command:

telnet %SFT_SOFTGRIDSERVER% 554
 
2. If the connection succeeds, the window is blank. Press ENTER two times and you will receive the following message:

RTSP/1.0 400 Bad Request
Server: Microsoft Application Virtualization Server/x.x.x.xxxxx [Win32; Windows NT x.x ]
Date: xxx, xx xxx xxxx xx:xx:xx xxx

If the connection is unsuccessful, you receive the following message:

Could not open connection to the host, on port 554: Connect failed

If the Application Virtualization Management Server service is started but the client cannot telnet to the server, verify that port traffic between the client and the server is not restricted by a firewall or by other software. For more information, contact the network administrator.
 
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: 2266481 - Last Review: June 29, 2010 - Revision: 1.0
APPLIES TO
  • Microsoft Application Virtualization 4.5 for Terminal Services
  • Microsoft Application Virtualization 4.5 for Windows Desktops
  • Microsoft Application Virtualization 4.6 for Terminal Services
  • Microsoft Application Virtualization 4.6 for Windows Desktops
  • Microsoft Application Virtualization for Terminal Services
  • Microsoft Application Virtualization for Windows Desktops
Keywords: 
KB2266481

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