Forum Discussion
Refresh failure in the Service. No problems in Desktop...
Hello everyone,
Recently one of my report refresh jobs started to fail in Power BI Service. Error message below:
There was an error when processing the data in the dataset.
Please try again later or contact support. If you contact support, please provide these details.
- MessageMicrosoft SQL: Invalid column name 't0_0'. ORDER BY items must appear in the select list if SELECT DISTINCT is specified. Table: EDITracking_NoResponseDetail.
- Cluster URIWABI-US-EAST-A-PRIMARY-redirect.analysis.windows.net
- Activity ID4585ac80-df28-4c77-8119-4eeb1c6c5dab
- Request ID00ef4d5f-3dce-c7c8-22bf-1de85f1fb099
- Time2019-12-18 13:53:17Z
The name of the table that it throws the error on seems to be mostly random as it changes when I run the job again. There is no column in the entire database with that name, and nothing with that name was added inside of the .pbix
I opened the .pbix and tested the refresh, where it works fine. I can republish with no errors, but as soon as I refresh in the service, it fails again. I searched around and found others with a similar issue that was related to dates, so I double checked that all dates are in a valid format.
From what I can tell, the error is referencing a SQL query that I don't have access to view/edit. Does anyone have additional ideas on how to troubleshoot this?
Thank you!
- Anonymous6 years ago
Thank you for trying to help me think through it. We finally resolved the error by removing some sorts in Power Query in the pbix. They had been there for months without issue but for some reason the job that processes the queries inside the Service suddenly had a problem with them. Fortunately they were not really neccessary and it wasn't a problem to remove them. This immediately resolved the error.
6 Replies
- GilbertQSuper UserHi there
Would it be possible to make sure that you have got the latest version of the Gateway installed?- AnonymousNot applicable
Hey GilbertQ ,
In this case, the dataset is a SQL database in Azure, so there is no Gateway being used. Perhaps that has something to do with the issue? However we have many other reports configured in the same manner and this is the first time a problem like this has occured.
- GilbertQSuper UserHi there
Could it be that something has changed in the underlying database?
What happens if you try and refresh in Power BI Desktop?