topic Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser in Report Server

Report was created with recent version of Power BI Desktop that is not yet supported by this server

Mark1764 — Fri, 30 Oct 2020 22:59:38 GMT

Hi,

Recently updated to the October version of Report Server (server and client). I'm able to create new reports without an issue, including saving to the report server. I am not able to publish existing reports back to the server though. I receive the generic "an error occurred while attempting to save the report to power bi report server" from inside PowerBI, and "We're not able to upload this report. The report was created with a recent version of Power BI Desktop that is not yet supported by this server." when trying to upload the existing report from a local copy.

Confirmed both server and desktop client are the new one (client has the new logo with the RS in the corner).

Any ideas? Thanks!

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

DavisBI — Sun, 01 Nov 2020 02:26:45 GMT

Hi，@Mark1764

Please try not to upgrade the new version when it is just released because there are usually potential bugs.

You can now try to download the latest PBIRS again. Although they are all October 2020 versions, remember that their version numbers may be different, which means that new patches will be added later (without any notice).

I just upgraded PBIRS, now I can upload my PBIX file without any error.

Mark this post as solution if this helps,thanks!

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

Mark1764 — Mon, 02 Nov 2020 17:36:51 GMT

Re-downloaded both the client and the server from Microsoft's website and both are the same version I had previously. Strangely, some existing files are working, while a few are not.

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

Anonymous — Mon, 02 Nov 2020 17:43:07 GMT

As of this moment (11/2/2020) there is not updated version for the October release. You can always check your changelog which is updated with latest. https://docs.microsoft.com/en-us/power-bi/report-server/changelog

@Mark1764 , is there anything common to the reports that are not working? Do they continuously fail to upload? And do you know which versions of Power Bi desktop for reportserver was used for those reports?

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

cncolomer — Mon, 02 Nov 2020 21:49:15 GMT

I´m on the same situation. I can´t upload reports created on old versions on my server installed with Power Bi server October 2020.

However, if I create a new simple report with Power BI desktop server, I can upload the report.

I have the next message:

2020-11-02 21:24:06.5400|ERROR|35|Failure in reportproperties| RequestID = s_9adad0db-2809-489a-9110-4d5b45e67452 Microsoft.PowerBI.Packaging.Storage.NewerFileVersionException: '1.21' is newer than the product version.

Versión: 2.86.961.0 64-bit (octubre de 2020) (desktop server)

Versión 1.9.7604.41261 (Octubre de 2020) (Server)

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

Anonymous — Mon, 02 Nov 2020 21:49:50 GMT

Can you clarify which old version are you using? Is it powerbi desktop optimized for reportserver from may release? or something else?

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

cncolomer — Mon, 02 Nov 2020 21:56:19 GMT

My old version is May 2020 in case of server and Power BI desktop server. With these version, run without problems. Uploading reports and working with normal mode.

My problems began with upgrade to October 2020.

Operative system --> Windows server 2012

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

Anonymous — Mon, 02 Nov 2020 22:05:49 GMT

Can you please post here the details from the File/About of the powerbi desktop you are using?

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

cncolomer — Tue, 03 Nov 2020 07:00:47 GMT

Details for my power bi desktop are:

I´m using Power BI desktop optimized to report server. Versión

Versión: 2.86.961.0 64-bit (octubre de 2020)

The files are confidential on my business. What do you need I post on the reply? See details on log or pass the file .pbix?

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

Mark1764 — Tue, 03 Nov 2020 16:36:39 GMT

I'm running into another glitch, after I edited an existing report (which allowed me to save back to the report server), scheduled refresh is failing and I am receiving this error:

[0] -1056505856: COM error: System.Core, Sequence contains no elements.

This report dates back to 2017 and I have not made any structural changes to it.

Prior to the upgrade, I was on the May verson (both client and server)

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

Anonymous — Tue, 03 Nov 2020 17:32:42 GMT

@Mark1764 Can you provide some details about the report. There are many factors that impact here, what is the datasource type, credential type used. If you are ok in sharing info, exporting the datasource as a pbids file, or your report as a pbit template (which removes) the data would be helpul.

Also, can you confirm that when you manage datasources for the report, all the datasources are there, and that credentials were retained.

In the meantime, here are a couple of workarounds to unblock refreshing this file. Once you saved your report with october release it was automaticaly upgraded by desktop to the enhanced metadata format, you can find a backup copy of the pbit in your appdata folder:

C:\Users\<<username>>\AppData\Local\Microsoft\Power BI Desktop SSRS\TempSaves\Backups

You can continue using May release of desktop for reportserver which will continue saving in the older format.

You can disable enhanced metadata (Menu file/options and settings/options/preview features), note that once the report is stored in the enhanced format, the only way to store in the previous format is by recovering the backup.

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

Mark1764 — Tue, 03 Nov 2020 22:00:17 GMT

Appreciate the tip, thank you gboreki. I've isolated an error below. I can confirm it was working as scheduled refresh today (long past Oct 2020 server upgrade ), and only broke when I opened/saved the file in my client. Below is the error message I am getting. What sticks out to me is the "authentication:null", as I've re-input the username/password for the account (database/basic authentication).

Another theory I had was the "Top" part of the Sql query potential causing the break. On another report I'm seeing this issue, I removed that part, still saw the same error. I deleted the Sql Server datasource, and any references in the book to it, and still saw the error on refresh, so my theory was busted.

SessionID: 8c076143-c28a-42cd-895f-3778a6f32f3b
[0] -1056505856: COM error: System.Core, Sequence contains no elements.
[1] -1055129594: The current operation was cancelled because another operation in the transaction failed.
[2] -1056505856: COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, Datasource {"protocol":"tds","address":{"server":"SqlServerName","database":"DatabaseName"},"authentication":null,"query":"SELECT Top 50000 gl_journal_entry_detail.journal_entry_id , \n gl_journal_entry.source_document_type , \n gl_journal_entry.source_document_id , \n gl_journal_entry_detail.line_number , \n gl_journal_entry_detail.account_id , \n gl_account.description , \n gl_journal_entry_detail.amount , \n gl_journal_entry_detail.description , \n gl_journal_entry.transaction_date , \n gl_journal_entry.description , \n gl_journal_entry.edit_date_time , \n gl_journal_entry.batch_id , \n gl_journal_entry_detail.reference_number , \n gl_journal_entry.company_id , \n gl_journal_entry.edit_user_id \nFROM gl_account RIGHT OUTER JOIN gl_journal_entry_detail ON \ngl_account.account_id = gl_journal_entry_detail.account_id , \n gl_journal_entry \nWHERE ( gl_journal_entry.journal_entry_id = gl_journal_entry_detail.journal_entry_id ) AND \n ( ( gl_journal_entry.transaction_status = \u0027P\u0027 ) AND \n ( gl_journal_entry.journal_entry_type = \u0027F\u0027 ) ) \n AND (gl_journal_entry_detail.account_id LIKE \u0027%0001\u0027) \nORDER BY gl_journal_entry_detail.journal_entry_id ASC, \n gl_journal_entry_detail.line_number ASC"} is not found..

*Redacted the server/db name in orange.

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

Mark1764 — Thu, 05 Nov 2020 16:29:51 GMT

Based on advice in this post, I can confirm the issue was data I entered directly into PowerBI (Via the "Enter Data" datasource). Deleting that info and linking to excel instead allowed the scheduled refresh to work.

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

blairblair — Mon, 09 Nov 2020 17:49:35 GMT

Hey @Anonymous , having a similar issue except this workbook contains no "Enter Data" data. Just 2 SQL queries to the same datasource. I have "fixed" another report by reverting to the May 2020 version and not editing in my October 2020 Desktop client, but now I have a this report that was created in October 2020 Desktop. Do I have any other recourse except for rebuilding the whole report in May 2020? Is there going to be a fix released at some point soon? I am unfamiliar on the timing of these things, or if we'll have to stick with May 2020 until January? Thanks for your help

2020-11-09 09:35:33.0437|ERROR|42|Error Processing Data Model Refresh: SessionId: 3f9a8a0a-b12b-490c-ac4d-888a0c2d2c65, Status: Error Failed Data Refresh, Exception Microsoft.AnalysisServices.OperationException: Failed to save modifications to the server. Error returned: 'COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, Datasource {"protocol":"tds","address":{"server":"SERVER_NAME","database":"DB_NAME"},"authentication":null,"query":"SQL_QUERY"} is not found.. The database operation was cancelled because of an earlier failure. '. at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.ExecuteActionWithLogging(Action methodToExecute, String description, String localizedDescription, String messageInFailure, RefreshInfo refreshInfo, DataAccessors dataAccessors, ReportEventType operation, Boolean isDataRetrieval, Boolean showInExecutionLog, Boolean sendToTelemetry) at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.AnalysisServicesDataRefresh.RefreshData(RefreshInfo refreshInfo) at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<>c__DisplayClass34_0.<ExecuteActionWithLogging>b__0() at Microsoft.PowerBI.ReportServer.WebHost.EventHandler.DataRefreshScope.<ExecuteFuncWithLogging>d__33`1.MoveNext()

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

blairblair — Mon, 09 Nov 2020 17:51:52 GMT

I'm at a point now where errors will no longer show in the UI when I click on the favicon in the below message.

Several errors occured during data refresh. Please try again later or contact your administrator.

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

blairblair — Mon, 09 Nov 2020 18:14:46 GMT

Ok @Anonymous have some more insight. When I exclude the query that has temp tables from refresh, the refresh is successful.

To test I created a new query using a pattern that is common in many of my embedded queries

IF OBJECT_ID('tempdb..#temp_table') IS NOT NULL DROP TABLE #temp_table select 1 as [Data] into #temp_table select * from #temp_table

I also tested a similar syntax and received the error in Report Server (but not on desktop)

select 1 as [Data] into #temp_table select * from #temp_table

SessionID: b64fe505-bd01-4ba8-9be8-3f3691ddd5a4 [0] -1056505856: COM error: Microsoft.PowerBI.ReportServer.ASEngineManagedRoot, Datasource {"protocol":"tds","address":{"server":"SERVER_NAME","database":"DB_NAME"},"authentication":null,"query":"select 1 as [Data]\ninto #temp_table\nselect * from #temp_table"} is not found.. [1] -1055129594: The current operation was cancelled because another operation in the transaction failed.

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

blairblair — Mon, 09 Nov 2020 18:22:08 GMT

Calling stored procedures with temp tables inside also causes this error.

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

Anonymous — Mon, 09 Nov 2020 18:44:11 GMT

Hi Blair,

Thanks for reporting back. We have identified one case where multiple native queries against the same datasource are failing to refresh, this should be fix in our first servicing release for October 2020. From you repro, just want to confirm if you have a report with a single query using this pattern it also fails to refresh or only for reports that have multiple?

IF OBJECT_ID('tempdb..#temp_table') IS NOT NULL DROP TABLE #temp_table
select 1 as [Data]
into #temp_table
select * from #temp_table

Thanks

-gboreki

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

blairblair — Mon, 09 Nov 2020 18:56:48 GMT

Ok, @Anonymous ...Have an update. I got a complex Temp Table filled query to run, but only when it is the only SQL Query. Any workbooks with multiple SQL Queries fail with similar to above error messages.

Re: Report was created with recent version of Power BI Desktop that is not yet supported by this ser

blairblair — Mon, 09 Nov 2020 20:23:18 GMT

@Anonymous wrote:
Hi Blair,

Thanks for reporting back. We have identified one case where multiple native queries against the same datasource are failing to refresh, this should be fix in our first servicing release for October 2020. From you repro, just want to confirm if you have a report with a single query using this pattern it also fails to refresh or only for reports that have multiple?
IF OBJECT_ID('tempdb..#temp_table') IS NOT NULL DROP TABLE #temp_table
select 1 as [Data]
into #temp_table
select * from #temp_table

Thanks
-gboreki

@Anonymous - I sent my other reply before seeing this.. yes it is the "multiple query" issue.. temp table behavior is normal as long as it is the only connection to the datasource.. I have worked around this by doing the JOIN in SQL and having just one connection.

Do you have an outline on servicing releases are timed and how they are communicated to the community? Want to evaluate a near term plan and also don't want to miss out.

Thanks for your help.