Data flow Gen 1 to Snowflake

[aj1973]

Hi community,

This morning my Dataflows Gen 1 have stopped refreshing from Snowflake. I tried to connect a new Dataflow to Snowflake and to a PostgreSQL and the result was the same. Is any body having the same issue in East US region? Could this be a new manipulation from Microsoft to push organizations to Fabric and use Dataflows Gen 2 instead!!!

Thanks

[v-veshwara-msft]

Hi @aj1973 ,
We're glad to hear that the issue has been resolved on your end!

To help others who might face a similar problem, could you kindly mark the helpful reply as the accepted solution? This will make it easier for others to find the resolution quickly.

Best regards,
Vinay Kumar.

[v-veshwara-msft · Accepted solution]

Hi @aj1973 ,

Thank you for sharing your experience regarding the connectivity issues with Dataflows Gen 1 to Snowflake.

This was a known issue that has since been resolved by Microsoft. Thanks for confirming that the issue has been resolved on your end.

@klinejordan , @john112 , could you kindly confirm if the issue has been resolved for you as well?
If you are still encountering problems with Dataflows Gen 1 and Gen 2, please try the following steps:

1. Update Data Source Credentials: Re-authenticating the connection by updating your data source credentials can sometimes resolve lingering issues.
2. Create a New Dataflow: Try setting up a new Dataflow connected to Snowflake to see if the issue persists. This can help determine if the problem is specific to the existing Dataflow.

If the issue remains unresolved after following these steps, we recommend raising a support ticket with Microsoft for further investigation.
Please follow this guide to create a support ticket:https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket 

Thank you again for your patience, and please let us know how things progress.

If this post helps, then please mark it as the solution to help the other members find it more quickly.

Best regards,
Vinay.

[john112]

Hi @v-veshwara-msft, this issue is solved for me. However, in my semantic model, I'm getting a new error:

Data source error: Resource Governing: This operation was canceled because there wasn't enough memory to finish running it. Either reduce the memory footprint of your dataset by doing things such as limiting the amount of imported data, or if using Power BI Premium, increase the memory of the Premium capacity where this dataset is hosted. More details: consumed memory 22508 MB, memory limit 22101 MB, database size before command execution 3498 MB. See https://go.microsoft.com/fwlink/?linkid=2159753 to learn more.

I have never gotten this error before. I deleted some tables from our model, with no changes, though not much more memory could have be used vs. the prior refresh, beyond a few additional hours of data. Were there other Power BI changes made that would cause this error?

[v-veshwara-msft]

Hi @john112 ,

Thank you for sharing the details about the resource governing error you're encountering in your semantic model.

Since this issue is unrelated to the original topic of this discussion, we kindly suggest creating a new post in the forum. This will help the community and experts focus specifically on your concern and provide the best possible assistance.

We appreciate your understanding and look forward to supporting you further in your new post!

Best regards,
Vinay Kumar.

[john112]

Getting the same issue. Did you find a solution? I'm having this issue with both Gen1 and Gen2 dataflows.

[aj1973]

It was an issue in MSFT side. Things went back to normal for me.

[klinejordan]

My organization experienced some failures with dataflow gen 1 connecting to any snowflake account in dataflows (power BI desktop and semantic models worked fine) but it was mostly an issue with trying to create/update dataflows connected to snowflake.

We were getting this message any time we tried to create or update a dataflow gen 1 connected to snowflake:

An exception occurred: DataSource.Error: ODBC: ERROR [HY000] [Microsoft][Snowflake] (4) REST request for URL https://xxxxxxxxx.snowflakecomputing.com:443/session/v1/login-request?requestId=125c3d1f-6ab9-4d9a-8... failed: CURLerror (curl_easy_perform() failed) - code=6 msg='Couldn't resolve host name' osCode=12 osMsg='Not enough space'. (Session ID: b86fa151-17f1-425b-bfaf-4e49b7682707, Region: us)

[Dube94_]

Hi everyone, 

I am still experiencing same issues with Power Apps Dataverse dataflows not loading data from Australia/Asia Pacific region. Anyone found an solves for this yet  ? 

[v-veshwara-msft]

Hi @Dube94_ ,

Thank you for sharing the issue you’re experiencing with Power Apps Dataverse Dataflows.
Here are some troubleshooting steps which may help resolve the issue:
1. Ensure that the dataflow is correctly set up to connect to your Dataverse environment in the appropriate region.
2. Clear Data Source Credentials:
      Navigate to the Power Platform Admin Center, and review your connection settings. Clear any stored credentials and re-authenticate the connection to Dataverse.
3. Try creating a new, simplified dataflow to test if the issue is specific to the existing one.

If the issue continues after trying the steps above, I recommend opening a support ticket with Microsoft.

It seems that a similar issue has already been reported in the Power Platform forum. I recommend following the discussion there for updates and potential solutions:https://community.powerplatform.com/forums/thread/details/?threadid=10d4336e-8bbb-ef11-b8e8-6045bddb... 

Hope these help.

Best Regards.