Seadrive on Windows 2019 (TS)

SeaDrive
#1

Hello! I want to run seadrive on Windows 2019 (work as Terminal Server).

I run seadrive-GUI, add account. GUI says that my libraries was synchronized.
But when i try access to drive S: i get error (File S:\ is not accessible)

seadrive_gui.log:
[05/08/20 07:22:01] seadrive gui started
[05/08/20 07:22:01] Using disk letter S:
[05/08/20 07:22:01] starting seadrive daemon: seadrive.exe “-d” “C:/Users/bang/seadrive/data” “-l” “C:/Users/bang/seadrive/logs/seadrive.log” “S:”
[05/08/20 07:22:03] Failed to connect to named pipe: Access is denied.
[05/08/20 07:22:05] Failed to connect to named pipe: Access is denied.

#2

It could be that it does not support the Cloud Files Api which was introduced in Windows 10. Unfortunately I couldn’t find documentation on this from Microsoft.

I think this is the API: https://docs.microsoft.com/en-us/windows/win32/cfapi/cloud-files-api-portal

#3

Can you check seadrive.log? Perhaps it’s some driver issues. 1.0.x version uses third-party driver named Dokany.

#4

seadrive.log contains no errors, only onfo about starting and sync state transition.
But seadrive-gui.log contains many errors:
[05/12/20 04:05:35] failed to write response to shell extension: ??? ??? ???.
[05/12/20 04:05:35] [ext] Failed to read command from extension(), error code 232
[05/12/20 04:05:35] [ext] Failed to read command from extension(), error code 232
[05/12/20 04:05:35] failed to write response to shell extension: ??? ??? ???.
[05/12/20 04:05:35] failed to write response to shell extension: ??? ??? ???.
[05/12/20 04:05:35] [ext] Failed to read command from extension(), error code 232
[05/12/20 04:05:35] [ext] Failed to read command from extension(), error code 232
[05/12/20 04:05:35] failed to write response to shell extension: ??? ??? ???.
[05/12/20 04:05:35] failed to write response to shell extension: ??? ??? ???.
[05/12/20 04:05:35] [ext] Failed to read command from extension(), error code 232
[05/12/20 04:05:35] failed to write response to shell extension: ??? ??? ???.

#5

Do you have any files under logs/dump folder?

You may also wait a little time until SeaDrive 2.0 is production ready. That may solve your problem.

#6

No. this folder is empty. And ok, we’re waiting 2.0.

Please tell me the estimated time for the release of the new version. The roadmap does not contain this information.

#7

SeaDrive 2.0.1 is available, but this is still a pre-production-ready version. I am not a Seafile developer, but I’d say it’s a matter of weeks rather than months.

1 Like