Unable to delete files when using the File Reader smb protocol

[erandavid]

Hi,
We have a very simple channel with a File Reader source which scans a network folder using the smb protocol for suitable name files to process.
The file reader gets the following error when trying to delete the file after it has been processed, and so is picked up again on the next poll:
ERROR (com.mirth.connect.connectors.file.FileReceiver:435): Error processing file in channel: com.mirth.connect.connectors.file.FileConnectorException: Error deleting file from [smb:https://...

The "Everyone" group has full control on this Windows share folder so it doesn't seems to be a permissions issue.

Did anyone encounter such an issue?

[jonbartels]

Is there more information in that stack trace? Further down the stack trace there may be a more specific cause that would help solve the issue. Anything in mirth.log? (Use code tags when posting stack traces please!)

Is the file path shown in the smb:https:// URL correct? Could this be something like a computed file path that isn't substituted properly?

[erandavid]

I tried adding a double-slash before the file name but same results...
There is nothing on the Windows logs.
BTW: I am able to delete the file manually with the user provided in the smb dialog. That's another indication that it's not a permission issue.

[tonygermano]

It's only possible to move files to another location on the same file system.

[pacmano1]

Meaning you are trying to move from a remote file system to a local file system. You can do that if you mount the file systems locally to the mirth server.

[tippenring]

I believe local system does not have access to network paths. Running the service as a different user with network access should be able to access network resources.

[tonygermano]

I almost brought that up, too, but the Windows service account doesn't matter since it is using the credentials added in the File Reader as shown in the screenshot.

Even though it's not relevant to this issue, Local System does have network access (it's Local Service that does not,) but it accesses the network as the Computer Account the machine used to join the domain, and there's a good chance that permission was not given to the server itself.