Problems with alias as Data Source

Fredrik M 246 Reputation points
2020-11-11T12:34:28.187+00:00

Hi,

I have a weird problem that I don't know how to address.

Having a PowerBi report with a view in the Data Warehouse as the Data Source. IN the data source connection I use the server alias;
39054-datasource.png

I get this error message then;
39065-errormessage.png

If I change from alias to full server name, it works. You kind of think that it is something wrong with the alias, but it is not. In fact, there are several other reports with no problems using the same alias. Even more weird is that it works with the alias when I use it locally, testing the report.

I don't even know where to start.... Any ideas?

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
Community Center | Not monitored
SQL Server | Other
0 comments No comments
{count} votes

Answer accepted by question author
  1. ZoeHui-MSFT 41,536 Reputation points
    2020-11-12T06:18:02.62+00:00

    Hi @Fredrik M ,

    Assume you are using PBI desktop to connect to the remote SQL Server instance using an alias.

    "SQL Alias" is a client Setting.

    You may need to create the alias on every client.

    Regards,

    Zoe


    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    What can I do if my transaction log is full?--- Hot issues November

    How to convert Profiler trace into a SQL Server table -- Hot issues November


1 additional answer

Sort by: Most helpful
  1. m 4,281 Reputation points
    2020-11-12T04:17:40.053+00:00

    Hi @Fredrik M

    I don't even know where to start.... Any ideas?

    I test it on my side, firstly I have the same issue as yours, then I clear cache and cookies and then follow steps as this :overview-of-sql-server-alias

    Check the protocol you used is enable in the SQL Server Client network utility, for my case, the protocol is disabled, so I choose TCP/IP into the enabled column and then it works.
    39108-20201112tcp.jpg

    BR,
    Mia


    If the answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.