Forum Discussion
Resolver IIImport mode on Warehouse
Hi,
Has anyone managed to create a workable model in TE2 with a connection to a Fabric Warehouse that doesn't fail after refresh? I can't get it wo work. Basically what I did:
- Create a legacy dataconnection in TE2 with this connection string pattern:
Provider=MSOLEDBSQL;Data Source=<sql server name>.database.windows.net;User [email protected];Database=<database name>;Authentication=ActiveDirectoryInteractive
- Imported tables
- Deploy the model to my workspace
- Try to refresh, this fails
I dont want to use Power Query because TE2 helps with schemadrifting, makes everything much easier. I particulary want Import mode because of calculated table support and advanced DAX possibilities.
Hi ray_codex ,
I encountered a similar issue reported in the community that closely aligns with your situation. I suggest reviewing it, as it might offer better clarification and assist you in finding a resolution.
Helpful Reference:
Re: Using Tabular ProviderDataSource with On Premi... - Microsoft Fabric Community
Thank You.
9 Replies
- burakkaragoz
Super User
Hi ray_codex ,
The issue you're hitting is likely due to authentication compatibility between TE2 and Fabric Warehouse when using Import mode. A few things to try:
1. Use the SQL Analytics Endpoint
Instead of the default Fabric Warehouse endpoint, try connecting via the SQL Analytics Endpoint. You can find it in the Fabric UI under the Warehouse settings.
2. Authentication Mode
The ActiveDirectoryInteractive method can be flaky in TE2 depending on the environment. Try switching to:
Authentication=ActiveDirectoryPassword
Or, if you're using a service principal:
Authentication=ActiveDirectoryServicePrincipal
3. Gateway Consideration
If you're deploying the model to a workspace and refreshing from the service, make sure a Data Gateway is configured and mapped to the same source.
4. Alternative: Use TE3
If possible, try using Tabular Editor 3 – it has better support for Fabric and modern authentication flows.
Let me know what error message you get during refresh – happy to help troubleshoot further.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
- ray_codex
This isnt the issue, I can connect and test the connection and it works. But, if I try to refresh the dataset, this happens:
So I can access the table metadata and import the tables, I can see the Warehouse and it's tables and views, but I can't refresh it.
- burakkaragoz
Thanks for the update. If you're able to connect and see the metadata but the refresh fails, it might be related to how the credentials are stored in the dataset settings in the service.
A couple more things to check:
Dataset Credentials in Power BI Service
Go to the dataset settings in the Power BI service and re-enter the credentials manually. Sometimes even if they look fine, re-authenticating helps.Privacy Level Settings
Make sure the privacy level settings for the data source aren't blocking the refresh. Try setting it to "Organizational" if it's not already.Gateway Mapping
If you're using a gateway, double-check that the data source is mapped correctly in the gateway settings and that the credentials there match what you're using in TE2.Check the Error Details
If there's a specific error code or message during refresh, feel free to share it here — that might help narrow it down.
V-yubandi-msftCommunity Support
Hi ray_codex ,
Thanks for reaching out to the Microsoft Fabric Community. In addition to burakkaragoz response, consider this as well'
You're using Tabular Editor 2 to connect to a Microsoft Fabric Warehouse via a legacy MSOLEDBSQL connection string in Import mode. While the connection works for importing metadata, the issue arises when trying to refresh the dataset in Power BI Service.
Some data sources or connection types can be used in Power BI Desktop, but scheduled refresh in the Power BI service isn’t supported.
Reference: Data refresh in Power BI - Power BI | Microsoft Learn
Additionally, the MSOLEDBSQL provider, commonly used in legacy connection strings, is not supported for scheduled refreshes in Power BI Service. This issue has been widely discussed in the other community, with users experiencing similar challenges.
Regards,
Yugandhar.
- V-yubandi-msft
Hi ray_codex ,
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.
- V-yubandi-msft
Hi ray_codex ,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.- ray_codex
This isn't a solution. This is something that in my opinion is not acceptable for a Analytics solution the size of Fabric.
- V-yubandi-msft
Hi ray_codex ,
I encountered a similar issue reported in the community that closely aligns with your situation. I suggest reviewing it, as it might offer better clarification and assist you in finding a resolution.
Helpful Reference:
Re: Using Tabular ProviderDataSource with On Premi... - Microsoft Fabric Community
Thank You.
- V-yubandi-msft
Hi ray_codex ,
If you’ve gone through the shared responses and reference links, and they helped solve your issue, please mark the most helpful reply as the Accepted Solution. It really helps others in the community who might be facing the same kind of problem. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.
Thank you for your understanding and participation.
