> Thomas Steinmaurer wrote:
>> I was working on a database today. Firebird 2.1.2 Classic 64-bit
>> (Windows 2003 Server). After a while, I wasn't able to connect to the
>> database anymore. Either remote or on the local server via isql.
>
> Did you try other than TCP protocols, namely named pipes and local?
>
>> Connecting to other databases on the same server is working just fine.
>
> The same question for the other databases.
>
>> It is just this one particular database on that server, where I get an:
>>
>> Statement failed, SQLCODE = -902
>> Unable to complete network request to host "localhost".
>> -Error writing data to the connection.
>> -An existing connection was forcibly closed by the remote host.
>>
>> when I'm trying to connect.
>
> Looks like a server crash. Do you have any ON CONNECT triggers? If so,
> have you tried to backup the problematic database with and without the
> -no_db_triggers (sorry, I don't remember the exact syntax :-) switch?

Can't remember, if I had installed ON CONNECT triggers. Tried the
-nodbtriggers switch. Same error message. ;-)

I've also tried to copy over the database file to my local machine
(while nobody was connected *g*) and connecting to the database gives
the same error message as well, so this sounds to be a problem with this
particular database.

I've also tried to do that with SuperServer on my local machine. After a
while, when trying to connect, I get:

Statement failed, SQLCODE = -913
deadlock



Any further ideas?




--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/