We’re pleased to announce that SeaDrive 2.0.2 is available. This version fixes most major issues reported by early users for previous versions. Although we still mark it as “beta”, it’s ready for daily usage. If no major issues are reported, we’ll mark it production ready. Both Windows and Mac versions are available for download on seafile website.
We switch back to WiX for packaging, which is more flexible. The previously installed 2.0.1 will not be automatically uninstalled when installing 2.0.2. Since SeaDrive 2.0 is an msi package, which is different from 1.0.x (.exe format), it’s not possible to automatically remove 1.0.x version when installing 2.0. We’ll investigate ways to auto remove 1.0.x version in future releases.
The virtual drive will not be unmount when exiting SeaDrive or switching to another Seafile account (if you logged into multiple Seafile accounts). This is to prevent Windows from removing the placeholder files under the virtual drive, which can cause unwanted removal of files. This behavior is similar to OneDrive. You can still see the placeholder files even if you exit OneDrive. But you cannot open an uncached file.
Does anyone else have issues with sync state shown is not what it is supposed to be? I marked a big nested structure (12k files) with ‘always keep on devices’, but sync state never reaches ‘full pinned’. Some folders always stay at ‘placeholder’ state even though all their content is marked ‘full pinned’.
There were no active downloads. But I noticed the Windows Search Indexer being active for quite a while. I disabled it and retry later again.
Also I am having issues with ‘dektop.ini’ files being automatically generated by Windows in some folders. Is there some kind of exclude list?
[05/26/20 07:51:00] Generating conflict file desktop (SFConflict …@… 2020-05-26-07-51-00).ini in repo ***.
[05/26/20 07:51:00] CfCreatePlaceholders failed on C:\Users\Axel\SeaDrive\7d6e74d3/Meine Bibliotheken/Videos/Captures/desktop.ini: Eine Datei kann nicht erstellt werden, wenn sie bereits vorhanden ist.
After encountering some unpleasant surprises with SeaDrive 2.0.1, I have (almost) only good things to say about version 2.0.2: The installation is comfortable, the autostart works as it should, it seems to be a lot faster than 2.0.1 and the “always keep on this device” feature is great.
I came across one oddity though on my computer and a similar observation on another machine makes me believe that it is a more general issue.
This is what the navigation bar in my Windows Explorer looks like:
Hi! I have just updated a coworker’s Seadrive to 2.0.2, and now when I try to start it, we get following error:
(“Internal error: error communicating with seadrive service”)
I uninstalled seadrive, removed both seadrive folders in user’s profile, reinstalled, logged in, and as soon as it starts to download the files list, this error appears. Seafile in browser works fine. Any ideas where to look?
I came across another small problem in SeaDrive 2.0.2: When switching languages, the category folders “My library”, “Shared with me”, … can become duplicated.
A similar problem was reported in 2.0.0 and then fixed in 2.0.1. I guess the problem reemerged because placeholder files in the virtual drive are not deleted any more.
Have the same issue when starting Seadrive as user “hydrandt”.
The log file for seadrive-gui shows: “Failed to connect to named pipe: Access is denied”. - And after 15 attempts it stops the seadrive daemon.
Any idea where seadrive cannot connect to so I can try to fix the access rights?
Seadrive-Log:
[05/28/20 16:33:02] Starting SeaDrive client 2.0.2
[05/28/20 16:33:02] rpc server started.
[05/28/20 16:33:02] Failed to create named pipe: Access is denied.
Seadrive-Gui Log:
[05/28/20 16:33:01] starting applet rpc service
[05/28/20 16:33:01] applet rpc service started
[05/28/20 16:33:02] seadrive gui started
[05/28/20 16:33:02] Using cache directory: C:/Users/xxx/seadrive_root
[05/28/20 16:33:02] starting seadrive daemon: seadrive.exe “-d” “C:/Users/xxx/seadrive/data” “-l” “C:/Users/xxx/seadrive/logs/seadrive.log” “C:\Users\xxx\seadrive_root”
[05/28/20 16:33:04] Failed to connect to named pipe: Access is denied.
…
[05/28/20 16:33:34] Failed to connect to named pipe: Access is denied.
[05/28/20 16:33:34] seadrive rpc is not ready after 16 retry, abort
[05/28/20 16:33:34] Exiting with error: SeaDrive failed to initialize
[05/28/20 16:33:41] SeaDrive failed to initialize
[05/28/20 16:33:41] app event loop exited with 1
[05/28/20 16:33:41] Not unmounting because rpc client not ready.
[05/28/20 16:33:41] [Daemon Mgr] stopping seadrive daemon
Do you still have 1.0.x client running? Or have you tried to restart the computer? Looks like some other process is opening the same named pipe, so the new seadrive client cannot access it.
In the end my colleague was able to resolve the problem by:
Uninstall Seadrive
Delete all Seadrive files in user’s home directory
Delete all Seadrive keys in the Windows registry
Install Seadrive again
Happily syncing again!
In the seadrive gui log, there was:
[05/28/20 17:26:21] loaded 0 accounts
[05/28/20 17:26:21] starting applet rpc service
[05/28/20 17:26:21] applet rpc service started
[05/28/20 17:26:22] seadrive gui started
[05/28/20 17:26:22] Using cache directory: C:/Users/annie/seadrive_root
[05/28/20 17:26:22] starting seadrive daemon: seadrive.exe "-d" "C:/Users/annie/seadrive/data" "-l" "C:/Users/annie/seadrive/logs/seadrive.log" "-L" "zh_cn" "C:\\Users\\annie\\seadrive_root"
[05/28/20 17:26:25] Unable to get config value download_limit: Config not exists
[05/28/20 17:26:25] Unable to get config value upload_limit: Config not exists
[05/28/20 17:27:05] Unable to switch to account https://seafile.ourdomain.com email@address.com ef603d8 : '[' or '{' expected near '@'
[05/28/20 17:27:05] Seadrive daemon process exited normally with code -529697949
[05/28/20 17:27:10] Trying to restart seadrive daemon
[05/28/20 17:27:10] starting seadrive daemon: seadrive.exe "-d" "C:/Users/annie/seadrive/data" "-l" "C:/Users/annie/seadrive/logs/seadrive.log" "-L" "zh_cn" "C:\\Users\\annie\\seadrive_root"
[05/28/20 17:27:13] Unable to switch to account https://seafile.ourdomain.com email@domain.com ef603d8 : '[' or '{' expected near '@'
[05/28/20 17:27:13] Failed to connect to named pipe: The system cannot find the file specified.
[05/28/20 17:27:14] Failed to connect to named pipe: The system cannot find the file specified.
[05/28/20 17:27:14] Failed to connect to named pipe: The system cannot find the file specified.
[05/28/20 17:27:15] Failed to connect to named pipe: The system cannot find the file specified.
[05/28/20 17:27:15] Failed to connect to named pipe: The system cannot find the file specified.
[05/28/20 17:27:16] Failed to connect to named pipe: The system cannot find the file specified.
[05/28/20 17:27:16] Failed to connect to named pipe: The system cannot find the file specified.
[05/28/20 17:27:16] Exiting with error: 内部错误: 与 seadrive 服务通信时出错
[05/28/20 17:27:16] Seadrive daemon process exited normally with code -529697949
[05/28/20 17:27:21] Trying to restart seadrive daemon
No previous version running. Version 2.0.1 was running fine. Only 2.0.2. does not work anymore. I have the seafile client running in parallel (but stopping the client did not help). And yes, many times rebooted without any change.
No previous version running. Version 2.0.1 was running fine. Only 2.0.2. does not work anymore. I have the seafile client running in parallel (but stopping the client did not help). And yes, many times rebooted without any change.
I had the same problem. Your version of WIndows 10?
-----
/20 10:07:45] All events are processed for repo c315c276-3604-4603-b699-e2b2dfcad309.
[05/28/20 10:07:45] Repo 'Perso' sync state transition from 'committing' to 'synchronized'.
[05/28/20 10:08:14] [obj backend] Failed to rename C:/Users/Utilisateur/seadrive/data\storage\fs/c315c276-3604-4603-b699-e2b2dfcad309/8a/70b43f85d35f85fb9579e7c3ca457513b667cc: Permission denied.
[05/28/20 10:08:14] [obj backend] Failed to write obj c315c276-3604-4603-b699-e2b2dfcad309:8a70b43f85d35f85fb9579e7c3ca457513b667cc.
[05/28/20 10:08:14] Failed to write fs object 8a70b43f85d35f85fb9579e7c3ca457513b667cc in repo c315c276.
[05/28/20 10:08:14] Failed to get file object 8a70b43f85d35f85fb9579e7c3ca457513b667cc from server https://seafile.abc.com.
[05/28/20 10:08:14] CfHydratePlaceholder failed on C:\Users\Utilisateur\seadrive_root\a6682be4\My Libraries/PA1\R2017b/create_acct_email_ver.png: **The cloud operation was unsuccessful.**
I had messages like this “The cloud operation was unsuccessful”.
Seadrive should try to resynchronize the files that have had this error.
It’s very tedious to have to search for unsynchronized files in a tree structure and do it manually
Small precision, the Parent folder is configured in “Always keep on this device”
