Issues

Jlindsey00 · ‎02-26-2024

Since the Power BI Feb 2024 release, all of the reports in our workspaces have had this SSL error: "The server name provided does not match the server name on the SQL Server SSL certificate ... " Everything was working fine and then all of a sudden this error showed up across our workspaces Some notes and highlights: We use Azure sql databases No credentials were changed before this error occured and none have changed since I have double checked the credentials and the server names match both in the desktop and in the service The error occurs both on desktop and in the service We connect through a sql privatelink (servername.privatelink.database.windows.net) and use a VNET data gateway That gateway has not changed We tried disconnecting from the VNET data gateway and using an on-prem gateway, no luck connecting either We can connect to our Azure sql dbs with any other method directly in SSMS through excel In web apps we use Any idea what could be going on? Thank you!

is001902 · ‎03-18-2024

I am accessing one SQL Server DB using direct query. This report works fine for varying lengths of time but then stops working with the error AN EXCEPTIONS OCCURRED DUE TO AN ON PREMISE SERVICE ISSUE. We checked if there was an SQL activity (backups etc.) going on to interrupt it but none. We run a subscription report to track when it fails and there is no consistency. When we refresh the report it usually starts working again, sometime we have to go and refresh the connections or on premise gateway. Any ideas?

Imrans123 · ‎07-19-2022

Was wondering if anyone is facing this issue? For all my Pro Workspaces, I cannot seem to edit the dataflow settings as they're all grayed out. They are going on about their pre scheduled refreshs properly as they should. I am also able to make edits in Datasets for pro workspaces. But cannot seem to make changes in pro dataflow. My Premium workspaces (via PPU) are working just fine.

Anonymous · ‎01-12-2023

I noticed when I published a report with an on-premise data source (SAP BW) along with cloud data sources (Sharepoint), the Apply button is greyed out in the gateway connection settings: Again, this is only applicable to newly published datasets. For the existing ones, there are no errors, and I can refresh successfully. Like this one, it has actually the same setup, just published in a different workspace some time ago: I just experienced this yesterday. Any of you are experiencing it now? Appreciate the responses! EDITED-- Check out the comments for the workaround Microsoft has also posted the issue on the Power BI Support page. Expect the fix to be on 24th of January

GregMarbais · ‎02-23-2022

Ever since about 6am Eastern today, my dataset refreshes have been failing and the reports are just spinning - no errors, just spinning like it's trying to load the data.

michaelsh · ‎04-14-2021

Simple SQL query that runs 7 seconds in SQL takes 19 minutes(!) to validate in Dataflows 19 minutes!!!??? Not just one query. I've tried SQL Server and PostgreSQL - the time it takes to Validate is just crazy. What is going on? Please help

shabeer · ‎07-06-2023

Hello Team, My Power Bi dataset is not getting refreshed from yesterday. I have found out the issue is with Dataset that contains the Power Bi Dataflow (Legacy) connection sources. It is throwing the error as "Access token has expired, resubmit with a new access token.". However, there is no issue when we go ahead with Power Bi desktop refresh. The issue is not only with one dataset. The issue reasons are changing time to time. The same datasets were OKAY till yesterday evening GST. Attaching the error messages for your reference. Best Rag, Shabeer M P

Tiemen · ‎05-31-2023

Hello, The datasets in the new Admin monitoring workspace wont refresh anymore. Also it is not possible as an Power BI admin to get an Admin role for this workspace. So i can't check te dataset settings. Error details: Data source error: {"error":{"code":"ModelRefresh_ShortMessage_ProcessingError","pbi.error":{"code":"ModelRefresh_ShortMessage_ProcessingError","parameters":{},"details":[{"code":"Message","detail":{"type":1,"value":"The credentials provided for the AdminInsights source are invalid. (Source at AdminInsights.)"}}],"exceptionCulprit":1}}} Cluster URI: WABI-WEST-EUROPE-B-PRIMARY-redirect.analysis.windows.net Activity ID: 706ff8a3-0141-46d3-870f-5ac5c38258b7 Request ID: aaee75b8-262c-4e9e-87a6-158967a5a2d5 Time: 2023-05-28 09:42:21Z

venal · ‎04-29-2023

Most of the datasets are failing and shows an error - DM_GWPipeline_Gateway_TimeoutError. Can anyone facing similar issue with the latest version - 3000.170.8, Is it something like global issue

JSanders28 · ‎01-05-2024

I'm on the Power BI administrator team for a large e-commerce company. Today we saw multiple operation timeouts for multiple datasets dependent on dataflows. Looks like there was an issue on Power BI service. The issue impacted multiple datasets dependent on different dataflows across different workspaces. Opened a ticket with Microsoft Support, but posting here to raise visibility to other customers as well that may be experiencing the same. [ValidateMarkupTags][ccon]DataSource.Error: [ccon]The operation has timed out[/ccon].

Link0978 · ‎12-13-2022

Hi, I am unable to configure gateway connections for dataset for a pbix report uploaded. I have created data source connections prior to uploading the file. All the 23 data sources are on-prem. When I tried to apply the gateway connections (all have green check marks), I got this error message: I also noticed this banner. The dataset does not have any cloud data souces: Edit: @v-yetao1-msft I originally just uploaded the pbix file to the web portal. The file was built using the Power BI Desktop RS Jan 2022 version. Then I tried to open the pbix file in the RS Jan 2022 and published to our P1 capacity-backed workspace. The issue persists. Then I opened the file in Power BI Desktop Oct 2022 for powerbi.com version. I saved the file and published it again. The issue persists. Some of the data source connections are also used by other reports without an issue. The other connections were created just for this report. The connections are consisted of SQL servers and file shares. We have 2 windows 2016 VMs in a cluster to host the on-prem gateway. Version Aug 2022.

grrly · ‎02-21-2023

Greetings, I have been receiving this error message every day since 02/02/23 when trying to refresh our dataset. Similar error message, but different tables/dbs each time. PowerBI is connected to multiple access databases to retrieve calculated data. Has been running successfully for the last 3+ years. Full error message today: Something went wrong. There was an error when processing the data in the dataset. Data source error: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Unspecified error"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Detail","detail":{"type":1,"value":"388 SSC Dashboard DB Control ACH.accdb"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataFormat.Error"}}],"exceptionCulprit":1}}} Table: tblControl_Score_SisterStore. Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net Activity ID: 21f8ec5e-0adb-409d-a7ee-ce91d17d30a7 Request ID: dc551385-46a8-498b-b8ed-623de6e4d3a2 Time: 2023-02-21 15:02:50Z Additionally, when checking all of our gateways, majority of them are showing as "offline". I have tried to resolve those to no avail: Error code: GatewayUnreachable Data source error: Gateway unreachable Cluster URI: https://api.powerbi.com Activity Id: b9db2528-0564-41a5-be56-c6f1e8607269 Request ID: 6e68fd9b-f9f7-40dc-9d40-a06d14231a3f Time: Tue Feb 21 2023 10:26:45 GMT-0600 (Central Standard Time) Gateway on endpoint 'sb://wabi-us-east2-relay15.servicebus.windows.net/f484105f-e8ad-401c-ab33-25185fe178c5/' is unreachable.

Karthikeyan_Jo · ‎05-30-2023

Power BI Desktop Version: 2.117.984.0 64bit(May 2023) When I try using Power BI Desktop Shortcut by Shift+Right click different user, It was previously working for me to login using different account. But recently I have updated the Power BI Desktop software(May 2023), after that I have getting below error, Kindly help on this. Unable to sign in Sorry, we encountered an error while trying to sign you in. Details: Unknown Status: Unexpected Error: 0xfffffffff80070520 Context: Unexpected exception while waiting for accounts control to finish: '(pii)' Tag: 0x1f7d734b (error code -2147023584) (internal error code 528315211)

Anonymous · ‎08-01-2022

Hello, After publishing a report, I try to set up a refresh schedule, and I receive the error below: "Failed to load data sources. Please try again later." I am using an on-premises gateway (personal mode). Here are the error details: Activity ID: fbaa47fb-bed3-497f-9c5f-629630eede0d Request ID: 71d6f731-dd38-fe2d-a671-354ffcd184a5 Correlation ID: 4697d43e-0e08-aff6-d80d-3045ed369aaa Status code: 500 Time: Mon Aug 01 2022 09:00:57 GMT-0400 (Eastern Daylight Time) Service version: 13.0.18756.45 Client version: 2207.4.12439-train Cluster URI: https://wabi-us-east-a-primary-redirect.analysis.windows.net/

sushovan93 · ‎01-02-2024

Power BI Report refrershes failing with Timeout Error using Data Gateway from 31st Dec. we are currently running on November 2023 update (3000.198.17). Error Messages We are gettin on different datasets on different Data sources, not any particular datasource or dataset. This similar issue we have faced in starting 1st Week of Dec 2023 also that time we have upgraded the Gateway version and the issue was gone for couple of week now again it has started from 31st Dec. Microsoft Article says it support Gatewya for last 6 release. For a Large enterprise runnig large scale data refresh and power bi environment if this kind of issue happens very frequently there is a problem/bug with the service release for Power BI service that needs to be fixed ASAP. As we are running it enterprise wide there should be a minimal time or support for the gateway as it is very difficult to updated anything on a daily basis espacially during the Holidays where you have to deal with change freeze. and this this refresh issue happens for critical reports. 1. {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Timeout expired. The timeout period elapsed prior to completion of the operation."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.HostingError.Reason","detail":{"type":1,"value":"Timeout"}}],"exceptionCulprit":1}}} 2. {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Timeout expired. The timeout period elapsed prior to completion of the operation."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.HostingError.Reason","detail":{"type":1,"value":"Timeout"}}],"exceptionCulprit":1}}} 3. {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Timeout expired. The timeout period elapsed prior to completion of the operation."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.HostingError.Reason","detail":{"type":1,"value":"Timeout"}}],"exceptionCulprit":1}}}

hannibalmads · ‎11-07-2022

Since October 24th 2022 the Microsoft version of the IBM DB2 connector returns an error on both Import and DirectQuery when working with JDEdwards on an IBM DB2 database (I haven't tried with other databases and tables). "HISMPCB0002 In BasePrimitiveConverter the SetCodePage method has been called with a invalid codepage: 937" This goes for the Power BI Desktop October 2022 version as well as the Power BI Service. When I roll back to the PBI Desktop September version I have no errors with my report. But when I publish the report to the service, the error reappears. Unfortunately this prevents us from doing any reports on the database. See also debate on Solved: Re: Error Message Trying to Hit iSeries DB2 - Microsoft Power BI Community which does not contain a solution even though it is marked as solved.

fgjerryjackson · ‎02-24-2023

Starting earlier this week, we randomly started having refresh failures on a dataset that was primarly using a Folder Data Source connection. After reviewing the datasource on the gateway, the Folder source shows being "Partially Online". When I refresh the data source status again, it will show "Online". I can then refresh the dataset on demand for a short time, but then it will default back to Partially Online after an extended period and fail the next scheduled refresh. Is this a known issue/bug??

Anonymous · ‎03-15-2021

Can't load the Manage Gateways page. Dataflows are not refreshing with this error: Error: An authentication problem is preventing the dataflow from being refreshed. Please have the owner of the dataflow sign out of Power BI and sign back in and try again. Request ID: c6da6c2f-dfa6-51d1-1b06-18da8b1d919e Activity ID: ba8a8bc2-dcc7-419f-8642-e63e89c4c98d Cleared cache and logged in and out. Can't open dataflows to edit them.

ericmarshall · ‎05-27-2023

Please advise specific instructions on how it is possible for data from an on-premises SQL server database to be fed into a Lakehouse. When using Gen2 dataflow to connect to on-premises SQL server via a gateway (client using Power BI Premium), configuring a Lakehouse as the data destination does not work: If I use a Gen1 dataflow to connect to the on-premises SQL server, and then reference the result of this dataflow using a Gen2 dataflow, interface (most of the time) allows for the Lakehouse to be assigned as the data destination, but then the Gen2 dataflow fails to refresh and gives the following error: When above dataflow is referenced in a pipeline, the associated run fails and below error message is received: Trying to connect to the on-premises SQL Server database via a pipeline does not appear to be an option as the only available connection method is "Basic" and there is no option to select the gateway.

powerbi-dev · ‎05-02-2022

I have a problem with a published dataset, with the error message "Looking up invalid data on a dense spool". It happens with a single measure and only in PBI Service. The dataset was fine and this suddenly started to happen. When I'm using PBI Desktop, there are no errors, but I soon as I publish the data and connect my report via Live Connection, any visual with the measure returns the error. The measure is quite simple, just a SUMX with a simple CALCULATE filter, and it's used in many other measures of the report which do not return any error message. I have already tried: - Recreating the measure; - Republishing the dataset; - Deleting and republishing the dataset; - Creating a new file with PBIT template and connecting/ None worked. If anyone has had this problem in the past, I'd appreciate some advice, thank you.

Share your ideas and vote for future features

Error in SQL server SSL Certificate Connection Since February '24 Release

powerbi an exception occurred due to an on premise service issue

Issue - Cannot seem to edit DataFlows Settings on Pro Workspaces.

Apply button is greyed out when adding a data source to the on-premise data gateway

Data Load Failures and Reports Spinning

Dataflows very very slow Validating Queries

Dataset refresh error on Service

Admin monitoring refresh failure

DM_GWPipeline_Gateway_TimeoutError

Dataflows Command Timeout - Multiple datasets, dataflows and workspaces - Production

Unable to configure gateway connections for dataset

Error when processing the data in the dataset - DM_GWPipeline_Gateway_MashupDataAccessError

NEW BUG: Version: 2.117.984.0 64bit (May 2023)

Error when trying to set up refresh schedule: Failed to load data sources. Please try again later.

Power BI Report refrershes failing with Timeout Error using Data Gateway.

Issue with IBM DB2 connector October 2022 release of Power BI Desktop and the Power BI Service

Gateway Data Source Partially Online

Gateways & Dataflow access down

Unable to feed on-premises SQL-Server data into Lakehouse

Looking up invalid data on a dense spool

Helpful resources

TypeConversionFailure when not trying to convert

filter pane values in service are showing in black...

Wrong french translation for "reader" permission

'Select All' option in a slicer is not intuitive w...

Error could not copy visual