I am hoping others might have solved this issue. What I am doing is running a store procedure and everything is working as it should, but the error message is not getting back to the app server even through the DBServer is sending back the correct error with no resultset.
I am using SQL Server 2000/SP4 with the latest JDBC drivers (version 2.2.0037) from MS JDBC Drivers for SQL Server 2000. I am using IBM's JDK (J2RE 1.4.1 IBM Windows 32 build cn1411-20031011) I am getting the below error:
When I go searching for the same error, I see the following explaination back in 2004:
I suspect that somewhere earlier in the JVM, someone called Statement.cancel() on some statement from the connection that created your current statement. I believe this is an example of a bug in the MS driver, where a conection will become useless after a statement cancel().
Joe Weinstein at BEA
Now it is two years later and the same problem still exist or does it really? I know I am missing something here in my logic concerning the problem, but where?
Thanks for any comments or suggestions you could provide.
Now it is two years later and the same problem still exist or does it really?
Microsoft never really provided support for their 2000 driver, which is not that surprising, since they didn't write it. The result being its had bugs from day one that are still there. Try the 2005 driver (which will work with 2000). This was a complete rewrite rather than an upgrade and I understand it is much better. Or alternatively use the (very good) jTDS driver.