MuleSoft · File Connector
FILE:ILLEGAL_PATH
FILE:ILLEGAL_PATH means a File Connector operation was given a path that does not exist while Create parent directories is set to false. Correct the path, or let the operation create the missing directories.
VerifiedLast verified
01Error text
Error type: FILE:ILLEGAL_PATH02Likely causes
- The
createParentDirectoriesproperty is set tofalseand neither the target path nor its parent exists. - The path is built from a property or expression that resolves to a different location than you expect in this environment.
03How to fix it
- Log the path the operation resolves to, and check that it exists on the machine or worker the app runs on.
- For Write, Copy and Move, set Create parent directories to
trueso missing directories are created. - Handle the failure with an error handler of type
FILE:ILLEGAL_PATHwhen the path comes from input you do not control.
iNotes
Related File Connector types: FILE:FILE_ALREADY_EXISTS (the target file exists and overwrite is false) and FILE:ACCESS_DENIED (the user lacks permission for the action).
04Official documentation
→Related errors
- OS:KEY_NOT_FOUNDOS:KEY_NOT_FOUND means an Object Store Retrieve or Remove operation asked for a key that has no value in the store. Check that the key exists first with Contains, or give Retrieve a default value.
- DB:CONNECTIVITYDB:CONNECTIVITY covers several possible connection problems in Database Connector, including a poorly configured connection, no response from the database and a lost connection. Check the connection configuration first, then add a reconnection strategy.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer