Forum Discussion
Scheduled Refresh failing immediately with COM error: "not found"
Hi all,
We've started testing Power BI Report Server recently and are trying to configure automated refreshes. Our report is currently hosted on powerbi.microsoft.com and automated refreshes work without issues. Unfortunately, when trying to configure refreshes with the same credentials we receive the following error:
[0] -1056505856: COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, Datasource {"protocol":"tds","address":{"server":"xxx.database.windows.net","database":"xxx"},"authentication":null,"query":"IF OBJECT_ID(\u0027tempdb..#xxx\u0027) IS NOT NULL\n\tdrop table #xxx\n\nIF OBJECT_ID(\u0027tempdb..#last_info_date\u0027) IS NOT NULL\n\tdrop table #last_info_date\n\nSELECT xxx[long SQL query]} is not found..
Does anyone have any experience with this error? I am not sure why this seems to be happening.
Just wanted to provide an update to this thread, we released a new build of Power BI Report Server yesterday which fixed the issues described in here. In case you still experience problems after the upgrade, I suggest to open a separate thread specific for that issue so we can better track. Feel free to tag me directly in those as well.
You can find more details about the update in this thread:
39 Replies
Hi,
I'm having the same issue. Couple days ago i wrote Usage Statistic Report for Report Server (i was using PB Desktop May Release) and everything used to work fine (visualizations, model and automatic refresh). After upgrading PB Server to October Release automatic refresh isn't working any more. On the refresh pane there is a message: Several errors occured during data refresh. Please try again later or contact your administrator. , in details you can find this explanation:
SessionID: 5626e868-608c-4d52-94c6-610b4a08c942 [0] -1056505856: COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, Datasource {"protocol":"tds","address":{"server":"mdmdev","database":"ReportServer"},"authentication":null,"query":"SELECT \n\t\t[Path]\n ,[Name]\n \n ,[Type]\n ,U.UserName [CreatedBy]\n ,[CreationDate]\n ,U2.UserName [ModyfiedBy]\n\t ,C.[ModifiedDate]\n ,[ContentSize]\n\t FROM [ReportServer].[dbo].[Catalog] C\n LEFT JOIN dbo.Users U on C.[CreatedByID] = U.UserID\n LEFT JOIN dbo.Users U2 on C.[ModifiedByID] = U2.UserID\n WHERE Type =13\n"} is not found.. [1] -1055784828: The database operation was cancelled because of an earlier failure.I can share either pbit file or log file or both. I also install clean version of PBi Server on separate machine and automatic refresh is still not working there. I'm able to refresh report only using PB Desktop.
Best regards,
K
We getting the same error. We need a solution for this !!!
We don't have a version to restore to -- we are currently trying out Power BI Report Server, so a solution would be very welcome indeed.
Hi, same issue here as we updated our report server version from May release to October.
Looks like a general problem to me. Any bug fixes to be released soon?
Anonymous responded in another thread with a similar error. His solution worked for me. I was getting the same errors above and it seems to be a result of the Desktop October 2020 update preview feature for enhanced meta data. I was able to revert to the last version (last save from May 2020), turn off the preview feature, and save. This solved my problem and scheduled refresh is working again. The link to the other thread is here: https://community.powerbi.com/t5/Report-Server/Report-was-created-with-recent-version-of-Power-BI-Desktop-that/td-p/1466731/page/2
Thank you Mike_Mellis After restoring original files from backup and downgrading desktop to May version both problems I reported here are solved.
Great - I'm glad it was useful. One thing to note though, I believe this error is a result of the preview feature enhanced metadata in the October 2020 Desktop update. You can still use October 2020 Desktop as long as you turn off the preview feature first before saving any files.
Anonymous I feel like the General at the end of Independence Day:
"Get on the wire, tell them how to bring those sons of b##### down."
Thank you for all your help on this. I did make a series of changes on a "infected" report after the upgrade, so my pre-upgrade backup does not have these changes. Will there be a point where the enhanced metadata files are workable again or should I just bite the bullet and make the changes again on the clean version?
Hi blairblair There are two root causes we identified that seem to causing the majority of issues reported here, one of them is that reports that have one or more 'EnterData' tables are failing to refresh. The other is that reports with more than one Native queries are failing to refresh. These two issues will be fixed in the next servicing update, at that point the reports you have should start to refresh again. We will update the related threads here once the build is out. But if you are facing issues that do not seem to fall in either category then I would like to work with you and finding the root cause so we can address that as well.
Thanks
gboreki
Anonymous / YonghunLee Your files are now "infected" since you saved them prior to unchecking the metadata preview feature box. You must revert to a file that was saved with May 2020 or earlier and then as long as the metadata preview feature is not enabled it will work with October 2020 Desktop / Report Server
Thanks a lot. It's very helpful. But my files have already infected. It' so sad.
Preview option should have been defaulty unchecked when It's installed.
I had a may 2020 copy on another computer. I remote desktop to that computer, and opened a blank report. I copy and pasted the controls and the queries. I fixed the relationships and saved the file . Then I published it. I saved the file and loaded it with the oct 2020 release (with the meta data disabled) and it loaded and I have published it with no issues. Thats the best work around I've found so far and the fastest.
