For the last 30 minutes it has not been possible to show reports in the service. They are just loading and never finishes. I have tried with reports from different sources, so the problem is in the Power BI Service.
Can someone fix this ASAP? I'm based in northern europe.
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.
The Search Box on the Slicer Visualization seems to have a bug when a PBIX file is loaded to the Power BI Service. This issue is affecting the drop-down format of a Slicer. Also it seems to only affect Slicers with a larger amount of items. When there are 2 or 3 items in the slicer the search box will appear however if there are 20 plus or more items it is not working. I've tried several different browsers, so I don't believe that is the issue. Below are screenshot showing the search box has been enabled and the missing search box when you select the drop down. Please help!!! We're on the verge of rolling out hundreds of new Power BI accounts and this is a serious issue when you have large slicer needs.
Since the latest PBI service update the Chiclet visual is not working within published reports. The issue has been raised in the Community forum but yet to be resolved:
From initial testig this is what we have found:
- various versions of the visual work within PBI Desktop (also variety of versions) but whenever published doesn't work as it should
- when published online the visual doesn't refresh the other affected visuals (instead it either does nothing, displays the wrong information, or requires a different visual to be clicked before it is refreshed)
- only under one circumstance were we able to get it published correctly (that was to an account we created years ago in O365 - all other accounts, including new accounts created in O365 today, fail to load the visual properly)
- the visual works fine within the Windows 10 PBI App
- the issue (that we have kown about) has been ongoing for the past few days - corresponding with the latets PBI Service update
Any help would be much appreciated as we have over 50+ reports using this visual and it's quite an embarassing to have to explain to users/customers we're not sure why or when the issue can be fixed.
I'm getting this error since yesterday on a new dataset. It is a simple excel file table. I've done the following.
Signed out of Power BI Desktop and back in
Got the latest personal gateway
turned the gateway service off / on
republished multiple times during this process.
Others seem to be having the same issue. see thread here
There is a current support site error message, but it is specific to SharePoint as a data source only.
When I try to update a content pack, (in app.powerbi.com, cog -> View Content Pack -> Edit (an existing content pack) -> click UPDATE button), I see an error message that begins "The following groups have failed validation..." This happens with all of my content packs, even when there are only 5 members of the workspace that the content pack is publishing to, and all members are definitely still current staff members. Any ideas?
I though this was fixed in the last release and seemed to stopped happening after I downloaded the newest version. Now it is back and is a complete pain to deal with. Please fix this issue.
We can no longer share a dashboard with users from our own workspace. I received the message:
"This dashboard contains Power BI Pro content. Only users that have Power BI Pro will have access to it"
I confirmed my fears by publishing the simplest of reports which is 100% non-pro content. There have been a few other mentions of it on the forum in the past couple of hours, but I thought I'd create an official post.
1st sharing was disabled from Group Workspaces to non-pro users. Surely Microsoft has accidentally disabled ALL sharing for non-pro users ? If not, you can imagine the uproar.
Is anybody else facing the same problem ?
Power BI clearly states that we are able to share personal dashboards with non-pro users.
Since yesterday I'm having an issue connecting to an excel file in a Sharepoint folder. It was already working, but I made some changes and republished it. Refresh works fine in Power BI Desktop, but online. It seem it's trying to connect to a Sharepoint list, instead of folder. I have an other report connecting to an other excel file in the same folder and it works fine. Could this be connected to the issue in North Europe? I'm in that datacenter.
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.
In the new January, 2017 release, I get a "Report has already been published" error message when I try to use the PUBLISH option to Update a report that exists on the Service from Desktop.
--I updated a report in Desktop that had been previously published to the Service.
--I selected the PUBLISH menu option in Desktop
--I selected MY WORKSPACE (where the report was located)
--I received an error "Report has already been published" and the update failed.
I've tried with several different reports both with the Service running and with the Service not running. I've also exited Desktop and restarted it and repeated the operation. In all cases, I got the same error.
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.
There's a bug in "Don't include in report refresh" like described here: http://community.powerbi.com/t5/Desktop/Disabling-quot-Include-in-Report-Refresh-quot-works/m-p/1017...
unfortunately I didn't test correctly and this thread is closed, but the bug is still there and preventing solutions for problems like this:
If the query that shall not be refreshed is not referenced by any other query or part of a UNION-operation in DAX, then everything works fine, but if it is referenced as mentioned, then it will be loaded again.
A lot of the usecases for this features are of this kind, so this bugfix is really needed !!!
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
I want to use the Selection pane to manage my visuals on a page. However, I use a lot of visuals (especially text boxes), and some of them at the bottom are not accessible via the Selection pane as there is no way to scroll down.
Can you please fix this?
I am having issues installing the Power BI Gateway (powerbigatewayinstaller.exe). It seems the installer doesn't initiate/run.
I think there might be an issue with the application itself, since I am having the same issues on three different computers.
I have tried:
- Run as administrator
- Start the installer from Run
- Check the Task Manager if the process is actually running, with no trace of the gateway.
So I figured I check the Event viewer, and found a .net runtime error with event id 1026. There's also an application error, but I presume this is down to the .net runtime error. The information from the event viewer is as follows:
Tillämpningsprogram: PowerBIGatewayInstaller.exe Framework-version: v4.0.30319 Beskrivning: Processen avslutades på grund av ett ohanterat undantag. Undantagsinformation: System.IO.FileNotFoundException vid Microsoft.DataProxy.PowerBIInstallDownloader.LandingPageViewModel..ctor(Microsoft.DataProxy.PowerBIInstallDownloader.MainViewModel) vid Microsoft.DataProxy.PowerBIInstallDownloader.MainViewModel..ctor() vid Microsoft.DataProxy.PowerBIInstallDownloader.MainWindow..ctor() Undantagsinformation: System.Windows.Markup.XamlParseException vid System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri) vid System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri) vid System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri) vid System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean) vid System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext) vid System.Windows.Application.DoStartup() vid System.Windows.Application.<.ctor>b__1_0(System.Object) vid System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) vid System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) vid System.Windows.Threading.DispatcherOperation.InvokeImpl() vid System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) vid System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) vid System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) vid MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) vid System.Windows.Threading.DispatcherOperation.Invoke() vid System.Windows.Threading.Dispatcher.ProcessQueue() vid System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) vid MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) vid MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) vid System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) vid System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) vid System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) vid MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) vid MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) vid System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) vid System.Windows.Application.RunDispatcher(System.Object) vid System.Windows.Application.RunInternal(System.Windows.Window) vid Microsoft.DataProxy.PowerBIInstallDownloader.App.Main()