Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
ilhan_berberler
Frequent Visitor

Datamart was not found error between two tenants

I have two tenants. (local and global)

I have a datamart that I created through the application I use on the local tenant. I created a report with this datamart in my local tenant. (Using SQL connection string information) The report is successfully refreshed in the Power BI desktop application and the service in my local tenant.

I published the same report on global tenant. I would set credentials . It was working successfully in the services on my global tenant until March 18, 2024. But after this date, I started getting the following refresh error. (Continues to work successfully in my local tenant)

 


Data source error: {"error":{"code":"DatamartNotFound","pbi.error":{"code":"DatamartNotFound","parameters":{"ErrorMessage":"Datamart was not found"},"exceptionCulprit":1}}} Table: .......
Cluster URI: WABI-EUROPE-NORTH-B-redirect.analysis.windows.net
Activity ID: b1136886-1532-41b0-b97b-aefbb1834d88
Request ID: a7f80cb5-26e3-e254-d72b-30420acbd3b6
Time: 2024-05-22 09:11:17Z
Details
# Type Start End Duration Status Error
1 Data 22.05.2024 12:11:14 22.05.2024 12:11:17 00:00:02.610 Failed (Show)

 

- I opened a support request to Microsoft regarding this issue. The process has been going on for 3 weeks.
- I recreated the datamarts for testing purposes. I tested it by creating a new report on the global tenant. While I refreshed successfully on the desktop, I continued to receive the same error on the service.

Are there others having this problem? I look forward to your help with the solution.

If I can find a solution, I will share it under this post.

1 ACCEPTED SOLUTION
ilhan_berberler
Frequent Visitor

The issue was resolved with a Microsoft update on June 12, 2024

View solution in original post

7 REPLIES 7
ilhan_berberler
Frequent Visitor

The issue was resolved with a Microsoft update on June 12, 2024

jankonas
Frequent Visitor

Our client encountered the same issue with the datamart. It looks like the Microsoft error from the description. If you find a solution through your request, please share it with us. Thank you.

The other day, Microsoft announced that it had made some adjustments regarding the issue and that the problem had been resolved for some users. My problem persists. What about you?

Hi @jankonas 

I think the same way you do.

The first day I got the error, I opened a support request to Microsoft. (March 18) I shared the message in my last post with the Microsoft team. They said they forwarded the issue to the developer teams. But I still haven't received a response from them.

ilhan_berberler
Frequent Visitor

I noticed something and I want to share it with you.
 
I created a datamart on Local Tenant.
 
I created a model in Power BI Desktop with the data in this datamart. I have published it in 5 different tenants whose features you have provided below.
 
Local
Region: Western Europe (Netherlands)
Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net
 
Global
Region: North Europe (Ireland)
Cluster URI: WABI-EUROPE-NORTH-B-redirect.analysis.windows.net
 
Consultant
Region: Western Europe (Netherlands)
Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net
 
Test1
Region: Western Europe (Netherlands)
Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net
 
Test2
Region: Western Europe (Netherlands)
Cluster URI: WABI-WEST-EUROPE-D-PRIMARY-redirect.analysis.windows.net
 
After organizing the credentials on the service in the same way in all tenants, the semantic model was successfully defeated in Local, Consultant and Test1 tenants.
 
I continued to receive the same error regarding the Global and Test2 tenants' own "Cluster URI" information. (Data was not found) Therefore, in the tests I have done so far, we seem to be getting this error in tenants with different "Cluster URI".

Test2 Tenant ErrorDetails
Data source error: {"error":{"code":"DatamartNotFound","pbi.error":{"code":"DatamartNotFound","parameters":{"ErrorMessage":"Datamart was not found"},"exceptionCulprit":1}}} Table: model Company.
Cluster URI: WABI-WEST-EUROPE-D-PRIMARY-redirect.analysis.windows.net
Activity ID: eee37b63-17f5-d77c-e794-0f09e8b56811
Request ID: 01ae8ac7-5bb5-84a8-4238-28f4c2915eba
Time: 2024-05-28 10:11:27Z

 



Global Tenant ErrorDetails

Data source error: {"error":{"code":"DatamartNotFound","pbi.error":{"code":"DatamartNotFound","parameters":{"ErrorMessage":"Datamart was not found"},"exceptionCulprit":1}}} Table: model Company.
Cluster URI: WABI-EUROPE-NORTH-B-redirect.analysis.windows.net
Activity ID: 5416fcd9-ced7-13ab-5b70-ad4aab3f06ee
Request ID: 367dad43-0e0e-5155-245c-8c62fd4b9b14
Time: 2024-05-22 17:59:01Z

Does anyone have any suggestions on this?

 
 

 

 

ilhan_berberler
Frequent Visitor

Hi @v-zhengdxu-msft ,

Thank you very much for taking your valuable time to reply.

"Access Sharing Semantic Model" actually doesn't fit very well with the model I'm talking about. Because I am using Datamart on an external tenant, not a semantic model. Unfortunately, a similar setting on Datamart does not seem possible.

As you said, when I say "Copy SQL Connection String" on Datamart, I see that the SQL Connection String changes.

Old: <tenantid>-<datamartid>.datamart.pbidedicated.windows.net
New: <tenantid>-<datamartid>.datamart.fabric.microsoft.com

However, I can connect to both SQL Connection Strings in both Azure Data Studio and Power BI Desktop applications.

I published my model by editing a new SQL Connection String in my PBIX file. While working on Local Tenant, I still get the same error on Global Tenant.

I wanted to test the report on different tenants. I found a third tenant. (Consultant Tenant) I published my same PBIX file here and defined the necessary credentials on the service. Semantic Model is successfully refreshed on Consultant Tenant.

I compared the tenant settings of Consultant and Global via Admin Panel. I detected 2-3 differences and arranged them to be the same. But my problem still persists in Global Tenant.

v-zhengdxu-msft
Community Support
Community Support

Hi @ilhan_berberler 

 

Ensure that the datamart you're trying to access is correctly configured to be accessible from your global tenant. This includes verifying any cross-tenant data sharing settings and ensuring that your global tenant has the necessary permissions to access the datamart located in your local tenant.

Access shared semantic models in Power BI as a guest user from an external organization (preview) - ...
Since the issue started occurring after a specific date, it's possible that there might have been changes to the credentials or the SQL connection string information. Double-check that the credentials used for the datamart in the global tenant are still valid and have not expired or been changed. Additionally, ensure that the connection string used in the report is correctly pointing to the datamart.
It's also important to review the tenant settings in both your local and global tenants to ensure that there are no restrictions or configurations that might be preventing the datamart from being found. This includes checking for any changes made around the date the issue started occurring.

Tenant settings index - Microsoft Fabric | Microsoft Learn

 

Best Regards

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

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.

Jan25PBI_Carousel

Power BI Monthly Update - January 2025

Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.

Jan NL Carousel

Fabric Community Update - January 2025

Find out what's new and trending in the Fabric community.