Plex 6 deployment issue

[purdygeoff]

We recently upgraded from 5.1 to 6 and are attempting to test the version 6 rollout ; our problem is that each time we try to launch the newly generated EXE, it bombs off with no specific error message. We've got the ob6xx.dll 's (ca\plex\bin) loaded and everything else is pretty vanilla. WinC -> AS400. Has anyone else successfully deployed Version 6 and worked around this issue ? Things work fine as long as they are executed from a development workstation. Thanks in advance

[purdygeoff]

Nevermind, we found the answer is to have each client workstation run the vcredist_x86.exe to install the runtime framework. That is a real bummer but at least we're up and running. Thanks

[Anon Anon]

Just hit this issue again. It turns out that there is more than one version of vcredist_x86.exe. We had been working fine, but when I rebuilt a dll for an existing .exe it broke.  The user had already run  vcredist so I didn't think that would be an issue. Eventually after rebuilding pretty much everything I re-downloaded vcredist and re-ran it on his PC and it worked.  Here's the link to CA's blurb on the issue  https://support.ca.com/irj/portal/anonymous/solndtls?docid=420216&searchID=420216&aparno=RI10301&product=CPLEX&os=WINDOWS&release=6.1&number=0000002&type=&actionID=5&pos=N/A  and to vcredisthttp://download.microsoft.com/download/6/B/B/6BB661D6-A8AE-4819-B79F-236472F6070C/vcredist_x86.exe      Adrian  

[Anon Anon]

FYI Here's an excerpt of an emaiI recently sent a customer on this topic. Please don't shoot the messenger - this problem is not directly-related to Plex and if you do a bit of web searching you'll find many Visual Studio C++ developers encountering this problem...   This is all related to updates to the Visual Studio 2005 runtime that CA cannot control. The VS 2005 runtime (not Plex) uses something that Microsoft call side-by-side (SxS) deployment.    The compiled DLLs/PNLs/EXEs are encoded in their manifests with the specific version of the VS runtime they require and they will refuse to run with an earlier version. If you watch carefully with something like Process Explorer you may have noticed that Plex 6.X C++ applications do not load the VS 2005 runtime DLLs from the application directory or the path â€" they always get loaded from a subfolder of \WINDOWS\WinSxS.      (Actually I did find out that it is possible to override the compiled manifest info with a .config file but you have to create one for every DLL/PNL/EXE so not very practical. If you want to get fancy it might even be possible to modify your builds to change the manifest info â€" for example http://stackoverflow.com/questions/1267195/is-it-safe-to-rewrite-an-exe-or-dll-manifest-to-force-a-particular-version-of-the )      This is all designed to avoid what used to be called DLL ****. Arguably it just introduces a different kind of DLL ****.   In our assessment, the Microsoft security update does not fix any problems that affect typical  Plex applications but it does the change the VS 2005 runtime version number. We have no idea when Microsoft might do this again…   If managing the updates is a problem for you, one option might be to NOT to deploy the security update to ANY of your developer machines. In effect that is what we have done at CA for the time being â€" our build machine has not been updated with these patches. By the way, all our “officialâ€? builds and releases are compiled on the same build machine â€" we don’t shipped DLLs created on different developer’s machines.    Message Edited by DanielLeigh on 12-10-2009 10:04 AM [left]

[Anon Anon]

Upgrading from Plex 4.5 to plex Plex 6.0. We are going to have the need to run  both our 4.5 generated and our 6.0 generated applications at the same time.  [left]  [left] I can't get the 6.0 generated exe  to run. I get our application menu  displayed with  a blank dialog box. I've run vcredist_86.exe, I have the ob600 dlls in system32 folder, Iseries Plex600 library is ok.  I am doing this on my own PC, and obviously I am a Plex developer.  When I look at the outq in the dispatcher I'm getting CPD2356(New Password cannot be the same as the existing password)  issued from CHGPW. I have no idea why it thinks I'm trying to change the password, I'm not. I also get CPF22E2(Password not correct) sporadically. The odd thing is I can gen and build Iseries objects against the dispatcher. Also I have no problems connecting with the  application exe generated from Plex 4.5.  Any help or advice would be appreciated. Thank You.      [left]  [left] Ken  [left]

[purdygeoff]

I think it sounds like that is the code page value in the INI file.   The Code Page=     value used to be 10, now it needs to be 101.   We had the same issue here and I believe that was the culprit.       As a side note, we put all of the OB600xx.***   into the runtime folder on the server as opposed to System32.   Makes for easier deployment.   I don't think that is related, just thought I would throw it in since you made a specific mention.   Let me know how it goes, thanks[left]

[Anon Anon]

Purdygeoff you are the absolute master! the code page change worked. Was that in the Plex Documentation and I missed it? How did you find that out?[left]  [left] Thank you so much!!!![left]  [left] Ken  [left]

[Anon Anon]

Thanks......double so much...I advised CA they need to update their documnetation AND buy you dinner.[left]

[purdygeoff]

We don't remember it being in the documentation anywhere, we  just  figured  it out through trial and error.   They rewrote the multi-lingual mapping piece and  that works perfectly out of the box now - so after the fact it made sense.   I'm just happy you posted (the forum system emailed me about a response to the original thread), and our pain could save someone  a few days.   This was my first participation in the forum, so it makes me feel good to contribute.   Good luck![left]

[Dean_Eshleman]

I think the code page change was done at Plex 5.5. That is the version we are using, and I remember making the change here. Therefore, if you skipped that release it may not have been mentioned anywhere in the 6.0 documentation. That doesn't mean that CA shouldn't update their documentation, they probably should add something to note this change.

Dean Eshleman
MMA, Inc.