Forum Discussion

MortenBakke's avatar
MortenBakke
Frequent Visitor
2 years ago

Datamart AutoPremiumInvalidIndex

I am recieving the following error when loading the changes in my datamart. I cannot find any other threads on this issue and have no idea why it is occurring. Please help..

"ErrorMessageThe operation failed, likely due to cross-region migration. Please retry the operation."


There is no ongoing migration between regions.

 

2 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi MortenBakke ,

    Please have a try.

    Cause:

    • The migration process may have encountered some internal server errors or timeouts that prevented the operation from completing successfully.
    • The migration process may have encountered some unsupported features or configurations in your Power BI service, such as extensions, backup, or PaaS deployments.
    • The migration process may have failed to find or access the virtual network that your Power BI service is using.

     

    Solution:

    • You can try to retry the operation after some time and see if the error goes away.
    • You may need to uninstall or remove these features or configurations before attempting the migration again.
    • You may need to check the name and location of your virtual network and make sure it matches the expected format.

    Common issues - Azure Database Migration Service | Microsoft Learn

    Frequently asked questions about classic to Azure Resource Manager migration - Azure Virtual Machines | Microsoft Learn

    Move Power BI between regions - Power BI | Microsoft Learn

     

    How to Get Your Question Answered Quickly 

     

    If it does not help, please provide more details.

     

    Best Regards
    Community Support Team _ Rongtie

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • MortenBakke's avatar
      MortenBakke
      Frequent Visitor

      Thanks for getting back to me. However, I am not aware of any current or recent migrations of our Power BI environments that may affect this. 

      It appears more like a bug to me as it will save successfully if I disable load for certain queries. From some debugging it appears to be happening whenever I combine queries reading data from google sheets and a PaaS SQL server.