Protocol Error In Tds Stream Error
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 datafrom few tables from protocol error in tds stream excel one SQL Server to another. Both the source and target servers are on SQL Server
Protocol Error In Tds Stream Ssis
2008 (10.0.2531) andData Flow Task(with OLEDB source and destination tasks) is used for data export. The package is created using Visual Studio 2008
Protocol Error In Tds Stream Communication Link Failure
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. Source: DFT_MyTable Source - MyTable
Protocol Error In Tds Stream Sql Server 2012
ns = "urn:schemas-microsoft-com:office:office" /> 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 changed fromTCP/IP to NamedPipes. Basically, an aliasfor the source is created on the destination protocol error in tds stream sql server 2008 r2 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 I click the stop button. Arsehole. Reply Michael says: July 31, 2012 at 9:22 am This solved a problem where we were trying to connect to a source stype 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 https://community.qlik.com/thread/142384 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: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]
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About http://stackoverflow.com/questions/25397910/job-failed-with-followign-error-message Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Job failed with followign error message protocol error up vote 0 down vote favorite SSIS package execution failed with following 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 11.0" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Protocol error in protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Protocol error in TDS stream". Code: 0xC0047038 Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on OLE DB Source returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). At this step SSIS package transfer data from one table to another table. Please advise, how to resolve it. sql-server ssis share|improve this question edited Aug 20 '14 at 6:32 Raja Simon 4,52531341 asked Aug 20 '14 at 6:17 Mamnoon khan 111 add a comment| 1 Answer 1 active oldest votes up vote -1 down vote Here are 2 great blog posts that cover this error in minute detail. They show in top 5 results when googling for "Protocol error in TDS stream". link 1 link 2 If neither contains the answer for you please update your question with a description how you eliminated the things covered in these blogs. share|improve this answer answered Aug 20 '14 at 8:07 Tristan 850414 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Fac