Subject Re: [firebird-support] firebird service terminated unexpectedly
Author Mark Rotteveel
On Mon, 28 Sep 2015 17:51:08 -0300, "Eduardo gusedum@...
[firebird-support]" <> wrote:
> Hello:
> I have an application developped in Delphi that uses Firebird
> SuperServer.
> The application is running well in many enterprises. But there is one
> place where there is a problem. They have a server with Windows and 4
> client computers with Windows. They have been using the application
> since 2011 without problems. But since May 2015, almost every day it
> happens that many times Firebird service terminates unexpectedly.
> Sometimes it happens once in a day, sometimes twice or may be more.
> It is not at regular times. Many times it happens at, for instance,
> 03:00am, when nobody is working and the only computer turned on is the
> server.
> In the Windows event viewer, each time this happens, I see an event with

> the text "Firebird Server - DefaultInstance service terminated
> unexpectedly.".
> In Firebird.log there are some messages that may be usefull. I copy some

> at the end of this message.
> Till 10 days ago, the server had Windows Server 2003. Now they changed
> the server for a new one and installed Windows Server 2008 R2 64bits.
> They changed the server just trying to solve this problem, but the
> problem is still there. Every day Firebird service terminates many
> Any idea of which may cause Firebird service termination?

At minimum, upgrade to 2.1.7 as it there have been several crashes fixed
since 2.1.4. However I have seen a similar problem with 2.1.7 as well. You
might have no choice but to upgrade to 2.5.4 (or 2.5.5 that will be
released in the near future).

The log seems to indicate that something or someone is sending malformed
packets to the Firebird server, but given the time between its occurrence
and the actual crash, I am not sure if that is the reason. Similar problems
were the reason for releasing 2.5.3 Security Update. As far as I know this
fix ended up in Firebird 2.1.7 as well, but I am not sure if this is
actually the same problem.