Forum Discussion

pmscorca's avatar
pmscorca
Kudo Kingpin
5 months ago
Solved

Connection failed using a Folder connection in a pipeline

Hi,

I need to read some CSV files deposited on a shared folder created on a server with On-Premise Data Gateway installed.

This folder is named C:\CSV-files, the shared path is \\hostname\CSV-files.

In the Folder connection I've specified:

  • Full path = \\hostname\CSV-files
  • Windows username = hostname\fabric-user

The hostname\fabric-user user has the read and write permissions on the shared folder, both NFTS and share.

I've created the Folder connection successfully, but when I test it on a pipeline I've a such error:

The value of the property '' is invalid: 'Access to hostname is denied, resolved IP address is ::1, network type is OnPremise'. Access to hostname is denied, resolved IP address is ::1, network type is OnPremise.

When I use a similar folder connection by Power Automate with the same parameters and the same ODPG machine, it doesn't occur any errors.

Any suggests to me to solve a such issue, please? Thanks

pipelines
  • pmscorca's avatar
    pmscorca
    4 months ago

    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

     

10 Replies

  • v-priyankata's avatar
    v-priyankata
    Community Support
    5 months ago

    Hi pmscorca 

    Thank you for reaching out to the Microsoft Fabric Forum Community.

     

    Maybe the issue happens because the gateway is resolving the server name (hostname) to ::1 (IPv6 loopback), so it ends up trying to access itself instead of the actual shared folder. To fix this, use an IPv4 path or a fully qualified domain name instead of the hostname, for example, \\192.168.x.x\CSV-files or \\hostname.domain.local\CSV-files. If the gateway is running on the same server as the folder, you can also just use the local path C:\CSV-files. This avoids the incorrect resolution and lets the pipeline access the files properly.

     

    If there are any deviations from your expectation please let us know we are happy to address. 

    Thanks.

    • pmscorca's avatar
      pmscorca
      Kudo Kingpin
      5 months ago

      Hi, thanks for your reply.

      The CSV files to get are deposited on the OPDG server.

      I've already tried to follow your suggests: using \\hostname.domain.local\CSV-files as a full path I've the same error; using C:\CSV-files I've that the access to this folder is not allowed.

      I repeat that when I use a similar folder connection by Power Automate with the same parameters and the same ODPG machine, it doesn't occur any errors.

      Is using the OPDG to deposit CSV files to get a problem as a practice to apply or not?

      Thanks

      • lbendlin's avatar
        lbendlin
        Super User
        5 months ago
        Is using the OPDG to deposit CSV files to get a problem as a practice to apply or not?

        The recommendation is to not do that.  Gateway VMs should not have any other function.  File servers and database servers should reside on separate VMs or physical machines.

  • lbendlin's avatar
    lbendlin
    Super User
    5 months ago

    A gateway ideally is the only service running on that VM.  File shares should reside on separate VMs or physical servers.