locked
4.5 to 4.6 migration problem RRS feed

  • Question

  • Hi all!

    We have some interesting situation in our test farm. We have some problems after migration from Client version 4.5 to 4.6. We have 2 applications (WinScp 4.1.7 and Microsoft Project 2k7 Pro) for now that worked perfectly in the 4.5 environment and failed to work properly after installing them in 4.6.

    We sequenced those applications with both 4.5 and 4.6 versions of sequencer. Then we deployed application to Win XP (x86) with installed App-V client and look what happens:

    MS Project:

    Client 4.5 - works perfectly;

    Client 4.6 - works but functionality is corrupted. This can be healed via allowing local interaction.

    WinScp:

    Client 4.5 - works fine, may fail if Symantec Endpoint Protection is installed and running;

    Client 4.6 - fails with WinScp.exe error code 0xC0000005 in any cases. Procmon doesn't show any critical errors during app launch.

    Is it some kind of backwards compatibility issue? Do you have any idea what caused these problems?

    Thanks in advance!

    Friday, June 11, 2010 7:42 AM

Answers

  • Hello,

    When upgrading a client, things may break. During the 4.1 -> 4.5 upgrade there were some talks regarding specific applications beeing dependt on app-v DLL files.

    Since I can't say anything how your specific environment is setup - try to locate why it doesn't work after upgrade. What is causing that behavior?

    /Znack

    • Marked as answer by Chiverel Monday, June 14, 2010 8:42 AM
    Saturday, June 12, 2010 7:20 AM