> Du to the problem we have with Firebird 2.1.4 (i will try to compile the demo project to simulate the problem monday), we decide to update the database to FB2.5 in ou production server (even if it a release, can not be worse than the actual FB2.1.4)

What build do you use ? The preferable is to use most current snapshot build, as it contains many fixes since RC2.

> it's run for one day and we receive this error :
>
> Sun Apr 11 08:50:47 2010
> Fatal lock manager error: invalid lock id (4550520), errno: 0

This is a bug. I never saw it by myself.

Do you have file "fb_lock_table.dump" at folder %ALLUSERSPROFILE%\Application Data\firebird ?

> Sun Apr 11 08:50:47 2010
> INET/inet_error: select in packet_receive errno = 10093
>
>
> Sun Apr 11 08:50:47 2010
> INET/select_wait: select failed, errno = 10093

WSANOTINITIALISED
10093

Successful WSAStartup not yet performed.
Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times.

Of course, Firebird called WSAStartup. If this call is not successful, then even listener port will not be create and Firebird can't accept connections via TCP\IP.

It is suspicious that this error happens at the same moment as "invalid lock id".

> Sun Apr 11 08:50:47 2010
> SRVR_multi_thread/RECEIVE: error on main_port, shutting down

This is consequence of 10093 error.

> What do you thing can cause this error ? i never receice this error in FB2.1

Any chance you run second instance of Firebird ? It shouldn't lead to such errors but probably there is some unknown factor...

Regards,
Vlad