July 2, 2004 at 4:01 am
We have a live application that is suffering from random Connectionwrite problems.
The exact error is:
=> Message : OpenCursor failed for dynamic SQL statement 3, error from database is:
ODBC SQLExecute failed.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send()).
Environment Info:
SQL Server 2000 SP3a
MDAC 2.7
SQL ODBC Driver: 2000.85.1050.00
We have done some tests on a third machine with MDAC 2.8 but the error remained.
The problem is that we can’t reproduce the problem not solve it. It just appears from time to time interrupting important (time-consuming) batch-jobs.
During these Jobs there is heavy data/communication between the application-servers and the database-server. Due to the random character of the errors feedback is iffy at best.
Does anyone have a solution for this problem?
Ryaka
It's not a Waste.
Naps are a way of traveling painlessly through time to the Future
July 2, 2004 at 5:25 am
One thing is to run profiler from the server side to montior your statements. Server exceptions (could be another issue causing) and connection states.
July 2, 2004 at 5:54 am
OK I'll try that
Ryaka
It's not a Waste.
Naps are a way of traveling painlessly through time to the Future
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply