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
SQLSTATE=08501 - or - Communication Link Failure
Hot Topic
- raw file destination and environment variables
- SQL server 2000 error
- Creating a project from an existing Database
- How do you use the upgrade.exe for sqlce 2.0 to sqlce 3.0?
- About data mining trainings for SQL Server 2005
- When can we use Profit chart?
- SQL Server 2005 incorrectly claims I don't meet minimum service pack level requirements?
- SQL Server Configuration Manager
- Mirroring and orphaned users
- Problem with Dimension
SQL Server
- Report server in sql 2005 standard edition does not work
- Function that returns a table
- Encapsulate encryption with an UDF and a view
- Is this possible?
- append data from a text file
- Extract Time from Timestamp in Named Calculation
- View and query optimization
- Can more than one database be queried
- Configuration file reused by different packages
- help on approach
SQLSTATE=08501 - or - Communication Link Failure
Misto
Bistesh
This doesn't sound like a T-SQL issue, so this may not be the best forum to get your question answered. Regardless, to start off, can you please specify exactly what version of SQL Server and which ODBC driver version you're using
Also - Do you see anything in the SQL error log or the NT event log that might give a clue
Also - Before you reboot SQL Server, have you checked Task Manager to see what its resource consumption is Is memory or CPU usage spiked Is there a deadlock Did you happen to notice if the spid you connected on is still running Did you tried to kill it Do you have an Perf Counter data that might be useful to diagnose the problem
Also - Does your "hourly throughout the day" process run concurrently with some other big load during the times it fails
You might want to considering calling CSS to diagnose and fix and issue like this.
Thanks