Forum Discussion

CGardn12's avatar
CGardn12
Regular Visitor
4 months ago
Solved

Power BI Server

 

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 — 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 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. 

     

  • 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 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. 

     

  • Hi CGardn12,

    We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.


    tayloramy , donbuser, BA_Pete Thanks for your prompt response.

     

     

     

    Thank you for your patience and look forward to hearing from you.
    Best Regards,
    Prashanth Are
    MS Fabric community support

  • Morning 

     

    Thank you for replying. I've just lef the reports to run as they are after updating all my credentials and automatic refreshes and left them for a few days and it's worked. 

     

    Thanks for everyone's help! 

11 Replies

  • Pegano's avatar
    Pegano
    Regular Visitor

    Had this exact one a few months back. In our case the dataset owner account had been deactivated by IT without anyone noticing, and the refresh kept failing with that same AADSTS700003 error.

     

    Check who owns the dataset (Settings → Dataset owner). If that account is gone or disabled, take over the dataset yourself and re-enter thecredentials. That fixed it for us.

    • CGardn12's avatar
      CGardn12
      Regular Visitor

      Morning 

       

      Thank you for replying. I've just lef the reports to run as they are after updating all my credentials and automatic refreshes and left them for a few days and it's worked. 

       

      Thanks for everyone's help! 

  • 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.

    • BA_Pete's avatar
      BA_Pete
      Super User

      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

      • donbuser's avatar
        donbuser
        Resolver I

        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.

    • CGardn12's avatar
      CGardn12
      Regular Visitor

      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 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. 

     

    • CGardn12's avatar
      CGardn12
      Regular Visitor

      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 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. 

     

  • v-prasare's avatar
    v-prasare
    Community Support

    Hi CGardn12,

    We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.


    tayloramy , donbuser, BA_Pete Thanks for your prompt response.

     

     

     

    Thank you for your patience and look forward to hearing from you.
    Best Regards,
    Prashanth Are
    MS Fabric community support

    • CGardn12's avatar
      CGardn12
      Regular Visitor

      Morning 

       

      Thank you for replying. I've just lef the reports to run as they are after updating all my credentials and automatic refreshes and left them for a few days and it's worked. 

       

      Thanks for everyone's help!