D
dbeavon
Guest
Bernhard, It sounds like a combination of two or more different bugs. These terminal server users don't share the same process, right? It is odd that your users would have a problem that crosses process boundaries. The problem might be *initially* triggered by an intermittent issue with the Progress CLR bridge. But If I had to guess, the *subsequent* failures within the *other* processes is probably *not* something that you can blame on Progress. It may be related to a shared resource (file on disk) or something along those lines. You might want to try running "process monitor" and see if the third-party tools (or your own code) write to a hard-coded path (ie. in a temp directory or such) that cause all of the processes on the same server to start "stepping on one another", after they have been triggered by the initial failure. Another thing to do is put CATCH Progress.Lang.Error blocks around small-ish sub-blocks of code so you know exactly which step is causing the failures. Finally, once the problems are initially triggered, it would be fairly easy to get to the bottom of the *subsequent* failures by installing visual studio and attaching the debugger. Visual studio will provide all the "first-chance" exception details. Alternatively you could configure procdump or to generate memory dumps for you that you could analyzed later on a development machine (see docs.microsoft.com/.../procdump ). I'd suggest using the -e 1 option for getting dumps from first-chance exceptions) Hope this helps, David
Continue reading...
Continue reading...