Ok, based on the error, since this is coming from the SQL Server driver, in
the application that is calling SQL Server are you specifying the
CommandTimeout, the default should be 0 which is no timeout.
You can also check the sp_configure value on SQL Server and look at the
"remote query timeout" value. The default is 0, which is no timeout. If this
value has changed then you can get this error.
Also check the linked server properties. Check the Progress driver to see if
there is a default value for query / command timeout.
Some things to troubleshoot the problem.
1. Can you reproduce the error by logging into SQL Server using Query
Analyzer and running select * from my_linked_progress_database. If the
problem occurs here then I would check the SQL Server sp_configure values or
the Progress driver for any default values.
2. If the problem does not happen with Query Analyzer then it is caused by
the client application settings. What database access technology are you
using to connect to SQL Server (ADO, RDO, ODBC, OLEDB). I seem to remember
that some of these technologies had different default command timeout