EServerFatalError

rbuser

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

nardmoseley

The exception originates in the thread in which the report is generating.
The Timer is used to allow the thread to terminate and then the Server
raises a FatalException in the main thread.

I just made a patch for RB 11.07 that will allow the server FatalException
to include the error message from the original exception. Registered users
of RB 11.07 can email support@ and request the patch.

Here is a couple of links to rbWiki How To's that may help you...

How To...write to the server log.

http://www.digital-metaphors.com/rbWiki/Server/Report_Server/How_To...Write_to_the_Server_Log

How To...handle server exceptions.

http://www.digital-metaphors.com/rbWiki/Server/Report_Server/How_To...Handle_Exceptions


--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com