Application Virtualization TechCenter > Microsoft Application Virtualization (App-V) Forums > App-V Clients > Cannot refresh publishing server (45242F4-19D0810A-10000005)
Ask a questionAsk a question
 

QuestionCannot refresh publishing server (45242F4-19D0810A-10000005)

  • Wednesday, October 21, 2009 7:57 PMMike Crowley Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    When I attempt to refresh my publishing server from the App-V client after a few seconds I get:

    ---------------------------

    Application Virtualization Error

    ---------------------------

    The Application Virtualization Client could not update publishing information from the server OTB6APPVT01.

     

    A network operation did not complete in time. Check your network connection, and then try again. If the problem persists, report the following error code to your System Administrator.

     

    Error code: 45242F4-19D0810A-10000005

     

    ---------------------------

    OK   

    ---------------------------

     

    Then in the application log of the machine I see:

    Log Name:      Application

    Source:        Application Virtualization Client

    Date:          10/21/2009 3:53:29 PM

    Event ID:      3131

    Task Category: (25)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      OT-CNU9249WL7.ad.domain.com

    Description:

    {tid=E4C:usr=c488796}

    Failure on Desktop Configuration Server request to URL {rtsp://OTB6APPVT01.ad.domain.com:554/} with header {Host: OTB6APPVT01.ad.domain.com

    Content-Type: text/xml

    } (rc 19D0810A-10000005).

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Application Virtualization Client" />

        <EventID Qualifiers="16384">3131</EventID>

        <Level>2</Level>

        <Task>25</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2009-10-21T19:53:29.000Z" />

        <EventRecordID>737</EventRecordID>

        <Channel>Application</Channel>

        <Computer>OT-CNU9249WL7.ad.domain.com</Computer>

        <Security />

      </System>

      <EventData>

        <Data>{tid=E4C:usr=c488796}

    </Data>

        <Data>rtsp://OTB6APPVT01.ad.domain.com:554/</Data>

        <Data>Host: OTB6APPVT01.ad.domain.com

    Content-Type: text/xml

    </Data>

        <Data>19D0810A-10000005</Data>

      </EventData>

    </Event>

     

    Not sure what I’m doing wrong.  From the client I can telnet to 554 on the streaming/management server without issue.  I am using the new App-V 4.5 SP1 on Windows Vista SP1.  My server is Win 2008 x86.

    I saw this, but the proposed resolutions did not help me.
    http://support.microsoft.com/kb/930697

    When I do a packet capture from the client I see:

    61.495308 sftlist.exe {RTSP:25, TCP:24, IPv4:7} OTB6APPVT01.ad.domain.com 10.200.224.189 RTSP RTSP:RESPONSE, RTSP/1.0, Status Code = 401 - Unauthorized



    I would assume this is related but not really sure what component is "unauthorized".


    UPDATE:
    When I open the osd file from \\OTB6APPVT01\Content I get a authentication pop-up box from the App-V client.  I enter my windows logon credentials and the package works as expected.  Does this mean there is a problem with NTLM?  It would seem the streaming works, its just the authentication and publishing elements.

    • Edited byMike Crowley Thursday, October 22, 2009 12:28 AMmore detail
    •  

All Replies

  • Thursday, October 22, 2009 2:02 PMkirk_tn Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I didn't see this error message before, but some things you could test.

    - Domain trust realtionship
    It might be the case that your Client/Users on the one hand and your Servers on the other hand are on different domains. The "server domain" has to trust request from the "client domain". It also might be that during logon the client does not authenticate against the domain (but uses cached credentials). Also you should check if the client machine still is a valid member of the domain (try to log onto that client with a user that never logged on before).

    - There is a small chance that the user you are using is not member of App-V's "default" user group. You may check in the Server Management Console the "Provider Policies" node, there is a Default Provider. Open in an verify that the user is member of the group listed there (In fact I doubt that is the problem because this would cause other error messages)



    Falko
  • Thursday, October 22, 2009 2:12 PMMike Crowley Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks for your reply.  The user is a member of both the admins and users group that was defined in the app-v install.  They are also joined to the same domain.  I've also rebooted several times during my test and I dont imagine cached credentials are the issue.  But I'll check this.