Hi Dmitry,

That makes sense, I am not having server crashes. We have a 3rd party application that makes use of Firebird, when the Firebird server (Windows 7) has only a few clients (XP and Windows 7) then we have no issues, but as soon as we go start having 15 more clients we start to drop transactions. I suspect this is happening because of locked records/dead locks or something like that. It think these types of things are happening but the application is not handling the errors correctly and that is why we their is data missing. I don't think firebird is loosing the data, it is just not arriving because of a resource conflict. This is what I am trying to determine. Will 2.5 give me this ability to see the lock errors, etc.

Regards
Sean

--- In firebird-support@yahoogroups.com, Dmitry Kuzmenko <kdv@...> wrote:
>
> Hello, sean!
>
> Wednesday, March 27, 2013, 8:07:10 PM, you wrote:
>
> syc> I am trying to enable logging on Firebird 2.1 on Windows 7, to
> syc> try and find a solution to certain issues. I cannot find how to enable this logging, I
> syc> have downloaded and installed the debug kits for my platform,
> syc> but I have searched the entire machine for firebird.log but it doesn't exist on the server
> syc> at all. There is obviously an undocumented flag or setting that
> syc> needs to be in place for this to happen. The information I want is the information
> syc> everybody else seems to have in their firebird.log file.
>
> First of all, you'd better explain, what you want.
> firebird.log contains only errors, and debug kits need to be used
> if server crashes.
> No error or crash - no firebird.log or dump.
>
> If you want to look what happens with the server right now -
> query MON$ tables.
> If you want to log (trace/audit) queries, etc - you need
> to install Firebird 2.5, because 2.1 doesn't have this ability.
>
> --
> Dmitry Kuzmenko, www.ib-aid.com
>