Protocol Error In Tds Stream Excel
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Excel Query Error Microsoft Office > Excel IT protocol error in tds stream excel 2013 Pro Discussions Question 0 Sign in to vote Hi, I'm trying
Protocol Error In Tds Stream Sql Server
to pull back some (a lot of)data from a SQL Server 2005 instance using Excel 2003 and protocol error in tds stream communication link failure Microsoft Query. I think that the volume of data has grown to a size were something is failing as I now get the following error: [Microsoft][ODBC SQL Server driver]Protocol
Protocol Error In Tds Stream Ssis
error in TDS stream Most of the articles i've read on line describe this as being a problem where the data packets sent via TCP/IP are split and start off as being syncronous but due to the delay become asyncronous. The switch and subsequent receipt of duplicate data throws this error. However I've not found any that protocol error in tds stream sql server 2008 r2 describe this error comming from Microsoft Excel and so I don't know how to resolve it. I've noted that if I upgrade to Office 2007 and use the 'From SQL Server' option instead of 'Micorosft Query' that the results are returned successfully. Any suggestions on how I can resolve this error in Excel 2003? Thanks, Mike Changed type renMike Wednesday, October 13, 2010 2:59 PM Wrong type Wednesday, October 13, 2010 2:53 PM Reply | Quote Answers 0 Sign in to vote Hello Renmike, Excel 2007 is using a different SQL Server driver than MSQuery uses which is most likely accounting for the error. There is a fix for this issue located here: http://support.microsoft.com/kb/945892and that KB Article references http://support.microsoft.com/kb/946608/LN/- that article contains a fix at the top of the page. The problem is with the operating system and SQL Server, Please try applying that fix to your SQL Server machine and let me know if the problem is resolved. Will Buffington Microsoft Excel Support Marked as answer by Jenni
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar
Protocol Error In Tds Stream Sql Server 2012
Who's On Home » SQL Server 7,2000 » General » Protocol
Protocol Error In Tds Stream Tableau
error in TDS stream Protocol error in TDS stream Rate Topic Display Mode Topic Options Author protocol error in tds stream linked server Message melthedbamelthedba Posted Wednesday, December 4, 2002 7:30 AM Old Hand Group: General Forum Members Last Login: Tuesday, October 18, 2016 1:48 PM Points: 310, Visits: 150 Hello,Recently, https://social.technet.microsoft.com/Forums/office/en-US/280be6c5-eb04-4658-aa75-bd86a558c96c/excel-query-error?forum=excel 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 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 http://www.sqlservercentral.com/Forums/Topic8585-9-1.aspx 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 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: Tuesday, October 18, 2016 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 #48
SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=95829 Come on over! We've restricted the ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums SQL Server 2000 Forums Import/Export (DTS) and Replication (2000) Protocol error in TDS stream Reply to Topic Printer Friendly protocol error Author Topic ZoneFX Starting Member United Kingdom 17 Posts Posted-01/20/2008: 06:41:05 I have a DTS set up that copies data across from the live server to a local "backup/development" copy. Everything runs fine except on occation the DTS fails kicking up a "Protocol error in TDS stream" The table that fails has just about 11,000 rows. It tends protocol error in to get to about 70% complete before it fails. Is this just a network traffic issue (I'm on a domestic 1 meg connection) or has my table got too big?I'm using SQL 2000 SP4 on Windows Server 2003 rmiao Flowing Fount of Yak Knowledge USA 7266 Posts Posted-01/20/2008: 20:20:36 Most likely. ZoneFX Starting Member United Kingdom 17 Posts Posted-01/31/2008: 12:49:02 Most likely which?Network or too big? eyechart Flowing Fount of Yak Knowledge USA 3575 Posts Posted-01/31/2008: 13:54:55 it could be a problem with the OLE db provider.Check this KB article for a hotfix for OLEDB provider regarding this error http://support.microsoft.com/default.aspx/kb/890759Also, have you tried reconfiguring your connection to use ODBC driver instead? it will be slower, but if it works then that points to a problem with OLE DB provider.I would try the hotfix, if it still doesn't work properly then try using the ODBC.-ec rmiao Flowing Fount of Yak Knowledge USA 7266 Posts Posted-02/01/2008: 00:08:34 >> Network or too big?They are related, transferring big table over slow network will cause problem. BigRig2112 Starti