{tocify} $title={Table of Contents}
I got this error while trying to set the input folder for
File System connector Trigger in Logic apps, which is intended to trigger the
Logic app which is watching a folder (with help of On premises Data gateway)
Why it happened
Before specifying the folder to watch, we need to create a
connection to File System – below are the details required
If you see, against username I had provided only user name,
whereas it is mentioned to provide Domain\Username
What to do
We need to follow the instruction 😊 , provide the username in correct format. Specify the domain along with the
username (Domain\Username).
In my case, am connecting to folder which is Virtual Machine
and it is not part of any domain, then in this scenario the Machine Name becomes the domain.
After correcting the mistake, I was able to see the folders
under the Root folder
If you have questions or suggestions, feel free to do in comments section below !!!
Do share if you find this helpful .......
Knowledge Sharing is Caring !!!!!!
Learn More about some more Logic App errors
- The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used
- Selected file must be between 1 and 2097152 bytes
- SplitOn property doesn't validate expression at design time
- The workflow with 'Response' action type should not have triggers with 'splitOn' property
- The template language function 'xpath' expects its first parameter to be an XML object
- The template language expression 'xxx' cannot be evaluated because property 'xxx' doesn't exist. Property selection is not supported on content of type 'application/xml'
Tags:
Azure Logic App Error
Hi Mahesh,
ReplyDeleteThanks for your useful blog.
I am facing the same issue while creating a file with extracted file contents. It is successfully accessing Read folder and extract the contents.
Error message: {
"status": 400,
"message": "The requested action could not be completed. Check your request parameters to make sure the path 'C:\\LogicApps-OPDGW-FileSystem\\Out/Customer_output.xml' exists on your file system.\r\nclientRequestId: 44e09de3-a9a8-4d40-8082-93a65c386b0e",
"source": "filesystem-si.azconn-si.p.azurewebsites.net"
}
Using the same File System (API Connector) for both File Read and File Write Action.
I am I missing something ?
I too find this problems but I found way to resolve this using LongPathTool.
ReplyDeleteThanks for this! I have been banging my head for a few hours now and this has helped me
ReplyDeleteHelped me solve my issue, thanks for this !
ReplyDelete