Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
All of my Power Bi reports are showing this message and I don't know how to fix this. All of my automatic refreshes have stopped due to this and I don't know how to fix this. Any advice?
Hi @CGardn12,
That last screenshot you posted is a different error than the first one. THis is a data problem.
SOmewhere you have something that isn't a date that Power BI is trying to parse into a date.
This will require that you look at the data sources and transformations in the powerquery section of the report to see what table/source is causing that error, and then correct it.
Proud to be a Super User! | |
Hi @CGardn12,
We saw this at my org when the account that owned the model was deactivated.
Check who owns your model, and ensure that that account still exists. You may need to take over the model and reset all the connections, and then your report should refresh again.
Proud to be a Super User! | |
Hello
Thanks for your reply. I've left the reports for the weekend, but I came back to work with emails letting me know that my reports haven't refreshed.
I've had a look and it's now showing this:
Would I be best doing as you recommneded for this issue and see who owns the Model and re-set all the connections and then set them off on a refresh?
Thank you!
Hi — this looks like it might be related to an authentication or connection issue rather than something wrong with your reports themselves.
From the screenshot, the key part is:
“DMTS_OAuthTokenRefreshFailedError” and “Device object was not found in the tenant”
That usually points to one of these:
🔑1. Credentials / Authentication Issue
Go to Power BI Service → Dataset Settings
Check Data source credentials
Try re-authenticating the connection
Sometimes tokens expire or get invalidated, especially with OAuth connections.
🔐2. Gateway / Tenant / Permission Issue
If you're using a gateway:
Check that the gateway is online
Verify the data source is still mapped correctly
Confirm your account still has access to the data source
The “device not found in tenant” message can happen if:
Credentials changed
Account permissions changed
Tenant/device registration issues (especially in enterprise environments)
🔄3. Try a Manual Refresh
Trigger a manual refresh from the Service
Sometimes this helps re-establish the connection and gives a clearer error message
🧠 Quick Question That Might Help Narrow It Down
Did anything recently change in your environment?
Password reset
MFA/security update
Gateway/server changes
That error often shows up right after something like that.
💡Big Picture
Since all reports are affected at once, it’s very likely:
👉a shared connection or authentication issue, not individual report problems
Hope that helps point you in the right direction — let me know what you find 👍
Note: I used AI to help structure my response, but the solution is based on my own experience and has been reviewed for accuracy.
Hi
Thanks for your reply.
I'm not using Gateway to build or run reports ETC.
I have updated my Credentials multiple times, which has not worked. I've updated the data source for all my resports and nothing has changed for a connection. I have updated my app multiple times and after doing all these, the message is still the same.
Any other ideas?
Thanks
Hi @donbuser ,
Please provide acknowledgement that you have checked and validated your answer when copying and pasting from ChatGPT.
Unfortunately, a number of users of late are just dumping AI answers here without actually checking whether they are relevant, make sense, or actually work. I'm sure that's not the case here, but it would be helpful for all involved to know whether a human has been involved in the process at all.
Thanks,
Pete
Proud to be a Datanaut!
Hi Pete,
That’s a fair point — I’ve seen the same trend and agree it can become an issue when responses aren’t validated.
In this case, I’m basing my answer on experience troubleshooting similar Power BI issues, and I always try to sanity-check suggestions before posting to make sure they’re relevant and actionable.
Appreciate you calling that out — it’s important for keeping the quality of the forum high.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 8 | |
| 6 | |
| 6 | |
| 6 | |
| 5 |