New Idea

Slow DB2 refresh Power BI Desktop

Status: New
by GTech01 Frequent Visitor on ‎01-16-2019 07:43 AM

Hi,

 

Since December update we have hard time refreshing data with our DB2 database. Previously we were able to refresh around 7000 records a second, now the first 100-150 000 records are relatively OK but after that the pace drop at around 100-200 records a second.

 

Thanks

Google Analytics Connector in PowerBI Desktop

Status: New
by Andy4581 New Member on ‎11-14-2018 08:43 AM

I've recently installed November update for PowerBI Desktop and the Google Analytics connector has stopped working.

Am getting error message "Unexpected error: Collection was modified; enumeration operation may not execute."

Any advice?

All Refreshes fail without indicating reason

Status: Accepted
by sabinek Occasional Visitor on ‎12-10-2018 12:59 AM

Hello everyone,

 

I have setup four datasets with schedueled refreshes (each once a day on different times). The first few days they all work well and all of a sudden they fail without any reason:

image.png

 

Manual refreshes in the power BI portal succeed (sometimes also the schedueld refresh the next day) but then the refreshes fail again

I had a MS consultant looking at it but his advices (recreate the DB connection and reconfigure the refreshes) did not resolve the problems on a long term.

 

Here also some of the most important information about the circumstances:

Is the data source in Azure or on premises with gateway?
It is an Azure SQL database for three data sets (alwas the same db) and once an application insigts of an azure web app.
Is the problem only with one data source?
No, besides the 3 error messages for datasets based on this Azure SQL DB, the same error message occurred in parallel for a data source based on Applications Insights.
Has the problem occurred several days in a row or by chance?
The first time and also now the initial error message occurs randomly. The error repeats itself with every refresh until the Scheduled Refresh is disabled by the system. When I reactivate it, it works for some days (a week?) and then fails again.
Does the problem always occur on certain days?
As mentioned above, on each refresh, once the error occurred.
If you then restart the refresh manually, does it work?
The manual refresh works and sometimes the scheduled refresh works the next day, but then it fails again.
Here you can see the history of one dataset:
image.png
One more hint: It doesn't seem to depend on the number of refresh runs, but on the duration:
I restarted the Scheduled Refreshs for all 4 datasets on 29.11. One refresh ran twice a day and all others only once. All 4 datasets started to throw error messages on the 4.12.
 
If there is anyone who can help with that problem, I would be very glad.
 
Thanks in advance!
Status: Accepted

While I was trying to load an excel which contians 750 column but was able to load only 255. Remaining are not showing up. 

I have a matrix visual which is displaying Row subtotals and Column subtotals.

I want to change the font family and font colour. When I make my selections the changes are applied to the 'Row subtotal' header and 'Column subtotal' header but not the VALUES in the subtotals row or columns. Other formatting selections are applied to the values in the subtotals row or columns such as font size and background colour.

 

In the example below I would expect the subtotals values (circled in red) to be pink and displayed in Courier New.

Dataflow (preview) - dd.mm.yyyy becomes mm.dd.yyyy when consuming data in PBI Desktop

Status: New
by tebones Visitor ‎11-08-2018 01:02 AM - edited ‎11-08-2018 01:08 AM

Hi, I am trying dataflows for the first time. Greate feautre by the way! Here is my issue:

 

When creating an entity in dataflow all looks well:

 

image.png


Note the dateformat is dd.mm.yyyy.

 

When trying to consume the same data fra PBI Desktop the date is changed to mm.dd.yyyy and the import is not correct.

 

This is the same data in Power BI Desktop:

 

image.png

 

Note that SID 02/101 has swapped the dd with mm, and that SID 02/1015 failes because month 18 don't exists.

 

I guess this is a locale/language issue, but I cant find out where to change it.

 

Pls advice!

BR
Trond Erik Bones

After updating Desktop to Nov 2018, my existing reports with Azure Data Lake Storage connections now fail to refresh, nor can I create a new connection to my Azure Data Lake Storage account.  I have just reinstalled Oct 2018 and everything works fine.

 

After entering the URL and then my organization credentials, I receive a message saying something like "Specify How to Connect" but with no button or action available to do anything about it.  I can either close or hit "Connect" again, and re-enter an endless loop of this warning message popping up.

Status: Needs Info

It is currently not possible for me to refresh reports on the report service.

The error i'm getting is: The command has been canceled.. The exception was raised by the IDbCommand interface.

 

few info:

* This started on Saturday 1st december 2018
* Refresh works fine on desktop app

* It only affects report with incremental refresh ON
* I tried to rename the report and reupload but same error occurs
* When I disable the incremental refresh, report service works fine (but unacceptable for production)

 

Can you help. This is affecting the reports I have in prodcution and it is pretty urgent for me to fix.

 

Status: Needs Info

August release: Refresh never completes

Status: New
by xerxel Frequent Visitor on ‎08-17-2018 03:33 AM

Model works and refreshes in July release. Tried in August release on two machines and refresh never completes. Model contains links to Sharepoint online and SFDC. Sharepoint data loads slowly and SFDC never completes. Model includes custom functions.

 

How can we debug the difference between August vs July of the exact same model?

 

 

I try to get my table from my dataset in Bigquery into Power BI Desktop. But unfortnately I m getting to follwing error:

 

DataSource.Error: ODBC: ERROR [HY000] [Microsoft][BigQuery] (100) Error interacting with REST API: Not found: Job first-projec:job_dm6z7i391YiYbOwjL7t-ydZ4V26dd6dfnv8
Details:
DataSourceKind=GoogleBigQuery
DataSourcePath=GoogleBigQuery
OdbcErrors=Table

 

I tried the following to lose this error:

- Changing this line in the M source code:

Quelle = GoogleBigQuery.Database(null)

to:

Quelle = GoogleBigQuery.Database([BillingProject="Billing-Project-Id"]) 

- I used the Simba ODBC driver as described here : Simba-BigQuery-ODBC-Driver-Quickstart2.pdf

 

Is this still a bug in Power BI?

 

P.S: my dataset and google cloud storage are in the same region, europ-west2

 

 

Fix the "Data Loading" / "Almost Done" issue

Status: New
by SMHolck Frequent Visitor on ‎10-02-2018 02:56 PM

Multiple people in my organization are unable to view published apps in our Power BI tenant.  They can sometimes click Apps and then wait for it to load forever.  You see a brief message "Data Loading" followed by "Almost Done."  And it will spin for hours.  My entire company has a Pro license.  The data loads fine in my Power BI desktop.  Issue happens on both IE 11 and Chrome 69.   Good thing I'm not currently doing my presentation on why you should use Azure!AlmostDone.png

 

I've seen this happen often and on.  You never know when it is going to happen.  My Azure admin says when he logs in to Azure portal it tells him no known outages.

 

 

Not able to open PBI file (even new blank one)

Status: New
by JorisVoorn Frequent Visitor on ‎03-16-2018 04:51 AM

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...

 

Feedback Type:
Frown (Error)

Timestamp:
2018-03-16T11:34:23.0617108Z

Local Time:
2018-03-16T12:34:23.0617108+01:00

Session ID:
a986f59a-fb3f-477b-852e-f5c8a5ebf5a6

Release:
March 2018

Product Version:
2.56.5023.942 (PBIDesktop) (x64)

Error Message:
Couldn't load the model schema.

OS Version:
Microsoft Windows NT 10.0.16299.0 (x64 en-US)

CLR Version:
4.7 or later [Release Number = 461308]

Peak Virtual Memory:
35.5 GB

Private Memory:
1.08 GB

Peak Working Set:
1.06 GB

IE Version:
11.309.16299.0

User ID:
f140123a-0dfa-4434-8f7c-e25e9a0abb0a

Workbook Package Info:
1* - en-US, Query Groups: 5, fastCombine: Enabled, runBackgroundAnalysis: True.

Telemetry Enabled:
True

Model Default Mode:
Import

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:
PBI_shapeMapVisualEnabled
PBI_EnableReportTheme
PBI_numericSlicerEnabled
PBI_SpanishLinguisticsEnabled
CustomConnectors
PBI_AdobeAnalytics
PBI_qnaExplore
PBI_variationUIChange
PBI_customVisualsGallery
PBI_canvasTooltips

Disabled DirectQuery Options:
PBI_DirectQuery_Unrestricted
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

DPI Scale:
125%

Supported Services:
Power BI

 

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?

 

Thanks,

K3

Status: Accepted

Dataflows - UK/US Date Format

Status: New
by tanyad Regular Visitor on ‎11-08-2018 02:47 PM

Just trying out the Dataflow feature and sadly anything other than US date format does not appear to work.  I am using a DimDate table which has dates in UK format.  Created a Dataflow, all date field that were in UK format came in as US Format - as far as I can see there is no where to set the date format to UK.  So i then connected to the Dataflow from the Desktop and all the date columns error because the service thinks they are invalid dates.  There is life outside of the US :-)  If this is a bug please fix it quicker than you did when PBI first came out and the same US/UK format issue took nearly a year to fix.

 

DataflowUKFormatError.png

Dataflows sets data types incorrectly

Status: Accepted
by Daniil Member ‎11-29-2018 04:20 PM - edited ‎11-29-2018 04:20 PM

In one of my entities, I have a column of type Date and a column of type Fixed Decimal Number. I have explicitly set the data types, and I can see the correct data type icons in column headers.

 

When I save and refresh my dataflow, then export the JSON file, the data types are set incorrectly to Date/Time (dateTime) and Decimal Number (double), respectively.

 

As a result, I have to set the data types again in Power BI Desktop.

Status: Accepted

DirectQuery Refresh Broken update january 2018

Status: Accepted
by Goofr Regular Visitor on ‎01-09-2018 08:11 AM

Hi,

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.

 

Frank

Status: Accepted

I seem to be having issues with the recent Power BI update (December 2017), whereby when invlaid relationships are trying to be established between two tables Power BI exits with no warning.

Status: Accepted

Hi guys,

We have an easy-to-reproduce issue that is critical to all users who have the Salesforce Objects connector in any of their queries.

The August 2018 version of Power BI Desktop (2.61.5192.601) does not allow the framework to refresh any queries that use the Salesforce Objects connector. [The Salesforce Reports connector is unaffected.]

To demonstrate this, simply add the following text into Power Query using the Advanced Editor.

let
    Source = Salesforce.Data(),
    SFDCObject = Source{[Name="Campaign"]}[Data], // Change this table name to be any SFDC table with >2000 records in it
    Custom1 = Table.Range(SFDCObject, 2001, 1)
in
    Custom1

The code is trying to return the 2001st record from any Salesforce Objects data set (assuming that it initially has >2000 rows!). Symptoms: The framework can happily extract the first 2000 rows without issue, but any subsequent rows fail to return and the Refresh data screen never completes. The only option is to cancel the dialog, and that often results in a hang.

 

As a result, we cannot refresh any Salesforce Object datasets within Power BI Desktop (Aug 2018 version). The functionality works fine with ALL previous versions of Power BI Desktop.

 

This is preventing us from being able to use the latest version of the software. please can you address this ASAP?

Many thanks,

Geoff Richardson

 

Status: Needs Info

 

direct query errors.png

So, I turned Composite Models preview feature on yesterday to review it. I got the top two errors on my imported tables.

I turned it off and restarted PBID and refreshed all. Then, I got the third error on a different table. I also continue to get the error on the other table.

 

 

 

Following error is preventing PBI Desktop (2.60.5169.3201 (18.07) (x64)) from running:

 

Feedback Type:
Frown (Error)

Error Message:
Для указанного алгоритма подписи не удалось создать SignatureDescription.

Cannot create SignatureDescription for signature algorythm

Stack Trace:
в System.Security.Cryptography.Xml.SignedXml.CheckSignedInfo(AsymmetricAlgorithm key)
в System.Security.Cryptography.Xml.SignedXml.CheckSignature(AsymmetricAlgorithm key)
в System.Security.Cryptography.Xml.SignedXml.CheckSignature(X509Certificate2 certificate, Boolean verifySignatureOnly)
в MS.Internal.IO.Packaging.XmlDigitalSignatureProcessor.Verify(X509Certificate2 signer)
в System.IO.Packaging.PackageDigitalSignature.Verify(X509Certificate signingCertificate)
в System.IO.Packaging.PackageDigitalSignatureManager.VerifySignatures(Boolean exitOnFailure)
в Microsoft.Mashup.EngineHost.Services.LibraryFile.PqxFile..ctor(Byte[] bytes, Package package, HashSet`1 artifacts)
в Microsoft.Mashup.EngineHost.Services.LibraryFile.PqxFile.Open(Byte[] bytes)
в Microsoft.Mashup.EngineHost.Services.LibraryFile.New(Byte[] bytes, LibraryFile& result, Exception& error)
в Microsoft.Mashup.EngineHost.Services.LibraryService.LibraryInfo..ctor(LibraryService service, ILibrary library)
в Microsoft.Mashup.EngineHost.Services.LibraryService.GetLibraryInfo(ILibrary library)
в Microsoft.Mashup.EngineHost.Services.LibraryService.EnumerateAndLoadLibraries()
в Microsoft.Mashup.EngineHost.Services.LibraryService.Reinitialize(ILibraryProvider[] providers)
в Microsoft.Mashup.Client.UI.Shared.UiExtensibility.UiExtensionHost.LoadModules(Trace innerTrace, IList`1 binaryModules, ILibraryProvider[] providers)
в Microsoft.Mashup.Client.UI.Shared.UiExtensibility.UiExtensionHost.LoadExtensions(IList`1 libraryExtensions, IApplicationPaths applicationPaths, ILibraryProvider internalProvider, String remoteExtensionsUrl)
в Microsoft.PowerBI.Client.Windows.PowerQueryExtensionsLoader.<Load>b__0()
в System.Threading.Tasks.Task.Execute()
--- Конец трассировка стека из предыдущего расположения, где возникло исключение ---
в System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
в Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass7.<HandleExceptionsWithNestedTasks>b__6()
в Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

Stack Trace Message:
Для указанного алгоритма подписи не удалось создать SignatureDescription.

Invocation Stack Trace:
в Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
в Microsoft.Mashup.Client.UI.Shared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace, String exceptionMessage)
в Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.ReportException(IWindowHandle activeWindow, IUIHost uiHost, FeedbackPackageInfo feedbackPackageInfo, Exception e, Boolean useGDICapture)
в Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.<>c__DisplayClass1.<HandleException>b__0()
в Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.HandleException(Exception e)
в Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
в Microsoft.PowerBI.Client.Program.Main(String[] args)

Feedback Type:
Frown (Error)

Timestamp:
2018-07-23T09:27:52.8938038Z

Local Time:
2018-07-23T12:27:52.8938038+03:00

Session ID:
db6ed80e-f366-4074-99a3-1aa15ac7d310

Release:
July 2018

Product Version:
2.60.5169.3201 (18.07) (x64)

Stack Trace:
в System.Security.Cryptography.Xml.SignedXml.CheckSignedInfo(AsymmetricAlgorithm key)
в System.Security.Cryptography.Xml.SignedXml.CheckSignature(AsymmetricAlgorithm key)
в System.Security.Cryptography.Xml.SignedXml.CheckSignature(X509Certificate2 certificate, Boolean verifySignatureOnly)
в MS.Internal.IO.Packaging.XmlDigitalSignatureProcessor.Verify(X509Certificate2 signer)
в System.IO.Packaging.PackageDigitalSignature.Verify(X509Certificate signingCertificate)
в System.IO.Packaging.PackageDigitalSignatureManager.VerifySignatures(Boolean exitOnFailure)
в Microsoft.Mashup.EngineHost.Services.LibraryFile.PqxFile..ctor(Byte[] bytes, Package package, HashSet`1 artifacts)
в Microsoft.Mashup.EngineHost.Services.LibraryFile.PqxFile.Open(Byte[] bytes)
в Microsoft.Mashup.EngineHost.Services.LibraryFile.New(Byte[] bytes, LibraryFile& result, Exception& error)
в Microsoft.Mashup.EngineHost.Services.LibraryService.LibraryInfo..ctor(LibraryService service, ILibrary library)
в Microsoft.Mashup.EngineHost.Services.LibraryService.GetLibraryInfo(ILibrary library)
в Microsoft.Mashup.EngineHost.Services.LibraryService.EnumerateAndLoadLibraries()
в Microsoft.Mashup.EngineHost.Services.LibraryService.Reinitialize(ILibraryProvider[] providers)
в Microsoft.Mashup.Client.UI.Shared.UiExtensibility.UiExtensionHost.LoadModules(Trace innerTrace, IList`1 binaryModules, ILibraryProvider[] providers)
в Microsoft.Mashup.Client.UI.Shared.UiExtensibility.UiExtensionHost.LoadExtensions(IList`1 libraryExtensions, IApplicationPaths applicationPaths, ILibraryProvider internalProvider, String remoteExtensionsUrl)
в Microsoft.PowerBI.Client.Windows.PowerQueryExtensionsLoader.<Load>b__0()
в System.Threading.Tasks.Task.Execute()
--- Конец трассировка стека из предыдущего расположения, где возникло исключение ---
в System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
в Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass7.<HandleExceptionsWithNestedTasks>b__6()
в Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

OS Version:
Microsoft Windows NT 6.3.9600.0 (x64 ru-RU)

CLR Version:
4.5.1 or later [Release Number = 378675]

Peak Virtual Memory:
33.4 GB

Private Memory:
170 MB

Peak Working Set:
196 MB

IE Version:
11.0.9600.18231

User ID:
74b21922-e0e9-4e74-a86b-6d2ba4eabeee

Telemetry Enabled:
True

DPI Scale:
100%

Supported Services:
Power BI

Idea Statuses