https://forums.qrecall.com/posts/list/6.page JForum - http://www.jforum.net ]]> https://forums.qrecall.com/posts/preList/633/2993.page https://forums.qrecall.com/posts/preList/633/2993.page GMT
Mike
]]> https://forums.qrecall.com/posts/preList/633/2994.page https://forums.qrecall.com/posts/preList/633/2994.page GMT
Thanks for the diagnostic report.

It's a bug.

The action terminated with an uncaught exception when trying to obtain exclusive access to the archive.

It's a random thing, unlikely to happen again, and doesn't involve any data loss. The code has been fixed and should appear in the next release.]]> https://forums.qrecall.com/posts/preList/633/2995.page https://forums.qrecall.com/posts/preList/633/2995.page GMT
[img]https://i.imgur.com/4aY4aYh.jpg[/img]

I managed to recover the file from a secondary (cloud) backup but this is obviously not good.

]]> https://forums.qrecall.com/posts/preList/633/3103.page https://forums.qrecall.com/posts/preList/633/3103.page GMT
If you haven't already, please sent a diagnostic report (in the QRecall application go to Help > Send Report). If the process crashed, there should be a crash log that we can look at.

If the process didn't crash, and it simply lost its connection with the action, that should be in the log too.]]> https://forums.qrecall.com/posts/preList/633/3107.page https://forums.qrecall.com/posts/preList/633/3107.page GMT https://forums.qrecall.com/posts/preList/633/3108.page https://forums.qrecall.com/posts/preList/633/3108.page GMT
Thank you for the diagnostic report.

Yes, it's a bug. QRecall is crashing when trying obtain the list of volumes on your system. For some unknown reason, one or more of the browsable volumes on your system returns an error when QRecall asks for the volume's specifics. And that's where it gets in trouble; it tries to log the volume details and crashes.

I've (hopefully) modified the code so it can log the failure without crashing. (I have no way of testing this since this situation has never arisen here and you're the first user to report it.) I'll email you link to a patched version of QRecall that you can try.

Please send a follow-up diagnostic report after you try this so I can see the success (or failure) of the new version.]]> https://forums.qrecall.com/posts/preList/633/3109.page https://forums.qrecall.com/posts/preList/633/3109.page GMT
FWIW I often have a VeraCrypt fully encrypted disk attached to my machine that obviously does not have any OS readable volume - it might be the one that is upsetting your code.

In any case will send another diagnostic when the restore finishes - hopefully without further issues.

UPDATE: The restore completed successfully - sent a new report.]]> https://forums.qrecall.com/posts/preList/633/3110.page https://forums.qrecall.com/posts/preList/633/3110.page GMT
That was indeed the problem. The latest report you sent shows the restore command couldn't get the info for the Boxcryptor volume.

Glad to hear the patch fixed it.]]> https://forums.qrecall.com/posts/preList/633/3111.page https://forums.qrecall.com/posts/preList/633/3111.page GMT
ralph]]> https://forums.qrecall.com/posts/preList/633/3152.page https://forums.qrecall.com/posts/preList/633/3152.page GMT
Diagnostic sent.]]> https://forums.qrecall.com/posts/preList/633/3160.page https://forums.qrecall.com/posts/preList/633/3160.page GMT Thanks for sending a diagnostic report.

The restore command is crashing inside the code that tries to match the volume identity of the captured items with the volumes you have on-line. There appears to be an empty/null/whatever volume name or something that's causing the crash.

I'm digging into it now, but in the mean time try to perform a recall instead of a restore (a recall doesn't need to find the original location of the captured item).]]> https://forums.qrecall.com/posts/preList/633/3161.page https://forums.qrecall.com/posts/preList/633/3161.page GMT