Forum Discussion
Dataset maintenance, custom connectors, something went wrong
Is anyone else using custom connectors to extract data from an on-prem enterprise gateway?
Everything worked fine for months then, all of a sudden on a random Tuesday, I get errors saying "something went wrong".
I get that error in the portal when trying to manage parameters and gateways for my dataset. I believe this issue is on the "status" page, but it isn't reflected as an outage:
https://powerbi.microsoft.com/en-us/support/
Also that status misrepresents the problem as one that only happens in personal gateways. This is affecting our enterprise gateway. Also it says the problem will be fixed by end of day 8/6. Why would production outages take that many days to fix? Shouldn't they roll back the change that broke this? Also, when they say end-of-day, whose day are they talking about? The programmer's or mine? (eg. Deepak Singh in India, or Joe Smith's day in the USA)?
FYI, for anyone affected the fix is to either delete your personal gateway, or allow someone to take ownership who doesn't have a personal gateway. This allows the calculation of the "settings" to run smoothly without encountering an offending gateway.
Here are more details:
-----
As discussed, I have reached out to our internal team for complete information on this issue and have the below Root cause analysis for you. Engineers have identified the root cause and a fix is expected to be deployed by end-of-day 08/06/2022.
Title:
The dataset settings page won't load for users with a personal gateway and datasets with a customer connector data source
User impact: Dataset settings page won't load for users with a personal gateway and datasets with a customer connector data source.
More info: Users who have a personal gateway and try to access the dataset settings page for a dataset that has a customer connector data source will see the following error: "Something went wrong. Failed to load data sources. Please try again later."
Additionally, affected users will also be unable to refresh the datasets.
While we’re focused on remediation, users without a personal gateway can take over the dataset to make the required changes to the dataset settings page.
Current status: We're finalizing the internal testing for our fix to ensure that its deployment successfully remediates impact. We're expecting internal testing to complete by our next scheduled update, when we're also anticipating the ability to provide an estimated fix deployment timeline for impact resolution.
Scope of impact: Your organization is affected by this event, and this impacts any user who has a personal gateway and tries to access the dataset settings page for a dataset that has an on-premises customer connector data source.
Root cause: A code regression within a data movement update is resulting in the impact.
Workaround that can be tried for non-personal gateway users :
1. If the dataset owner has a personal gateway (but may not be using it), and is using enterprise gateway to refresh the dataset they may run in to this issue, they can ask any other user with permission to data source and no personal gateway created with his account, take over the dataset and try refreshing it.
2. If the personal gateway is present (not being used)and is not critical, then the user can try deleting his personal gateway and try refreshing the dataset.
3 Replies
FYI, for anyone affected the fix is to either delete your personal gateway, or allow someone to take ownership who doesn't have a personal gateway. This allows the calculation of the "settings" to run smoothly without encountering an offending gateway.
Here are more details:
-----
As discussed, I have reached out to our internal team for complete information on this issue and have the below Root cause analysis for you. Engineers have identified the root cause and a fix is expected to be deployed by end-of-day 08/06/2022.
Title:
The dataset settings page won't load for users with a personal gateway and datasets with a customer connector data source
User impact: Dataset settings page won't load for users with a personal gateway and datasets with a customer connector data source.
More info: Users who have a personal gateway and try to access the dataset settings page for a dataset that has a customer connector data source will see the following error: "Something went wrong. Failed to load data sources. Please try again later."
Additionally, affected users will also be unable to refresh the datasets.
While we’re focused on remediation, users without a personal gateway can take over the dataset to make the required changes to the dataset settings page.
Current status: We're finalizing the internal testing for our fix to ensure that its deployment successfully remediates impact. We're expecting internal testing to complete by our next scheduled update, when we're also anticipating the ability to provide an estimated fix deployment timeline for impact resolution.
Scope of impact: Your organization is affected by this event, and this impacts any user who has a personal gateway and tries to access the dataset settings page for a dataset that has an on-premises customer connector data source.
Root cause: A code regression within a data movement update is resulting in the impact.
Workaround that can be tried for non-personal gateway users :
1. If the dataset owner has a personal gateway (but may not be using it), and is using enterprise gateway to refresh the dataset they may run in to this issue, they can ask any other user with permission to data source and no personal gateway created with his account, take over the dataset and try refreshing it.
2. If the personal gateway is present (not being used)and is not critical, then the user can try deleting his personal gateway and try refreshing the dataset.Here is the information on the PBI service status screen:
Power BI customers using on-premises gateway (personal mode) with a custom connector data source attempting to perform on-demand refresh or access Gateway connection from Data settings page may see the error message, "Something went wrong ..Failed to load data sources". Engineers have identified the root cause and a fix is expected to be deployed by end-of-day 08/06/2022.For anyone else affected, this seems to affect enterprise gateways as well. I am uncertain why someone said it is specific to personal mode gateways. Probably just because it sounds better.
It wasn't clear to me how to find and delete my personal gateway. For those who aren't familiar with the new gateway management U/I, remember to look for a drop-down filter in the least obvious place you might look for that: