Protocol Error In Tds Stream 2008
Contents |
30, 20098 Share 0 0 Encountered this error while running a SSIS package through a SQL Agent Job on SQL Server 2008. The processing in the package is a pretty simple andthe purpose is to export
Protocol Error In Tds Stream Excel
datafrom few tables from one SQL Server to another. Both the source and target protocol error in tds stream ssis servers are on SQL Server 2008 (10.0.2531) andData Flow Task(with OLEDB source and destination tasks) is used for data export. The protocol error in tds stream sql server 2012 package is created using Visual Studio 2008 and the job is running on the destination server. The job continuously failed with the following error and in each run the failure occured at a different table.
Protocol Error In Tds Stream Communication Link Failure
Source: DFT_MyTable Source - MyTable Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available The issue is solved when the Network Protocol used to connect to the source SQL Server is
Protocol Error In Tds Stream Sql Server 2008 R2
changed fromTCP/IP to NamedPipes. Basically, an aliasfor the source is created on the destination server using the below steps. 1. Go to Start-> All Programs-> Microsoft SQL Server 2008-> Configuration Tools -> SQL Server Configuration Manager 2. Expand the node SQL Native Client 10.0 Configuration 3. Right click on "Aliases" and then select "New Alias…" 4. Provide the IP address of the Source SQL server against the "Server" field and specify the Source server name against the "Alias Name" field. 5. Choose the protocol as "NamedPipes" and click OK Please drop me a note if you have come across this error and this blog has helped you in resolving the issue.
Comments (8) Cancel reply Name * Email * Website Jennie says: October 13, 2010 at 9:15 am That solved our problem, thanks! We are running a 32-bit application with SQL Server 2008 on Windows Server 2008 R2 (64 bit). Reply Anon says: October 5, 2011 at 5:54 am Not only did this not work, SSIS now refuses to end the job and stays yellow until I click the stop button. ***. Reply Anon says: October 5, 2011 at 5:55 am Not only did this not work, SSIS now refuses to end the job and stays yellow until Itype 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 Qv 11 Sr 2 to Qv 11 Sr protocol error in tds stream tableau 9.After this change some of my reloads of Application are failing from QMC at Stage1
Protocol Error In Tds Stream Linked Server
(which means When I am fetching the data from Database SQL).When I am Trying to fetch the data 1st time it fails giving protocol error in tds stream excel 2013 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 time when I reload it , it Succeeds without giving any error.Please help !!!!RegardsErika 3914Views Tags: none https://blogs.msdn.microsoft.com/ramoji/2009/12/30/ssis-package-fails-with-protocol-error-in-tds-stream/ (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 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 https://community.qlik.com/thread/142384 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:49 AM (in response to Bruno Garcia) Hi,Updated the driver, but no succes... It keeps giving the same error.SQL##f - SqlState: S1000, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC SQL Server Driver]Protocol error in TDS streamWith the Debugger on it gives a little bit more information, SQL##f - SqlState: S1000, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC SQL Serv
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 ability http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=95829 to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | http://geekswithblogs.net/WTFNext/archive/2008/12/29/sql-server-2000-tip---protocol-error-in-tds-stream.aspx 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 Author Topic ZoneFX Starting Member United Kingdom 17 Posts Posted-01/20/2008: 06:41:05 protocol error 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 to get to about 70% complete before it fails. Is this just a network traffic issue (I'm on a domestic 1 protocol error in 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 Starting Member USA 1 Posts Posted-08/05/2010: 11:02:02 It may be more of an issue with the version of Excel you're using as well.I received this error using MS Excel 2007. I looked at the connection properties and un-checked the option of "Enable
many files from a SharePoint Document Library the easy way Code Documentation Generation with SandCastle Test Data Builder pattern with object initializers in .NET Model-View-What? Unit Testing Role-based Authorization in ASP.NET MVC 3 SharePoint 2007 / 2010 Content Indexing “The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled.” Anonymous Access and Sharepoint Web Services VS2010 SP1 - The file is under source control and is not checked out .NET XPath Returns No Results News Post Categories My Blog C# C++ Software .NET Fundamentals Little Wonders vNext Toolbox Little Pitfalls Reviews Little Puzzlers .NET vNext Little Wonders Little Pitfalls C# .NET Little Wonders Software Technology vNext CSharp vNext Little Wonders Little Puzzlers vNext Archives May 2013 (1) December 2012 (1) November 2012 (1) October 2012 (1) June 2012 (1) May 2012 (1) April 2012 (2) March 2012 (1) February 2012 (1) January 2012 (1) November 2011 (1) October 2011 (2) September 2011 (1) August 2011 (1) June 2011 (2) May 2011 (1) March 2011 (1) February 2011 (1) August 2010 (2) April 2010 (2) March 2010 (2) February 2010 (1) January 2010 (1) December 2009 (1) October 2009 (2) September 2009 (2) August 2009 (6) July 2009 (2) June 2009 (2) May 2009 (3) April 2009 (4) March 2009 (2) February 2009 (2) January 2009 (14) December 2008 (12) November 2008 (18) October 2008 (35) September 2008 (2) WTF Next? Dev ramblings from a master of nothing. << 25% off plus free second shot on 070-536 | Home | .NET Tip: Char.IsDigit revisited >> SQL Server 2000 Tip - Protocol error in TDS stream Comments (1) | Share This tip might not fix everyone's issue, but for the problem I was facing today this worked out just fine. We have a scheduled weekly DTS package that is failing for the reason specified in this title: "Protocol error in TDS stream". For weeks we've just been running the thing manually, but that's not a solution, just a delay of the problem. I decided to investigate. I found an article on the SQLTeam.com forums that helped get this working finally. For us, all that was necessary was to switch the database connection to ODBC over OLE DB. For some reason the OLE DB driver wasn't enjoying the network traffic from the stored procedure the package was calling, or that would be my best guess. An