Fault 6025: Failed to execute operation

General
1

Hi,

I recently set up Backendless standalone on Windows 2012 VM. Uploading files works fine but listing a directory (one that was created by Backendless using file upload) returns Fault 6025: Failed to execute operation. I checked permissions on the directory and it’s world readable. So, kind of stumped and looking for help.

Thanks.

2

Hi Alex,

Please provide the logs from apps/backendless/logs and also apps/backendless/htdocs/play-logs.

3

Please see attached.

logs.zip (349.01kB)

4

Bad news - unfortunately, the code which handles the listing retrieval just swallows the original error and shows the “Failed to execute operation” one, so the logs aren’t helpful and there’s no way to find the cause now. =/

As a possible way to investigate it, could you please create the application in the online version, upload the same files there and check if the error would persist?

5

Ok, shame. I ported the app from the cloud version to a Windows VM. The exact same code used to work fine on the cloud. I’m finding I have to make several changes that I think are related to the issue. Chief among them is that creating a directory and uploading a file like: /recordings/work/myfile.txt used to resolve to:

https://api.backendless.com//<version name>/files/recordings/work/myfile.text

However, on Windows, this same upload results in a public URL that looks like this;
https://myserver.com/api//<version name>/files/recordings%5Cwork%5Cmyfile.text

As you can see, forward slashes (/) are replaced by () somewhere in the guts of Backendless I assume because this is a Windows machine. Note that the physical directories “recordings” and “work” are created as expected.

Thanks.

6

Thanks, that’s kind of a hint. Is it possible to download a file on Standalone using the link with replaced slashes?

7

Yes, once \ is replaced with %5C, then the file can be downloaded.

8

Does the “listing” method return this error on an initial File repository or only when you add some files?

9

It seems to return the error on anything below “recording”, like “recording/work”. Listing “recording” appears to succeed.

10

Assuming that your “recording” folder lies in a root folder of File Service, I think that the problem is with the inner files and folders uploaded manually. Could you please verify it?

11

There is nothing wrong with the files, unless you mean some kind of file permission which I’m happy to check if you tell me what to look for. Like I said, the file and folders are created fine and the public URLs generated can be used to retrieve the files. Part of the problem may be the munging of the paths due to the backslashes.

12

I mean, the problem is in Backendless File Service when having uploaded the files to some custom directories and then trying to list them.

We shall investigate this use case and notify you about our findings.

13

Ah, gotcha, I understand. That will be great.

14

Hi Alex,

Could you please provide concrete example how to reproduce this issue or contact sales@backendless.com to get more info about support of standalone installation.

Regards,

Denys

15

Hi Denys, please see the previous thread for a detailed description. Assuming you can test on a Windows machine (Window 2012 R2 in my case), you should be able to reproduce the problem from the information provide.