Forum Discussion
Error refreshing in Service, but not on Desktop.
Specific error message:
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":"The underlying connection was closed: An unexpected error occurred on a send."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Detail","detail":{"type":1,"value":"https://ulteig.crm.dynamics.com/api/data/v9.2"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: DIMClient.
Cluster URI: WABI-US-NORTH-CENTRAL-H-PRIMARY-redirect.analysis.windows.net
Activity ID: 7a6f91fb-240e-45c6-a683-09bdfd8bad7c
Request ID: b2456a60-6bd0-6ff3-8e43-945392b27e25
Time: 2023-10-04 16:46:16Z
This was fine for months, then today suddenly started kicking this error.
I've tried:
- Refreshing in Desktop (is fine)
- Refreshing in a different worksapce (error)
- Switching between using the datagateway, vs not, fo rthe above mentioned datasource - no difference.
Per Microsoft Ticket - this is just how it is. If it fails, try the query again.
I'm trying the Dynamics Finance team now to ask if there's some best practice we're missing, since this seems pretty bad.
4 Replies
- mmace1
Impactful Individual
Everyone says, no.
I can connect from Power BI Desktop (Whether on our VPN, or not)
I cannot connect from the Power BI service, whether attempting to utilize our Gateway, or not.
This might have to be a MS ticket.
- mmace1
Impactful Individual
Not really a solution - but I ended up just bypassing the API via Power BI (we have a seperate integreation that pulls things down into a SQL Server, just ended up pulling the additional fields via that).
- mmace1
Impactful Individual
Per Microsoft Ticket - this is just how it is. If it fails, try the query again.
I'm trying the Dynamics Finance team now to ask if there's some best practice we're missing, since this seems pretty bad.