Forum Discussion
'Unable to connect to data source undefined'
Trying to refresh a dataset from 3 different sources - two are databases within the same server and then one additional server. All have been set up with the gateway I'm using.
I haven't seen the error I'm receiving 'Unable to connect to data source undefined' anywhere online.
Has anyone seen this before? I have tried refreshing a dataset from each of the sources individually with no issues.
29 Replies
I am glad to hear I am not the only one struggling, though I am sorry you are experiencing this! I updated my version of Power BI yesterday. Today I am going to build a new report from just one data source and see if I get the same error when set on an automatic refresh.
I had the same issue. In my case the problem were different privacy level settings in Power BI Desktop and Power BI Service. Make sure you have the same privacy level security:
In Power BI Desktop:
Options and Settings --> Data Source Settings
For every Datasource: --> Edit Permissions
Set Privacy Level: e.g. „Organizational“
Power BI Service:
Datasets --> (Choose you Datasets which does not update properly) --> settings --> Gateway Connection --> Actions --> (expand you cluster to show all Data Sources) --> (Choose relevant Datasource) --> Advanced Settings --> Privacy setting --> set same level (e.g. „Organizational) as in Power BI Desktop
That's brilliant, worked for me, thanks very much.
Hi Folks,
I am getting the same error for last 4 weeks. This error is not related to a particular report. I am having this error for 7, 8 reports daily. It's very frustrating. Please help us to resolve this issue.
I don't know what to try either. Some of mine refresh fine, some fail. The next day they succeed and others fail. No idea what the issue is. I was thinking it is something to do with our server, but not after I see that so many are having the same error.
Can anybody help to resolve the issue in PBI Service? The issue has been reported in many places of Internet, but never got fixed. Thanks.
My data source is only from OData API, using Import mode. Refreshing succeeded in PBI Desktop but failed in PBI Service, so I consider the issue is at gateway or PBI service self. Thus, I reinstalled both standard and personal modes of gateway, reinput the credentials, and even republished the pbix file on PBI Service ... does not work yet.
The tables are different, but error message and error code are always same.
Something went wrong
Unable to connect to the data source undefined.
Please try again later or contact support. If you contact support, please provide these details.
Underlying error code: -2147467259 Table: DocumentToProtocolRelationships.
Underlying error message: OData: Request failed: Unable to connect to the remote server
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error
Cluster URI: DF-MSIT-SCUS-redirect.analysis.windows.net
Activity ID: 84726276-12ae-46cb-b636-b1a81fe4c0fe
Request ID: 436e8798-ef78-40fb-b5c2-24fafc412259
Time: 2019-10-02 00:17:05Z
Something went wrong
Unable to connect to the data source undefined.
Please try again later or contact support. If you contact support, please provide these details.
Underlying error code: -2147467259 Table: Implementations.
Underlying error message: OData: Request failed: Unable to connect to the remote server
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error
Cluster URI: DF-MSIT-SCUS-redirect.analysis.windows.net
Activity ID: 3e3e62d0-d5af-4022-a19f-828ad65d7078
Request ID: 74c1a014-4cd6-4c10-831f-c53f485cf78a
Time: 2019-10-01 16:19:10Z
My reports have been working well on PBI Service for long time, but now cannot refresh successfully with the following error message always:
Last refresh failed: Tue Oct 08 2019 14:32:21 GMT-0700 (Pacific Daylight Time)
Unable to connect to the data source undefined.Hide detailsUnderlying error code:
-2147467259 Table: Products.
Underlying error message:
OData: Request failed: Unable to connect to the remote server
DM_ErrorDetailNameCode_UnderlyingHResult:
-2147467259
Microsoft.Data.Mashup.ValueError.Reason:
DataSource.Error
Cluster URI:
DF-MSIT-SCUS-redirect.analysis.windows.net
Activity ID:
6029d4c4-55f3-4928-b640-229166fe5d14
Request ID:
e2edc094-9a1a-6907-4632-e8d4d5ff3330
Time:
2019-10-08 21:32:21Z
Last refresh failed: Tue Oct 08 2019 15:15:18 GMT-0700 (Pacific Daylight Time)
Unable to connect to the data source undefined.Hide detailsUnderlying error code:
-2147467259 Table: ProtocolToChildProtocolRelationships.
Underlying error message:
OData: Request failed: Unable to connect to the remote server
DM_ErrorDetailNameCode_UnderlyingHResult:
-2147467259
Microsoft.Data.Mashup.ValueError.Reason:
DataSource.Error
Cluster URI:
DF-MSIT-SCUS-redirect.analysis.windows.net
Activity ID:
6029d4c4-55f3-4928-b640-229166fe5d14
Request ID:
c3350f39-ee6a-6bf5-665b-4cd1b3f5fdeb
Time:
2019-10-08 22:15:18Z
It is able to refresh successfully from PBI Desktop, but cannot refresh from PBI Service. Even though refreshed the same dataset multiple times, I got the same error code(-2147467259) on different tables above. The error "Unable to connect to the remote server ( error code: -2147467259)" was prompted multiple times in lots of articles from Internet, inculding the PBI community, but looks never be resolved?
Certainly, I doubt some issue in Gateway, and verified the Gateway network connection successafully. However, I cannot find any *.zip log file under relevant folders at all after clicking the 'Export Logs' link from the App UI (I submitted another post for this problem).
I am receiving this error for all my datasets that I have on a scheduled refresh. Some of them are connected to two data sources, some are only connected to one. But I am getting this same error.
Also getting that error message, among others. We have a multiple datasets refreshing daily and they fail for different reasons at different times. We autorefresh datasets using an on-premise gateway. It has been going for over 6 months. You may want to try all the things we have tried in case that helps:
- Set Privacy Level to Organizational
- Made sure all reports are refreshed at different times
- Created another on-premise gateway to split the load
- Created database tables rather than views to reduce processing between PowerBI and MSSQL
- Ensured both desktop and gateway has the latest version installed at all times
- Set Privacy Level to Organizational
- Made sure all reports are refreshed at different times
- Created another on-premise gateway to split the load
- Created database tables rather than views to reduce processing between PowerBI and MSSQL
- Ensured both desktop and gateway has the latest version installed at all times
Great list, Sonia!
- After the June 2019 update...
* remove orphaned queries with old data sources even if they don’t in any way get loaded (always a good idea)
* make sure if hitting two databases that they use the same windows credentials.
* remove any queries that trigger the “”hand authored queries” warning
Making all privacy settings "Organizational" and updating my gateway worked for me.
Anonymous,
What's type of the third additional data source? Does this issue also happens in power bi desktop? If this issue only happens in power bi service, please check if there's something wrong with the schedule refresh configuration and credentials.
Community Support Team _ Jimmy Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I am getting this on one of my reports this morning as well. But the rest of them were successful.
I did update my BI and this newer report was created in the new version.
Something went wrong
Unable to connect to the data source undefined.
Please try again later or contact support. If you contact support, please provide these details.
Underlying error code: -2147467259 Table: DATA.
Underlying error message: Microsoft SQL: The server principal "XXXXXXX is not able to access the database "XXXXXX" under the current security context.
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.Class: 14
Microsoft.Data.Mashup.ValueError.DataSourceKind: SQL
Microsoft.Data.Mashup.ValueError.DataSourcePath: XXXXXXX.net;XXXXXXX
Microsoft.Data.Mashup.ValueError.Message: The server principal "XXXXXXX" is not able to access the database "XXXXXX" under the current security context.
Microsoft.Data.Mashup.ValueError.Number: 916
Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error
Cluster URI: WABI-US-NORTH-CENTRAL-redirect.analysis.windows.net
Activity ID: 36b4f496-bcf9-4310-ae37-5bd5ca055ac6
Request ID: 538b9b60-164c-3ac3-d192-812cdeae84c5
Time: 2019-01-25 15:36:08ZI am getting this on one of my reports this morning as well. But the rest of them were successful.
I did update my BI and this newer report was created in the new version.
Something went wrong
Unable to connect to the data source undefined.
Please try again later or contact support. If you contact support, please provide these details.
Underlying error code: -2147467259 Table: DATA.
Underlying error message: Microsoft SQL: The server principal "XXXXXXX is not able to access the database "XXXXXX" under the current security context.
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.Class: 14
Microsoft.Data.Mashup.ValueError.DataSourceKind: SQL
Microsoft.Data.Mashup.ValueError.DataSourcePath: XXXXXXX.net;XXXXXXX
Microsoft.Data.Mashup.ValueError.Message: The server principal "XXXXXXX" is not able to access the database "XXXXXX" under the current security context.
Microsoft.Data.Mashup.ValueError.Number: 916
Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error
Cluster URI: WABI-US-NORTH-CENTRAL-redirect.analysis.windows.net
Activity ID: 36b4f496-bcf9-4310-ae37-5bd5ca055ac6
Request ID: 538b9b60-164c-3ac3-d192-812cdeae84c5
Time: 2019-01-25 15:36:08Z
