/build/static/layout/Breadcrumb_cap_w.png

APPV 4.5.0.1485 Client issue

hi,

need some help. We are sequencing an application using 4.5 sp2 sequencer but the client version for some of our systems are 4.5.0.1485. The sequnced applications are faling to run in this client but running in other 4.5.X.y clients. I know that this is a very old RTM client but other applications are running fine in it. Is there any known issues for this situation.

I know client upgrade is the way to solve it but presently we need some time to carry on the upgrade so please dont suggest this option.


0 Comments   [ + ] Show comments

Answers (1)

Posted by: EVEEN 11 years ago
Green Belt
0

So you are looking for an answer but you will not be satisfied with the answer :) Upgrade is the way.

 

But you could try: open the sequence made with the sp2 sequencer in an older version of the sequencer and save with that tool as as a different sequence (Name and unique identifier.) Test with one but it should work.

Use these dedicated "old-style" streams for your old machines. You'll double your managed SW objects but you save in the pesky update.


Comments:
  • @EVEEN: Not helping. I am asking whether there are any known issues. I have tried all possible things that you can think of. Cheers.
    In my situation upgrade is a very big word as my target desktops are around 35000 running more than 350 APPV applications, with 25% critical machines running 24/7. The upgrade becomes and project by itself. I am upgrading but it is time consuming. - imavanurabanerjee 11 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ