This is a discussion on Connection broken error within the MS SQL ODBC forums, part of the Microsoft SQL Server category; --> hi, I have a application that has many stored procedure running fine on a Win 2000 sp3 / SQL ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| hi, I have a application that has many stored procedure running fine on a Win 2000 sp3 / SQL 7 sp3 server. Recently i created a new proc. and when i run it the system always abort the execution and shows the message: [Microsoft][ODBC SQL Server Driver][DBNETLIB] ConnectionRead (WrapperRead()). Server: Msg 11, Level 16, State 1, Line 0 This proc. inserts records on a table and i noticed that each time i run it the proc stops after inserting a different number of rows. Sometimes just after 30 records (when running on the Query analyser, and sometimes after 270 records when running on the MICROSOFT development Environment 2002. When i get the same stored procedure restore it on a different server and run it the system completes the execution with no problem. Is there any way to identify why the same proc. that runs on a server does not run in other server and aborts with the message mentioned above? Thanks a lot for your support José Rocco |
| |||
| >-----Original Message----- >hi, > >I have a application that has many stored procedure running >fine on a Win 2000 sp3 / SQL 7 sp3 server. > >Recently i created a new proc. and when i run it the >system always abort the execution and shows the message: > >[Microsoft][ODBC SQL Server Driver][DBNETLIB] >ConnectionRead (WrapperRead()). >Server: Msg 11, Level 16, State 1, Line 0 > > >This proc. inserts records on a table and i noticed that >each time i run it the proc stops after inserting a >different number of rows. Sometimes just after 30 records >(when running on the Query analyser, and sometimes after >270 records when running on the MICROSOFT development >Environment 2002. > >When i get the same stored procedure restore it on a >different server and run it the system completes the >execution with no problem. > >Is there any way to identify why the same proc. that runs >on a server does not run in other server and aborts with >the message mentioned above? > >Thanks a lot for your support > >José Rocco >. >Check your ODBC Data Source to see if you have SQL Server 2000. If not you will need to update the mdac to 2.7 it can be found in http://www.microsoft.com/downloads/search.aspx? displaylang=en |
| ||||
| HI, I had already installed MDAC 2.8 but i got the same errors. I did not understood why you said that i shuoul have sql2000 driver because my database is SQL 7.0. And if i run the procedure in the query analyser that does not need odbc support i get the same error. I think that this problem has something to do with the sqlserver buffer, because each time the error appears after a different number of rows has been inserted in the table. Sometimes i get the error after 270 lines, sometimes after 280 and so. thanks a lot for your response. >-----Original Message----- > >>-----Original Message----- >>hi, >> >>I have a application that has many stored procedure >running >>fine on a Win 2000 sp3 / SQL 7 sp3 server. >> >>Recently i created a new proc. and when i run it the >>system always abort the execution and shows the message: >> >>[Microsoft][ODBC SQL Server Driver][DBNETLIB] >>ConnectionRead (WrapperRead()). >>Server: Msg 11, Level 16, State 1, Line 0 >> >> >>This proc. inserts records on a table and i noticed that >>each time i run it the proc stops after inserting a >>different number of rows. Sometimes just after 30 records >>(when running on the Query analyser, and sometimes after >>270 records when running on the MICROSOFT development >>Environment 2002. >> >>When i get the same stored procedure restore it on a >>different server and run it the system completes the >>execution with no problem. >> >>Is there any way to identify why the same proc. that runs >>on a server does not run in other server and aborts with >>the message mentioned above? >> >>Thanks a lot for your support >> >>José Rocco >>. >>Check your ODBC Data Source to see if you have SQL Server >2000. If not you will need to update the mdac to 2.7 it >can be found in >http://www.microsoft.com/downloads/search.aspx? >displaylang=en >. > |