Application Virtualization TechCenter > Microsoft Application Virtualization (App-V) Forums > App-V 4.5 Beta (Retired) > "... could not update the Desktop configuration information from the server SG1."
Ask a questionAsk a question
 

Proposed Answer"... could not update the Desktop configuration information from the server SG1."

  • Wednesday, March 05, 2008 5:47 AMbarkingdog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I’m following the  “MS Desktop Optimization Pack: MS Application Virtualization, Version 4.5, Trial Guide.”   My SoftGrid management server is  called “SG1”; Desktop client “SG2’.

     

    On page 21, item 16, I am told to select “Refresh Server” in the Desktop client  on SG2. When I do I get the error

    >>> 

    “The SoftGrid client could not update the Desktop configuration information from the server SG1.

    No connection could be made because the target machine actively refused it”

    Error code:  450260-19D06C2A-0000274D.

    >>> 

     

    And indeed no Desktop icon (on SG2) is produced.

    The sftlog.txt file  on SG2 shows

    >>> 

    [03/04/2008 21:22:09:527 MIME ERR] {tid=F5C:usr=bills}

    Failure on Desktop Configuration Server request to URL {rtsps://SG1:554/} with header {Host: SG1

    Content-Type: text/xml

    } (rc 19D06C2A-0000274D).

    >>> 

     

     

    Help!

     

    TIA,

     

    barkingdog

     

All Replies

  • Wednesday, March 05, 2008 8:22 AMRodney MedinaMVP, AnswererUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    The log says to stream over the rtsps protocol over port 554. This is not correct. You either need to stream over rtsp with port 554 or rtsps with port 332.

     

    So first check the OSD file of the application and see if the error is in there.

     

    If not check the client and see if the server is not accidentally pointing to "Secure SoftGrid Virtual Application Server" instead of "SoftGrid Virtual Application Server".

     

    And last check the properties of the client if it is not accidentally configured to only allow secure connections.

     

    Regards,

    Rodney

     

  • Wednesday, March 05, 2008 9:07 PMSeanDo-MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I'd have to agree. Seems like during the client install the default allow only secure connections was chosen (port 322 now in 4.5). Is the SGVAS setup for secure connections as well? With certificates?

     

    Gene F wrote a great blog on installing the certificates for SG on the team blog.

     

     

  • Thursday, March 06, 2008 4:49 AMbarkingdog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Rodney,

     

    You wrote

     

    >>>

    If not check the client and see if the server is not accidentally pointing to "Secure SoftGrid Virtual Application Server" instead of "SoftGrid Virtual Application Server".

    >>>

     

    Yes, it was set to Secure mode. I changed it and, for good measure, rebooted the SG Management Server and the Desktop client. Finally in the Desktop client I right-clicked Refresh Server but got the same error dialog box as before, Here are the detials of the log:

     

     

     

    [03/05/2008 20:17:12:301 SRVC WRN] {tid=708}
    --------------------------------------------------------
    Initialized client log (C:\Program Files\Microsoft SoftGrid\Microsoft SoftGrid Application Virtualization for Desktops\sftlog.txt)

    [03/05/2008 20:17:12:471 VSCM INF] {tid=708}
    Starting Virtual Service Control Manager.


    [03/05/2008 20:17:12:772 JGSW INF] {tid=708}
    The SoftGrid file system was initialized successfully.


    [03/05/2008 20:17:13:112 INTF WRN] {tid=708}
    The SoftGrid Client Core initialized correctly.
    Installed Product:
    Microsoft SoftGrid Application Virtualization for Desktops
    Version: 4.5.0.608 (Beta)
    Install Path: C:\Program Files\Microsoft SoftGrid\Microsoft SoftGrid Application Virtualization for Desktops
    Global Data Directory: C:\Documents and Settings\All Users\Documents\
    Machine Name:
    SG2
    Operating System: Windows 2003 Terminal Server Service Pack 2.0 Build 3790
    OSD Command: "C:\Program Files\Microsoft SoftGrid\Microsoft SoftGrid Application Virtualization for Desktops\sfttray.exe" "%1" %*


    [03/05/2008 20:17:13:112 SRVC INF] {tid=708}
    ---- The SoftGrid Client Service version 4.5.0.608 has started ----

    [03/05/2008 20:18:10:020 MIME ERR] {tid=738:usr=bills}
    Failure on Desktop Configuration Server request to URL {rtsps://SG1:554/} with header {Host: SG1
    Content-Type: text/xml
    } (rc 19D06C2A-0000274D).


    [03/05/2008 20:26:22:414 SRVC WRN] {tid=980}
    Unable to cancel wait operation. error: 997

    [03/05/2008 20:26:22:644 SRVC WRN] {tid=DF0}
    Unable to cancel wait operation. error: 997

    [03/05/2008 20:26:33:370 MIME ERR] {tid=974:usr=bills}
    Failure on Desktop Configuration Server request to URL {rtsp://SG1:554/} with header {Host: SG1
    Content-Type: text/xml
    } (rc 19D06C2A-0000274D).


    [03/05/2008 20:28:20:724 MIME ERR] {tid=974:usr=bills}
    Failure on Desktop Configuration Server request to URL {rtsp://SG1:554/} with header {Host: SG1
    Content-Type: text/xml
    } (rc 19D06C2A-0000274D).


     

     

     

    barkingdog

  • Thursday, March 06, 2008 8:15 AMRodney MedinaMVP, AnswererUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Did you also check my last suggestion?

     

    "And last check the properties of the client if it is not accidentally configured to only allow secure connections."

     

    Rodney

     

     

  • Friday, March 07, 2008 5:12 AMbarkingdog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I went to the Management Server, right-clicked "Default Softgrid Application", then to Properties but could not find any mention of "secure connection".  Am I looking in the right place? (Incidentally, the Default Softgrid App does not appear on the Desktop client so I figured the check you referred to is done on the Management Server.)

     

    Barkingdog

     

  • Friday, March 07, 2008 12:16 PMBrian Kelly Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    They are referring tho the Application Virtualization Client in Administrative Tools on the *client*.

    Right click the root node (Application Virtualization (Local)" and choose properties and look on the Network tab

     

  • Sunday, March 09, 2008 11:39 PMbarkingdog Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Under the "Network" tab on the Client, "Connection Security" option, "Allow any connection" option is selected. So that isn't the source of the issue.

     

    Barkingdog

     

  • Monday, March 17, 2008 11:09 AMvkleinerde Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    Hi barkingdog,

    try to check the connection analog KB930730 with telnet ServerName Port .

    In you case telnet SG1 554 from client side.

     

    vkleinerde

  • Thursday, March 27, 2008 1:21 PMKalle SaunamäkiMVP, AnswererUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Also, is the port 554 being enabled on the server? Check that from Management Console (the *backend* one) -> Server Groups -> your VAS server -> Properties -> Ports..

     

    /Kalle

  • Friday, June 27, 2008 2:37 AMGert_Jensen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    If you use a different content share than the one set during install, you must change the HKLM\SoftWare\Microsoft\SoftGrid\4.5\Server\SOFTGRID_CONTENT_DIR to the new value

     

    \Gert

  • Thursday, September 25, 2008 10:45 PMDerek Bowen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    This key does not seem to exist in 4.5RC

     

  • Friday, September 26, 2008 5:53 PMkirk_tn Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer

    Hi,

     

    to get things a liitle bit more structured.

     

    - check on the Server machine, if the MS Application Virtualization Management Server service is started. If it is an older system (I don't think it is, because your client is 4.5 so I asume your Server is 4.5 as well), the service is called SoftGrid Virtual Application Server service.

    If ythe service was not started but you can start it without problems, remember to check its status every time you start the server machine. It is a common issue that tha App-V service tries to start, but the Database (on the same machine) is not active yet - so it fails. When zou try to start it later (DB active), it works...

     

    - If the service is started, try "telnet sg1 554" on the server.

    -- If no error (but a black window) occurs, everything is fine. close that window

    -- If an error occurs, try the same with 322 instead of 554.

    If also this fails, verifiy if the App-V Management Service still is running. If so, you have a serious problem (not a common one ;-) ).

    If the Service is stoppped, also this is an unusual error.

    You might refer to the Server's Event Log to see if there are any errors

     

     

    If the Service is running and you can Telnet 554 from the server, try to telnet 554 from the client

     

    As mentioned above, you should check on the server in the Server's properties, if RTSP/554 is enabled (and not RTSPS/332). If you changed something here, you need to restart the service.

     

     

     

     

    • Proposed As Answer byznack Wednesday, July 29, 2009 8:41 AM
    •  
  • Tuesday, April 14, 2009 4:19 PMmniccum Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer

    I was getting the same error and found after the install, the managament service wasn't running.  This was the case even after the reboot.  Starting the management service obviously fixed the issue.
    • Proposed As Answer byznack Wednesday, July 29, 2009 8:41 AM
    •  
  • Tuesday, April 28, 2009 11:19 AMBoris Mikhailovski Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,
    I encountered this error today. It happens on vista nosp installed.
    The only workaround which worked for us is by using IP. It seems that this somehow relates to encoding of host line.
    Telnet worked perfectly and procmon doesn't produce any error, except tcp retrans.

    I'm going to open bug on it
    Regs,
    Boris Mikhailovski
  • Tuesday, July 14, 2009 2:11 PMBoris Mikhailovski Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    I have found that IPS McAfee is blocking RSTP requests from clients - the problem was solved after i've turned ips policy for RSTP off
    • Proposed As Answer byznack Wednesday, July 29, 2009 8:41 AM
    •