Excel Odbc Sql Server Driver Protocol Error In Tds Stream
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 Pro Discussions Question 0 Sign in to vote Hi, I'm trying to pull microsoft odbc sql server driver protocol error in tds stream excel back some (a lot of)data from a SQL Server 2005 instance using Excel 2003 protocol error in tds stream sql server 2012 and Microsoft Query. I think that the volume of data has grown to a size were something is failing as I protocol error in tds stream sql server 2008 r2 now get the following error: [Microsoft][ODBC SQL Server driver]Protocol 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 protocol error in tds stream excel 2013 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 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
Protocol Error In Tds Stream Sql Server
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 Jennifer ZhanModerator Thursday, October 21, 2010 5:22 AM Thursday, October 14, 2010 4:25 PM Reply | Quote Moderator All replies 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 experts to answer whatever question you can come up with. Our new SQL Server Forums are live! Come on over! We've restricted the
Protocol Error In Tds Stream Ssis
ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics protocol error in tds stream communication link failure | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? protocol error in tds stream tableau All Forums SQL Server 2005 Forums Transact-SQL (2005) EXCEL Import Data Query Reply to Topic Printer Friendly Author Topic sureshkumarnaidu Starting Member 3 Posts Posted-12/11/2007: 06:35:53 Hi All,Iam trying to import https://social.technet.microsoft.com/Forums/office/en-US/280be6c5-eb04-4658-aa75-bd86a558c96c/excel-query-error?forum=excel data from Excel using Import Data query which has 125 columns. iam getting an error message"microsoft ODBC SQL Server Driver Protocol error in TDS Stream"Pls help meUrgentAdvances thanksRegardsSuresh Edited by - spirit1 on 12/11/2007 07:44:04 ditch Flowing Fount of Yak Knowledge South Africa 1466 Posts Posted-12/11/2007: 06:45:16 I think there is a limt of 25 columns when using this.Check this link: http://forums.aspfree.com/microsoft-sql-server-14/protocol-error-in-tds-stream-39882.htmlDuane. SwePeso Patron http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=94018 Saint of Lost Yaks Sweden 30421 Posts Posted-12/11/2007: 06:46:02 This is a forum for WORKING scripts only.Your problem is described herehttp://www.sqlteam.com/forums/topic.asp?TOPIC_ID=49926even though the header says "Export".E 12°55'05.25"N 56°04'39.16" Topic Reply to Topic Printer Friendly Jump To: Select Forum General SQL Server Forums New to SQL Server Programming New to SQL Server Administration Script Library Data Corruption Issues Database Design and Application Architecture SQL Server 2012 Forums Transact-SQL (2012) SQL Server Administration (2012) SSIS and Import/Export (2012) Analysis Server and Reporting Services (2012) Replication (2012) Availability Groups and DR (2012) Other SQL Server 2012 Topics SQL Server 2008 Forums Transact-SQL (2008) SQL Server Administration (2008) SSIS and Import/Export (2008) High Availability (2008) Replication (2008) Analysis Server and Reporting Services (2008) Other SQL Server 2008 Topics SQL Server 2005 Forums Transact-SQL (2005) SQL Server Administration (2005) .NET Inside SQL Server (2005) SSIS and Import/Export (2005) Service Broker (2005) Replication (2005) High Availability (2005) Analysis Server and Reporting Services (2005) Express Edition and Compact Edition (2005) Other SQL Server Topics (2005) SQL Server 2000 Forums SQL Server Development (2000) SQL Server Administration (2000) Import/Export (DTS) and Replication (2000) Transact-SQL (2000) Analysis Services (2000) MSDE (2000) Development Tools ASP.NET R
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get https://www.experts-exchange.com/questions/23307846/When-iam-executing-query-iam-getting-this-error.html Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers http://microsoft.public.sqlserver.connect.narkive.com/IPMakOra/protocol-error-in-tds-stream-vs-network-packet-size Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > When iam executing query iam getting this error Want to Advertise Here? Solved When iam executing query iam getting this error Posted on 2008-04-09 MS SQL Server Databases MS SQL Server 2005 3 Verified Solutions 6 Comments 1,767 Views Last Modified: 2008-09-13 When ever protocol error iam executing a query in query analyser i get this error earlier it was working fine now this err is seen. what is default database connection methods in sql server 2000/2005? Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server [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]Protocol error in TDS stream [Microsoft][ODBC SQL Server Driver]Protocol error in TDS protocol error in stream [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]Protocol error in TDS stream [Microsoft][ODBC SQL Server Driver]TDS buffer length too large [Microsoft][ODBC SQL Server Driver]TDS buffer length too large [Microsoft][ODBC SQL Server Driver]TDS buffer length too large [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 Server [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server [Microsoft][ODBC SQL Server Driver]TDS buffer length too large [Microsoft][ODBC SQL Server Driver]TDS buffer length too large [Microsoft][ODBC SQL Server Driver]TDS buffer length too large 0 Question by:Sandeepiii Facebook Twitter LinkedIn Google LVL 75 Active today Best Solution byAneesh Retnakaran open a new Query analyser and run that query Go to Solution 4 Comments LVL 75 Overall: Level 75 MS SQL Server 59 MS SQL Server 2005 45 Databases 22 Message Active today Accepted Solution by:Aneesh Retnakaran2008-04-09 open a new Query analyser and run that query 0 LVL 23 Overall: Level 23 MS SQL Server 20 MS SQL Server 2005 7 Databases 2 Message Assisted Solution by:adathelad20
that connectto SQL Server 2000 (SP3) with MS Query. We later found that this occurs whenthe user select too many fields from the MS Query Designer.Interestingly, we later found that this can be fixed by enlarging the'Network Packet Size' configuration setting in the SQL Server! From myunderstanding, I would think that if something is too large for a singlenetwork packet, it will just be broken into smaller pieces and that should betransparent to the application. However, what we found here seems to meansomething else. We dare not to apply this on production as we are afraid ofthe possible side effect.Is this a bug in MS Query, Excel or SQL Server and is there any betterworkaround for this problem? Kevin McDonnell [MSFT] 2005-03-17 20:43:14 UTC PermalinkRaw Message It could be a bug, however everyone's network could impact the behavior.Does this also occur if you were to query the server locally?Thanks,Kevin McDonnellMicrosoft CorporationThis posting is provided AS IS with no warranties, and confers no rights. Gavin Chan 2005-03-18 01:47:02 UTC PermalinkRaw Message Do you mean that query the server locally by ms excel and msquery? We didn'ttry that before. However, if we are using query analyzer, this problem didnot occur.We can simulate the same problem with Excel 2000, XP and 2003. If this is abug, it seems to be related to SQL Server. We are using SQL Server 2000 + SP3(8.00.847) but I am not able to find any fix that is related to the problem.Post by Kevin McDonnell [MSFT]It could be a bug, however everyone's network could impact the behavior.Does this also occur if you were to query the server locally?Thanks,Kevin McDonnellMicrosoft CorporationThis posting is provided AS IS with no warranties, and confers no rights. Gavin Chan 2005-05-03 10:52:04 UTC PermalinkRaw Message We reported this problem and finally we confirmed that it is a bug.For MSQuery, ODBC driver is used which has a problem in retrieving largerecordset. With our default setting in SQL Server - Network Packet Size =4096, the field definition for the recordset is too large to fit in onenetwork packet and ODBC driver do not handle this properly and the problemoccur. Microsoft said that a fix will be available in next version of Windows....Post by Gavin ChanDo you mean that q