locked
App-V Client Timeouts - Error 4513CDC-19D06A0A-10000005 RRS feed

  • Question

  • App-V 4.5 has been working great for the most part…but I’ve been working WEEKS on this reoccurring issue, which I finally found a way to replicate. Here’s the issue:

    Two individually sequenced suites: Microsoft Office 2003 and Office 2007

    Individual user groups created for each Office application (Word 2003, Excel 2003, etc… / Word 2007, Excel 2007, etc…).

    If a user is assigned to MS Word 2003, MS Powerpoint 2003, MS Publisher 2003, etc (everything BUT Excel 2003), everything works just fine.

    If a user is assigned to MS Excel 2003, MS Powerpoint 2003, MS Publisher 2003, etc (everything BUT Word 2003), everything works just fine.

    If a user is assigned to MS Word 2003, MS Powerpoint 2003, MS Publisher 2003, and MS Excel 2003, client receives App-V Client Timeout Error 4513CDC-19D06A0A-10000005 and only one of the items (Word or Excel) appears

    So essentially, I cannot have a user assigned to both MS Word and MS Excel at the same time or I get a timeout. This even crosses the 2003/2007 Office boundaries. If a user is assigned Word 2003 and Excel 2007 (or vice versa), I get the timeouts with the same message.

     

    I have spent countless googling hours with the error code and everything around it and found nothing that applies (even articles such as http://support.microsoft.com/kb/930697 which seem right up the alley do not help).

     

    I’m stumped – any suggestions?

    Thanks,

    Jeremy Cioara

    Thursday, August 27, 2009 10:14 PM

Answers

  • Finally, two years later, I found the solution :). Thanks Tor-Andre for being the catalyst leading there. My Cisco ASA was performing RTSP inspection as described in this article:

     

    http://blogs.technet.com/b/appv/archive/2010/03/24/network-devices-that-use-rtsp-inspection-may-cause-problems-in-specific-app-v-scenarios.aspx

     

    Case closed.

    Wednesday, March 30, 2011 12:00 AM

All replies

  • Hello,

    How are those packages sequenced?

    /Znack
    Friday, August 28, 2009 6:16 AM
  • Hello Jeremy,

    You are aware of that if your Office applications are in the same package, user could launch other office apps [by browsing the installation directory from within published office app] from that same package even if you don't publish shortcuts to them, right? So by creating different groups for different apps does not provide real security as such.

    Ok, having that said, have you tried to enable verbose logging on the client and/or the server to see if there's anything more in the logs? And you haven't done any modifications to the OSDs after sequencing by hand?

    br,

    Kalle

    Thursday, September 10, 2009 3:52 PM
    Moderator
  • FYI:  I had these errors when trying to set up the trial system.  Everything suggested using port 554 and non-secure access.  In the OSD's I missed the fact that Microsoft had edited the RTSPS (real time streaming protocol secure) to RTSP (real time streaming protocol)  and used port 554 instead of port 332.  Getting these right in the OSD fixed my problems.
    Monday, September 28, 2009 8:43 PM
  • The problem sounds like an issue with how it was sequenced, not how it was deployed.  Please provide info on how it was sequenced to have the potential of usefull posts.
    • Proposed as answer by znack Saturday, March 20, 2010 9:05 AM
    • Unproposed as answer by Aaron.ParkerModerator Wednesday, July 13, 2011 11:28 AM
    Wednesday, September 30, 2009 12:38 AM
    Moderator
  • Did you find a solution for this problem JeremyCioara?
    Wednesday, March 17, 2010 10:26 AM
  • Thursday, March 25, 2010 7:26 AM
  • Finally, two years later, I found the solution :). Thanks Tor-Andre for being the catalyst leading there. My Cisco ASA was performing RTSP inspection as described in this article:

     

    http://blogs.technet.com/b/appv/archive/2010/03/24/network-devices-that-use-rtsp-inspection-may-cause-problems-in-specific-app-v-scenarios.aspx

     

    Case closed.

    Wednesday, March 30, 2011 12:00 AM