Forum Discussion
OLE DB or ADC error: [outsource.error] An error happened while reading data from the provider
Hi All - I connect to two different servers when I run my power bi queries. The issue is that when I run a data refresh (run daily) I am consistently getting stuck at one particular table as part of the refresh: "OLE or ODBC error: [DataSource.Error] An error happened while reading data from the provider: 'A transport-level error has ocurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connectionw as forcibly closed by the remote host.)'
My DA is telling me that the issue is the third party software that Power Bi is using to access the database. I do not get this error if I manually refresh each table individually, but that takes forever. Please help!
17 Replies
Hi gsalas,
To troubleshoot and narrow down the issue, could you try making a copy of your pbix file, and delete the particular table which raises the refresh issue, to see if the "Refresh All" works or not?(Note: Make sure you're using the latest version of Power BI Desktop):smileyhappy:
In addition, are you using the ODBC connector to get data from your servers in Power BI Desktop? If so, what provider are you using?
Regards
I think it's an ODBC connector. I have no idea. I just log into the SQL Server via Power Bi.
I deleted the tables as a test and the refresh works perfectly. But that isn't a solution. I HAVE to have the other two problem tables in my report - non negotiable.
Just so I understand
Do the error happens in Power BI service when a refresh is scheduled?
If so, did it just start happening or has it always happened
Can you refresh your data with no issie in Power BI Desktop?
You said you connect to two different SQL servers
Is the issue only happening for one of the servers?
Sorry for all the questions, just trying to understand in case I can help
MaxDegreeOfParallelism - degree of parallelism, that is the number of processors employed to run a single statement, for each query that has a parallel execution plan. There should be a server wide setting, however in some scenarios this might work as an overwrite.
MultiSubnetFailover- Is useful if you have an SQL Server Always On Availability cluseter. Here is what MSDN has to say about this option in the connection string:
"Always specify MultiSubnetFailover=True when connecting to a SQL Server 2012 availability group listener or SQL Server 2012 Failover Cluster Instance. MultiSubnetFailover enables faster failover for all Availability Groups and or Failover Cluster Instance in SQL Server 2012 and will significantly reduce failover time for single and multi-subnet AlwaysOn topologies. During a multi-subnet failover, the client will attempt connections in parallel. During a subnet failover, will aggressively retry the TCP connection."
