Urgent Issue with Data Mart Power BI and Refresh Errors - AADSTS700082

[VickyMarga]

Hello everyone, 

I am encountering the following error in Power BI when trying to refresh my Data Mart:

Error: GatewayPipelineErrorCode=DM_GWPipeline_UnknownError
InnerType=OAuthWebException
InnerMessage=AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2023-09-08T17:50:13.2538670Z and was inactive for 90.00:00:00. Trace ID: 3aec08a9-9821-4e96-8555-7bd89a713f00 Correlation ID: bfd274ee-e7c9-466f-a9cb-8669d7622e00 Timestamp: 2025-01-23 07:30:14Z

Additionally, I am also receiving the following error message:
An error happened while reading data from the provider: 'Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.'. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action.

To provide some context:

• I am working with a Data Mart that has incremental updates.
• The Data Mart connects to Gen1 Dataflows, and when I publish it, I see the following message in the connections:
  "A gateway is not required for this semantic model because all the related data sources are in the cloud. However, a gateway can be used to better control the connection method."
• Everything works fine when I refresh from Power BI Desktop, but as soon as I publish it online, I encounter these errors.

I have tried everything: disconnected and reconnected credentials, updated and restarted the gateway. The administrator on the Azure portal has checked and confirmed there are no expired tokens.

I am at a loss for what to do next, and this issue has been ongoing for a week. Our clients are getting frustrated as we cannot provide the data, and we urgently need help resolving this. Everything was working fine before, and now it has stopped.

I would greatly appreciate any assistance you can provide as we are facing significant pressure.

Best regards

[VickyMarga · Accepted solution]

Hi everyone,

In the end, the only solution I was able to find was to move the data flow connection from the cloud directly to the gateway. This change has improved the timing, and the update has been successfully completed.

I’m honestly surprised, as I expected the cloud data flow connection to be faster compared to the gateway, which connects directly to SQL Server. However, given the time constraints for testing, I proceeded with this solution, and everything is working correctly now.

I was expecting more from the dataflows and their performance.

Thanks to everyone who provided feedback.

[Sergii24]

Hi @VickyMarga, as the error message says, your access token has expired.

"the refresh token has expired due to inactivity. The token was issued on 2023-09-08T17:50:13.2538670Z and was inactive for 90.00:00:00"

When you work with Power BI Desktop, usually you make a login to your account. When clicking on "Refresh" Power BI uses your credentials to acess the data source. After publishing the report online to Power BI service, you need to re-insert credentials for a semantic model in settings section:

So, get a new token (ask your IT team to help you) and insert it here, refresh on PBI Service should start working again.

Good luck! 🙂

[VickyMarga]

Hi @Sergii24,
thanks a lot for response 
I followed this procedure,

but now I’ve received this error. What does it mean?

An internal service error occurred, causing the cancellation of previous refresh attempts. New attempts will now be initiated.Errore dell'origine dati: DataSource.Error: An error happened while reading data from the provider: 'Internal error DirectQueryUnexpectedEndOfStream.'. Microsoft.Data.Mashup.ErrorCode = 10434. DataSourceKind = PowerPlatformDataflows. DataSourcePath = PowerPlatformDataflows. DataSourceKind.2 = AdoDotNet. DataSourcePath.2 = Microsoft.PowerBI.Dataflows/dataflowid=aec9d012-8df3-4602-9ba9-c3c325993e80;powerbiendpoint=https://api.powerbi.com;workspaceid=7e052c47-7679-42e1-bc24-c16fba27be44. . The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action.

thank you !

[Anonymous]

Thanks for the reply from Sergii24 , please allow me to provide another insight:

Hi, @VickyMarga 
Thanks for reaching out to the Microsoft fabric community forum.

Yes, if you do not find any issues after checking the data source credentials, we recommend that you create a support ticket for free. This way, a dedicated Microsoft engineer will help you resolve the issue.

The link of Power BI Support: https://powerbi.microsoft.com/en-us/support/

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Fabric Community

As Sergii24 mentioned, it would be great if you could continue to share the problem and its root cause or solution after you find it, to help others who encounter similar issues. Looking forward to your response.

 
Of course, if you have any new discoveries or questions, please feel free to get in touch with us.
 

Best Regards,

Leroy Lu

[Sergii24]

Hi @VickyMarga, I'm glad that first suggestion helped to move forward! Unfortunately, I don't have a single answer to why you received the second error. If you can't solve it, I suggest you contact the Microsoft Support team. They'll be able to review the log and guide you on how to resolve the issue.

Once resolved, make sure to share the solution with the community so we all know how to handle it if happends 😉

Thanks and good luck!