Subject | Re: [firebird-support] Unknown ISC Error 0 |
---|---|
Author | Helen Borrie |
Post date | 2014-01-16T07:07:09Z |
At 06:28 p.m. 16/01/2014, Cam wrote:
But WNET is a noisy protocol, prone to Connection Lost and Connection Reset errors with no cause other than poor error recovery.
All that said, it would make sense to check the network hardware - cards, connectors, cables, routers, including wifi if it's in use.
Helen Borrie, Support Consultant, IBPhoenix (Pacific)
Author of "The Firebird Book" and "The Firebird Book Second Edition"
http://www.firebird-books.net
__________________________________________________________________
>HiIt appears your clients are using Named Pipes protocol (WNET) to connect to the server. The number of simultaneous WNET connections will be limited by the Windows licence. It's not just database connections that are counted: so are network and shared printers, file shares, NAS directories, etc. If the network is being stretched to the limit, the NMS will disconnect any "quiet" connections to let the next connection request through. Watch the Firebird log when the app gets a 335544648: there might be a corresponding WNET error there.
>
>Using Firebird 2.5.2 32 bit SuperServer.
>Happens on Win XP, WIN7 64 BIT oS'S
>
>Occasionally on some sites I am getting a dialog Box with
>
>ISCErrorCode 335544648
>Unknown ISC Error 0
>
>According to the error code list the 335544648 code means
>335544648 conn_lost Connection lost to pipe server.
>
>Not sure what this means.
>
>I have terminated the application using Firebird.
>Stopped and Started the Firebird Service.
>Backed up and restored the database with no errors.
>Restart the application and the error occurs immediately.
>
>The only way I have been able to clear the error is to reboot the PC.
But WNET is a noisy protocol, prone to Connection Lost and Connection Reset errors with no cause other than poor error recovery.
>Is there another way to clear the conditions causing this error?Better to *avoid* the error. Use TCP/IP as the connection protocol for your database clients. It isn't affected by the Windows licence limitations. It's less noisy, as well.
All that said, it would make sense to check the network hardware - cards, connectors, cables, routers, including wifi if it's in use.
Helen Borrie, Support Consultant, IBPhoenix (Pacific)
Author of "The Firebird Book" and "The Firebird Book Second Edition"
http://www.firebird-books.net
__________________________________________________________________