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.
This topic has been locked.
3 replies Latest Post - 2009-07-07T16:26:50Z by Ron_Wright
Pinned topic Visual WorkFlo Desktop 3.6
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2009-07-07T16:26:50Z at 2009-07-07T16:26:50Z by Ron_Wright
donl1967 270000WCCR1 PostACCEPTED ANSWER
Re: Visual WorkFlo Desktop 3.62009-02-06T19:23:18Z in response to SystemAdminWe 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 270000ER6Q1 Post