Topic
3 replies Latest Post - ‏2009-07-07T16:26:50Z by Ron_Wright
SystemAdmin
SystemAdmin
9 Posts
ACCEPTED ANSWER

Pinned topic Visual WorkFlo Desktop 3.6

‏2008-05-12T17:07:49Z |
Anybody out there still using thick-clients to access eProcess?

We upgraded to eProcess 5.2 (aka Image Manager Process 3.5.4).

When using the updated VWDT 3.6 Conductor to access the isolated region, VWCOND.exe will randomly crash.

I'm trying to determine whether my upgrade did not go so well, or if there is indeed a problem.

So, is there anybody out there using eProcess 5.2 successfully with VWDT 3.6 thick clients?
Will save me the time of re-creating a clean environment to eliminate the upgrade as the cause.
Updated on 2009-07-07T16:26:50Z at 2009-07-07T16:26:50Z by Ron_Wright
  • SystemAdmin
    SystemAdmin
    9 Posts
    ACCEPTED ANSWER

    Re: Visual WorkFlo Desktop 3.6

    ‏2008-09-17T12:42:57Z  in response to SystemAdmin
    Were you able to resolve the problem? We are also trying to upgrade to eProcess 5.2 and thick client 3.6 and seeing the same vwcond.exe error.

    Thanks
  • donl1967
    donl1967
    1 Post
    ACCEPTED ANSWER

    Re: Visual WorkFlo Desktop 3.6

    ‏2009-02-06T19:23:18Z  in response to SystemAdmin
    We are in the process or upgrading to eProcess 5.2. However we run into an issue with IS 4.1.2. We were at 4.1.1 and upgraded eProcess and it worked fine. We then upgraded to IS 4.1.2. It removed eProcess 5.2 and when we tried to reinstall it, it says the system needs to be at 4.1.1. Any suggestions?
  • Ron_Wright
    Ron_Wright
    1 Post
    ACCEPTED ANSWER

    Re: Visual WorkFlo Desktop 3.6

    ‏2009-07-07T16:26:50Z  in response to SystemAdmin
    If the error you are getting is abnormal termination, this is a known bug fixed in a one-off patch VW 3.6.0-1001. Please open a PMR with support and they will provide the fix for you.