Hi All,   Our gateway, datasets, reports etc have all disappeared from Power BI Service. Workspaces are either not loading or not viewable. I spoke to a Power BI administrator at another company and they are also experiencing similar problems. I also note that there is has been a spike in reported issues with M365. - https://downdetector.co.uk/status/microsoft-365/   Anyone else experiencing similar?   ... View more

Currently running into some difficulties editing dataflows within the PBI Service that connect to SAP BW: Partitioning the data pull due to SAP BW memory issues  Able to set it all up within PBI Desktop and refresh it manually, however unioning the data can sometimes fail due to memory issues Moved all of the above to be dataflows Able to create the dataflow initially and refresh it via PBI Gateway - seems to work so far Started to receive an error when pulling this data into PBI desktop around "there were more columns in the result than expected" - unsure why so following advice from a different post: https://community.powerbi.com/t5/Service/DataFlow-Refresh-Error-and-Fix-for-added-Fields-in-Dynamics-365/m-p/615147   However, I've found that I am unable to edit the entities within the dataflow due to the following error and unclear why (especially since I am able to create the dataflow and refresh in the first place):   DataSource.MissingClientLibrary: This error could've been the result of provider-specific client software being required, but missing on this computer. To download client software for this provider, visit the following site and choose the 64-bit (x64) version of, at minimum, 'SAP .NET Connector 3.0.0.42': https://go.microsoft.com/fwlink/?linkid=872300 Details ClientLibraryName = SAP .NET Connector 3.0.0.42 DownloadLink = https://go.microsoft.com/fwlink/?linkid=872300   Should also point out, the dataflow still appears to refresh.   ... View more

This is only a recent problem I am facing.   When I use a dataflow in a report/dataset, it refreshes ok within PowerBi desktop. When I publish to the service, the dataflow causes the gateway to be "Not configured correctly"   What is causing this problem? ... View more

Hello,   Recently the past few days, we have encountered multiple issues with the Power BI Service: Pro users are unable to Takeover the existing Power BI datasets from other Pro users. Whenever a takeover action is done, the users receive the following error:   Power Bi Service is unable to discover data sources. Whenever a Pro user tries to discover the data sources in the dataset, they receive the following error:   Kindly address these two issues on an immediate basis as this is a huge blocker for our software development cycle. ... View more

I have 2 issues:   1) OAuth2 authetication no longer works (both Service and Desktop), coming up with the error "Unable to update this data source's credentials. Unable to connect to the data source."   2) Dataset refresh comes up with this error even when all gateway status shows "online"     Data source error: {"error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","pbi.error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"The credentials provided for the VSTS source are invalid. (Source at sita-pse.)"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceKind","detail":{"type":1,"value":"VSTS"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceOriginKind","detail":{"type":1,"value":"VSTS"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceOriginPath","detail":{"type":1,"value":"sita-pse"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourcePath","detail":{"type":1,"value":"sita-pse"}},{"code":"Microsoft.Data.Mashup.CredentialError.Reason","detail":{"type":1,"value":"AccessForbidden"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"VSTS\",\"path\":\"sita-pse\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"AccessForbidden"}}],"exceptionCulprit":1}}} Table: defect by sprint. Cluster URI: WABI-NORTH-EUROPE-G-PRIMARY-redirect.analysis.windows.net Activity ID: d702d841-7cdc-45b3-8ef2-e194561b5cf5 Request ID: 212fdc9d-4ea3-c251-e107-2b5a53966f33 Time: 2022-05-17 11:59:38Z     ... View more

I'm currently trying to schedule a refresh for a Power BI report which uses python to transform the loaded data.   I can get the python script to run on my local machine in powerbi desktop, but when I publish it and attempt to schedule the refresh, I get an error concerning invalid credentials (Your data source can't be refreshed because the credentials are invalid. Please update your credentials and try again.). The other data sources connect fine through the personal gateway. When I click on 'Edit Credentials' for Python, I get the following specifics:       Failed to update data source credentials: ADO.NET: Python script error. Traceback (most recent call last): File "PythonScriptWrapper.PY", line 2, in <module> import os, pandas, matplotlib File "C:\ProgramData\Anaconda3\lib\site-packages\pandas\__init__.py", line 19, in <module> "Missing required dependencies {0}".format(missing_dependencies)) ImportError: Missing required dependencies ['numpy']       Activity ID: 177ce143-63b1-422a-8852-ca1bef96a846 Request ID: 9f20ee17-91cb-ab92-75d9-7688929f6157 Status code: 400 Time: Fri Feb 28 2020 11:07:32 GMT+0000 (Greenwich Mean Time) Service version: 13.0.12439.190 Client version: 2002.3.018 Cluster URI: https://wabi-north-europe-redirect.analysis.windows.net/         I can't see any way to select the python installation to run the script with, but all of my local environments should be able to run the script (notably, they all have numpy installed)   Thanks in advance for your help. George Kinnell (Altius) ... View more

Hello Recently we have been receiving frequent failures on datasets, the most frequent error is a schedule refresh specifically to the source Teradata. The gateways are connected successfully using a service account. For the Teradata error, the Teradata DBA says issue is not from a Teradata aspect. We have logged into Teradata with the service account and have intermittent issues doing so, ultimately able to log in successfully. The 2nd error is for a SQL server which has started popping up more frequently... These are the 2 errors: Teradata Error: Refresh failed: __________ has failed to refresh. Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support. {"error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","pbi.error":{"code":"DM_GWPipeline_Gateway_InvalidConnectionCredentials","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"<pi>The credentials provided for the Teradata source are invalid. (Source at td_prd.)</pi>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourceKind","detail":{"type":1,"value":"Teradata"}},{"code":"Microsoft.Data.Mashup.CredentialError.DataSourcePath","detail":{"type":1,"value":"________"}},{"code":"Microsoft.Data.Mashup.CredentialError.Reason","detail":{"type":1,"value":"AccessUnauthorized"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"Teradata\",\"path\":\"______\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"AccessUnauthorized"}}],"exceptionCulprit":1}}} Table: PIN_View_Reset_Combined. Next refresh for __________ is scheduled for June 8, 2020 11:00 UTC. SQL Error:   Refresh failed: __________ has failed to refresh. Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support. {"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":"<pi>Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.</pi>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Class","detail":{"type":1,"value":"11"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"SQL"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"__________________;__________________"}},{"code":"Microsoft.Data.Mashup.ValueError.Message","detail":{"type":1,"value":"Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding."}},{"code":"Microsoft.Data.Mashup.ValueError.Number","detail":{"type":1,"value":"-2"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: _____________. Next refresh for __________ is scheduled for June 8, 2020 23:00 UTC. ... View more