none
SSAS 'Alias' issue - Not able to connect via SSRS report RRS feed

  • Question

  • Hello,

    We have created 'alias' names for SSAS Tabular servers and trying to use this in SSRS connection string. Actual SSAS tabular server name works but 'alias' name is throwing the below error when deployed in SSRS server.

    /**

    • An error has occurred during report processing. (rsProcessingAborted)
      • The execution failed for the shared data set 'DataSet1'. (rsDataSetExecutionError)
        • Cannot create a connection to data source ' Data source for shared dataset'. (rsErrorOpeningConnection)
          • The connection either timed out or was lost.
            • Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
              • An existing connection was forcibly closed by the remote host

    **/

    Tried pinging actual / alias ssas server from ssrs server - Works fine pointing to the same IP address.

    Please advise for any insight on this issue.

    Wednesday, September 18, 2019 6:23 PM

All replies

  • Hi Manoj,

    Thanks for your question.

    Per the error message above, have you granted cube or model permissions of SSAS server to that alias user?

    Reference

    Grant cube or model permissions (Analysis Services)

    Best Regards,

    Will


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, September 19, 2019 2:45 AM
  • We have created 'alias' names for SSAS Tabular servers

    How did you, DNS alias or host file entry or ...? Can you ping the alias from the machine where SSRS is running?

    Olaf Helper

    [ Blog] [ Xing] [ MVP]


    Thursday, September 19, 2019 5:20 AM
  • Oh, I was misunderstanding OP's description. I think that it refers to windows domain account.

    Thanks for your reminder, Olaf.

    The issue could be caused by several factors. Therefore, you could follow the content of this article to troubleshoot it.

    Understanding “Connection forcibly closed by remote host” Errors Caused by TOE/Chimney

    On SSRS server side, could you please help check if it has abnormal information in SSRS server log?

    On SSAS server side, please check SSAS Log, too.

    Reporting Services Log Files and Sources

    Log operations in Analysis Services

    Manoj, if you still have questions about this, please feel free let me know.

    Best Regards,

    Will


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, September 19, 2019 5:59 AM
  • It's a DNS alias. And ping from SSRS server to the alias points correctly to the actual server/IP address.
    Friday, September 20, 2019 7:10 PM
  • It's a DNS alias. And ping from SSRS server to the alias points correctly to the actual server/IP address.

    So have you followed my advice to troubleshoot that issue? How do you deal with the problem after then? Have you solved it?

    Best Regards,

    Will


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, September 23, 2019 5:50 AM
  • It's a DNS alias. And ping from SSRS server to the alias points correctly to the actual server/IP address.

    So have you followed my advice to troubleshoot that issue? How do you deal with the problem after then? Have you solved it?

    Best Regards,

    Will


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    The issue is still there, troubleshooting does not help.

    Thanks,

    Manoj M

    Thursday, October 3, 2019 3:17 PM
  • Hi Manoj,

    Thanks for your reply.

    What about windows Event error log on server side or client side? If there is no error message reminding you the reason of the issue, I guess the issue is more likely related to network hardware or network configuration. Therefore, you need to ask network administrator for further check.

    Best Regards,

    Will


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, October 4, 2019 3:25 AM