Protocol Error In Tds Stream Hy000
Contents |
30, 20098 Share 0 0 Encountered this error while running a SSIS package through a SQL Agent Job on SQL Server 2008. The protocol error in tds stream excel processing in the package is a pretty simple andthe purpose is to
Protocol Error In Tds Stream Ssis
export datafrom few tables from one SQL Server to another. Both the source and target servers are on protocol error in tds stream sql server 2012 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 Studio 2008 and the job is
Protocol Error In Tds Stream Communication Link Failure
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: 0x80004005. An OLE DB record is available. Source: protocol error in tds stream sql server 2008 r2 "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 * Email * Website Jennie says: October 13, 2010 at 9:15 am That solved our problem, thanks! We are runninup Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000
Protocol Error In Tds Stream Tableau
» General » Protocol error in TDS stream Protocol error in TDS
Protocol Error In Tds Stream Linked Server
stream Rate Topic Display Mode Topic Options Author Message melthedbamelthedba Posted Wednesday, December 4, 2002 7:30 AM Old Hand Group: protocol error in tds stream excel 2013 General Forum Members Last Login: Tuesday, October 18, 2016 1:48 PM Points: 310, Visits: 150 Hello,Recently, I began receiving error messages while connecting to a server via Query Analyzer and running https://blogs.msdn.microsoft.com/ramoji/2009/12/30/ssis-package-fails-with-protocol-error-in-tds-stream/ sp_helptext, for instance. I received the below error on numerous occasions:[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]Unknown token received from SQL Server[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL ServerDoes anyone have a reason for this error and a fix? I've been searching the web and http://www.sqlservercentral.com/Forums/Topic8585-9-1.aspx already updated MDAC to 2.7 but still the error persists. Other than MDAC, I haven't seen any other resolution suggested for the problem.Thank you so much,Melanie Post #8585 Antares686Antares686 Posted Saturday, December 7, 2002 10:08 PM SSCrazy Eights Group: Moderators Last Login: Monday, May 16, 2016 7:45 AM Points: 8,376, Visits: 780 Try reinstalling your NIC drivers. If the buffer is too large the driver may be screwing up packets. Might be server side or client side. ALso, as you stated you did MDAC 2.7 make sure both client and server. Post #48551 melthedbamelthedba Posted Monday, December 9, 2002 6:27 AM Old Hand Group: General Forum Members Last Login: Tuesday, October 18, 2016 1:48 PM Points: 310, Visits: 150 Hello Antares686,Thank you very much for your recommendation. I'll try this and let you know how it goes.Melanie Post #48552 melthedbamelthedba Posted Tuesday, December 17, 2002 12:22 PM Old Hand Group: General Forum Members Last Login: Tuesday, October 18, 2016 1:48 PM Points: 310, Visits: 150 Hello,Well, our network guy decided to defrag all of our systems and so far we haven't experienced any TDS errors again... and hope we nev
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 to create new threads on these forums. SQL Server Forums Profile | http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=95829 ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password: http://www.forumtopics.com/busobj/viewtopic.php?p=922025 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 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 protocol error 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 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 protocol error in 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 resolved the issue.The Hotfix from MS, had some ugly instructions of backing up the machines system before installing the Hotfix. I decided to try and reduce the query time and found the Refresh Options.Hope this helps someone.Have A Blessed Day..!Big Rig Topic Reply to Topic Printer Friendly Jump To: Select Forum General SQL Server Forums New to SQL Server Programming New to SQL Server Administration
Oct 28, ASUG Northern California: Nov 2, ASUG Arizona Chapter: Nov 3, ASUG All Texas Chapter Meeting: Nov 11. Protocol error in TDS stream Search this topic...|Search DI: Installation, Administration, and Connectivities...|Search Box Select a search Explain These Choices... --------------------Recent Topics (All Forums) Unanswered Posts Register or Login to Post Forum Index -> Data Integrator -> DI: Installation, Administration, and Connectivities Author Message searchforarunSenior MemberJoined: 09 Oct 2012Posts: 36Location: Pune,India Posted: Wed Nov 21, 2012 12:30 amPost subject: Protocol error in TDS stream Hi Folks, We have two of Source databases which are configured as a Linked Server. We receive this error when our production job is running in BODS 4.0 The database error message is