none
Protocol error in TDS stream error; A connection cannot be made. Ensure that the server is running.

    Question

  • SSAS 2008 Upto date Service pack and CUs.

    Below are the errors we are receiving:

     

    Error 1:

     

    Internal error: The operation terminated unsuccessfully. OLE DB error: OLE DB or ODBC error: Protocol error in TDS stream; HY000; Protocol error in TDS stream; HY000; Protocol error in TDS stream; HY000; Communication link failure; 08S01; TCP Provider: An existing connection was forcibly closed by the remote host.

    ; 08S01. Errors in the OLAP storage engine: An error occurred while the 'Referring URL Dim' attribute of the 'Referring URL' dimension from the 'Marketing' database was being processed. Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Server: The operation has been cancelled.

     

     

    Error 2:

     

    Happens many times a day connecting via ADOMD.Net

     

    Executed as user: MI\SQLAgentAccount. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 7:00:00 AM Error: 2009-07-30 07:00:24.43 Code: 0x00000002 Source: stFull Process DB Dimensions Description: The script threw an exception: A connection cannot be made. Ensure that the server is running. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 7:00:00 AM Finished: 7:00:26 AM Elapsed: 25.25 seconds. The package execution failed. The step failed.

    Help is appreciated.

    Thursday, July 30, 2009 3:03 PM

Answers

  • These errors sound like there may be a networking issue between SQL and SSAS. Possibly a faulty network card in one of the computers or an issue with the networking hardware inbetween them. Have you checked the event logs on both computers for networking errors at the OS level
    http://geekswithblogs.net/darrengosbell - please mark correct answers
    • Marked as answer by Naggy_sr Wednesday, August 05, 2009 9:23 PM
    Friday, July 31, 2009 5:58 AM
    Moderator

All replies

  • These errors sound like there may be a networking issue between SQL and SSAS. Possibly a faulty network card in one of the computers or an issue with the networking hardware inbetween them. Have you checked the event logs on both computers for networking errors at the OS level
    http://geekswithblogs.net/darrengosbell - please mark correct answers
    • Marked as answer by Naggy_sr Wednesday, August 05, 2009 9:23 PM
    Friday, July 31, 2009 5:58 AM
    Moderator
  • Thanks for the reply Darren. The DB engine box and SSAS boxes are on different site, but they are on the same domain. All the communication between the boxes are via HIGH  speed WAN. No "Error log" in te Event viewer on both the machines. 

    Friday, July 31, 2009 2:10 PM
  • Hi,

    Are you sure that all firewalls between both computers and on the computers themselves do not block the connection?

    Frank
    Sunday, August 02, 2009 9:49 PM
  • The issue has been resolved. The first error with "TDS" in the error steam was a network issue between both the sites.

    But the second error

     The script threw an exception: A connection cannot be made. Ensure that the server is running.

    was due to an anonymus connection. Its weird that SSAS kills all the connections when an anonymus connection is made(this was determined using profiler trace.) As as interim solution I have added the Anonymus user to the Server role but I still have to research as to which process is creating these anonymus connections and why SSAS killing other connections when this user logs in.

    Nagy 
    • Marked as answer by Naggy_sr Monday, August 03, 2009 6:35 PM
    • Unmarked as answer by Naggy_sr Monday, August 03, 2009 6:36 PM
    Monday, August 03, 2009 6:35 PM
  • Thanks Frank. I will check the firewall rules between the two sites. Strangly this happens was sporadically not always. Is this issue load related?

    Regards,
    Nagy 
    Tuesday, August 04, 2009 10:06 AM
  • Darren was correct there was a network issue. Thanks for your help Darren.
    Wednesday, August 05, 2009 9:24 PM
  • The link in this post takes you to an adware/malware site.  Don't click it!  I hit this on 2015/08/26.
    Wednesday, August 26, 2015 9:58 PM