Hi there

I have a weird issue with active upgrades I was hoping someone could help with?

We're upgrading from 4.2 to 4.5. Servers are 4.1, clients are 4.2, some clients are now 4.5. Sequencer is 4.2. We have a strange issue with Active Upgrades. We are sure we are doing the upgrades correctly and are moving the new package to the server (not just replacing/overwriting them). When we first launch the package that has been upgraded we receive this message - " An unexpected error occurred, report the following error code to your system administrator 4505cd-16d1100a-0000e005 " "cache full" When we try again the application will launch and will execute fine, and it will work successfully from this point on.

From sftlog.txt -
[04/03/2009 14:32:25:710 JGSW ERR] {hap=31C:app=testxrdn 3.0 SFT:tid=FF8:usr=admin}
The Application Virtualization Client could not connect to stream URL 'rtsp://vmcapp.test.biz.lodh.com:554/LOH/TestXRDN/3.0/testxrdn_3.0_10.sft' (rc 16D1100A-0000E005, original rc 16D1100A-0000E005).


[04/03/2009 14:32:25:741 SWAP ERR] {hap=31C:app=testxrdn 3.0 SFT:tid=FF8:usr=admin}
The client was unable to connect to an Application Virtualization Server (rc 16D1100A-0000E005)


[04/03/2009 14:32:25:850 TRAY ERR] {tid=D24:usr=admin}
The Application Virtualization Client could not launch testxrdn 3.0 SFT.

An unexpected error occurred. Report the following error code to your System Administrator.

Error code: 4505CD-16D1100A-0000E005

Does anyone have any advice on what to look at and where to get started?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi,

I guess, the link below would be a bit help for you

http://technet.microsoft.com/en-us/appvirtualization/bb676740.aspx

regards,
Ram.
Answered 04/30/2009 by: Ram
Senior Purple Belt

Please log in to comment
0
Hi,

I had the same issue in a mixed environment with 4.1.3.16 server, 4.2.1.20 sequencer and 4.5.0.1485 client. The problem still persisted after we upgraded to an App-V 4.5.1.16811 client.

Solution was to do an active upgrade of the package with an App-V sequencer 4.5.1.15631. This package could be updated on the 4.1.3.16 server without any problems using the "new version" function of the server console.

However, you must have 4.5 clients on all machines before you can run packages from a 4.5 sequencer.

Regards,

Peter
Answered 01/14/2010 by: pebro
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity