After instalation of PBI Desktop update (March) I am not ableto open any PBI file (even new blank one). I tried to repair PBI desktop via Control PAnel, reinstall back to rpevious verison, change x64 bit to x32 bit version, but nothing worked.
Error messages varies based on PBI file that i am trying to open, below is one of the error logs that PBI shown me after PBI failed. Sometimes is error message only announcement that PBIDesktop is not able to load data modle and nothing else (what is kinda strange when this error message appear during opening of blank PBI file...
2.56.5023.942 (PBIDesktop) (x64)
Couldn't load the model schema.
Microsoft Windows NT 10.0.16299.0 (x64 en-US)
4.7 or later [Release Number = 461308]
Peak Virtual Memory:
Peak Working Set:
Workbook Package Info:
1* - en-US, Query Groups: 5, fastCombine: Enabled, runBackgroundAnalysis: True.
Model Default Mode:
Snapshot Trace Logs:
C:\Users\v-pavsch\AppData\Local\Microsoft\Power BI Desktop\FrownSnapShot360440546.zip
Performance Trace Logs:
C:\Users\v-pavsch\AppData\Local\Microsoft\Power BI Desktop\PerformanceTraces.zip
Disabled Preview Features:
Disabled DirectQuery Options:
Lately while I was maintaining the published reports from the Power BI desktop; noticed that after save, when I clicked on the Publish button, it calls the sqldmper.exe (the command window) and crashes; sometimes hanged and had to kill the task.
Then I noticed PBD keeps logging me out during publish, calls that sqldmper.exe and after crash, have to relogin and publish till now.
I believe there's a bug in latest update; I am running the january 2018 update.
Is anyone else facing the same issue?
I've been using Power BI desktop for visulaization of data in scatter plot. the problem is, the data I have is in million and billions of entries. so while visualizing it over the scatter plot, the bubbles of scatter plot often overlaps because of thier size even when the size is set to 0. is there any way to squeeze the size of the bubble more even it looks like a simple dot. so that the visualization can be a bit understandable and demonstrable? Thank you.
After I updated my Power BI Desktop to February update I noticed that everytime I refresh the datasets the sorting by column resets and goes to default. That's so disturbing that I will have to downgrade to the December update, because the January upgrade had issues in DirectQuery mode.
I've tested on two different machines and on the machine with the December version there was no such issue as reseting the column sort to default.
Seems to me there's a bug in the new January update.
I have a report using DirectQuery, and when I refresh my model it keeps saying:
"Connecting to tables from more than one database isn't supported in DirectQuery mode.".
If I rollback my installation to PBI December, the refresh works, as I don't have multiple datasources in my model.
Thanks in advance.
In Power BI Desktop Jan 2018 release, with a Date or Date/Time field selected in the Fields pane, when you navigate to the Modeling ribbon / Format / Date Time menu, the options at the top (marked with an *) that respect the machine locale now show in US format (e.g. M/d/yyyy) on machines with non-US locales e.g. English (Australia).
This appears to only be a problem in the display of the menu. When date fields are shown in a visual e.g. a Table, the expected non-US locale is used e.g. d/M/yyyy.
This issue was introduced with the Jan 2018 update to PBI Desktop.
Since the new December version has been released, I keep having crashes of Power BI over and over trying to link two tables...
As soon as I want to create the link (drag and dropping a dimiension to a table to another table) the windows terminal opens with SQLDUMPER.exe and close/crash Power BI.
I have never experienced this before the last release.
Thank you for your help
Okay, We had the issue last month with unable to join tables together.
Now after updating to the January I cannot load any DIRECT QUERY pbi files as it says it cannot connect to multiple databases when it is only connecting to one.
We are a multi million pund business and have made an investment into using PowerBI as tool. This breaking on and off all the time is not very viable. Please can this be fixed ASAP!!!!!!!!
Yesterday I installed the latest PBI Desktop update for January 2018 - the second one for January.
Now, when I Edit Queries and create a new table, then try to apply those changes, the "Apply Query Changes" step gets stuck on the "Creating connection in model" step. It never finishes.
I have reverted to the earlier (12th Jan) version and it works fine.
Has anyone else seen this?
Is the relationships display in Desktop supposed to save the current position. In other words, if I drag the hierarchy the way that I want, isn't it supposed to save it? I seem to get constant issues where I clean up the display only to come back in and it is all hosed up. Sometimes it seems to save it properly. What am I missing? I had the one below all nicely laid out and then come back in later and it is all messed up per below.
In November 2017, we created and published a data model combining Odata feeds and excel files stored on a shared drive. The different sources are merged in the query editor.
After publishing the model, we were able to select the on premise data gateway to schedule refreshes of the model.
After the latest update of the Power BI gateway (End of January 2018) the scheduled refresh stopped working and we were not able to select the gateway anymore.
When we upload a model with all the sources but without merging them, the gateway works fine.
Anyone encountering the same issue or having any feedback?
Whenever I try to add new data to the model in DirectQuery mode I receive the error stating "Sequence contains more than one element", which makes no sense and there isnt really anything online that would suggest a workaround. I assume it just means Power BI Desktop is broken.
If I rollback to previous version I have no problem. Although I have to rollback 2 versions as the January update had it's own problems with DirectQuery. I want to use functionality in February version, so quite frustrating to be uninstalling and reinstalling versions just to add data to my model.
Have sent a frown and it states that it is a known problem being worked on. Would like an update here.
While Loading data in Power BI with Vertica Direct Query mode, Power BI is not working.
We are getting "we cannot convert the value null to type table" error message.
1) Open Power BI and select option Get Data.
2) Use Vertica as Data Source.
3) While making connection select mode as "Direct Query".
4) Select option "Load Data".
Expected Result: We will get "we cannot convert the value null to type table" error message.
Actual Result: Data should get loaded..
Version having issue: 2.54 (January Release)
Version Working fine : 2.51 (October Release)
We are using directquery reporting with SQL Server and up until the January updates, everything worked fine. Now this morning the directquery is not working (filters aren't working, error saying there are multiple databases, etc.). When I switch to "import' mode, everything works fine.
Yesterday, all my datasets were refreshing just fine but today nothing happens.
- The automatic refresh hasn't done anything.
- When I press "Refresh now", I get a "popup" saying "preparing refresh" for a split second and then nothing happens.
The only way to update the data is to refresh the Desktop version and then upload it.
I have datasets connection to an on-premises database and one connecting to a sharepoint site.
- The on-premises connection usually works perfect, but now nothing happens.
- The sharepoint connection usually brings up an error, if I try to refresh, but now nothing happens (I just tried it this time as a test, as it usually doesn't work automatically).
Can you please help troublefinding - It seems like an issue on you online portal somehow.
Thanks in advance.
Bug in PowerBI Desktop Version: 2.51.4885.701 64-bit (October 2017)
When you single click a query in the "Queries" selector on the left hand side, it thinks you want to move the query up or down to re-order.
This did not happen in the previous version.