Forum Discussion

Puneethreddy_'s avatar
Puneethreddy_
Regular Visitor
3 months ago
Solved

Trying to load SQL data into the desktop, popping the following message

Hi folks, When I tried to load the SQL server data into the power bi desktop, the following message is popping up saying   "We were unable to connect to the data source using an encrypted connecti...
  • Ritaf1983's avatar
    3 months ago

    Hi Puneethreddy_ 

    The encryption warning and the empty Navigator are most likely two separate issues.

    The warning means that Power BI couldn't establish a trusted encrypted connection to SQL Server. Clicking **OK** allows Power BI to continue using an unencrypted connection, but this shouldn't be considered the permanent solution. The SQL Server certificate and its trust chain should be checked by the DBA.

    The empty database list is more likely caused by permissions or by using the wrong authentication credentials.

    Please try the following:

    1. Connect to the same server in SQL Server Management Studio using exactly the same authentication method and credentials.
    2. Check whether the expected database is visible and accessible there.
    3. In the Power BI SQL Server connection window, enter both the server name and the known database name instead of leaving the Database field empty.
    4. In Power BI Desktop, go to **File > Options and settings > Data source settings**, clear the permissions for this server, and reconnect using the correct credentials.
    5. Ask the DBA to confirm that the login is mapped to a user inside the target database and has at least the required `CONNECT` and `SELECT` permissions on the relevant schemas, tables, or views.

    A SQL Server login doesn't automatically have access to every database. It must be mapped to a database user and granted the appropriate database or object permissions. SQL Server can also hide databases from users who don't have permission to view them.

    Therefore, this doesn't appear to be a Power BI loading problem. The first thing to verify is whether the same account can see and query the database through SSMS.

    If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.