Learn how to a build a cloud-first strategyRegister Now


[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream

Posted on 2014-08-20
Medium Priority
Last Modified: 2015-06-27
I've got a Server2008 SP1 32 bit server using ODBC to connect to Server2012 running SQL2012.  It runs some file build utilities that have worked fine until 3 days ago and then I got the error in the title.  Both servers run on VMware boxes with dual port twinax 10 GB NICs.

I ran Windows Updates on the Server2008 box, but it didn't change anything.  

I could use some help.
Question by:Scott Miller
  • 4

Expert Comment

by:Chad Franks
ID: 40274339
was something changed on the network side?  I have seen this when the switch/nics didn't match their duplex...

Author Comment

by:Scott Miller
ID: 40274453
Nope.  We upgraded to SQL2012 a couple of weeks ago and it has run perfectly since.....up until 3 days ago.

I just upgraded the Server2008 (where the processes run and get the errors) to SP2.  It ran the processes fine the first time and errored out on the second time and nearly every time after.

Author Comment

by:Scott Miller
ID: 40274831
ODBC timeout issue.  Why it suddenly stopped working, I don't know.  I increased the timeout to 120 seconds and it's worked perfectly every time I've tested it since.

8/21/14 - I lied ;)  
I've still got one file rebuild that causes the above error.  I'll increase the timeout to 180 and see if that helps.  The last timeout increase got the error from 2-3 times down to one, so I think I'm on the right track.

8/21/14 - I lied again.  I changed the ODBC timeout settings yesterday, but today when I thought I'd change them again to a higher value - the ones I set yesterday were gone and it's back to default.  Not sure what to do at this point.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.


Author Comment

by:Scott Miller
ID: 40276938
8/22/14 - trying a different approach, I changed the timeout on the TCPIP configuration on the SQL server.  
Yesterday, things ran fine manually, but when I set them up to run automatically (like normal), I started getting the error back again.  I ran all the processes manually today and they worked fine.  I'm in the midst of running them for the third time automatically; so far, no errors.  

Stay tuned.......

Accepted Solution

Scott Miller earned 0 total points
ID: 40279144
Figured it out.  I've got 5 VMware servers.  VM1 is where the S2008 server that runs the processes resided.  VM2 is where the SQL2012 server resides.  VMware manages the 20GB connections from the servers to the switch, so when other servers on the VM1 box got busier, they took some of the bandwidth that the S2008 server was using, causing a slowdown in bandwidth, which caused the error.  That also shows why the problem was intermittent; when the other servers on VM1 were less busy, the processes ran fine; when they were more busy, the processes had the errors.  
I moved the S2008 server in question onto VM2 where the SQL2012 server resides - problem solved.  There's no worry about interference because it runs at bus speed.  I've tested it half a dozen times flawlessly and even let it run at it's normally scheduled time.

This question can be closed.  

I won't accept my own answer as the solution (even though it was) because there people here that think I've done that to build up my own points.  I don't care about points, I care about getting my issue resolved.
LVL 36

Expert Comment

by:Seth Simmons
ID: 40854330
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to install and use the NTBackup utility that comes with Windows Server.
Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question