Seadrive daemon process crash with code 62097

#1

Hey guy’s!

I facing an issue since a couple of day’s. After update from Seadrive 1.0.7 to 1.0.8 it won’t work anymore. After a couple of seconds I get a dialog with the error that SeaDrive couldn’t be initialized.

Here from the log’s:

seadrive-gui.log:

[12/02/19 13:55:03] loaded 0 accounts
[12/02/19 13:55:03] starting applet rpc service
[12/02/19 13:55:03] applet rpc service started
[12/02/19 13:55:04] seadrive gui started
[12/02/19 13:55:04] Using disk letter S:
[12/02/19 13:55:04] starting seadrive daemon: seadrive.exe "-d" "C:/Users/MagesJoh/seadrive/data" "-l" "C:/Users/MagesJoh/seadrive/logs/seadrive.log" "-L" "de_de" "S:"
[12/02/19 13:55:06] Failed to connect to named pipe: 
[12/02/19 13:55:08] Failed to connect to named pipe: 
[12/02/19 13:55:10] Failed to connect to named pipe: 
[12/02/19 13:55:12] Failed to connect to named pipe: 
[12/02/19 13:55:14] Failed to connect to named pipe: 
[12/02/19 13:55:16] Failed to connect to named pipe: 
[12/02/19 13:55:18] Failed to connect to named pipe: 
[12/02/19 13:55:20] Failed to connect to named pipe: 
[12/02/19 13:55:22] Failed to connect to named pipe: 
[12/02/19 13:55:24] Failed to connect to named pipe: 
[12/02/19 13:55:26] Failed to connect to named pipe: 
[12/02/19 13:55:28] Failed to connect to named pipe: 
[12/02/19 13:55:30] Failed to connect to named pipe: 
[12/02/19 13:55:32] Failed to connect to named pipe: 
[12/02/19 13:55:34] Failed to connect to named pipe: 
[12/02/19 13:55:36] Failed to connect to named pipe: 
[12/02/19 13:55:36] seadrive rpc is not ready after 16 retry, abort
[12/02/19 13:55:36] Exiting with error: SeaDrive konnte nicht initialisiert werden (Transl.: SeaDrive couldn't be initialized.)
[12/02/19 13:55:45] SeaDrive konnte nicht initialisiert werden (Transl.: SeaDrive couldn't be initialized.)
[12/02/19 13:55:45] app event loop exited with 1

[12/02/19 13:55:45] Not unmounting because rpc client not ready.
[12/02/19 13:55:45] [Daemon Mgr] stopping seadrive daemon
[12/02/19 13:55:45] Seadrive daemon process crashed with code 62097

seadrive.log:

[12/02/19 13:55:05] seadrive.c(697): Starting SeaDrive client 1.0.8
[12/02/19 13:55:05] seadrive.c(699): SeaDrive client source code version 840de1e28786f3d791d6126dc04664eec9b9605b
[12/02/19 13:55:05] seadrive.c(725): rpc server started.
[12/02/19 13:55:05] seadrive.c(745): Mount virtual drive as removable disk.

It’s a company PC that is in a domain. But that should not be the issue because it worked properly before.

System: Windows 10 Enterprise 1803 (Build 17134.1130)

What I already did:

  • Un- and reinstalled SeaDrive properly as default user with special elevated rights and as local administrator
  • Changed back to 1.0.7 -> don’t work anymore too
  • Un- and reinstalled the MS VC redist’s.
  • Un- and reinstalled the Dokan library.
  • Used the repair function

And nothing worked. Our Service Desk said that the cancel the support at this point because it’s an issue by the Seafile Co.

If you need some more information’s so please let me know.

#2

Can you see any dump files under logs/dumps?

#3

Unfortunately not, the folder is empty.

Edit:
I started seadrive.exe in a command window and only get this:

C:\Program Files (x86)\SeaDrive\bin>seadrive.exe "-d" "C:/Users/MagesJoh/seadrive/data" "-l" "C:/Users/MagesJoh/seadrive/logs/seadrive.log" "-L" "de_de" "S:"
initializing crash reporter

The drive S: is mounted but the libraries are empty. No error msg, no dump etc.

#4

Do you use Kaspersky AV on this machine?

#5

Nope. Avecto Defendpoint is running and the Windows Defender. But seadrive is allowed in Avecto and Windows Defender is also okay with it.

#6

Can’t do any harm to disable/uninstall Avecto (which I don’t know) to rule out conflicts with their AV engine.

I have seen cases where Kaspersky caused massive conflicts even after having added SeaDrive to the trusted apps.

#7

Unfortunately it’s impossible to disable/uninstall Avecto but this can’t be the issue because it worked before the update.

#8

Your conclusion is incorrect.

#9

Aha and why? 1.0.7 worked properly till the point I updated to 1.0.8. The version of Avecto hasn’t change in the meanwhile. So where is my conclusion incorrect? This is a Workstation Notebook, a device from my company I work and I’m not able to disable/uninstall Avecto. Btw. Avecto is not a AV program. Avecto is rule just the program start and installation rights. The way is free for SeaDrive in Avecto. Windows Defender gives a fuck about SeaDrive. The Firewall is disabled for the company domain.

#10

If you moderate your tone, you will get an answer.

#11

Pfff… keep it. You’re not an important person.

#12

Agreed. I am not an important person.

And you won’t get community support when you bark at community members.

#13

xD Yeah… and you get no friends with such kind of answers. It is as broad as it is long.

My goal is to get support from the dev’s not from the arrogant community members. Community members are mostly not helpful - especially in the German sector.

#14

From your log, it seems that the seadrive GUI cannot communicate with seadrive daemon. Given that 1.0.7 doesn’t work either, I suspect it’s an environment change that cause the issue. Anti-virus software may be the reason that block the communication.

BTW, what’s your username on the Windows desktop?

#15

Ah okay. Because I also tried to start the SeaDrive Daemon separately and then the GUI and it didn’t work either. It’s truly strange. But there is no additional AV software, it’s Windows Defender only.

My username is magesjoh.

#16

Have you tried to disable Windows Defender?

#17

Yes, no change.