Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
I just wanted to leave this for the next guy/gal who may run into this.
I was struggling to understand why one SSAS project was able to deploy a model to my workspace and have a valid Gateway Connection, while another SSAS project deployed successfully, but no Gateway connection.
"You can't schedule refresh for this dataset because the following data sources currently don't support refresh: Discover Data Sources"
After much labor and comparing the two projects, I was able to see that one had a Data Connection string wtih the Provider as SQLNCLI11 and the other (bad) one with SQLNCLI11.1.
Once I removed the ".1", the model deployed to the PBI Workspace successfully with a valid Gateway.
Also, our Microsoft contact said to be sure to use the OLEDB provider going forward.
Hi @mbutler71 ,
Thanks for your sharing.
Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 |
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 2 |