Microsoft Odbc Sql Server Driver Protocol Error Tds Stream
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Protocol protocol error in tds stream excel 2013 Error In TDS Stream SQL Server > SQL Server Data
Protocol Error In Tds Stream Sql Server 2008 R2
Access Question 0 Sign in to vote I have a client workstation trying to pull data
Protocol Error In Tds Stream Communication Link Failure
from a SQL 2012 server. It is set up with an ODBC connection. An error is encounter while the report is pulling the data. Database Connector
Odbc Driver 11 For Sql Server]protocol Error In Tds Stream
Error: 'HY000:[Microsoft][SQL Native Client 11.0] Protocol error in TDS stream' I figured the issue was with the ODBC connection so I dropped and re-created it but the error persisted. I've removed the firewall as well. I tried updating the native client driver. I don't know what else to try. Thursday, January 17, 2013 2:30 PM Reply | Quote Answers 0 Sign in to vote TDS stream errors indicate either corrupted driver installations or severe physical network error. So when you have already done a clean reinstall of the driver, I would take a look at the network hardware. If only on client has the problem try changing the NIC or wires.. Proposed as answer by Papy NormandModerator Wednesday, January 23, 2013 1:07 PM Marked as answer by Iric WenModerator Friday, January 25, 2013 8:48 AM Thursday, January 17, 2013 2:34 PM Reply | Quote All replies 0 Sign in to vote TDS stream errors indicate either corrupted driver installations or severe physical network error. So when you have already done a clean reinstall of the driver, I would take a look at the network hardware. If only on client has the problem try changing the NIC or wires.. Proposed as answer by Papy NormandModerator Wednesday, January
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » General » Protocol error in TDS stream Protocol error in TDS stream Rate Topic Display Mode Topic Options Author Message melthedbamelthedba Posted Wednesday, December 4, 2002 7:30 AM Old Hand Group: General Forum Members Last Login: 2 days ago @ 1:48 PM Points: 310, Visits: 150 Hello,Recently, I began receiving error messages while connecting to a server via Query Analyzer and running sp_helptext, for instance. I received the below error on numerous occasions:[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream[Microsoft][ODBC SQL Server Driver]Protocol https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9a68b2f5-a033-44a5-ab1b-ec76967ebfd4/protocol-error-in-tds-stream?forum=sqldataaccess error in TDS stream[Microsoft][ODBC SQL Server Driver]TDS buffer length too large[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL ServerDoes anyone have a reason for this error and a fix? I've been searching the web and already updated MDAC to 2.7 but still the error persists. Other than MDAC, I haven't seen any other resolution suggested for the problem.Thank you so much,Melanie Post #8585 Antares686Antares686 Posted http://www.sqlservercentral.com/Forums/Topic8585-9-1.aspx Saturday, December 7, 2002 10:08 PM SSCrazy Eights Group: Moderators Last Login: Monday, May 16, 2016 7:45 AM Points: 8,376, Visits: 780 Try reinstalling your NIC drivers. If the buffer is too large the driver may be screwing up packets. Might be server side or client side. ALso, as you stated you did MDAC 2.7 make sure both client and server. Post #48551 melthedbamelthedba Posted Monday, December 9, 2002 6:27 AM Old Hand Group: General Forum Members Last Login: 2 days ago @ 1:48 PM Points: 310, Visits: 150 Hello Antares686,Thank you very much for your recommendation. I'll try this and let you know how it goes.Melanie Post #48552 melthedbamelthedba Posted Tuesday, December 17, 2002 12:22 PM Old Hand Group: General Forum Members Last Login: 2 days ago @ 1:48 PM Points: 310, Visits: 150 Hello,Well, our network guy decided to defrag all of our systems and so far we haven't experienced any TDS errors again... and hope we never do. We did not update MDAC nor touch the NIC cards.Thanks,Melanie Post #48553 JonrJonr Posted Wednesday, January 26, 2005 5:22 AM SSC-Enthusiastic Group: General Forum Members Last Login: Friday, June 19, 2015 7:41 AM Points: 142, Visits: 65
Just as a follow up to this, we saw the same problem on a brand new, 4 processor HP sertype your message and try again. 7 Replies Latest reply: Oct 5, 2015 3:08 AM by Protocol Error in TDS Stream Erika Jain Nov 17, 2014 4:59 AM Hi All,I Have upgraded my Qlikview server and Desktop from Version https://community.qlik.com/thread/142384 Qv 11 Sr 2 to Qv 11 Sr 9.After this change some of http://windowsitpro.com/windows/i-am-getting-message-protocol-error-tds-datastream-sql-server-query my reloads of Application are failing from QMC at Stage1 (which means When I am fetching the data from Database SQL).When I am Trying to fetch the data 1st time it fails giving the following Error:SQL##f - SqlState: S1000, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC SQL Server Driver]Protocol error in TDS streamSQL SELECT * FROM AirReconLive.dbo."tbl_SalesHeader"2nd protocol error time when I reload it , it Succeeds without giving any error.Please help !!!!RegardsErika 3874Views Tags: none (add) This content has been marked as final. Show 7 replies Re: Protocol Error in TDS Stream Sai Maguluri Nov 17, 2014 12:51 PM (in response to Erika Jain ) Hi,I got the similar issue here and will investigate further... Like Show 0 Likes (0) Actions Re: Protocol Error in TDS protocol error in Stream Sai Maguluri Nov 17, 2014 4:23 PM (in response to Erika Jain ) Hi,This is what I heard from Qlik Support below. So, update the ODBC Driver to the Latest one and it should help... Like Show 0 Likes (0) Actions Re: Protocol Error in TDS Stream Jared Papador Nov 17, 2014 4:29 PM (in response to Erika Jain ) This issue is really annoying. Like the replies above it is an ODBC driver issue. Try updating the driver or connecting via OLEDB and see if the issue persists. Like Show 1 Like (1) Actions Re: Protocol Error in TDS Stream Stephane Chivet Jan 14, 2015 5:37 AM (in response to Erika Jain ) Hi Erika,I had exactly the same problem. Now I have updated the ODBC Driver and it work as before: Like Show 0 Likes (0) Actions Re: Protocol Error in TDS Stream Bruno Garcia Jan 14, 2015 5:44 AM (in response to Erika Jain ) Hi friend.I had the same problem. I think the issue is about the ODBC Drive. Try to connect using OLEDB direclty.This solved my problem.See ya! Like Show 0 Likes (0) Actions Re: Protocol Error in TDS Stream Armin Oct 2, 2015 9:4
WindowsWindows 10 Windows Server 2012 Windows Server 2008 Windows Server 2003 Windows 8 Windows 7 Windows Vista Windows XP Exchange ServerExchange Server 2013 Exchange Server 2010 Exchange Server 2007 Exchange Server 2003 Outlook Unified Communications/Lync SharePoint Virtualization Cloud Systems ManagementSystem Center PowerShell & Scripting Active Directory & Group Policy Mobile Networking Storage TrainingOnline Training IT/Dev Connections Webcasts VIP Library Digital Magazine Archives InfoCentersIT Innovators Mobile Computing Business Now Desktop VDI All About Converged Architecture Advertisement Home > Windows > I am getting a message Protocol error in TDS Datastream from a SQL Server query. I am getting a message Protocol error in TDS Datastream from a SQL Server query. Feb 4, 2000 Neil Pike | Windows IT Pro EMAIL Tweet Comments 0 Advertisement A. Three things may be happening :- 1. SQL Server is internally gpf'ing/AV'ing (same thing) - you should see messages to this effect in the SQL errorlog. 2. Net-lib bug with overlapped/fragmented packets. 3. A complex query is generating incorrect TDS syntax in the packets For all problems you can try applying the latest SP to the server. You should also search the knowledgebase at http://support.microsoft.com For net-lib bugs you will need to apply to the client as well. Also the version of ADO/ODBC can help cause the problem as well, so try upgrading. The latest versions of these drivers can be downloaded from www.microsoft.com/data. If you're getting access violation messages, then see the FAQ entry on access violations in the FAQ. If it is being caused by a complex query, then try re-writing the query - breaking it up into smaller chunks. If this is not possible, see if the problem occurs when you run the query via ISQL/W instead of via the application. If you are getting a problem with TDS packet fragmentation (TDS is SQL's application level protocol) then try a different net-lib - e.g. tcp-ip instead of named-pipes or vice-versa. If still no-go then you'll need to call Microsoft PSS. Even if a different net-lib fixed the problem, then please still report the problem to Microsoft PSS. Unless Microsoft get these bug reports then they can't fix them. (With a repro script an MVP will do it for you). Your call fee WILL be re-imbursed as all calls about bugs are free. (However, on the "normal" support-line the person answering the phone can't know it's a bug, so they'll need your credit card details anyway). Microsoft will need you to supply :- SQL Errorlog(s) NT event log(s) - if any NT errors were occuring at the time TSQL code run