Accessing Shared Folder on Azure VM from ISE

Syed Sajid Hussain 41 Reputation points
2020-09-21T17:27:39.72+00:00

Hi Guys,

I have done the following setup.

  1. ISE setup in a VNet with Access endpoint 'Internal'
  2. Added File System Connector ISE version (by default it isn't added to ISE)
  3. Added a Private DNS Zone and linked it to the same VNet (so we can have dns/hostname resolutions)
  4. To test connectivity from Logic Apps to another service in VNet, I created a VM in the same VNet but in a different subnet
  5. Shared a folder on that VM, which gave me the shared path like this \MachineName\SharedFolder
  6. Came to Logic App and selected 'File System (ISE)' Connector and created a connection, gave the user name same as the admin user of VM
  7. Then when trying to do any operation, like Get Files, Create File when I try to select a folder, I always get this error.

BadGateway. Client request id: 'E2CE0B74-4E52-4EB5-A14C-ABAC35DE4ABD'

26187-image.png

  1. NSG on the VM is set to allow all Inbound and Outbound traffic from VM
  2. To check whether it's just an issue with Logic App or in general, I created another VM in the same VNet but a different subnet and tried to access the shared folder from there using the same path and it worked without any issues

I am really running out of options of what could be wrong here, please guide me.

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,870 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Mike Urnun 9,756 Reputation points Microsoft Employee
    2020-09-24T05:03:56.95+00:00

    Upon reaching out to the OP, @Syed Sajid Hussain , privately, we were able to get more specific info (details that makeup ARM Resource ID) and took a closer look with the help of our support team. The support team determined that the root cause originated from an unresolved DNS hostname and provided the following response:

    This looks to be a DNS issue. The LA was unable to resolve the file server name. You can log into a machine in the same vnet and do a nslookup to see whether you can resolve the file server name. You might be able to work around the issue with IP address instead.

    @Syed Sajid Hussain I hope the above helps bring clarity and gets you a step closer in overcoming this issue. If you continue to run into this error, please let me know and we'd be happy to provide further assistance.

  2. RamprasadThirumalai 1 Reputation point
    2021-08-13T10:04:48.577+00:00

    Do we have a resolution to this item? I am stuck with the same error and I have no idea how to resolve or how was it resolved?

    0 comments