Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. 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.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
11 | |
6 | |
4 | |
2 | |
2 |
User | Count |
---|---|
4 | |
3 | |
3 | |
3 | |
3 |