I have several users that log into a remote session, run a vb.net executable program that fires off Logicity Desktop to print PDF files. Occasionally, the Logicity program fails. It may have something to do with re-printing a document, but that doesn't seem to always be the case. The only way the program runs correctly again is to log off the remote session, wait a while, then log back in.

I'm suspecting it has something to do with TEMP files that the program creates (and that get deleted when the user logs off)? Is there any way to identify those files and/or delete them through a program?

Thanks...

Or, is it possible that there are conflicts with multiple copies of the program running at the same time in different remote sessions?

What is this Intermittent Program Failures problem.How can we resolve this problem?

When the program "fails", it runs, but the logicity splash screen flashes real quickly, and no output is generated

GarrettWilson wrote:
You can also get the whole idea about it here:

ncsu.academia.edu/RazaAbbasSyed/Papers/746226/Investigating_Intermittent_Software_Failures