Forum Discussion
Error message on refresh- An unexpected error occurred (file 'tmdatasourceregistry.cpp'
hello ,
this is a known issue for which there is a Fix expediately rolling out across production instances of Power BI , with an ETA of 06/29 EOD for reaching saturation , there has been CSS (customer service support awarness shared to our support teams to better assist any Customers reaching out ) and also we are continuing to post proactively Tenant level (Customer level) communications for the impacted tenants we have been identifying , and basing on the IDs of error you shared , we see that Comms were posted to your Tenant admins already with regard to this issue. Please let us know .
Seems like it’s a small group affected by this problem otherwise I would have expected it to be a lot busier here. Microsoft must have a reason to postpone the fix for over a week. It would be nice to know what they are going to fix, and if there is another workaround. Can’t imagine that all other Power BI users are on premium capacity/user. What do we have in common?
- Here it’s only happening on datasets with custom connectors via a gateway.
- MySQL via the same gateway still works fine.
- OData without gateway works fine.
Not sure if this is the case for anyone else, but I was experiencing this same issue all last week - My datasets all have custom data connectors on our gateway.
as of 10 minutes ago, i was able to hit the refresh button on each of my data sets in the service and they all refreshed correctly. I've set them back up to auto-refresh and am waiting to see if they fail, but it's at least encouraging that the manual refresh of the data set on the service worked this time (something that didn't work at all last week)
