infeo
May 16, 2019, 2:27pm
2
Installing Dokany does not change anything since you are using WebDAV as the unlocked vault provider. (; You can change this in the settings.
Otherwise, there are a ton of posts about Systemerror 67 regarding crpytomator:
opened 01:37PM - 31 Mar 16 UTC
closed 10:05PM - 29 Nov 16 UTC
type:upstream-bug
os:windows
I upgraded to version 1.0.3 today and now I cannot access my vault. Here is the … logfile with the error:
```
2016-03-31 09:33:00,286 INFO [SingleInstanceManager:299] no running instance found
2016-03-31 09:33:01,296 DEBUG [SingleInstanceManager:325] InstanceManager bound to port 52942
2016-03-31 09:33:01,434 DEBUG [WelcomeController:151] Current version: 1.0.3, lastest version: 1.0.3
2016-03-31 09:33:40,819 INFO [WebDavMounterProvider:39] Using WindowsWebDavMounter
2016-03-31 09:33:40,833 INFO [log:186] Logging initialized @40939ms
2016-03-31 09:33:40,886 INFO [Server:345] jetty-9.3.3.v20150827
2016-03-31 09:33:40,906 INFO [ContextHandler:775] Started o.e.j.s.ServletContextHandler@741ab977{/,null,AVAILABLE}
2016-03-31 09:33:40,912 INFO [ServerConnector:270] Started ServerConnector@5322abd3{HTTP/1.1,[http/1.1]}{0.0.0.0:50502}
2016-03-31 09:33:40,913 INFO [Server:397] Started @41021ms
2016-03-31 09:33:40,913 INFO [WebDavServer:79] Cryptomator is running on port 50502
2016-03-31 09:33:41,115 INFO [WebDavServer:117] Servlet available under http://localhost:50502/data
2016-03-31 09:33:41,119 INFO [AbstractWebdavServlet:169] authenticate-header = Basic realm="Jackrabbit Webdav Server"
2016-03-31 09:33:41,119 INFO [AbstractWebdavServlet:174] csrf-protection = null
2016-03-31 09:33:41,120 INFO [AbstractWebdavServlet:181] createAbsoluteURI = true
2016-03-31 09:33:41,120 INFO [ContextHandler:775] Started o.e.j.s.ServletContextHandler@12ba5742{/data,null,AVAILABLE}
2016-03-31 09:33:41,148 DEBUG [CommandResult:85] Command execution finished. Exit code: 0
Output: The operation completed successfully.
2016-03-31 09:33:41,172 DEBUG [CommandResult:87] Command execution finished. Exit code: 2
Error: System error 53 has occurred.
The network path was not found.
2016-03-31 09:33:41,173 ERROR [UnlockController:301] Decryption failed for technical reasons.
org.cryptomator.frontend.FrontendCreationFailedException: org.cryptomator.frontend.CommandFailedException: Command execution failed. Exit code: 2
# Output:
# Error:
System error 53 has occurred.
The network path was not found.
at org.cryptomator.ui.model.Vault.activateFrontend(Vault.java:137) ~[Cryptomator-1.0.3.jar:1.0.3]
at org.cryptomator.ui.controllers.UnlockController.unlock(UnlockController.java:280) ~[Cryptomator-1.0.3.jar:1.0.3]
at org.cryptomator.ui.controllers.UnlockController.lambda$didClickUnlockButton$0(UnlockController.java:274) ~[Cryptomator-1.0.3.jar:1.0.3]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_74]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_74]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_74]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_74]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_74]
Caused by: org.cryptomator.frontend.CommandFailedException: Command execution failed. Exit code: 2
# Output:
# Error:
System error 53 has occurred.
The network path was not found.
at org.cryptomator.frontend.webdav.mount.command.CommandResult.assertOk(CommandResult.java:98) ~[frontend-webdav-1.0.3.jar:?]
at org.cryptomator.frontend.webdav.mount.command.CommandRunner.execute(CommandRunner.java:69) ~[frontend-webdav-1.0.3.jar:?]
at org.cryptomator.frontend.webdav.mount.command.Script.execute(Script.java:42) ~[frontend-webdav-1.0.3.jar:?]
at org.cryptomator.frontend.webdav.mount.WindowsWebDavMounter.mount(WindowsWebDavMounter.java:91) ~[frontend-webdav-1.0.3.jar:1.0.3]
at org.cryptomator.frontend.webdav.mount.WindowsWebDavMounter.mount(WindowsWebDavMounter.java:71) ~[frontend-webdav-1.0.3.jar:1.0.3]
at org.cryptomator.frontend.webdav.WebDavFrontend.mount(WebDavFrontend.java:48) ~[frontend-webdav-1.0.3.jar:1.0.3]
at org.cryptomator.ui.model.Vault.activateFrontend(Vault.java:134) ~[Cryptomator-1.0.3.jar:1.0.3]
... 7 more
2016-03-31 09:33:43,813 DEBUG [Server:416] doStop org.eclipse.jetty.server.Server@3516fcf3
2016-03-31 09:33:43,814 DEBUG [Server:438] Graceful shutdown org.eclipse.jetty.server.Server@3516fcf3 by
2016-03-31 09:33:43,819 INFO [ServerConnector:310] Stopped ServerConnector@5322abd3{HTTP/1.1,[http/1.1]}{0.0.0.0:50502}
2016-03-31 09:33:43,820 INFO [ContextHandler:885] Stopped o.e.j.s.ServletContextHandler@741ab977{/,null,UNAVAILABLE}
2016-03-31 09:33:43,822 INFO [ContextHandler:885] Stopped o.e.j.s.ServletContextHandler@12ba5742{/data,null,UNAVAILABLE}
2016-03-31 09:33:43,824 DEBUG [Cryptomator:102] Shutting down
```
Any ideas?
opened 04:40PM - 28 Jan 18 UTC
closed 10:32PM - 31 Jan 18 UTC
## Issue Checklist
I made sure that I:
- searched existing (and closed) issu… es: **Yes** (some exists which "might" have some relations)
- searched the knowledge base: **Yes**
- have read the support guide: **Yes**
- have read the contribution guide: **Yes**
- have read the code of conduct: **Yes**
## Basic Info
I'm using Windows 7 in version: 64-bit Professional
I'm running Cryptomator in version: 1.3.3
## Description
Hallo,
gerade wollte ich seit etwas längerer Zeit auf meine mit Cryptomator verschlüsselten Daten zugreifen.
Ich wurde auf ein Update auf Version 1.3.3 hingewiesen und habe dieses installiert.
Nun kann ich leider kein einziges Vault mehr öffnen, da ich nur noch die Meldung bekomme: “Verbinden des Laufwerks fehlgeschlagen”.
Ich schreibe nun hier, da im offiziellen Cryptomator Forum seit mehr als 10 Tagen nicht auf mein Hilfegesuch reagiert wird.
## Attachments (optional)
Hier die Log-Datei:
```
16:33:59.169 [main] INFO org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.3.3 on Windows 7 6.1 (amd64)
16:33:59.564 [JavaFX Application Thread] INFO o.c.launcher.MainApplication - JavaFX application started.
16:33:59.643 [JavaFX Application Thread] INFO o.c.common.settings.SettingsProvider - Failed to load settings, creating new one.
16:34:00.018 [JavaFX Application Thread] INFO org.cryptomator.jni.JniModule - loaded WinFunctions.dll
16:34:00.733 [pool-4-thread-1] INFO o.c.ui.controllers.WelcomeController - Current version: 1.3.3, lastest version: 1.3.3
16:34:22.071 [JavaFX Application Thread] INFO org.eclipse.jetty.util.log - Logging initialized @-1ms to org.eclipse.jetty.util.log.Slf4jLog
16:34:22.109 [JavaFX Application Thread] INFO o.c.frontend.webdav.WebDavServer - Binding server socket to 127.0.0.1:42427
16:34:22.127 [JavaFX Application Thread] INFO o.e.jetty.server.AbstractConnector - Started ServerConnector@68853224{HTTP/1.1,[http/1.1]}{127.0.0.1:42427}
16:34:22.247 [JavaFX Application Thread] INFO o.c.k.WindowsProtectedKeychainAccess - Creating new keychain at path C:\Users*Zensiert*\AppData\Roaming\Cryptomator\keychain.json
16:34:23.133 [pool-3-thread-1] INFO o.c.common.settings.SettingsProvider - Settings saved to C:\Users*Zensiert*\AppData\Roaming\Cryptomator\settings.json
16:34:27.224 [pool-4-thread-1] INFO org.eclipse.jetty.server.Server - jetty-9.4.7.v20170914
16:34:27.248 [pool-4-thread-1] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@5f2d489a{/,null,AVAILABLE}
16:34:27.248 [pool-4-thread-1] INFO org.eclipse.jetty.server.Server - Started @-1ms
16:34:27.248 [pool-4-thread-1] INFO o.c.frontend.webdav.WebDavServer - WebDavServer started.
16:34:27.286 [pool-4-thread-1] INFO org.eclipse.jetty.server.session - DefaultSessionIdManager workerName=node0
16:34:27.287 [pool-4-thread-1] INFO org.eclipse.jetty.server.session - No SessionScavenger set, using defaults
16:34:27.287 [pool-4-thread-1] INFO org.eclipse.jetty.server.session - Scavenging every 600000ms
16:34:27.293 [pool-4-thread-1] INFO o.a.j.w.server.AbstractWebdavServlet - authenticate-header = Basic realm="Jackrabbit Webdav Server"
16:34:27.295 [pool-4-thread-1] INFO o.a.j.w.server.AbstractWebdavServlet - csrf-protection = null
16:34:27.296 [pool-4-thread-1] INFO o.a.j.w.server.AbstractWebdavServlet - createAbsoluteURI = true
16:34:27.296 [pool-4-thread-1] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@2a25b16f{/CwdXzke5SDO-/VaultCro,null,AVAILABLE}
16:34:27.296 [pool-4-thread-1] INFO o.c.f.w.s.WebDavServletController - WebDavServlet started: /CwdXzke5SDO-/VaultCro
16:34:27.340 [pool-4-thread-1] INFO o.c.f.w.s.WebDavServletController - Mounting http://cryptomator-vault:42427/CwdXzke5SDO-/VaultCro using org.cryptomator.frontend.webdav.mount.WindowsMounter
16:34:27.416 [JavaFX Application Thread] ERROR o.c.u.controllers.UnlockedController - Mount failed.
org.cryptomator.frontend.webdav.mount.Mounter$CommandFailedException: Command failed with exit code 2. Expected 0. Stderr: Systemfehler 67 aufgetreten.
Der Netzwerkname wurde nicht gefunden.
at org.cryptomator.frontend.webdav.mount.ProcessUtil.assertExitValue(ProcessUtil.java:28)
at org.cryptomator.frontend.webdav.mount.WindowsMounter.mount(WindowsMounter.java:43)
at org.cryptomator.frontend.webdav.servlet.WebDavServletController.mount(WebDavServletController.java:102)
at org.cryptomator.ui.model.Vault.mount(Vault.java:140)
at org.cryptomator.ui.controllers.UnlockedController.lambda$mountVault$1(UnlockedController.java:164)
at org.cryptomator.ui.util.AsyncTaskService.lambda$asyncTaskOf$0(AsyncTaskService.java:43)
at org.cryptomator.ui.util.AsyncTaskService$AsyncTaskImpl.lambda$null$6(AsyncTaskService.java:106)
at org.cryptomator.ui.util.AsyncTaskService.logExceptions(AsyncTaskService.java:135)
at org.cryptomator.ui.util.AsyncTaskService.access$100(AsyncTaskService.java:24)
at org.cryptomator.ui.util.AsyncTaskService$AsyncTaskImpl.lambda$run$7(AsyncTaskService.java:104)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
16:34:35.161 [JavaFX Application Thread] INFO o.e.j.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@2a25b16f{/CwdXzke5SDO-/VaultCro,null,UNAVAILABLE}
16:34:35.161 [JavaFX Application Thread] INFO o.c.f.w.s.WebDavServletController - WebDavServlet stopped: /CwdXzke5SDO-/VaultCro
16:34:35.186 [JavaFX Application Thread] INFO o.c.k.WindowsProtectedKeychainAccess - Creating new keychain at path C:\Users*Zensiert*\AppData\Roaming\Cryptomator\keychain.json
16:34:37.080 [JavaFX Application Thread] INFO o.c.launcher.MainApplication - JavaFX application stopped.
16:34:37.083 [Thread-1] INFO o.c.launcher.CleanShutdownPerformer - Goodbye.
```
I try to open my vault with win 2008 server. What can I do?
11:40:12.849 [JavaFX Application Thread] ERROR o.c.ui.controllers.UnlockController - Unlock failed for technical reasons.
org.cryptomator.ui.model.Volume$VolumeException: org.cryptomator.frontend.webdav.mount.Mounter$CommandFailedException: Command failed with exit code 2. Expected 0. Stderr: Systemfehler 67 aufgetreten.
Der Netzwerkname wurde nicht gefunden.
at org.cryptomator.ui.model.WebDavVolume.mount(WebDavVolume.java:63)
at …
Was genau steht in der Log-Datei ? Um den Fehler besser einordnen zu können.
Hi all,
I’m on Windows 7 (up to date) and running Cryptomator 1.3.4. Until shortly without any problem! However, for reasons unknown I can still open my vault but Cryptomator fails to connect the drive. Which of course makes accessing my data impossible. Anyone got a suggestion how to solve this issue? Thanks in advance.
Kind regards,
Paul
My first suggestion is to check up the names and order of items in the registry keys of:Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrderComputer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\OrderComputer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder