Forum Discussion
Power BI Report Server September 2022 Issues
Hello everyone,
I want to ask, who you are using September 2022 release of Report Server in a test or production environment, if you register any problems or other unexpected behavior, please list them here.
I think it would be helpful to share all known issues in one place.
Thank you very much.
46 Replies
I've also seen a number of people reporting issues with custom visual not loading
Error in visualization of custom visuals. - Microsoft Power BI Community
Custom visuals not rendering after upgrade to Sept... - Microsoft Power BI Community
Petebro - are either this custom visual issue or the data refresh problem known issues that you are tracking?
Hi Josef,
another problem seems to be the deployment of (any?) Custom Visuals.
I tested with Charticulator and WordCloud custom visuals. When I upload to PBI Service (Cloud) any
of my reports work. When I upload (via PBI Desktop Sep.2022 or direct upload) exactly the same report .pbix to my local PBI Report Server (Sep. 2022), I get following error when running the report page with the visuals in browser:
"Can't display this visual, add it to this report first: <custom visual name> ... "
Any workarounds available, yet?
Kind Regards,
Peter
Hi Petebro ,
Please can you help? There are some new issues in latest release of PBIRS, especially first three. Is possible check with product team is these issues are identified and if there is any progress or ETA?1) ODBC connector failing if data source contains text column with text length greater then 512 characters (with Error: ODBC: SUCCESS_WITH_INFO [01004].
2) Custom visuals not working in new reports when saved from Power BI Desktop September 2022
3) Paginated reports subscriptions schedule based on Day (with specified weekdays), Week or Month period, is not able to create or edit.
4) Little performance drop after upgrade to September 2022
5) Some UX issues with data slicer visual.
Hi josef78,
I am pleased to bring good news today. We investigated all of the listed issues, please see details below.
1) ODBC connector failing if data source contains text column with text length greater then 512 characters (with Error: ODBC: SUCCESS_WITH_INFO [01004])
The issue was fixed and the fix will be included in the planned QFE release for PBIRS September. ETA for the release is in December, before Christmas holidays.
Workaround: to refresh data through PBI Desktop for RS (I understand it is not a good workaround for cases when you have many reports, or need to refresh often, but it is the way that can help to refresh)
2) Custom visuals not working in new reports when saved from Power BI Desktop September 2022
This issue was fixed as well and fix is coming in QFE. There is a workaround which you can use until the fix is released:
Add a URL parameter to the URL: ?consumePublicCvsWithoutRps=1, and visuals will start working
for example: http://servername/Reports/powerbi/reportname?consumePublicCvsWithoutRps=1
3) Not able to save paginated reports subscriptions schedule based on weekdays
The issue is fixed and fix is coming in the QFE
Workaround: use shared schedules
4) Little performance drop after upgrade to September 2022
We investigated this complaint and tried to reproduce it, but we didn't observe the performance drop. We'll keep an eye on this one.
5) UX issues with data slicer visual
The issue was identified, and now it's being worked on. Unfortunately, fix for this one will not be included in the coming QFE, but we will aim to fix in for January 2023 release.
Thanks,
Alexandra
Hey Alexandra,
I can see there is a January 2023 version of PBIRS, is this officially out including all the fixes??
After upgrading to the September 2022 version, many datasource refreshes started to fail, with a similar error:
"Error: ODBC: SUCCESS_WITH_INFO [01004] Fetched item was truncated." (if PostgreSQL ODBC source)
or "Error: ODBC: SUCCESS_WITH_INFO [01004] String data, right truncated." (if Netezza ODBC source).
Before the upgrade, these refreshes were running fine. I'm still looking for the cause. Does anyone have similar problems?We have the same problem after upgrading to September 2022 version.
The same error message, we are using PostreSQL and Exasol ODBC sourceyes, I met the same problem yesterday, this is a new published report in PBI Report server and there is no issues when refreshed in PBI desktop.
More and more developers from my company reported this issue in Sep22 release.
It's looks like bug.
In case when ODBC connection returning status "SUCCESS_WITH_INFO", which means successful finish with some warning message, then Power BI Report Server wrongly interpret this as failure (from Power BI Desktop it is interpreted well).
Yes, we encountered the same problem. We are using Denodo ODBC data source.
Anyone has a solution?
I just upgraded our environment to September 2022 and the date slicers have changed to where you can no longer type the date. You have to first right-click, highlight the whole date, and then it seems like you can type. Is anyone else experiencing this?
Same issue here
Hi There,
I am having the same issue; the visual does not get a SetFocus; you can either do what you mentioned in your post or pick a date from the calendar to force Power BI to "activate" or SetFocus on the visual.
I opened the report using the Power BI desktop (RS) September 2022 version to check if the visual exhibited the same behavior in design mode, and it does.
Previously, if I remember correctly, a user just had to click in the slicer field and type the date. Now it seems even using your process it places the cursor on the end of the date and you have to remove it. If you attempt to backspace to remove all of the characters, when you get to the last character it seems to remove the SetFocus and re-enter the default value. The only way I can get the value to remove is by highlighting the whole thing and hitting delete or backspace.
Hi Gemw87
We don't observe such consumption changes in any of our test machines, are you sure it's the Report Server process that is taking more now?
Also, do you see it with just one machine or more than one? and could you please specify any computer specifications with which you see it?
Thank you
hello Josef,
Here we we meet a issue after upgrated to Sep 2022 version.
When we edit data in power query, we found that the SQL query scripts would be boxed in Value.NativeQuery automatically, and then we could not click the step option on the right to edit the SQLI'm not able to reproduce this issue. For my sources edit sql button works fine. Is it related to some specific data source type (SAP HANA)?
Hello,
I was trying to update a Daily Data-Driven subscription and when I click Apply, I got the error message:
An error has occurred.Something when wrong. Please try again later.
The error message logged on RSPortal file shows the following
WARN|65|BadRequest, Errors: An unexpected instance annotation name 'DaysOfWeek.Sunday' was found when reading from the JSON reader, In OData, Instance annotation name must start with @.| RequestID = s_5b8b8f1f-4f52-4a36-ae9c-037bc450428bI did not have this issue before upgrading to the September 2022 version.
Any help is greatly appreciated.
Thanks!
The following forum discussion helped me with the same issue:
Solved: Problem altering a subscription / JSON reader erro... - Microsoft Power BI Community
Hi,
I implemented a Subscription Schedule for the report I was having the issue with, as suggested in the link, and it worked.
It was the only report we had running under its schedule. It is a good practice to run the reports under a subscription schedule.
Thanks!
Hello, I have same issue in this release.
It's relevant for paginated reports subscriptions, with subscription schedule based on Day (with specified weekdays), Week or Month period.
Another (minor) issue, after upgrade to Sep22, end-users report me little slower response.
After investigating logs (executionlog3) on two weeks of production usage data after upgrade, there visible significant change, especially on QueryData execution time (ms between TimeStart and TimeEnd), which is slower.
On my environment, during two weeks before upgrade (on May version) average query execution time is 720ms (on 87k queries daily average).
After upgrade on Sep22, during two week, I have average query execution time 890ms (on 76k queries daily average). It's mean, on my production environment, after upgrade, query execution time is about 24% slower (on little smaller load).
Is there anyone else who see any performance change?
Hi there, some feedback came into our notice that we think 2 of them are critial:
- Folders not accessible which have legacy type report ".rsmobile" in them, but turns good when we restore the previous version(May.2022) and reomove the ".rsmobile" reports then upgrade to version(Sep.2022);
- Some users are not able to access the report portal while it tells "An error occurred when invoking the authorization extension." only on the new version(Sep.2022), but they're all good to access the previous version(May.2022) in our another environment restored; (with AD authentication)
I believe on number 1) Mobile reports functionality was discontinued. It was listed in the Deprecated features:
