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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

0

Cannot connect PowerBI Desktop to Datverse Connector

as the title suggests

A network-related or instance-specific error occurred while establishing a connection to SQL Server. Verify that the instance name is correct and that SQL Server is configured to allow remote connections

according to the splendig MS forums and the error message, it seems the SQL Server is not running, not accpeting TCP or ports are blocked. 

funny thing. its the MS own Dataverse I am trying to connect to, via the built in BI -> Dataverse connector. 

Seriously: one of the things MS claims is the all integrated dataverse, seamless reporting yadda yadda yadda

 

btw: the label function to report issues is a joke, isn´t it ? 
and tis is not an idea as well, its a serious connection issue 
yet the Dataverse (and Business Central for that matter) integration has to be the worst performing connection ever. 

it´s performance is abysmal and it is extremely unreliant. 
MS , what is goin on ?



Status: Delivered
Comments
Anonymous
Not applicable

Hi @bco_lde ,

 

This error usually means that the client can't find the SQL Server instance. This issue occurs when at least one of the following problems exists:

  • The name of the computer hosting SQL Server is incorrect.
  • The instance doesn't resolve the correct IP.
  • The TCP port number isn't specified correctly.

 

For the solutions ,please refer to A network-related or instance-specific error occurred - SQL Server | Microsoft Learn

 

Best Regards,
Community Support Team _ Caitlyn

bco_lde
Helper I

thanks. 

as to your response: its the dataverse server. I doubt its not running. 
the address is correct (our crm and bc instances are running and fine)
in the dataverse connector I cannot specify a port. I can in a normal SQL connector though, so at least thats something, right ? 


why we have the Dataverse connector when we could also use the actual SQL connector instead (just tested this) is beyond me. where´s the benefit again ? 

thanks anyways.