Issues

CKSanalyst · ‎04-22-2024

Hi Team, I noticed a potential bug in PBI Service. In the Query Editor of PBI Desktop, I'm merging a table multiple times with two other tables (overall 6 merges, first two tables are web sources, third table is an xml-file retrieved from a local drive). Each merge is performed as a new table and the final table is a reference to the last merge step. Refreshing works in Power BI Desktop, but when uploading and refreshing the semantic model in PBI Service, I'm receiving different error messages - sometimes even resulting in our Gateway going offline. Pls. find an error message example below: {"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":"Evaluation ran out of memory and can't continue."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}}],"exceptionCulprit":1}}} Table: xxx I've found a workaround by unchecking "enable load" of all intermediate steps, only enabling load for the final table. Nonetheless, comparing to other queries that we already did it doesn't seem reasonable that loading the merge-steps into the model should result in crashing the gateway. I hope you can help with this issue. Thanks!

sgengie2020 · ‎02-27-2024

I have a Power BI report which I triggered refresh at 2:54PM and while refreshing, schedule refresh kick in at 3:04PM. Then I saw 2 records showing "in progress" and never gets ended. Try canceled both and refresh but the refresh never gets complete again. I try published the report to another workspace and refresh no issue and therefore cancel this refresh and publish again the report to this workspace and triggered refresh but same issue - it never gets completed. I wanted to log an issue to Microsoft but then the page doesn't allow me to go through. Can the team fix and improve this please?

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!

Elmarie_Kies · ‎02-08-2024

Hi there, we upgraded our on-prem gateway to the newest version. I have created a test Data Flow Gen 2 to check if it works. When trying to refresh we get the following error: 104100 Couldn't refresh the entity because of an internal error I see the person here also had the same issue but there was no resolutoin: https://community.fabric.microsoft.com/t5/Dataflows/104100-Couldn-t-refresh-the-entity-because-of-an-internal-error/m-p/3637085

ocasares · ‎10-02-2023

Hi, From today, the access to the old Power BI Gateway UI have been removed. We can only access to the new PowerBI Gateway UI And, because of that, we have lost the capability to manage the users being mapped in the Analysis Services connection, to route requests from Azure AD users to the on-premises Active Directory ones, with which it is bases the RLS security of the Microsoft SQLServer SSAS. You can see that the mapping rules for the initial users appear correctly: But when scrolling down, all the rest of the mappings seems to disappear, leaving a blank space: Please fix this. The mapped users cannot be seen and therefore cannot be managed correctly anymore!.

RomBec · ‎07-25-2023

There has been a dataflow refresh problem that started on 2023-07-01. Some Dataflows that contain SharePoint data sources randomly fail to refresh (sometimes the refresh works and sometimes is does not). The error messages can be different. The most recent one was: Error: Encountered user gateway exception: '[GatewayPipelineErrorCode]=DM_GWPipeline_Client_GatewayUnreachable [ErrorShortName]=GatewayUnreachableException/CommunicationObjectFaultedException[HResult=-2146233087] [ExceptionErrorShortName]=GatewayUnreachableException'. RootActivityId = debae686-23e3-4ec2-8c69-37c87fb9ad03.Param1 = [GatewayPipelineErrorCode]=DM_GWPipeline_Client_GatewayUnreachable [ErrorShortName]=GatewayUnreachableException/CommunicationObjectFaultedException[HResult=-2146233087] [ExceptionErrorShortName]=GatewayUnreachableException Request ID: 6eb5f485-f9eb-4b39-8f86-4c3e53ea95a3. Very often I also got the “An existing connection was forcibly closed by the remote host.” error. Maybe the issue I’m facing is related to the problem described here: Unable to read data from the transport connection: An existing connection was forcibly closed by the

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

mhasan27 · ‎07-05-2023

Hello Everyone, One of the dataflow which has all the source from SharePoint is failing to refresh since last week. I triggered manual refresh but it is failing with the same error with different table. Kindly suggest ways to resolve this issue. Follwoing is the error message: Error: An existing connection was forcibly closed by the remote host Request ID: 4ad4a72d-d4d0-43b6-8c46-2d402d1a3443 Activity ID: 96dcd502-4720-473d-97fc-be6936663e98

The_Bishop · ‎06-07-2023

I cannot even see our on-prem gateway in fabric.microsoft.com. There are no gateways or connections listed. If I use the old app.powerbi.com route, then the gateway and connections are all there and I can continue to manage them. In both cases, I navigate to the page from Settings > Manage connections and gateways. I can get round it for now, but it seems to be a bug.

user180618 · ‎06-05-2023

I have two datasets in my workspace and I have access to the Sharepoint site that the data is connected to (one is at sharepoint.com/Sitename/Subsite and the other is at sharepoint.com/Sitename, so the parent site). One of them has scheduled refresh on and it works fine, the data source credentials are configured to OAuth2 and Private. My other dataset gives me the error: Scheduled refresh is disabled because at least one data source is missing credentials. To start the refresh again, go to this dataset's settings page and enter credentials for all data sources. Then reactivate scheduled refresh. When I go to edit credentials, it only gives me the authentication method Anonymous. However, in the pbix file I have authenticated with my Organizational account and set the privacy level to Organizational. I have tried clearing the permissions and setting them up again but that doesn't resolve it. Any suggestions appreciated.

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)

TrevLc · ‎05-11-2023

Most of our datasets are failing with the error DM_GWPipeline_Gateway_TimeoutError Here are some detailed logs of one of the failures Data source error: {"error":{"code":"DM_GWPipeline_Gateway_TimeoutError","pbi.error":{"code":"DM_GWPipeline_Gateway_TimeoutError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: XXXXX. Cluster URI: WABI-AUSTRALIA-SOUTHEAST-redirect.analysis.windows.net Activity ID: 102863cf-9705-4230-8356-90c55b612706 Request ID: 5b83fab5-5fd3-496f-abc3-d3214466f572 Time: 2023-05-11 15:01:26Z

JczTampa · ‎05-04-2023

Upload Issue: Unable to write data to the transport connection: an existing connection was forcibly closed by the remote host This started happening on 5/2 with an updated report being published to the server. Uploading files doesn't work from the service and publishing from the desktop gives this error. I have a Pro License and the file size is 344 MB (I thought the limit was 10G?). This worked fine until 5/2.

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

info-autocat · ‎02-09-2023

I've getting error DM_GWPipeline_Gateway_TimeoutError since mid-January on my Personal Gateway. It used to happen 1-2 times a day (my data is updated 8 times a day). But since 02/04/2023, updates have ceased to take place at all. {"error":{"code":"DM_GWPipeline_Gateway_TimeoutError","pbi.error":{"code":"DM_GWPipeline_Gateway_TimeoutError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: [table name] Cluster URI: WABI-AUSTRALIA-EAST-B-PRIMARY-redirect.analysis.windows.net Activity ID: 233859e2-1c3f-4cc6-be85-bcfdd16ab969 Activity ID: 3a73f793-7741-4275-b308-3b7f482e5ebc Time: 2023-02-04 06:31:32Z I am using connection to PostgreSQL with 30 minutes timeout setting (it take 10-15 minutes to load data from all tables locally). Normal data refresh on Power BI service also takes about 15 minutes. What can I do to solve this problem?

andrecxl · ‎02-07-2023

i have been using on prem data gateway for years and it worked fine until 2PM yesterday (Feb 6) uninstalled, reinstalled, reconfigured data gateway but issues persist however, no issue when the same dataset is refreshed manually using power bi desktop Power BI Support team - can you please help? thanks

clemlanoe · ‎02-07-2023

Hi, I've had a data flow that is connected to a Sharepoint csv for months without issue and now I'm getting the following error when refreshing the data: "SharePoint: Request failed: The underlying connection was closed: An unexpected error occurred on a send." I've tried clearing the permissions and reconnected but end up with the same error. I've also tried uninstalling and reinstalling Power Bi desktop. The file is not large (5 mb) and I am able to navigate my SharePoint library from within Power Bi. [EDIT] Upon further investigation, I found that it succesfully located my CSV file on SharePoint but then fails when retrieving the binary content with a slightly different error message: "DataSource.Error: The underlying connection was closed: An unexpected error occurred on a send." [EDIT 2.0] I have managed to extract a more detailed error message: Unexpected error: The underlying connection was closed: An unexpected error occurred on a send. Details: Microsoft.Mashup.Evaluator.Interface.ErrorException: The underlying connection was closed: An unexpected error occurred on a send. ---> Microsoft.Mashup.Evaluator.Interface.ErrorException: The underlying connection was closed: An unexpected error occurred on a send. ---> Microsoft.Mashup.Evaluator.Interface.ErrorException: The underlying connection was closed: An unexpected error occurred on a send. ---> Microsoft.Mashup.Evaluator.Interface.ErrorException: The underlying connection was closed: An unexpected error occurred on a send. ---> Microsoft.Mashup.Evaluator.Interface.ErrorException: The underlying connection was closed: An unexpected error occurred on a send. ---> Microsoft.Mashup.Engine1.Library.Http.ResponseException: The underlying connection was closed: An unexpected error occurred on a send. ---> Microsoft.Mashup.Engine1.Library.Http.ResponseException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.WriteHeaders(Boolean async) --- End of inner exception stack trace ---

swebster225 · ‎02-06-2023

Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net Activity ID: 9ed34d41-5f06-4248-96b6-6a42d072e5d3 Request ID: a2aec422-257d-3a99-4686-f88e16cbe3a0 Time: 2023-02-06 14:07:46Z Started a few days ago, most dashboards refresh fine, but any linked to SQL Tables aren't refreshing. I've checked our on prem data gateway, and rechecked the credentials and it is showing online, but I keep getting errors.

Tanaka · ‎01-26-2023

Hello, Since past week i am been facing this error: Data source error: {"error":{"code":"DM_GWPipeline_Gateway_TimeoutError","pbi.error":{"code":"DM_GWPipeline_Gateway_TimeoutError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: [table name]. Cluster URI: WABI-BRAZIL-SOUTH-redirect.analysis.windows.net Activity ID: 34b96fa6-fc68-4e5a-9c49-92e8459864d6 Request ID: bfff473b-fdc6-7742-ff8e-eaad01521a26 Time: 2023-01-26 19:58:05Z I am using a gateway to Athena Data Lake, tables with large number of rows (2kk and beyond) are getting this error, and when using a gateway to SQL Server i do not have this error. Already tried to reinstall gateways, install gateways in differents desktops, reinstall ODBC drivers in all those machines. Something to highlight, when updating data via PBI Desktop it is noticed that tables from Athena Data Lake upload 10k rows / min, or 100k rows/ 7~10 min, as i said, this started to occur since past week. Thanks in advance for your support.

marcritchie · ‎01-19-2023

I'm having a problem with a dataflow that seems to reoccur every morning after functioning correctly the previous afternoon. In the refresh history log it gives the following error: Error: Encountered user gateway exception: '<ccon>The credentials provided for the PowerBI source are invalid. (Source at PowerBI.)</ccon> [DM_ErrorDetailNameCode_UnderlyingErrorCode]=-2147467259 [DM_ErrorDetailNameCode_UnderlyingErrorMessage]=<ccon>The credentials provided for the PowerBI source are invalid. (Source at PowerBI.)</ccon> [DM_ErrorDetailNameCode_UnderlyingHResult]=-2147467259 [Microsoft.Data.Mashup.CredentialError.DataSourceKind]=PowerBI [Microsoft.Data.Mashup.CredentialError.DataSourceOriginKind]=Web [Microsoft.Data.Mashup.CredentialError.DataSourceOriginPath]=https://api.powerbi.com/powerbi/globalservice/v201606/clusterdetails [Microsoft.Data.Mashup.CredentialError.DataSourcePath]=PowerBI [Microsoft.Data.Mashup.CredentialError.Reason]=AccessForbidden [Microsoft.Data.Mashup.MashupSecurityException.DataSources]=[{"kind":"PowerBI" "path":"PowerBI"}] [Microsoft.Data.Mashup.MashupSecurityException.Reason]=AccessForbidden [InnerType]=MashupCredentialException The credentials provided for the PowerBI source are invalid. (Source at PowerBI.) [GatewayPipelineErrorCode]=DM_GWPipeline_Gateway_InvalidConnectionCredentials [ErrorShortName]=GatewayClientErrorResponseException[GatewayId=830927]/MashupDataAccessCredentialException[ErrorCode=-2147467259 HResult=-2147467259]/Wrapped(MashupCredentialException)[ErrorCode=-2147467259 HResult=-2147467259] [ExceptionErrorShortName]=GatewayClientErrorResponseException[GatewayId=830927]'. RootActivityId = b7685438-32e7-4086-a129-0e9d5ec4ac91.Param1 = <ccon>The credentials provided for the PowerBI source are invalid. (Source at PowerBI.)</ccon> [DM_ErrorDetailNameCode_UnderlyingErrorCode]=-2147467259 [DM_ErrorDetailNameCode_UnderlyingErrorMessage]=<ccon>The credentials provided for the PowerBI source are invalid. (Source at PowerBI.)</ccon> [DM_ErrorDetailNameCode_UnderlyingHResult]=-2147467259 [Microsoft.Data.Mashup.CredentialError.DataSourceKind]=PowerBI [Microsoft.Data.Mashup.CredentialError.DataSourceOriginKind]=Web [Microsoft.Data.Mashup.CredentialError.DataSourceOriginPath]=https://api.powerbi.com/powerbi/globalservice/v201606/clusterdetails [Microsoft.Data.Mashup.CredentialError.DataSourcePath]=PowerBI [Microsoft.Data.Mashup.CredentialError.Reason]=AccessForbidden [Microsoft.Data.Mashup.MashupSecurityException.DataSources]=[{"kind":"PowerBI" "path":"PowerBI"}] [Microsoft.Data.Mashup.MashupSecurityException.Reason]=AccessForbidden [InnerType]=MashupCredentialException The credentials provided for the PowerBI source are invalid. (Source at PowerBI.) [GatewayPipelineErrorCode]=DM_GWPipeline_Gateway_InvalidConnectionCredentials [ErrorShortName]=GatewayClientErrorResponseException[GatewayId=830927]/MashupDataAccessCredentialException[ErrorCode=-2147467259 HResult=-2147467259]/Wrapped(MashupCredentialException)[ErrorCode=-2147467259 HResult=-2147467259] [ExceptionErrorShortName]=GatewayClientErrorResponseException[GatewayId=830927] Request ID: ad7bb2b3-f898-43f7-9788-7fab4416aa79. I've checked all connections in 'Manage connections and gateways' and reauthenticated everything. I've also checked the dataset for this dataflow to make sure it is all set up correctly. It's becoming really frustrating as it seems to break overnight every day and I have to spend time every day trying different things to get it to work.

Share your ideas and vote for future features

Bug Report - Gateway offline when refreshing semantic model with merged table

Power BI service refresh appear in progress for 2 records and never complete

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

Data Flow Gen 2 not refreshing

Unable to map users in Analysis Service connection in the Power BI Gateway

Dataflow refresh in the service is failing

Dataset refresh error on Service

Dataflow Failing to refresh

No gateway shown in Fabric

Scheduled refresh disabled despite correct permissions

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

DM_GWPipeline_Gateway_TimeoutError

Upload Issue: Unable to write data to the transport connection: an existing connection was forcibly

DM_GWPipeline_Gateway_TimeoutError

DM_GWPipeline_Gateway_TimeoutError

refresh issues with on prem data gateway

Dataflow Refresh Error with SharePoint

Error Refreshing Dashboard linked to SQL

DM_GWPipeline_Gateway_TimeoutError

Encountered user gateway exception. The credentials provided for the PowerBI source are invalid

Helpful resources

Multiple Refresh schedules in single report

R and Python - Standard Gateway

PowerBi consistently crashes when chosing Quick Me...

Bug in quick filter in PBI Desktop

Something went wrong endless loop