Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
AdithyanVee
Regular Visitor

Error While connecting to SQL Server From Power Bi Desktop

Hey Folks,

 

"DataSource.Error: Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) Details: DataSourceKind=SQL DataSourcePath=tcp:pvagn.sever.databse11.windows.net1433 Message=A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) ErrorCode=-2146232060 Number=64 Class=20 State=0 ConnectionId=b1117e1d-edf1-305bc69dab"

 

Getting this error while connecting to sql server from pbi desktop

 

please help in resolving this 


1 ACCEPTED SOLUTION
FarhanJeelani
Super User
Super User

Hi @AdithyanVee ,

 

Check Network Connectivity
Ensure you have a stable internet connection.
Try pinging the SQL Server from your system using Command Prompt:
ping pvae-sql.database1.windows.net


Try connecting to the SQL Server using SQL Server Management Studio (SSMS) to check if the issue is specific to Power BI.


Verify SQL Server Firewall Settings
Since you're connecting to Azure SQL, ensure that the client IP is whitelisted:

Go to Azure Portal → Navigate to SQL Server (pvae-sql.database1.windows.net).
Click on Networking → Check Firewall and Virtual Networks.
Under Firewall Rules, add your Public IP Address (Find it here).

https://whatismyipaddress.com/


Enable TLS 1.2 on Your Machine
If your system does not support TLS 1.2, you might face this issue.

Open Registry Editor (Win + R → regedit).
Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols


Create the following keys if not present:
TLS 1.2
Inside, create Client and Server keys.
Inside each, create a DWORD value:
makefile
Name: Enabled
Type: REG_DWORD
Value: 1


Restart your system.


Check if Ports Are Open
Azure SQL requires port 1433 to be open.
Use PowerShell to check if your system can reach the server:
powershell:
Test-NetConnection -ComputerName pvae-sql.database1.windows.net -Port 1433
If it fails, check your network settings or try switching to a different network.


Check Power BI Connection Settings
Open Power BI Desktop.
Go to File → Options and Settings → Data Source Settings.
Remove the SQL Server connection and re-add it.
Use "SQL Server Authentication" instead of Windows Authentication if needed.

 

Please mark this post as solution if it helps you. Appreciate Kudos.

View solution in original post

2 REPLIES 2
freginier
Super User
Super User

Hey there!

 

Here some possible solutions to your problem: 

Check SQL Server Configuration
- TCP/IP Enabled: Ensure that TCP/IP is enabled on your SQL Server instance. You can do this through SQL Server Configuration Manager.
- Go to SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for [YourInstance].
- Ensure that TCP/IP is enabled.

Check SQL Server Authentication Mode
-Ensure that the SQL Server is set to allow SQL Server Authentication or Windows Authentication, depending on the method you're using to log in.

Retry Connection After Some Time
- Sometimes, temporary network issues or SQL Server resource constraints may cause a failed handshake. Wait for a few minutes and try reconnecting again.

Verify the SQL Server Instance
- Verify that the SQL Server instance is running and accessible from the machine where Power BI is installed. You can test this by trying to connect to the server using SQL Server Management Studio (SSMS) or any other SQL client.
Hope this helps!

😁😁

FarhanJeelani
Super User
Super User

Hi @AdithyanVee ,

 

Check Network Connectivity
Ensure you have a stable internet connection.
Try pinging the SQL Server from your system using Command Prompt:
ping pvae-sql.database1.windows.net


Try connecting to the SQL Server using SQL Server Management Studio (SSMS) to check if the issue is specific to Power BI.


Verify SQL Server Firewall Settings
Since you're connecting to Azure SQL, ensure that the client IP is whitelisted:

Go to Azure Portal → Navigate to SQL Server (pvae-sql.database1.windows.net).
Click on Networking → Check Firewall and Virtual Networks.
Under Firewall Rules, add your Public IP Address (Find it here).

https://whatismyipaddress.com/


Enable TLS 1.2 on Your Machine
If your system does not support TLS 1.2, you might face this issue.

Open Registry Editor (Win + R → regedit).
Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols


Create the following keys if not present:
TLS 1.2
Inside, create Client and Server keys.
Inside each, create a DWORD value:
makefile
Name: Enabled
Type: REG_DWORD
Value: 1


Restart your system.


Check if Ports Are Open
Azure SQL requires port 1433 to be open.
Use PowerShell to check if your system can reach the server:
powershell:
Test-NetConnection -ComputerName pvae-sql.database1.windows.net -Port 1433
If it fails, check your network settings or try switching to a different network.


Check Power BI Connection Settings
Open Power BI Desktop.
Go to File → Options and Settings → Data Source Settings.
Remove the SQL Server connection and re-add it.
Use "SQL Server Authentication" instead of Windows Authentication if needed.

 

Please mark this post as solution if it helps you. Appreciate Kudos.

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.