EServerFatalError

edited January 2010 in Server
Good morning,

One of our customers keeps getting the exception EServerFatalError, after
which the report server turns off. Even when we restart the data module
automatically by intercepting the exception, which works correctly with 2
other customers who had the save problem, the service will not work anymore.
It will throw up connection failures after receiving an EServerFatalError.

When we use debug logging, the call stack shows that the exception
originates from a TTimer event. We are not able to reproduce the problems in
our development environment, so using a debugger is not possible.

Is there a way to find out more about the underlying problem and somehow log
call stacks and/or other details? Is it for instance possible to have the
original exception break through to application level?

Thanks in advance,

Mariëlla Bakker
P&A Software

Comments

This discussion has been closed.