Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please confirm - What errors can be written to Log File #89

Open
greavette opened this issue Nov 8, 2022 · 1 comment
Open

Please confirm - What errors can be written to Log File #89

greavette opened this issue Nov 8, 2022 · 1 comment

Comments

@greavette
Copy link

Hello,

I'm looking to monitor my CryptSync using the log file. I see in the ErrorMsg.cpp the following messages. Are these the only errors I should be looking for:

// case ERROR_NO_MORE_FILES : s = "No more files"; break;
// case ERROR_DIRECTORY : s = "Error Directory"; break;
case E_NOTIMPL : s = "E_NOTIMPL : Not implemented"; break;
case E_NOINTERFACE : s = "E_NOINTERFACE : No such interface supported"; break;
case E_ABORT : s = "E_ABORT : Operation aborted"; break;
case E_FAIL : s = "E_FAIL : Unspecified error"; break;

Search String:

ERROR|Error|ABORT|FAIL

Thank you.

@stefankueng
Copy link
Owner

the log file is not created automatically. Only when you press the show log button. So you can't use the log file.
but maybe you can use the debug output (dbgview from sysinternals shows those):
create the registry DWORD value HKCU\Software\CryptSync\DebugOutputString and set the value to 1, after that CryptSync will use the debug output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants