Forum Discussion
Post ProdigyConnection failed using a Folder connection in a pipeline
Hi,
the gateway's service runs as a NT SERVICE\username. This user has added to the shared folder with the read and write permissions, both NFTS and share, unsuccessfully.
The internal ping has returned ::1, but the IPv6 network card was disabled.
I've tried to specify the IP returned from Resolve-DnsName powershell command, record A, not the hostname, unsuccessfully.I've solved using an existing file server in the same network having a folder already reachable from a Fabric folder connection; also for this server, the internal ping has returned ::1, the only difference is that it is a server external to the gateway.
Thanks
Hi pmscorca
Thank you for reaching out to the Microsoft Fabric Forum Community.
lbendlin Thanks for the inputs.
In addition to the user's suggestions, please also try the below.
May be the issue is that in Microsoft Fabric, pipelines access the folder using the gateway’s service account rather than the connection credentials. So even if your user has access, the gateway might not.
please try update the On-Premises Data Gateway service to run under a user (for ex, hostname\fabric-user) that has permission to C : \CSV-files, and then restart the gateway.
If there are any deviations from your expectation please let us know we are happy to address.
Thanks.
Post ProdigyHi,
the gateway's service runs as a NT SERVICE\username. This user has added to the shared folder with the read and write permissions, both NFTS and share, unsuccessfully.
The internal ping has returned ::1, but the IPv6 network card was disabled.
I've tried to specify the IP returned from Resolve-DnsName powershell command, record A, not the hostname, unsuccessfully.
I've solved using an existing file server in the same network having a folder already reachable from a Fabric folder connection; also for this server, the internal ping has returned ::1, the only difference is that it is a server external to the gateway.
Thanks
Hi pmscorca
Thanks for the update. glad your issue is resolved. If any of the replies helped, please mark the most useful one as the accepted solution so it can help others facing a similar problem.