The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
I have a PowerBI report that has been refreshing successfully via scheduled refresh for several months. It's now failing with the above error code - screenshot attached. This doesn't give any usable details on what is wrong. The report refreshes succesfully with no errors locally and also if I download the PBIX and refresh, there are no problems. It's not a big report - Data sources are 3 SQL views & 1 stored procedure. Biggest table 40k rows. Any ideas on what is wrong....? Thanks
Gateway is fine and working & latest version.
Solved! Go to Solution.
Ok - So I've found and fixed my issue. One of my tables had an old calculated column that is returning an error - The calculation is not used anywhere else and is not used on the report so wasn't immediately obvious - and of course the report refreshes fine locally without returning any errors - The column just shows as an exclamation mark in the data model. By removing this, the report now refreshes successfully in the service - I can only assume that MS changed some logic in the service very recently that now means the data model refresh will fail if there are any errors anywhere - not just on visuals on the reports.
Hope this helps!
Hi,
I've cought the exactly the same problem when fetching data from SQL Server data source via data gateway (enterprise mode). The error rised on the 31st of october without evident changes in any configuration and data itself.
During investigation I tried to run a data refresh via Power BI Desktop (version as of october-2017) and it succeeded. Also I have several other datasets that read data from flat files, and the continue to work properly.
Well, I even reinstalled the latest version of On-premises data gateway (enterprise mode), but no success. Moreover, both SQL Server and data gateway are on the same host.
An Idea came to me from the https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-onprem-tshoot/ post, when referreing to TLS 1.0 desupport. So, I even added a parameter to system registry as following:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]"SchUseStrongCrypto"=dword:00000001
bu still no success. I shall post an SR for this issue today.
Hope MS helps )
Ok - So I've found and fixed my issue. One of my tables had an old calculated column that is returning an error - The calculation is not used anywhere else and is not used on the report so wasn't immediately obvious - and of course the report refreshes fine locally without returning any errors - The column just shows as an exclamation mark in the data model. By removing this, the report now refreshes successfully in the service - I can only assume that MS changed some logic in the service very recently that now means the data model refresh will fail if there are any errors anywhere - not just on visuals on the reports.
Hope this helps!
Hi @spiderrob,
Could you accept your helpful reply as solution to help others who have similar issue find the answer easily and close this thread?
Regards
Thanks spiderrob. You're a lifesaver. I had tow broken calculated columns and were causing me all the trouble.
Hi spiderrob,
Thank you for suggestion! That helped me. Indeed there was a broken calculated column not in use.
Fixed & republished & done!
Good luck!
Wow. Lifesaver! Thank you so much spiderrob. Found old calculated columns that were broken, removed them and re-published. This solved my problem! Like you said, they must have changed something, for this to suddenly start happening, and to not offer a failure reason. I am guessing this will catch a few people out. Thanks again!!
Im having the exact same problem. I downloaded the pbix file and refreshed it manually and seems to be refreshing properly. However, it throws me error when I update it through gateway. I am using SQL server connection in the dataset. other reports seems to be refrshing fine with sql source.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
53 | |
22 | |
11 | |
10 | |
9 |
User | Count |
---|---|
113 | |
33 | |
28 | |
19 | |
18 |