locked
App-V Client could not update publishing information from server. No Connection could be made because the target machine actively refused it. RRS feed

  • Question

  • Running App-V 4.5 CU 1  on both client and server, trying to test the "default application" and got the error message below when trying to refresh the client.

    "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: 4513CDC-19D0682A-0000274D"

    What am I missing here?  Any help is appreciated, I'm new to App-V.

    Thanks, -marcelo
    Friday, April 17, 2009 1:10 AM

Answers

All replies

  • Try this out to see if it will get you on your way.

    http://support.microsoft.com/default.aspx/kb/930730/en-us

    mattmcdermott
    Friday, April 17, 2009 3:04 AM
    Moderator
  • Almost certainly indicates that the "Application Virtualisation Management Server" Service isn't running for one reason or another.. 
    Friday, April 17, 2009 8:00 AM
  • Hi Marcello,


    With App-V 4.5, the default app has RTSPS enabled in the CODEBASE by default regardless if you are able to enable on Management Server or not. In your case, I see you are refreshing from normal RTSP port but trying to stream in from RTSPS.

    So edit the DefaultApp.osd file and change RTSPS to RTSP and port from 322 to 554.

    GRz

    Roelk

    Roel
    • Proposed as answer by Bruno Estrozi Friday, April 24, 2009 8:08 PM
    Friday, April 17, 2009 9:39 AM
  • I altered the DefaultApp.os as you mentioned above, I followed the instructions on "App-V 4.5 Trial Guide". Thank you.
    Friday, April 17, 2009 3:39 PM
  • You were right, the "Application Virtualisation Management Server"  Service wasn't running. 

    Wouldn't be easy to just get an error message saying that? Thanks. -m
    Friday, April 17, 2009 3:41 PM
  • that' very helpfull, turned ou the "Application Virtualisation Management Server"  Service wasn't running. Thanks. -m

    Friday, April 17, 2009 3:42 PM
  • Thanks for the information. I had the similar problems but turned out that I had done 3 things wrongly,

    1. "Application Virtualization Management service" was not running
    2. DNS configuration for the client machine was pointing to wrong DNS server
    3. I had mistyped port number in .OSD file to 544 instead of 554

    Regards,
    Sandeeo
    Monday, May 11, 2009 10:54 AM
  • Hi there,

    I have the same error BUT...

    1 service is running
    2 DNS ok
    3 OSD is correct 554

    4 no firewall
    5 telnet to server and port 554 is succesfull

    any ideas?

    regards Leeuw

    Tuesday, June 15, 2010 4:03 PM