- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Snowflake connector shows Unable to read beyond the end of the stream
Power BI Desktop Version: 2.140.1351.0 64-bit (February 2025)
In PowerQuery, using the Snowflake connector, after a table (or view) is selected and it loads into PowerQuery. When clicking apply or apply and close. The following error appears:
Unable to read beyond the end of the stream
This is due to the new Snowflake connector update after checking the box "Use new Snowflake connector implementation".
The only way of getting this resolved is by unchecking the box or by removing the attribute Implementation="2.0"
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @tomordonezmiron ,
Thank you for the detail information. To resolve this, I recommend first clearing the cache (File > Options and settings > Data Load) and restarting Power BI Desktop to ensure no leftover data is causing the issue. Next, please check the query’s M code in Advanced Editor to make sure the Implementation="2.0" attribute is fully removed this ensures the query doesn’t unintentionally use the newer connector. If the problem persists, try creating a new Power BI file and setting up a basic Snowflake connection to rule out any potential corruption in the original file.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am now seeing the issue that even after disabling the new Snowflake connector implementation. When adding a new query that uses the Snowflake connector and saving from PowerQuery, two popups show up "Waiting", one in PowerQuery and one in Desktop. The first one appears to actually save, while the second one gets stuck and crashes PBI. Basically every time that a change is made in PowerQuery it renders PBI Desktop unusable.
This is the workaround I found that often works:
- Make changes in PowerQuery and click Apply and Close
- From Desktop, then Save.
This is what makes PBI crash:
- From PowerQuery, save
- A popup shows Waiting, it gets stuck there forever, and the only way to exit is to hard close PBI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @tomordonezmiron ,
Thank you for the detail information. To resolve this, I recommend first clearing the cache (File > Options and settings > Data Load) and restarting Power BI Desktop to ensure no leftover data is causing the issue. Next, please check the query’s M code in Advanced Editor to make sure the Implementation="2.0" attribute is fully removed this ensures the query doesn’t unintentionally use the newer connector. If the problem persists, try creating a new Power BI file and setting up a basic Snowflake connection to rule out any potential corruption in the original file.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @tomordonezmiron ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hello @tomordonezmiron ,
I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.
If my response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.
Thankyou.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @tomordonezmiron ,
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @tomordonezmiron ,
Thank you for reaching out to the Microsoft Fabric Community.
The issue you're facing is due to the new Snowflake connector implementation introduced in recent Power BI updates. Since enabling this feature triggers the 'Unable to read beyond the end of the stream' error, the best solution for now is to disable the new connector by unchecking the 'Use new Snowflake connector implementation' option. Alternatively, you can manually remove the attribute Implementation="2.0" from the query in Power Query Advanced Editor.
If you want to keep using the new connector, make sure your Power BI Desktop and Snowflake drivers are fully updated, as Microsoft may release a fix in an upcoming version.
For detailed guidance on managing Snowflake connections in Power BI, you can refer to Microsoft's official documentation: Power Query Snowflake connector - Power Query | Microsoft Learn. Additionally, staying updated with the latest Power BI Desktop releases is advisable, as newer versions may contain fixes for such issues. You can monitor updates here: Connect to Snowflake with Power BI - Power BI | Microsoft Learn.
If the issue persists, consider reporting it through Microsoft’s official support channel as mentioned by @lbendlin .
I hope my suggestions give you good idea, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mmm, was this an automated answer? Your solutions are the same that I put in my original post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @tomordonezmiron ,
The reason my earlier reply seems repeated is because after looking into the issue, it’s still the most reliable way to fix the error. I wanted to confirm that your approach is correct and remains the recommended solution for now.
If you’re interested in trying other options, I’m happy to explore those too but from what I’ve found, your current workaround is the safest choice until a permanent fix is released.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .
