On-Prem Data Gateway default local path?

[kbelitski]

Having trouble using an On-premises Data Gateway to copy files from SharePoint Online to my local server.  

I have an existing connection setup that works, finding files that are copied through a local script to a "C:\SSC\" folder daily, to use Power Automate (through the Data Gateway) to move those files up to SharePoint Online.

I am trying to create a new Power Automate flow that also copies files from a SharePoint Online Document Library down to a different path on this same server (D:\Works\).  

Setting up new connectors in Power Automate, I continously get failures running the flow that reference "Action 'Create_file' failed" due to "status 403 the credentials for this connection do not have access to the path - try using a different location or account".  

My flow is created using a domain service account.  My Data Gateway Administrator is the same service account.  I have file share permissions all setup for full read/write to the D:\Works path and can manually navigate to the path and manipulate files when signing into the server using the service account.  

I have tried different folder paths in my Power Automate Flow (create file action) to test, and they all fail with the same error. UNC is the one I would expect to work:  \\SRVservername\Works   

I have also tried sharing out the folder on the server and \\SRVservername\Works$  still fails with the same error.

Trying all the connectors available through a new Power Automate Flow, I did stumble on one that did not immediately error out.  Testing that connector I was able to save a file to C:\SSC\SRVservername\Works\, even though I had still only specified 

\\SRVservername\Works  in the flow folder path.  The connector is my existing, original, working connector, which apparently defaults somehow to C:\SSC???  

How can I get a second connector setup using this same gateway and have it work, but to a different local server path?  

Where can I find this default path "c:\SSC" that is specified and would I even want to consider changing it if my original connector is working as expected?

What else should I be asking to help resolve this situation?  

[Anonymous]

HI @kbelitski 

So when you use Power Automate to copy files from “C:\SSC\” to SharePoint Online, it works fine, but when you use Power Automate to copy files from SharePoint Online to local, there is a problem. Even if you have full permissions to that local folder, it doesn't work, right? Then you tested copying files from SharePoint Online to “C:\SSC\” and it worked fine, which means the problem is in the newly configured connector, right?

Best Regards,
Community Support Team _ Ailsa Tao