Adding the server address to the drive name may be too long.
We’ll add the ability to change drive letter after assigned.
Hi,
this is on windows 10, this not Windows 7, cannot install seadrive-0.3.1.exe, get this error:
…
[2444:2440][2016-10-30T14:20:05]i301: Applying execute package: DokanSetup_redist.exe, action: Install, path: C:\ProgramData\Package Cache\21B92ECC8BFF65F14A53A2B0D8D4C3BDE4260AD7\DokanSetup_redist.exe, arguments: ‘“C:\ProgramData\Package Cache\21B92ECC8BFF65F14A53A2B0D8D4C3BDE4260AD7\DokanSetup_redist.exe” /quiet’
[2444:2440][2016-10-30T14:20:28]e000: Error 0x80070643: Process returned error: 0x643
[2444:2440][2016-10-30T14:20:28]e000: Error 0x80070643: Failed to execute EXE package.
[2650:2654][2016-10-30T14:20:28]e000: Error 0x80070643: Failed to configure per-machine EXE package.
[2650:2654][2016-10-30T14:20:28]i319: Applied execute package: DokanSetup_redist.exe, result: 0x80070643, restart: None
…
I have original Dokan 0.6 installed, but that should work together with newer versions?
You need to uninstall the old version of Dokan manually (which would ask you to reboot the system after uninstallation). We’ll improve this in seadrive client 0.4.
But the reboot is a limitation of the dokan kernel driver which is hard to fix.
Then I have a problem and cannot use seadrive for the moment.
This is an original dokan driver which I still need. Dokany broke compatibility with original version with release 0.8, software not adapted will not work with the newer drivers.
Now, this was not the directly the reason, however, your hint was right,
however the reasons was not the original version, but an “older” 1.0 rc4 version
I had a it installed, but never used as it was not compatible.
I uninstalled and reinstalled manually to the newest 1.0 version (bundle 5000).
now I get a different error, the seadrive installation still wants to install its driver, but an older version bundle 4000
21B92ECC8BFF65F14A53A2B0D8D4C3BDE4260AD7\DokanSetup_redist.exe, arguments: ‘“C:\ProgramData\Package Cache\21B92ECC8BFF65F14A53A2B0D8D4C3BDE4260AD7\DokanSetup_redist.exe” /quiet’
[2638:26A4][2016-10-31T11:25:57]e000: Error 0x80070666: Process returned error: 0x666
[2638:26A4][2016-10-31T11:25:57]e000: Error 0x80070666: Failed to execute EXE package.
[2728:14D0][2016-10-31T11:25:57]e000: Error 0x80070666: Failed to configure per-machine EXE package.
[2728:14D0][2016-10-31T11:25:57]i319: Applied execute package: DokanSetup_redist.exe, result: 0x80070666, restart: None
[2728:14D0][2016-10-31T11:25:57]e000: Error 0x80070666: Failed to execute EXE package.
[2638:26A4][2016-10-31T11:25:57]i351: Removing cached package: DokanSetup_redist.exe, from path: C:\ProgramData\Package Cache\21B92ECC8BFF65F14A53A2B0D8D4C3BDE4260AD7
[2638:26A4][2016-10-31T11:25:57]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{3b463797-108a-4b59-885f-372356e49de1}, resume: None, restart: None, disable resume: No
Yeah, seadrive 0.3.1 is bundled with dokan 1.0.0beta4, so actually you need to uninstall any other version of dokan before installing seadrive. As I mentioned above we’re working to improve this in the upcoming seadrive 0.4 release.
Hi,
just installed SeaDrive couple days ago and run into couple of problems, maybe someone could help clear this out
-
it appears that SeaDrive is not accepting passwords with spaces in it, there’s no such problem with SeaFile client. Found this out just by testing, don’t have any prove of this, just that with password containing space it always said “wrong email or password” and when i changed password without space, everything worked right away.
-
is there a way to keep some files offline accessible? for example, if I have big directory with lot’s of stuff in it, I can access it while I have connection to server (using seadrive client). but once i’m offline there’s no way. tried to sync some folders from all of stuff via seafile but nevertheless the client said synced (green checkbox) files were just not there. I want to use this for part of folders not all but don’t want to ruin all the folder tree (otherwise i could use different approach for each type of files/folders). So will there or is it even possible to implement feature where you could mark some folders and make them offline accessible?
btw using SeaDrive 0.3.1 / SeaFile 6.0.0 / Server 6.0.5 and Win10 computer as client.
Some good news: we have released seadrive client 0.4.0, and now it supports skipping the installation of the bundled dokan driver. This is useful for corner cases like yours, i.e. your system already have dokan driver installed for other programs.
To do this, download the latest seadrive client from https://www.seafile.com/en/download/, then run the seadrive installer from windows command prompt with "nodriver=1", i.e.:
c:\path\to\seadrive-0.4.0.exe nodriver=1
However, it’s still recommended to always use the latest stable version of dokan driver. SeaDrive Client 0.4.0 has dokan driver 1.0.1 (the current latest stable release) bundled with it.
Thanks for reporting, we’ll take a look at it.
It’s a planned feature that may be available in earlier 2017.
I upgraded Dokan myself to the latest version, then installed seadrive .4. The installation was now successful, i.e. it did not throw any error. Unfortunately, there is still something not quit right. In explorer the total and free sizes are correctly reported, 13gb/4.81 GB in my case, however the s: drive does not show any data. the seafile.log says:
…
[11/06/16 11:38:13] sync-mgr.c(2114): All operations of repo Mein Wiki(e72722f2) have been processed.
[11/06/16 11:38:13] sync-mgr.c(362): Repo ‘Mein Wiki’ sync state transition from ‘committing’ to ‘synchronized’.
[11/06/16 11:38:23] utils.c(969): FindFirstFile failed \?\C:\Users\nei\seadrive\data\file-cache\root\https___xxxxx@xxxxx: 3.
…
is there any other log or debug level I can adjust to get more information?
I am using: seafile-server-latest -> seafile-server-6.0.5
seafile gui.log looks fine, except, other another small issue, when quitting via menu in taskbar it throws and error:
…
[11/06/16 12:29:20] app event loop exited with 0
[11/06/16 12:29:20] Unmounting before exit
[11/06/16 12:23:24] failed to unmount : ‘[’ or ‘{’ expected near end of file
[11/06/16 12:23:24] [Daemon Mgr] stopping seadrive daemon
[11/06/16 12:23:44] loaded 1 accounts
[11/06/16 12:23:44] seadrive gui started
[11/06/16 12:23:44] Using disk leter S:
[11/06/16 12:23:44] starting seadrive daemon: seadrive.exe “-d” “C:/Users/nei/seadrive/data” “-l” “C:/Users/nei/seadrive/logs/seadrive.log” “S:”
[11/06/16 12:23:47] Switched to account https://xxxx@xxx efad954
The error should be irrelevant to the issue that libraries are not shown. Can you post more complete seadrive.log after a restart of the client? Can you find error messages in server’s seafile.log?
there is not much more, the complete seadrive.log after restart, server and email changed to xxxxxx,
no other error messages, that’s why I asked for a debug flag or verbose messages above.
seafile.log of client:
[11/07/16 07:42:04] seadrive.c(433): Starting SeaDrive client 0.4.0
[11/07/16 07:42:04] seadrive.c(457): rpc server started.
[11/07/16 07:42:06] repo-mgr.c(2197): switching account to https://xxxxx xxxxx.
[11/07/16 07:42:07] utils.c(969): FindFirstFile failed \?\C:\Users\nei\seadrive\data\file-cache\root\https___xxxxx_xxxxx: 3.
[11/07/16 07:42:08] sync-mgr.c(1020): All repo fs trees are loaded.
[11/07/16 07:42:08] sync-mgr.c(362): Repo ‘_rohos’ sync state transition from ‘synchronized’ to ‘committing’.
[11/07/16 07:42:08] sync-mgr.c(362): Repo ‘_cs_installed’ sync state transition from ‘synchronized’ to ‘committing’.
[11/07/16 07:42:08] sync-mgr.c(2114): All operations of repo _rohos(e6801346) have been processed.
[11/07/16 07:42:08] sync-mgr.c(362): Repo ‘_cs_camera_upload’ sync state transition from ‘synchronized’ to ‘committing’.
[11/07/16 07:42:08] sync-mgr.c(2114): All operations of repo _cs_installed(60a3571f) have been processed.
[11/07/16 07:42:08] sync-mgr.c(2114): All operations of repo _cs_camera_upload(84a1ab60) have been processed.
[11/07/16 07:42:08] sync-mgr.c(362): Repo ‘My Library’ sync state transition from ‘synchronized’ to ‘committing’.
[11/07/16 07:42:08] sync-mgr.c(2114): All operations of repo My Library(847c3293) have been processed.
[11/07/16 07:42:08] sync-mgr.c(362): Repo ‘Mein Wiki’ sync state transition from ‘synchronized’ to ‘committing’.
[11/07/16 07:42:08] sync-mgr.c(362): Repo ‘_cs_installed’ sync state transition from ‘committing’ to ‘synchronized’.
[11/07/16 07:42:08] sync-mgr.c(362): Repo ‘_cs_camera_upload’ sync state transition from ‘committing’ to ‘synchronized’.
[11/07/16 07:42:08] sync-mgr.c(362): Repo ‘My Library’ sync state transition from ‘committing’ to ‘synchronized’.
[11/07/16 07:42:08] sync-mgr.c(2114): All operations of repo Mein Wiki(e72722f2) have been processed.
[11/07/16 07:42:08] sync-mgr.c(362): Repo ‘_rohos’ sync state transition from ‘committing’ to ‘synchronized’.
[11/07/16 07:42:08] sync-mgr.c(362): Repo ‘Mein Wiki’ sync state transition from ‘committing’ to ‘synchronized’.
[11/07/16 07:42:10] utils.c(969): FindFirstFile failed \?\C:\Users\nei\seadrive\data\file-cache\root\https___xxxxx_xxxxx: 3.
[11/07/16 07:42:13] utils.c(969): FindFirstFile failed \?\C:\Users\nei\seadrive\data\file-cache\root\https___xxxxx_xxxxx: 3.
[11/07/16 07:42:18] utils.c(969): FindFirstFile failed \?\C:\Users\nei\seadrive\data\file-cache\root\https___xxxxx_xxxxx: 3.
server seafile log I will check later in detail, first quick view did not show anything at all
on the server:
ccnet.log has a new entry like this. …/common/session.c(398): Accepted a local client
seafile.log has no new entries at all
The bug is fixed in version 0.4.1
thanks, this works now
another issue:
I purposely set up/download limit to 500KB/s, to see when/where downloads ocurr,
a) it seems to my a simple view of the folder already downloads the full content
(but then again, I used ls -l in a cygwin window, maybe thats different from windows explorer)
b) in any case, it downloads at a speed of 3 to 5MB/s, not honoring the limit set in the settings
Hi everyone,
one remark regarding bandwidth usage, not a bug or anything, just one thing thought worth mentioning. as from my experience, when antivirus program decides to scan all local drives and gets to seadrive drive, this is resulting in quite a traffic forwarding to computer, thus generating load on network. Traffic is towards endpoint (Download), i believe that this happens because of AV getting files from server, checking them and moving on. workaround for me was excluding this drive letter from regular scans, leaving scan active only when I open the file. just keep this in mind when putting someone on low level internet connection with automatic AV full scans.
once again I believe that this is in no way a bug or problem with SeaDrive and no need to overcome this from that side, it’s more from AV point.
Hi,
I am running the Seafile Drive Client on a Win10 machine and it was running just fine until I installed some Windows 10 Updates two days ago. ( KB3200970 , KB890830 , KB3118390, KB3202790 , KB3115120)
Since then the Drive Client refuses to start with a popup message: “SeaDrive could not be initialized”
Below I pasted the relevant parts from seadrive.log and seadrive-gui.log
seadrive.log
[11/15/16 10:55:57] seadrive.c(433): Starting SeaDrive client 0.4.1
[11/15/16 10:55:57] seadrive.c(457): rpc server started.
[11/15/16 10:55:57] seadrive.c(479): Can’t install driver
[11/15/16 10:55:57] utils.c(1175): seaf_pipe failed to connect socket: 10038
[11/15/16 10:55:57] job-mgr.c(96): [Job Manager] pipe error: No error
seadrive-gui.log
[11/15/16 10:55:56] loaded 1 accounts
[11/15/16 10:55:56] seadrive gui started
[11/15/16 10:55:56] Using disk leter S:
[11/15/16 10:55:56] starting seadrive daemon: seadrive.exe “-d” “C:/Users/Sean/seadrive/data” “-l” “C:/Users/Sean/seadrive/logs/seadrive.log” “S:”
[11/15/16 10:56:03] seadrive rpc is not ready after 6 retry, abort
[11/15/16 10:56:03] Exiting with error: SeaDrive konnte nicht initialisiert werden
[11/15/16 10:56:08] SeaDrive konnte nicht initialisiert werden
[11/15/16 10:56:08] app event loop exited with 1
[11/15/16 10:56:08] [Daemon Mgr] stopping seadrive daemon
I do not believe it is a problem of the new Dokan version, since the client was already running with it without any problems. I also made sure that I have a network connection because I saw that “Failed to initialize” error before when no network connection was available. Still the Drive Client would not start.
Btw the normal Seafile Client is working just fine as always.
Perhaps it’s related to the Windows updates. Have you tried to re-install the Drive client?
Thanks alot, deinstalling Seafile Drive and Dokan, then installing Seafile Drive 0.4.1 worked!
(The problem started when I was using version 0.4.0 of the drive client and an upgrade to 0.4.1 did not help. It seems Dokan had to be reinstalled)
Is there a way too rename the drive permanently? If I rename it, it changes back to ‘seadrive’ next time that the client is started.
Awesome idea, I love that something like this is in development. It’s basically exactly what I’ve wanted for my own “dropbox” and as an alternative to network shares.
I’d really like to disable the offline syncing, so there is only the Network drive without any local caching. Setting the option “maximum cache size” to 0 does not have the expected result.