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'm Experiencing translation problems in PowerBI when uploading my Tabular model from SSAS v. 10.0.1.439 (compatability level 1400)
I have downloaded the latest On-premises data gateway version number: 14.16.6650.1 and it works fine.
In app.powerbi.com I have changed the settings to the same local language as have been made in the tabular model, but it doesn't translate the table names and table columns.
It does however translate the folders and the measures. Is there a setting that I'm missing. On other sql setups, there is no problem with the translation it works fine, however it is not SSAS 2017 and it is with an older version of the on-premises data gateway.
As mentioned in these threads:
PowerBI has a bug since the March release when it comes to reading files from Sharepoint and using the date fields provided by Sharepoint. This not only affects the desktop but also the service.
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.
I have two identical datasets uploaded to powerbi.com. One of them I updated today and while trying to schedule refresh I get an error:
" You can't schedule refresh for this dataset because one or more sources currently don't support refresh."
(PS: It was working perfectly fine for a month+)!!!
I haven't touched the other dataset and it is still working well.
I know where the issue is -> I'm using parameters for my SQL Stored Procedure.
But its extremely annoying. Please let us know if this is a bug or will be a real thing?
This is from my Power Query editor
// Check ExcludeMMFId PQ Parameter
if ExcludeMMFId = "'N/A'"
else ",@ExcludeMMFIdExternalFilter = @ExcludeMMFIdExternalFilter"
// Query based on ExcludeMMFId Parameter
DECLARE @UserID VARCHAR(255);
DECLARE @ExcludeMMFIdExternalFilter VARCHAR(4000);
SET @ExcludeMMFIdExternalFilter = " & ExcludeMMFId & "
SET @UserID = " & UserID & "
@UserID = @UserID " & ExcludeMMFIdParm & "
// Get data
Source = Sql.Database(SQLServerName, SQLDatabase, [Query= dbQuery]),
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.
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
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.
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!!!!!!!!
The formatting of datetime in Power BI doesn't work if you only use mm:ss. Power BI will format the value as if it was MM:ss displaying Month then seconds. If I use an hour indicator, then Power BI will recongnize the lowercase mm as minutes.
MyMeasure:=TIME(0, 0, 195.6)
Has a value of "12/30/1899 12:03:16 AM"
Has a displayed value of 12:16 which is actually December and 16 seconds. If I used mmm:ss, I get Dec:16.
Has a displayed value of 00:03:16, but this is actually wrong because my hh indicates a 12-hour clock and should read 12:03:16. For some reason it treats the hh as HH.
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.
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.
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?
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.
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 trying to use Power BI to pull data from SAP BW leveraging both BEx queries and cube connections. With each scenario we are running into different issues and were trying to figure out if this is a Power BI Limitation/Issue with 1. Connecting to a Warehouse 2. They way that Power BI is communicating with SAP BW to pull its data or is this a SAP BW Limitation/Issue based on how SAP BW servers up data.
Tested With Cube:
0FIGL_C10 -General Ledger (New) Transaction Figures
Data Load is very slow
Adding new columns and refreshing data seems to take a very long time. I don't know if this is a sap warehouse issue, an OLAP issue, or a power bi Issue. I had our basis team monitor our BW environment when connecting to a cube where I selected all the columns. The cube contains 349,628 records which is based on generating the SQL Statement from the cube (In SAP BW RSA1) and executing that in SQL Server Management Studio. This call eventually failed with the following ‘RFC_ABAP_RUNTIME_FAILURE: TSV_TNEW_PAGE_ALLOC_FAILED which I was told was due to running out of memory. Prior to testing this I had Basis increase our memory footprint on the server in an attempt to rule out memory issues.
Column limitation (selecting to many columns) or possibly and combination of Columns + Rows
When I connect to a cube and select 1-4 fields everything is pretty responsive. But as you start adding more and more fields the performance starts to suffer. In testing it looks like we can add 12 fields without any issue (Super Slow Refresh Times) but once we hit the 13th field we get an RFC_ABAP_RUNTIME_FAILURE – TIME_OUT.
I don’t write a lot of MDX statements so my statement could be the cause of the issue but I run into the same issues remain. Which makes sense because I believe Power BI is connecting to SAP BW through the BW Open Analysis Interface OLBAP BAPIs regarless of if you going againt a Cube, BEx Query, or MDX.
Select NON EMPTY [Measures].MEMBERS ON COLUMNS, NON EMPTY [0FISCYEAR].Members * [0CO_AREA].Members * [0COMP_CODE].[LEVEL01].Members PROPERTIES [0COMP_CODE].[20COMP_CODE] on rows from [$0FIGL_C10] WHERE ([0COMP_CODE]., [0FISCYEAR].[K12016])
Select NON EMPTY [Measures].MEMBERS ON COLUMNS, NON EMPTY [0FISCYEAR].Members * [0CO_AREA].Members * [0COSTCENTER].Members * [0CHRT_ACCTS].Members * [0CO_AREA].Members * [0CURTYPE].Members * [0FUNC_AREA].Members * [0GL_ACCOUNT].Members * [0PROFIT_CTR].Members * [0SEGMENT].Members * [0VALUATION].Members * [0VERSION].Members * [0FISCPER].Members * [0FISCPER3].Members * [0FISCVARNT].Members * [0FISCYEAR].Members * [0COMP_CODE].[LEVEL01].Members PROPERTIES [0COMP_CODE].[20COMP_CODE] on rows from [$0FIGL_C10] WHERE ([0COMP_CODE]., [0FISCYEAR].[K12016])
Key and Text Values
The last think I want to touch on is the key values. Power BI does not appear to give you the ability to select or toggle between the text and key values. Though MDX I was able to include the properties section and include the key value (Which was nice) but this should be standard functionality.
I wanted to try and cover all my bases and rule out as much as I could to try and pin point the issue. As such I used Tableau to connect to the same structure as it’s my understanding that it also utilizing the BW Open Analysis Interface OLBAP BAPIs to query SAP BW. I’ll point out that I don’t really use Tableau but it was a tool that was available to use a test. Once again I had Basis monitor the SAP Environment to help track down any issues. Within seconds tableau had pulled in the Metadata and I was able to create a sheet. Tableau appears to provide a live query connection to the cube whereas Power BI appears to try and load the data first which may also be contributing to the performance issues. Again I just wanted to test with another tool to try and rule out the SAP environment.
With SAP being our ERP system we need the ability to effectively be able to query our data warehouse and provide the user community with self-service reporting/analytics. With the issues listed above its making this a very difficult process to move forward with. Any ideas or suggestions would be greatly appreciated. We love Power BI and the users who have seen our demos love what it can do and I feel like we are always installing this on someone’s machine.
I have a client who is on the latest release of Power Bi Desktop (v 2.46.4732.721), although this issue also occurs on the previous version (2.46.4732.581). When they create a new measure on top of a live tabular model connection and set the formatting, the formatting only persists for that Power BI Desktop session. When they save the file and close and reopen, the formatting reverts back to the default, which is especially unreadable for percentages and currency. Is this fixable? Thanks!