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

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
tryingPowerBI
Frequent Visitor

Unable to connect to SQL server

Hello, does anyone have the same issue before?

 

I was trying to connect SQL server, called it server A and server B. 

I can connect both servers on other apps, and I have no problems to get databases. 

 

On Power BI, I can only connect to server A. 

On server B, it shows --- Details: "Microsoft SQL: Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgment.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=18201; handshake=14361; "

 

There are something I tried but nothing work:

  • use IP address instead of server name 
  • setup "command timeout in minutes" to 2, 10, 100, 100000
  • write a custom SQL statement in “SQL statement”
  • turn off firewall 
  • open port 1433

 

Anyone can help on this issue? Thanks!!!

5 REPLIES 5
Vicky_Song
Impactful Individual
Impactful Individual

@tryingPowerBI

 

1). Do you try to connect to SQL on Server B via Power BI Desktop or Power BI online service?

2). Did you ever tried to connect to that SQL via SSMS on the same machine you have questions?

3). Can you successfully ping Server B IP address?

Hi, 

 

I am trying to connect SQL on Server B via Power BI Desktop. 

I tried to ping the IP address, it was 100% receive. And I could connect SQL via SSMS on the same machine. 

 

Anything I can do on it?

 

Thanks for your help!!!

@tryingPowerBI, do you still need further help for your issue? 

@tryingPowerBI, could you please help to provde the following information?

 

  1. Version of Power Bi
  2. Version of his SQL Server version number as well.
  3. Also see if the user can try to connect through Excel using Power Query, and see if that would work.
  4. Find the SQL ports they are using, the standard is 1433
  5. Capture a Network trace

Download link for Wireshark

Wireshark:

  1. Download and install Wireshark from the link above.
  2. Open the application as an Administrator using Right Click > Run as Administrator
  3. Click on Capture > Options at the top

T1.jpg

4. Select the connection that the traffic is processing on.  In my screenshot below, this is Etherne

T2.jpg

5. Click on Start

T3.jpg

6. Recreate the connection and/or refresh issue

7. As soon as the issue is recreated, come back into Wireshark and click on "Stop"

T4.jpg

8. Save the file by going to File > Save As

 

Download Link for Message Analyzer

Steps to capture the network trace:

 

Message Analyzer:

  1. Download and install Message Analyzer from the above link then open the application as an Administrator using Right Click > Run as Administrator
  2. Click on "New Session"

T5.jpg

3. Click on Live Trace

T6.jpg

4. Ensure that you are using "Localhost" as the Target Computer

T7.jpg

5. Click on Select Scenario

T8.jpg

6. Select "Local Network Interfaces"

T9.jpg

7. Change the Parsing Level to "Network Analysis"

T10.jpg

8. Click on Start

9. Recreate the connection and/or refresh issue

10. As soon as the issue is recreated, come back into Message Analyzer and click on "Stop"

T11.jpg

11. Save the file by going to File > Save As

 

 

@tryingPowerBI, your issue seems very strange to me. I'm trying to involve other senior engineers to have a check on it. 

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

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