Because we have learned to monitor connections in Pervasive monitor. We have some staff that have a habit of doing things that either kick them out of Evo (application errors they ignore) or they CTRL-ALT-DEL out of Evo when they've locked it up through impatience. So those sessions get left behind, and we clear them out. We also can see which sessions are locking a file when someone gets a continuous Pervasive code that the file is locked by someone else. Usually someone is mid-way through a process and just either levaes their desk, stops to talk, or takes a phone call and just leaves Evo waiting for a response. Or, at the end of the day we hav everyone out of Evo for posting (learned this is something we need to do), and we can make sure no one hops in to disturb the processing, or when we run MRP we have learned to run it with none of the MRP talbes open by anyone else.
We also look at the SQL sessions to moinitor connections for UPS and FedEx, and java things that may get hung up like sometimes Features and Options (it's user related).
So we just keep Pervasive monitor open.
Pages: 1
Evo Auto Restarts Leaving Pervasive Ghost Sessions (Read 489 times)
