The Microsoft App-V Team Blog

The official blog for Microsoft Application Virtualization

Solution: A virtualized application on a Microsoft App-V client fails to launch with Error Code: 2A-00002AF9

Solution: A virtualized application on a Microsoft App-V client fails to launch with Error Code: 2A-00002AF9

  • Comments 2
  • Likes

KB

Just an FYI on a new Microsoft Application Virtualization (App-V) Knowledge Base article we published today.  If you're having trouble running virtualized apps on your clients and getting something along the lines of Error Code: xxxxxxx-xxxxxx2A-00002AF9 then you'll want to check this one out:

Symptoms

An application on an App-V client fails to launch with the following error:

The Application Virtualization Client could not launch application name.
No such host is known.
Error Code: xxxxxxx-xxxxxx2A-00002AF9

Cause

This issue can occur if the server name specified in the HREF attribute in the application .osd file is incorrect.

Resolution

To resolve this issue, perform the following steps:

1. On the App-V Management Server, open the application .osd file and scroll down to the following line:

<CODEBASE HREF="rtsp://servername:554/ApplicationDirectory/Application.sft"

2. Verify that the server name specified in the HREF attribute is correct.

Example: If the App-V Management Server name is Appv-Svr, the HREF attribute should look like the example below:

<CODEBASE HREF="rtsp://Appv-Svr:554/ApplicationDirectory/Application.sft"

3. Once the sever name is corrected in the application .osd file, open the Application Virtualization Client MMC snap-in on the App-V client and refresh the Publishing Server.

4. Launch the application on the App-V client.

For the latest version of this information please see the following new Knowledge Base article:

KB2271253 - A virtualized application on a Microsoft App-V client fails to launch with Error Code: 2A-00002AF9

J.C. Hornbeck | System Center Knowledge Engineer

clip_image001 clip_image002

Comments
  • Any movement on getting a hotfix out so we can sequence and deploy Visual Studio 2010 sometime before 2011?

    Apparently we're not the only one experiencing the issue: social.technet.microsoft.com/.../2d5f572a-f764-468e-816e-6c8b8c42265a

    It would be nice to have some official nod on this...

  • This is definitely something we're working hard on but I don't really have anything concrete to offer right now.  As soon as I hear something I'll be sure to post it here.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment