Closed theklap closed 2 years ago
Can you provide the full path in Event Viewer for this issue? Or a screenshot?
I wonder if it's similar to this issue which Eset say is safe to ignore.
Screenshot of event.
Can confirm the same on my exc2019 cu12 - though I cannot complain about something that does not work like it should ;)
I can confirm this issue at EXC-2016-CU23-May22SU and it wasn't present before CU23. No final user have sent any issue regarding this.
This issue is fixed by v3.4.1. This is currently flagged as pre-release but I've installed it in my production environment and not seen any instances of this error since. If you want to try this before the pre-release flag is removed, check the "Include prerelease versions" in the UI.
This turned out to be a regression of #215.
Hi.
I'm getting error after upgrade to 3.4.1 (by the way, it still shows 3.4.0 in DKIM Signer version info)
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
** Exception Text ** System.IO.FileLoadException: Could not load file or assembly 'BouncyCastle.Crypto, Version=1.9.0.0, Culture=neutral, PublicKeyToken=0e99375e54769942' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'BouncyCastle.Crypto, Version=1.9.0.0, Culture=neutral, PublicKeyToken=0e99375e54769942' at Configuration.DkimSigner.MainWindow.GenerateKey(String fileName) at Configuration.DkimSigner.MainWindow.btDomainKeyGenerate_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
** JIT Debugging ** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
Sorry, I've forgot to add version - Exchange 2016 CU23 here
snip
Does BouncyCastle.Crypto.dll exist in the program directory?
I get the same error about BouncyCastle.Crypto.dll. BouncyCastle.Crypto.dll exist in the directory and shows to be version 1.8.15362.1, while the error shows its looking for Version=1.9.0.0.
The version in the release package is 1.9.0.1;
I ran the upgrade from inside the GUI and it seems to not update correctly, wrong .dll version. Downloading the zip from the release page contains the correct .dll version. Is there a process to upgrade from zip that we need to follow?
DLL version is 1.8.10.1
I also got couple of new DLLs with after upgrade to 3.4.1: System.Memory.dll System.Numerics.Vectors.dll System.Runtime.CompilerServices.Unsafe.dll System.Text.Encoding.CodePages.dll
Guys I'm stuggling with this one. I would stick with 3.4.0 until this issue is resolved - although there's an error in the event viewer, it doesn't appear to be causing an issue whereas my attempts to fix it have caused a further issue.
If anybody would like to take a look at the dependency issue with bouncycastle that would be appreciated.
Can we reopen this as there is currently no pre-release available that fixes the bug?
Yes, sorry. Reopened.
v3.4.0 is the recommended version until this issue is resolved. I am struggling with the BouncyCastle dependency as no matter what I do the 1.8 version is bundled with the application and it needs 1.9. If anybody can assist please submit a PR.
Versions
Description
Receive an error in the windows application Log.
Source : MSExchange Extensibility Agent 'Exchange DKIMSigner' went async but did not call Resume on the new thread, while handling event 'OnCategorizedMessage'
Steps to Reproduce
Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]