locked
Not going good with App-V RRS feed

  • Question

  • Well I have the management server, a XP SP2 machine with the App-V Client on and have sequenced a test app (Winzip 12.1) for testing functionality.

    Unfortunatley I have no idea why but I cannot see any published application upon my desktop client, The furthest I have got so far is with the client connecting to my Mgmt server over RTSP and saying apps will deploy upon next login.

    I seem to not be able to find any logs like SMS was so good at giving me, any idea if anyone can help or if there are any troubleshooting logs for AppV?

    UPDATE -

    I tried also running the OSD manually from the App-V share and got "the specified app virtualisaton server could not be accessed. Try again in a few minutes if the problem persists, report the following error code to your system administrator

    Error code: 4513CDC-19D02C0A-10000002"

    Thanks

    Dan
    • Edited by Deason Monday, August 24, 2009 8:39 AM
    Monday, August 24, 2009 8:01 AM

Answers

All replies

  • Hello,

    I would start with reviewing the following log-file;
    http://technet.microsoft.com/en-us/library/cc817103.aspx

    /Znack
    • Proposed as answer by znack Monday, August 24, 2009 8:06 AM
    • Marked as answer by Aaron.ParkerModerator Saturday, November 17, 2012 2:11 PM
    Monday, August 24, 2009 8:06 AM
  • LOL great....app now visable....was my proxy settings!

    Next problem! can't load app

    [08/24/2009 09:46:05:079 AMGR WRN] {tid=42C}
    Attempting Transport Connection
    URL: RTSPS://%SFT_SOFTGRIDSERVER%:322/Win%20Zip%2012.1_2.sft
    Host: :0
    IPAddr: 0.0.0.0
    Error: 19D02C0A-10000002


    [08/24/2009 09:46:20:126 AMGR WRN] {tid=42C}
    Attempting Transport Connection
    URL: RTSPS://%SFT_SOFTGRIDSERVER%:322/Win%20Zip%2012.1_2.sft
    Host: :0
    IPAddr: 0.0.0.0
    Error: 19D02C0A-10000002


    [08/24/2009 09:46:35:173 AMGR WRN] {tid=42C}
    Attempting Transport Connection
    URL: RTSPS://%SFT_SOFTGRIDSERVER%:322/Win%20Zip%2012.1_2.sft
    Host: :0
    IPAddr: 0.0.0.0
    Error: 19D02C0A-10000002


    [08/24/2009 09:46:35:204 JGSW ERR] {hap=1:app=WinZip 24.0.8519.0:tid=2C8:usr=daadmin1}
    The Application Virtualization Client could not connect to stream URL 'RTSPS://%SFT_SOFTGRIDSERVER%:322/Win Zip 12.1_2.sft' (rc 19D02C0A-10000002, original rc 19D02C0A-10000002).


    [08/24/2009 09:46:35:204 SWAP ERR] {hap=1:app=WinZip 24.0.8519.0:tid=2C8:usr=daadmin1}
    The client was unable to connect to an Application Virtualization Server (rc 19D02C0A-10000002)


    [08/24/2009 09:46:35:220 SWAP ERR] {hap=1:app=WinZip 24.0.8519.0:tid=2C8:usr=daadmin1}
    Could not load app

    It seems to be trying to connect on port 322 which is weird as Im set to use 554

    Monday, August 24, 2009 8:58 AM
  • Hello,

    You probably have two issues;
    When you saved the application you set it to utilize the environment variable (SFT_SOFTGRIDSERVER) and the port of 322.

    As you state that 554 is the port inuse and the environment variable doesn't seem to be resolved here comes some ideas;
    1. To make the current application run, manually edit the .OSD-file changing the specified values
    2. Set the environment variable on the client, unless you wish to set the server in the OSD-file
    3. In the future save your applications with correct settings, to avoid having these issues....

    /Znack
    Monday, August 24, 2009 9:06 AM
  • Will resequencing the app be ok for this?

    Also silly question but is resquencing the app from the Management server SMB share supported?

    Dan
    Monday, August 24, 2009 9:30 AM
  • Hello,

    Yeah, it would as long as the new app has a unique osd and version / name combination.

    I don't understand the latter question, if you mean opening from the share I suppose its ok....

    /Znack
    Monday, August 24, 2009 10:10 AM
  • Also silly question but is resquencing the app from the Management server SMB share supported?

    You should never directly open a package from the Content share with the Sequencer, because once you save anything in the Sequencer it would overwrite files in the Content share - and that's not what you usualy want. Also, sometimes the files have a lock so you can't open them.

    What you should do is to open a COPY of that files with the Sequencer (File open... is appropriate) and then make the modification in the deployment tab (you should not modify the path, only the server name and/or protocol) and save the package (on the Sequencer).

    Then, you have two options:
    1. Delete the old app from the Management Server (Management Console: Applications Node, Management Console: Packages Node and in the file system) and import the new app again.
    2. Smart "Active Upgrade":
    - first copy the new SFT to the same location like the old one. The new one should have a _2 attached
    - in the Server-MMC, Packages node right-click on the "old" entry and select "add version"
    - enter the path to the new SFT
    - make sure the old and the new path for both version are equal (except the filename)
    - copy the other new files (ICON subfolder, OSDs, SPRJ, XML...) to the file location of the "old" package and overwrite the files.

    Thus you created a "New version" of an exisitng package.



    Falko
    Monday, August 24, 2009 2:25 PM
    Moderator
  • You should never directly open a package from the Content share with the Sequencer, because once you save anything in the Sequencer it would overwrite files in the Content share - and that's not what you usualy want. Also, sometimes the files have a lock so you can't open them.

    ..and it also deletes the old version of SFT while generating new version (with _version suffix), which would be really bad if done against content share directly!

    /Kalle
    Thursday, September 10, 2009 7:10 PM
    Moderator
  • Will resequencing the app be ok for this?

    Also silly question but is resquencing the app from the Management server SMB share supported?

    Dan

    You don't need to resequence just for this little change:

    1) Open up all your OSD files associated with the package (XML capable editor preferred, Notepad works if you really must)
    ´
    2) Search & Replace "RTSPS" for "RTSP", "322" for "554" and "%SFT_SOFTGRIDSERVER%" for whatever is your server's name or ip-address

    3) Refresh on the client by manual refresh or logging in again

    /Kalle
    Thursday, September 10, 2009 7:13 PM
    Moderator
  • ... or just add a cert to the server and enable RTSPS also.  You just might forget to change RTSPS to RTSP when you sequence another app in the future.

    Thanks, Microsoft, for making us "secure by default".  I sleep better at night.  Yeah right!
    Saturday, September 12, 2009 1:38 PM
    Moderator