Hi bsa,

I noticed you posted a similar question about a year age (Sept 7, 2001 to be precise) involving this error. Searching Google.com led me to this link on the Microsoft Knowledge base:

Pipe error 231

This would lead me to believe the error has to do with the setup of the Terminal Server and the volume of printing being done, and not with Adagio in particular. Here are a couple quotes from that link:

quote:
When SQL Server receives many simultaneous Named Pipes connection requests, some connection requests may fail if the pipe is busy. In the SQL Server error log, multiple "17832 Unable to read login packet" errors are typically logged. On the client side, error 231 "connection busy" or "pipe busy" may be generated.

quote:
There is only one thread that handles incoming SQL Server Named Pipes connection open requests. In an environment where multiple simultaneous named pipes connection requests are issued, it is very likely that no pipe instance is available to service the next pipe open request at any particular moment. In this case, a pipe busy status is returned to the client and the client retries the connection within the specified timeout period until the pipe is available. From a network sniffer trace, on the Windows NT Server Create response, error code (172) STATUS_PIPE_NOT_AVAILABLE is returned to the client. In case of a 16-bit client connection, code (231) ERROR_PIPE_BUSY is returned to the client.

quote:
Increase the application logon timeout value. In this interval, DB-Library and the ODBC driver manager will retry connecting to SQL Server, thereby increasing the chance of a successful connection. Configure SQL Server to listen on multiple pipes. Doing this will increase the number of threads available to process incoming Named Pipes connections. Different client workstations must be configured to use alternate pipes to evenly distribute the load on each pipe.

You can configure SQL Server to listen on multiple pipes by using the registry editor.

Regards,