Forum Discussion
Semantic Model Won't Refresh: Token Expired On Dataflow (Gen1)
Hi,
I have a dataflow Gen1 with two different excel data sets within it, both of these are drawing information from SharePoint.
The dataflow refreshes fine on-demand, and on the scheduled refresh with no issues. However, any report which uses the dataflow cannot refresh on the Service, reporting a "Token Expired" error. Within the reports, the SharePoint excel data is combined with SQL data which is provided via a database connection and an On-Premises Gateway.
Privacy Levels are set to "None" on all data sources within the app. All my reports refresh fine within the app, so at the moment I'm having to do daily manual refreshes and publish them all to the Service.
I've tried signing in again on all the connections on the Service, I've tried signing in again within the dataflow itself, I've tried deleting the dataflow connection within the model via the app and creating a new one; nothing seems to clear this infuriating Token Expired error.
Has anyone encountered this before? Thanks.
Hi bimotor,
Thanks for reaching out to the Microsoft fabric community forum.It looks like you're experiencing an issue with reports that didn't refreshed in the Power Bi Service and returns a "Token Expired" error even though it is refreshing fine with both on-demand and on a scheduled refresh. You also mentioned that the dataflow and report are set up correctly but still there seems to be an authentication issue preventing the report in the service. It seems the core of the problem comes from the use of authentication tokens that is used for data sources like SharePoint and SQL Server.
These may be the possible reasons for expired token error :
* Check if the authentication token for the SharePoint is expiring.
* Also check if there is a mismatch in token authentication method.
* Check your Power Bi service refresh process as they handled differently than on-premiserefreshes.
If you're still unable to solve the issue, please raise a ticket as suggested by lbendlin.
If this post helps then please mark it as a solution, so that other members find it more quickly.
If you have any other queries, feel free to reach out to community forum for assistance.Thank you.
9 Replies
Hilarious. They can't even find their own error message. Reminds me of the first chapter of "Mostly Harmless" by DNA.
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .Ha - indeed! Thanks, will do. I have a feeling this is going to be something beyond my control. As much as I want to advocate for Power BI within my org, I'm finding issues like this are putting off the budget holders somewhat!
Hi bimotor,
Thanks for reaching out to the Microsoft fabric community forum.It looks like you're experiencing an issue with reports that didn't refreshed in the Power Bi Service and returns a "Token Expired" error even though it is refreshing fine with both on-demand and on a scheduled refresh. You also mentioned that the dataflow and report are set up correctly but still there seems to be an authentication issue preventing the report in the service. It seems the core of the problem comes from the use of authentication tokens that is used for data sources like SharePoint and SQL Server.
These may be the possible reasons for expired token error :
* Check if the authentication token for the SharePoint is expiring.
* Also check if there is a mismatch in token authentication method.
* Check your Power Bi service refresh process as they handled differently than on-premiserefreshes.
If you're still unable to solve the issue, please raise a ticket as suggested by lbendlin.
If this post helps then please mark it as a solution, so that other members find it more quickly.
If you have any other queries, feel free to reach out to community forum for assistance.Thank you.
Thanks for this. I should point out to any readers that my issue resolved itself, but not by following any of the above, although this may work for others. It may be unrelated, but after a Windows password change across our organisation and updating the passwords on our connections in BI, the token error cleared.
Hi bimotor,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help?
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.Hi bimotor,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.Hi Anonymous
Thanks for your reply.
After weeks of not working, it appears to have corrected itself. The only thing I changed my end was my windows password. But I have no idea why that would affect the token, so probably unrelated. Either way, it seems to be working - just wish I knew for certain why!
Hi bimotor,
As your issue has been resolved, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi bimotor,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
