I am pleased to announce we have released an update to the Power BI Report Server (October 2020) with several fixes to problems commonly reported here on the Power BI Community Forums. The release can be found here:
Changelog will be updated tomorrow with the following information:
I have upgraded to Version: 1.9.7675.15620 (Build 15.0.1104.300), Released: January 8, 2021 and still have the same issue with reports not refreshing. So far, only reports originally created or edited with the preview feature enabled are affected.
My only workaround has been to repeat hours of work re-creating reports or re-editing recovered AppData reports again with the preview feature disabled. Simply resaving the report or making new edits to the original report won't fix this if the report was ever saved with the preview feature on. It's basically a burned file at that point.
I love PowerBI, but this release has been an epic failure wasting too much of my time.
I agree. The October version has left such an impact with the Power BI report server customers, that we have to think twice before accepting the next release. In regards to your issue, I have been doing the same thing. But for me, I copy paste the advanced editor query for each data source, make the connections and then copy paste the visuals. This has reduced quite some time on my hands from redoing everything from scratch. But then again, didn't expect to go through this trouble at all when I had updated to October version.
We are facing issues during data refesh for the Data Source "Xtract Universal", which is extracting data from SAP to any destination (PBI / SQL).
Please find the below System configuration :
Power BI Server Product version : 15.0.1104.264
Power BI Desktop (RS) - 2.86.1321.0 (20.10) (x64)
OS Version: Microsoft Windows NT 10.0.14393.0 (x64 en-US)
CLR Version: 4.7 or later [Release Number = 528049]
IE Version: 11.3986.14393.0
Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 Copyright (C) 2019 Microsoft Corporation Enterprise Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
There are some Questions you have asked and i am providing the answer
1.Are you having issues with all reports or just this one? - Only One DataSource is having Issues.
2.Can you say the types of datasources found within this report? - "Xtract Universal" From Theobald-Software
3.Anything different/unique as it related to datasources connectivity in it? - Connectivity through XU Webserver.
4.I assume the refresh fails consistently as well? - Yes
Note : - Apart from Xtract Universal, the Power BI server doing well data refresh on other data sources.( SQL server)
Error Msg :
 -1056505856: COM error: mscorlib, An item with the same key has already been added..
 -1055129594: The current operation was cancelled because another operation in the transaction failed.
 -1056505856: COM error: mscorlib, An item with the same key has already been added..
We are absolutely not ignoring or taking the customer pain lightly. We are working on solutions to issues and updates to products. I would recommend you take a look at the pinned thread found here:
Thanks @Petebro - hadn't seena reply from MS users in the various original threads - glad to see this is underway elsewhere. Thanks.
I have the same issue as everyone else. Fresh install on Dev server and not able to get scheduled refreshes to work with or without Preview feature. When will this get fixed?
I am having the same issue (no cred). I've actually started writing my pbix with may 2020 version and upgraded the server (and desktop) to Oct 2020 during development so my backup copy of the pbix in the appdata folder is old and unusable. Other reports are refreshing fine.
I've tried to resave data sources as suggested in p. 4 of this thread but that did not solve my issue. I cannot refresh this new pbix with the preview feature turned on or off. I even copy and pasted the pbix elements to a new pbix file but the refresh doesn't work for that file either.
Any other solutions I've missed?
I think the question of making a preview feature enabled by default is so important that it should have its own thread:
The October updates are really a joke. 😡
Lastest Report Server and latest Desktop Applikation (Oct Release).
I have unchecked the preview feature mentoined above... edited my report, saved it, uploaded it to the report server -> its working.
Then I reopend the report from my local disk, errror while opening:
Because of n:m Relationship which is not supported -> Report has no n:m Relationships
Model with DirectyQuery AND Imported FIles whis is also not supported -> Report has only DirectQuerys
I edited the report, saved it, closed Power BI Desktop, uploaded it to Report Server and reopend the SAME file from my local disk and then boom error.
Now, the report is working in our report server but I'am unable to edit it, because I can't open it...
Iam totaly pissed, really. Its a shame, sorry.
@DenisPH Do you have any copies of the report in the backup folder here:
C:\Users\<user>\AppData\Local\Microsoft\Power BI Desktop SSRS\TempSaves\Backups
If you do, try opening that copy but make sure you have the Ehanced Metadata switch turned off before opening. Also you mention the report is working fine in the server, were you seeing issues either in Desktop or Server when the switch was turned on? You can also try reopening your existing report with Enhanced metadata turned on and I suspect it will work, however that goes to my question above on what issues were seeing before.
Do you have any copies of the report in the backup folder here
No backup available, folder is empty.
If you do, try opening that copy but make sure you have the Ehanced Metadata switch turned off before opening.
Ehanced Metadata is/was already off while opening the report.
Also you mention the report is working fine in the server, were you seeing issues either in Desktop or Server when the switch was turned on?
With Ehanced Metadata on, I was not able to open the report in the server.
You can also try reopening your existing report with Enhanced metadata turned on and I suspect it will work
With Ehanced Metadata on, I can't open the report in the desktop applikation, same error like before with Ehanced Metadata turned off.
Since I upgraded some of my reports have been wiping themselves, and it's still happening after the update. First the custom themes disappear and then the visuals themselves just totally vanish and new visuals can't be added. I also can't save reports that have the new 2.0 version of the Sharepoint online list connector.
I was given the same work-around from someone from Microsoft earlier today. I was also told this was going to be fixed during the January 2021 release.
We continue to have problems with the October 2020 release even after applying the update. We continue to get 'credentials missing' errors even though there are credentials. I've created a support ticket, but that hasn't helped yet. Is another patch being worked on?
I managed to fix this. I tried a fresh install on my own PC and everything worked fine, which led me to think that something was messed up with the update process. I then turned off the Power BI service on the server, renamed C:/Program Files/Microsoft Power BI Report Server, and ran the installer again with the "Repair" option. Once it was done, I copied the config files from the old install folder to the new one. These files were:
C:\Program Files\Microsoft Power BI Report Server\PBIRS\Portal\RSPortal.exe.config
C:\Program Files\Microsoft Power BI Report Server\PBIRS\PowerBI\RSPowerBI.exe.config
C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\rsreportserver.config
C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\rssrvpolicy.config
C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\web.config
C:\Program Files\Microsoft Power BI Report Server\PBIRS\RSHostingService\RSHostingService.exe.config
I don't know that all these configs were necessary, but I copied them anyway just to be safe. Also, I did not try just doing a straight repair first...that might have been enough to fix it. The rename/repair/replace definitely fixed it. Now my dashboards that were broken are refreshing like they should.
My company have PowerBi Report Server working about 2 years and doing all the upgrades and never goes wrong.
This time, when upgrades to Oct 2020, after that, some reports, with google sheets, csv and excel as datasources stop schedule refresh.
Some erros comes like:
"COM error: mscorlib, An item with the same key has already been added."
"The module named 'Html' has been disabled in this context"
"COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, Datasource xxxxx is not found."
I try some workarounds, some people suggest, but didn't work for me.
Rollback to previous version is not possible, Microsoft will repair this in next version?
I have tried this but I still have the same error below:
0] -1056505856: COM error: mscorlib, An item with the same key has already been added..
In order to know the source of the problem, I have deleted all Merges in the dashboard => the Scheduled Refresh worked.
Once I do a simple merge, the Scheduled Refresh works on the desktop but not on the Server(with the same error).
I am really confused here. Could you help me, please?
Another issue with October version (18th NOV build) with enabled "Enhanced Metada format". Not critical. But we are not able save reports with "IBM Netezza" conector with error "There was an error uploading your .pbix file."
Saving to Power BI Report Server (2nd October release) from PBI Desktop RS May 2020 or from October with disabled Enhanced Metadata format, works fine.
Also all current reports (saved from PBI Desktop RS May 2020 or from October with disabled Enhanced Metadata format) works fine including scheduled refreshs.
It is definitely issues in new metadata format (I don't know if on Server or Desktop side, or both).
Why why why this first "PREVIEW", unfished and buggy feature, is in production release, set as enabled by default?????
Why was not be re-released Desktop application with by default disabled this featerure, immediately when it shown as big problem?
This is a must watch for a message from Power BI!
Click here to read more about the December 2020 Updates!
Click here to read the latest blog and learn more about contributing to the Power BI blog!
Mark your calendars and join us for our next Power BI Dev Camp!.