At 08:47 PM 06-02-02 +0530, you wrote:

>Dear Friends,
>
>I have a production Database application which is being implemented
>on a NT Lan.
>I gives following error intermittently say after almost 10 to 12 days
>working normal.
>
>ISC ERROR Code : 335544721
>ISC Error Message :
>Unable to complete network request to host "Ntserver"
>Error writing data to connection
>The Pipe being closed.

How on earth do you manage to keep an NT server running for 10-12 days ??? :))
First recommendation would be to move to TCP/IP. My guess is that, if you look at the interbase.log you will see rashes of Windows network errors around those crashes.

>After backing up the .gdb and Restoring it the application starts working normal. No errors are shown in backup and restore process. (No Network hardware/software setup is
>changed in-between not even pressing of connections)
>
>The Setup is
>Server
> PI 64 MB Ram, 4 GB scsi hdd, 10 MBPS 10baseT card.
> NT 4, Interbase 6.0 First open server release d/l from IBPhoenix site.

Kill it! That release has hundreds upon hundreds of known bugs, some critical. The world has moved on by leaps and bounds since that beta release. If they want a free database, use Firebird. If they want to pay, use InterBase 6.5.

>Networking
> 8 Port HUB no cascading.
>Clients
> 6 to 7 at a time doing mainly data entry work. only validation
>queries are being executed at server
> celeron 32 MB RAM, 10 MBPS 10baseT cards, w98.

RAM seems low for Win98 clients. Could some of these clients be crashing from resource problems?

>Database size
> 65 MB only.
>
>The client has started doubting Interbase and indicating that we should
>go by either Oracle or M$ SQL server. We believe strongly in Interbase and want him to continue
>with Interbase only.

See comments above. I believe in Interbase too, but that old beta is just too flaky to wheel into production. It can't compete with Oracle or MSSQL except on price.

>so before he makes his mind to shift away from Interbase we would like
>to get help on this issue. So please help us out by giving tips about how to solve this
>problem and preventive measures to be taken to avoid such problem in future.

The best tip of all would be to stay in touch with what's happening in the world of the opened IB 6 code. IB 6.0 isn't production-capable. Firebird is.

Oh, and make a point of watching the database statistics, if just to eliminate the possibility that your application's management of transactions is causing the crashes.

Helen

All for Open and Open for All
Firebird Open SQL Database · http://firebirdsql.org
_______________________________________________________