Power BI Report Server October 2020 update has been released.

upgraded to latest version. scheduled refresh still not working. report refreshing ok until saving report with enhanced metadata turned on.

Scheduled refresh breaks when scheduling:

SessionID: 65497027-7267-4f16-8ef4-2fb3206e3e0a
[0] -1056505856: COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, No credentials were found for the datasource.
[1] -1055784828: The database operation was cancelled because of an earlier failure.

credentials are tested and correct.

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. 

Upgraded Power BI Report Server and confirmed Version: 1.9.7627.11028  is now installed.

Chose Manage for an existing report then confirmed Data Sources credentials are correct and connection tested successfully. Attempted a Refresh Now and received this error:

SessionID: 6bbca19a-154f-4758-bb4c-a62cbbe06ae3
[0] -1056505856: COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, No credentials were found for the datasource.
[1] -1056505856: COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, No credentials were found for the datasource.
[2] -1055784828: The database operation was cancelled because of an earlier failure.

Installed Microsoft Power BI Desktop (October 2020) (x64) version 2.86.1321.0.  Chose Edit in Power BI Desktop and Refreshed All.  Confirmed data refreshed, saved, and closed.  Succesfully tested credentials again, and attempted to Refresh Now, only to receive similar error.  Tested reports with Teradata data sources then tested with Vertica sources using direct connection and ODBC.  All fail with error regarding "No credentials were found for the datasource."

Still have hundreds of unhappy users with non-working reports in a corporate environment.

Before you connect to PBIRS  they will be hidden, but show up when you connect to the instance. Perhaps this is what you saw.

Hello,

October 2020 latest update version still has got some problems. When You're planning to release new version of October update.

Power BI Reporting Server & Dekstop versions : 

I can successfully refresh data from power bi dekstop, but when it comes to scheduled refresh from power bi report server it starts to show below error. On the other hand, simple sample report with only one dataset from mssql working properly with preview feature disabled. But complex models with multiple dataset from mssql and enter data funcion from power bi is not working it gives below error. Previous version May 2020 was working properly with no problem. 

Datasources : MSSQL 2017 Enterprise, Enter Data option in power bi 

And also mobile reporting starts to show nothing for this situation reports. But we can open report from web.

Please help ! 

Hi again,
I reverted back on Power BI Desktop version, re-installing May 2020 version on my laptop.
When opening a report saved with this version and pushing it to the Report Server in October 2020 version, it seems that the data refresh scheduling is working.
I wondering if the troubles we are having with the data refresh scheduling with October 2020 Desktop version are not due to the new preview functionnality "Store datasets using enhanced metadata format".
If it's possible for you, Microsoft guys, could you please make a version of Power BI Desktop October 2020 without this preview functionnality, and with the previous mode of DataSets storage which is implemented into May 2020 version of Power BI Desktop?

Best regards,

BenT

I have a similar experience which might help Microsoft to identify and resolve the issue.

I upgraded our DEV server to the latest October 2020 version (Version 1.9.7627.11028).

After the upgrade, a scheduled refresh for a Power BI report using a Web connection retrieving data from the ServiceNow API started to fail with the following error:
"Errors":[{"ErrorCode":-1055784932,"Message":"Credentials are required to connect to the Web source. (Source at https://*******.service-now.com/api/now/table/incident.). The exception was raised by the IDbCommand interface.","CallStack":null}

The stored Connection string in PBIRS is the following:
https://*******.service-now.com/api/now/table/incident

I opened the report in Power BI Desktop Version: 2.81.5831.1181 64-bit (May 2020) and saved it. Then I saw that the Connection string in PBIRS got updated to the following:
https://*******.service-now.com/api/now/table/incident?sysparm_query=priority%3D1%5EORpriority%3D2%5Esys_created_on%3E%3Djavascript%3Ags.dateGenerate('2020-01-01'%2C'00%3A00%3A00')&sysparm_display_value=true&sysparm_exclude_reference_link=true&sysparm_fields=number%2Cpriority%2Cincident_state%2Ccategory%2Cshort_description%2Cservice_offering%2Cassignment_group%2Cproblem_id%2Cassigned_to%2Csys_updated_on%2Crfc%2Ccaller_id%2Cclosed_at%2Ccompany%2Csla_due%2Cseverity%2Csys_created_on%2Cstate%2Copened_at%2Curgency%2Ccmdb_ci%2Cresolved_at%2Cu_external_parent_ticket%2Cu_external_problem_ticket%2Cu_external_reference%2Cu_external_ticket

And this made the refresh to start working again. (However, I would say the Connection string should obviously not contain the full API call...)

To confirm that the issue is coming with the new PBIRS version I saved the report to our TEST server, which is still on Version 1.8.7485.35104 (May 2020). Here the Connection string is saved as it was before, that is:
https://ferring.service-now.com/api/now/table/incident

And the refresh also works without any issues on this version.

I really hope Microsoft is able to resolve the issue with the October 2020 version as soon as possible, as the users are screaming for the new features that comes with it.

However, I would never dream of upgrading our PROD server with this release - just imagine having to manually open each report and save it again in order to fix the scheduled refreshes gives my nightmares!

Regards,

Thomas

Hi,

I can confirm that the issue still exists where the sources are folder types. 

Regards,

Modasher.

My mistake I thought it did. I sent you a PM. It's possible the credentials weren't saved after you tested the connection. Reenter the credentials, click save, then click test connection to ensure they are working.

I rolledback the version of PBIRS for May 2020 and now it's ok!
I will wait a while longer to update again.

But, ansewering your questions:
1) A few
2) Web and SQL servers
3) Not at all. The web content is to get a Json from a website. The others are SQL Server tables.
4) Yes.