SQLSTATE=08501 - or - Communication Link Failure

[chrisb.]

Hello,

Was just trying to solve an issue that keeps coming up
periodically.

We are using PowerBuilder v9.0 as our front end and MS SQL
Server as our back end. We are using ODBC as opposed to
using the Native SQL Server Database driver that comes with
PowerBuilder.

We have a process that runs hourly throughout the day,
everyday, and about every two weeks we start to get strange
errors coming from this process.

Most notably, the following error message (written in its
entirety):

SQLSTATE=08501
[Microsoft][ODBC SQL Server Driver] Communication Link
Failure

We cannot seem to isolate the cause of this issue. We do
know that if we reboot our SQL Server Database Server, the
problem goes away and all is well for about another 2 weeks,
where we have to reboot the server again.

Does anyone have any clues as to the possible or most-likely
cause of this problem?

[Sanjiv Das [TeamSybase]]

What version of SQL Server are you using? ANy particular reason to use ODBC?
With SQL Server 2000 you could use OLE DB.

Does your process connect at startup and keep an open connection to the
database? Have you tried dropping the connection after the work is
completed, then reconnecting when you need it again about an hour later?

Could the issue be network connectivity where the SQL Server machine, for
example, has general network problems?

Sanjiv.

<Chris B.> wrote in message news:434147af.678...@sybase.com...