Protocol Error In Tds Stream Excel 2003
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Protocol Error In TDS Stream SQL Server > SQL Server Data Access Question 0 Sign in to vote I have a client workstation protocol error in tds stream excel 2013 trying to pull data from a SQL 2012 server. It is set up with
Excel Odbc Sql Server Driver Protocol Error In Tds Stream
an ODBC connection. An error is encounter while the report is pulling the data. Database Connector Error: 'HY000:[Microsoft][SQL Native Client 11.0] Protocol
Protocol Error In Tds Stream Sql Server
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
Protocol Error In Tds Stream Communication Link Failure
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 protocol error in tds stream ssis 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 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 0 Sign in to vote Which drivers - on the Server itself? And could you explain how to determine which drivers and how to reinstall them. Thanks. Wednesday, January 08, 2014 4:50 PM Reply | Quote 0 Sign in to vote The SQL Server client drivers. Run odbcad32 on the command line. See the drivers page for installed drivers. For reinstalling the drivers: Installing SQL Server Native Client and Microsoft SQLNCli team blog. Thursday, January 09, 2014 9:54 AM Reply | Quote 0 Sign in to vote I have seen this where theserver doesn't respond in time, pulling data from SQL via ODBC using Excel
(Nederlands)Polska (Polski)România (Română)Singapore (English)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)香港特別行政區 (中文) Microsoft Home Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums protocol error in tds stream sql server 2012 Answered by: Got the Protocol error in TDS stream when opening protocol error in tds stream sql server 2008 r2 the excel sheet exported from CRM4 Dynamics > CRM Question 0 Sign in to vote Hi all,Seems the protocol error in tds stream tableau number of the records is too big. (larger than 400). Is there a way to solve this?Office 2007, windows 2003, CRM4. Thanks in advance.Alanwww.ProSourceDev.com Friday, April 24, 2009 https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9a68b2f5-a033-44a5-ab1b-ec76967ebfd4/protocol-error-in-tds-stream?forum=sqldataaccess 9:27 AM Reply | Quote Answers 0 Sign in to vote Go to SQL Server Management studio and run the same query--does it give you the same error? I suspect it is not a problem with CRM, but rather a problem with network connectivity. There is a hotfix for Windows MCAC OLEDB regarding this issue http://support.microsoft.com/default.aspx/kb/890759 I'm curious, https://social.microsoft.com/Forums/en-US/2ac6b03c-c5f5-430f-a4e1-a52f50609097/got-the-protocol-error-in-tds-stream-when-opening-the-excel-sheet-exported-from-crm4?forum=crm if you try this from one of your desktops with XP or Vista do you get the same issue? Marked as answer by Donna EdwardsMVP, Owner Sunday, June 28, 2009 6:26 PM Monday, April 27, 2009 10:18 AM Reply | Quote Moderator All replies 0 Sign in to vote You should be able to export more than 400 records. the limitation is 10,000 records.You sure you are exporting all records in the current view, not just all records in the current page of the view?Are you doing a dynamic spreadsheet? If you are, go to the data tab, look at the current data source--you can edit the query that the dynamic spreadsheet uses. Monday, April 27, 2009 1:42 AM Reply | Quote Moderator 0 Sign in to vote thanks for your response, Joel.yes, I do a dynamic spreadsheet. If I use "top 400", the spreadsheet gets the data, if I use "top 500", the spreadsheet gets the error 'Protocol error in TDS stream".there are nearly 4000 records I need to export! help!Alanwww.
SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=95829 are live! 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 protocol error to Topic Printer Friendly 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 protocol error in just about 11,000 rows. It tends 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 r