Asp Protocol Error In Tds Stream
Contents |
30, 20098 0 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 protocol error in tds stream ssis tables from one SQL Server to another. Both the source and target servers are on
Protocol Error In Tds Stream Communication Link Failure
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 protocol error in tds stream linked server 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. Source: DFT_MyTable Source - MyTable protocol error in tds stream sql server 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
Protocol Error In Tds Stream Sql Server 2012
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 I click the stop button. Arsehole. Reply Michael says: July 31, 2012 at 9:22 am This solvedfrom GoogleSign inHidden fieldsSearch for groups or messages
here for a quick overview of the site http://stackoverflow.com/questions/24648130/protocol-error-in-tds-stream-error Help Center Detailed answers to any questions you might http://forums.aspfree.com/microsoft-sql-server-14/protocol-error-tds-stream-39882.html have Meta Discuss the workings and policies of this site About 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 protocol error Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Protocol error in TDS stream - error up vote 1 down protocol error in vote favorite We have two servers. An application server and a SQL server. When running this simple program from the application server: static void Main(string[] args) { OleDbCommand cmd; OleDbConnection cnn; string connectionString = "Provider=SQLNCLI10;Integrated Security=SSPI;User ID=***;Password=***;Persist Security Info=False;Initial Catalog=MCS_BATCH;Data Source=CD6S01;Initial File Name=;"; string sql = "EXEC [msp].[MasterMSP] @BTYPE = N'B_PVM_KNN', @AC_KEY = NULL, @RUN_TS = '2014-05-02 17:29:31.1400555', @CHUNK_ID = 8794"; System.IO.StreamWriter file = new System.IO.StreamWriter("MasterMSP_output.txt"); cnn = new OleDbConnection(connectionString); try { cnn.Open(); cmd = new OleDbCommand(sql, cnn); try { OleDbDataReader reader = cmd.ExecuteReader(); int numberOfFields = reader.VisibleFieldCount; StringBuilder sb = new StringBuilder(); while (reader.Read()) { for (int i = 0; i < (numberOfFields - 1); i++) { file.Write(reader[i].ToString()); } file.WriteLine(""); } file.Close(); } catch (Exception ex) { file.Write("Execption ex at : {0}", System.DateTime.Now); file.Write(ex.Message.ToString()); Console.WriteLine("Exception ex time is : {0}", System.DateTime.Now); throw; } cmd.Dispose(); cnn
Remember Me? Register Lost Password? facebook google twitter rss Free SEO Tools Advanced Search Forum Database Microsoft SQL Server Here Thread: Protocol Error in TDS stream Share This Thread Tweet This + 1 this Post To Linkedin Subscribe to this Thread Subscribe to This Thread October 25th, 2004,06:40 PM #1 No Profile Picture jmancuso Contributing User Join Date May 2004 Posts 41 Rep Power 13 Protocol Error in TDS stream Not sure if this is the correct forum to answer this question or not? Any help with my problem will be greatly appreciated. I'm trying to pull over 150 fields from a SQL Server view into an Excel Workbook for user display. It's a very simple view using a single table. However, when I try importing the results I get an error saying: [Microsoft][ODBC SQL Server Driver]Protocol error in TDS Stream The problem almost seems to be related to size, though I'm not certain. Originally I was pulling the fields directly from the table and received the above error. So I went through and assigned length and data type for each field. This worked great and I was able to get the results I wanted. However, I then proceeded to add more fields to the view at a later time and again began receiving the error. I've been unable to track the error to a specific field. I'm using varchar in most instances with no greater then 50 spaces in length, a few dates and floats. Is this a size issue. I'm also using the wizard to import the data directly (which uses MSQuery). Do I need to bring the query in with VBA? Again any help will be greatly appreciated. Let me know if I can exchange any help in return. Faq Reply With Quote October 25th, 2004,10:42 PM #2 Leslie Contributing User Join Date Oct 2004 Location Honolulu Posts 184 Rep Power 16 It may not be related to the number of fields or data length returned from the server, but instead to the length of the request string itself. MSQuery may be building a SQL string ("SELECT field1, field2, field3 FROM table") behind the scenes and that string may be too many charcters for the connection (provider). Then again it may be that the length for the total data in a given data row is too larg for the provider. Either way it sounds like Excel does not much like your data ..