Forum Discussion
Can't use Folder connector with on-premises data gateway
Hello,
We are trying to copy a file from a Lakehouse to a folder using "Copy Data" activity in a pipeline.
We are using Folder connector with our on-premise data gateway to connect to destination.
The connection is successfully established.
I can even see the content of the destination folder:
But when I execute the pipeline, I am getting this error:
I usually solve this type of error with enabling this option by editing the connection:
But I can't select this option because it is grayed out.
This connector should work with the on premise gateway as described in the documentation.
https://learn.microsoft.com/en-us/fabric/data-factory/connector-folder-overview
Did I miss something ?
Can anyone point me in the right direction?
Regards
I did find the solution.
I was focusing on the wrong part. The issue was not from the destination connection but from the source connection.
It is the normal behavior to not be able to tick the option to "Allow this connection to be used with gateways" when you configure a connection going through the gateway.
The connection is implicitly allowed, because you are using a gateway to connect to your on prem network!To solve the issue, check if the source connection is allowed to be used with gateway.
Thanks to anyone who tried to help
Regards
5 Replies
- lbendlinSuper User
You need to enable that on the gateway level.
- AzGharbiFrequent Visitor
Thanks for your answer.
I asked our Fabric Admin to enable this option on the gateway level:but i sill have the same issue:
-The checkbox to allow this connection to be used with gateways is still grey when I try to recreate the connection
-The "Copy data" pipeline activity still fails with the same error- lbendlinSuper User
Looks like your gateway only has a single cluster member?!?
Anyway, 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 .
- v-pnaroju-msftCommunity Support
Thankyou, lbendlin for your response.
Hi AzGharbi,
Thank you for the followup.Based on my understanding, the error “6501 some cloud connections are incompatible with gateway” occurs when the connection itself, and not merely the gateway cluster, is not permitted to be used with on‑premises gateways. Even though your Fabric Admin has enabled the option “Allow user’s cloud data sources to refresh through this gateway cluster,” the checkbox within your connection settings remains greyed out. This may be due to one of the following reasons:
The current Folder Connector connection was created as a cloud only connection or under an account that is not the Owner. As a result, the setting “Allow this connection to be used with gateways” cannot be modified.Please follow the steps below, which may help resolve the issue:
- Have the connection Owner either Edit the connection to enable “Allow this connection to be used with gateways,” or recreate a new Folder Connector connection as On‑premises, selecting the same gateway cluster, and ensure the box “This connection can be used with both on‑premises and cloud data gateways” is checked.
- Update your Copy Data activity to use the new or corrected connection, and then re‑run the pipeline.
If the issue persists, we kindly request you to raise a Microsoft Support ticket using the provided link for further investigation:Microsoft Fabric Support and Status | Microsoft Fabric
We hope the information provided helps to resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
- AzGharbiFrequent Visitor
I did find the solution.
I was focusing on the wrong part. The issue was not from the destination connection but from the source connection.
It is the normal behavior to not be able to tick the option to "Allow this connection to be used with gateways" when you configure a connection going through the gateway.
The connection is implicitly allowed, because you are using a gateway to connect to your on prem network!To solve the issue, check if the source connection is allowed to be used with gateway.
Thanks to anyone who tried to help
Regards