locked
Side By Side error sequencing Reuters EcoWin RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    I'm using the latest 4.2.2.15 sequencer and client on a v4.1 server.

     

    The program sequences without incident and I get a package which can be deployed.

     

    When running the sequence I receive the following error:

     

    "The SoftGrid Client could not launch EcoWin Pro

    5.60.0.437.

    The application has failed to start because its side-by

    -side configuration is incorrect. Please see the

    application event log for more detail.


    Error code: 42200F-0060922C-800736B1"

     

    Looking at the SXS logs its the Vinga components that it can't run. This is a .NET Framework v2 application.

     

    Could anyone suggest what I might do to resolve this?

     

    Thanks,

     

    Martin Searle

    University of Kent, UK

    Thursday, April 17, 2008 11:26 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm currently working on a similar problem with Filemaker Pro needing the C++ Redistributable SP1. The MS knowledgebase article gives two solutions.

    http://support.microsoft.com/kb/939084/

    I went for the second and copied the Policies and Manifests contents from the sequence to the local folder on a test machine. Filemaker worked fine but it broke a few other things on the machine as it seems you also need the DLL folders too (basically the whole contents of the sequenced WinSxS folder). I'm guessing those broken apps find there is a later version of the DLLs via the Manifests and Policies files but then obviously can't find the DLLs themselves whereas Filemaker uses it's virtualized DLLs.

    As a normal user won't have rights to copy the files to the machine WinSxS folder in our environment I'm hoping to get a prelaunch script sorted that runs an SMS install of them. I'm also a little worried as I know nothing about WinSxS really and I'm just assuming copying contents into the folder like that is a valid option that won't break anything. Guess that's what testing is for. Wink

    Ideally installing the C++ Redistributable SP1 to all out clients is the best option for me but I've been told that's not going to happen anything soon...
    Tuesday, April 22, 2008 10:24 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm currently working on a similar problem with Filemaker Pro needing the C++ Redistributable SP1. The MS knowledgebase article gives two solutions.

    http://support.microsoft.com/kb/939084/

    I went for the second and copied the Policies and Manifests contents from the sequence to the local folder on a test machine. Filemaker worked fine but it broke a few other things on the machine as it seems you also need the DLL folders too (basically the whole contents of the sequenced WinSxS folder). I'm guessing those broken apps find there is a later version of the DLLs via the Manifests and Policies files but then obviously can't find the DLLs themselves whereas Filemaker uses it's virtualized DLLs.

    As a normal user won't have rights to copy the files to the machine WinSxS folder in our environment I'm hoping to get a prelaunch script sorted that runs an SMS install of them. I'm also a little worried as I know nothing about WinSxS really and I'm just assuming copying contents into the folder like that is a valid option that won't break anything. Guess that's what testing is for. Wink

    Ideally installing the C++ Redistributable SP1 to all out clients is the best option for me but I've been told that's not going to happen anything soon...
    Tuesday, April 22, 2008 10:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for that. I copied the WinSXS  and the assembly folders from the discovered sequence onto my in development desktop and after that the sequence worked correctly on the machine. Not the ideal solution but one to go with for now, it won't work on our staff desktops but its mainly for student use on our public system.

     

    One for Microsoft really: are there any plans in v4.5 to ensure that .NET applications can be sequenced correctly in this sort of situation when they utilize additional controls like these applications?

     

    Martin Searle

    University of Kent, UK

    Wednesday, April 30, 2008 10:15 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello!

    I'm too having problems with sequencing EcoWin Pro!
    - But EcoWin Pro version 6.0 on Win Vista with Sequencer 4.5.0.1485..


    Error Code 4505CD-1B40212C-000036B1, side- by side configuration is incorrect.
    In the Windows log: Dependent Assembly Vinga.vscom90u,processorArchitecture="X86",publicKeyToken="e520fe831c9439c8",type="Win32",version="1.0.0.55" could not be found.



    As I understand MS dont provide permission in Vista to write or modify folders in WinSxs folder so the method 2 in http://support.microsoft.com/kb/939084 isn't working for me..

    I have The Microsoft .NET Framework 3.5 SP1 and Microsoft Visual C++ ( 2005 and 2008) Redistributable Package installed locally.



    What to do??

    Any suggestions appreciated!
    /Marie

    Wednesday, March 18, 2009 4:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello,

    What prereqs does the software have?
    Do you have SP1 of Visual C++ 2005 and 2008?

    Are they all installed at both the client and the sequencer (pre-sequencing?)

    /Znack
    Wednesday, March 18, 2009 9:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello!

    Thanks for replying! Yes, both Visual C++ SP1 installed locally on both the client and the sequencer..

    But as Martin says above, and reading the windows log, it seems to be the Vinga components that it can't run..
    Martin's case was solved by copying the WinSXS folder but I guess that must've been a non- Vista machine?

    br
    Marie

    Wednesday, March 18, 2009 10:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello,

    Any possibility to find a redistributable for those or make one yourselfs?

    /Znack
    Thursday, March 19, 2009 7:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I would really like to make -only- an App- V package of this :(

    You mean I have to get a way to deploy these locally.. Doesn't App- V manage WinSXS?? Aren't there another workarounds that works in Vista?

    /Marie
    Thursday, March 19, 2009 7:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello,

    Considering that Visual C++, .NET Framework etc is installed locally - the assembly is probably in the same category as them.

    Support policy regarding .NET Framework;
    http://technet.microsoft.com/en-us/appvirtualization/dd146065.aspx

    You could try the CU1, but then again you would have to deploy that. So if the deployment of an assembly is a struggle, well CU1 should be in the same category....
    (I think that support policy reflects changes implemented with CU1)

    Regarding assemblies I always try to deploy them locally, but if someone has a reason todo it otherwise and or any other suggestion - I am glad to hear it.
    /Znack

    Thursday, March 19, 2009 8:15 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had interesting find on Visual C++ 2008 components, which might or might not be relevant for this discussion:

    I was sequencing a smallish CAD viewer -application, which insisted on installing those 2008 VC++ libraries on the machine (as the Sequencer did not had those locally). After trying to deploy this package to a client, I noticed that while the application started, it started to burn CPU on 100% and the whole interface just freezed. Seeing that there's VCR90 folder or something in the sequence, I immediate thought that installing that runtime locally is the way to go to solve this problem.

    HOWEVER, I also noticed that the Sequencer had created these .config files files for all application DLLs/EXEs and .Manifest files for VCR90 subdirectory. Config files has been discussed here and there in the past, and they are known to cause slowness in application start and DLL loading when executing under SG/App-V. Deleting those away from my package, and testing again on the client after making sure that everything from the previous package version was really gone, the application started to work correctly.

    So you might want to check, if your sequence contains these extra .config files (App-V 4.5 seems to be generating those very liberally when doing SxS privatization process) and if so, delete those away. This can be done at the Sequencer's Files -tab, so that you don't risk that Sequencer re-generates them if you do it during installation process.

    br,

    Kalle

    Thursday, March 19, 2009 10:17 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for answers!

    But Kalle, this still means I have to get the Vinga assembly which it complains about (included in the Reuters installation package) locally installed?? Or how to get this one in the sequence?

    I asked the vendor for redistributables but would be surprised to get one...(?)


    Registered for the CU1.. and can try to delete files in my sequence.. But there are a lot of them vc90..- files and I don't know how to handle these assemblys really :S

    /Marie

    Thursday, March 19, 2009 12:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Marie,

    As I said, I don't know if my experience is relevant to your case but there were similarities.

    For the Vinga assembly, does the installer install that to your package during sequencing? If so, try to look .config files related to that assembly and let VC90 as-is. Without knowing your application more in detail, I'm afraid I cannot give you exact guidance on this matter (.NET assemblies can be as DLLs at the application's directory or they might be installed to GAC, but if it's complains about SxS it seems that this Vinga is non-.NET thing?).

    /Kalle
    Thursday, March 19, 2009 12:39 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    The vinga system is provided by these folks:

    http://www.vinga.se/w2/en/default.htm

    Its used to access the various reuters databases. I did try to isolate the vinga install from EcoWin with not much success since EcoWin only provide the install as a single file and the components are installed during that.

    I did try it on my Vista desktop but as Marie says you can't copy in anything to those folders it needs to be installed there. But my main desktop was XP when I was looking at this but in the end I went for a local installation of the application to avoid any problems.

    It would be better if MS could properly vitrualize these 3rd party .net controls.

    Martin Searle
    Computing Service,
    University of Kent, UK
    Thursday, March 26, 2009 11:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    See this workaround;

    http://www.viridisit.se/eng/blog/?p=629

    New-link; http://www.applepie.se/sequence-ecowin-pro-6


    One final issue not resolved - but anyone with application expertise at hand could probably resolve it...

    /Znack


    • Edited by znack Wednesday, August 13, 2014 8:42 PM
    Saturday, July 17, 2010 9:10 AM