Protocol Error In Tds Stream Sql Server 2005
Contents |
30, 20098 Share 0 0 Encountered this error while running a SSIS package through a SQL Agent Job on SQL Server
Protocol Error In Tds Stream Excel
2008. The processing in the package is a pretty simple andthe protocol error in tds stream ssis purpose is to export datafrom few tables from one SQL Server to another. Both the source protocol error in tds stream sql server 2012 and target servers are on SQL Server 2008 (10.0.2531) andData Flow Task(with OLEDB source and destination tasks) is used for data export. The package is created using Visual
Protocol Error In Tds Stream Communication Link Failure
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. Source: DFT_MyTable Source - MyTable Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code:
Protocol Error In Tds Stream Sql Server 2008 R2
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 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 * EmailSQL 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 to protocol error in tds stream tableau create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members
Protocol Error In Tds Stream Linked Server
| Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums protocol error in tds stream excel 2013 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 I have https://blogs.msdn.microsoft.com/ramoji/2009/12/30/ssis-package-fails-with-protocol-error-in-tds-stream/ 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 meg connection) or http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=95829 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 Background Refresh" and it
struggled with the following issue in SSIS: I specified a stored proc as the SQL command text in an OLE DB Source in a data flow. When I clicked the http://gieliesknowledgebase.blogspot.com/2008/12/yesterday-i-struggled-with-following.html Preview button the data I expected was returned. The Columns were also picked up successfully in the source editor.But everytime I ran the package it failed with the following errors:SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "Protocol error in TDS stream"...SSIS Error Code protocol error DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "OLE DB Source" (1135) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure...A component has returned from its protocol error in PrimeOutput call. : 1135 : OLE DB SourceSSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038. There may be error messages posted before this with more information on why the thread has exited...SSIS Error Code DTS_E_THREADCANCELLED. Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown. There may be error messages posted before this with more information on why the thread was cancelled...SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC0047039. There may be error messages posted before this with more information on why the thread has exited...After searching the whole day for a solution I finally stumbled accross this post by Adam Machanic. At first sight it did not fit my problem, but out of desperation I decided to give it a bash; and it worked.I am not going to repeat what he said in his post because he did a brilliant job of it. But in short: tables, views and table-valued UDFs have explicitly defined output columns; and stored procs don't. So SSIS will have guaranteed success in retrieving the correc