mirror of
https://github.com/Pro/dkim-exchange.git
synced 2026-04-25 08:55:52 +03:00
[GH-ISSUE #109] MS Exchange Transport crash if private key is locked by another app #89
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stevemayster on GitHub (Nov 11, 2015).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/109
Hello.
Recently install dkim-exchange and faced with issue.
In event log appears a error event like this:
Couldn't load the key key for domain example.com. Error message: Invalid DER format for key. (The process cannot access the file because it is being used by another process.) and when message transport crash and queue database is rebuilded.
Based on my research file maybe locked by antivirus software and backup software.
And now i don't now what to do.
I cannot backup server and i can't stop av software(it's not safe)
Per my understanding transport agent addresses to private key every time then it sign a message.
Is it possible to maybe load key to memory?
@gogglespisano commented on GitHub (Nov 11, 2015):
Are you using 2.1.8? I think the latest version only loads the keys on start or a settings change.
@stevemayster commented on GitHub (Nov 12, 2015):
Hello gogglespisano.
No at that moment stable version is 2.1.7.
I think we need to wait what will Pro says)
@Pro commented on GitHub (Nov 12, 2015):
You should upgrade to 2.1.8
We (esp. @gogglespisano) did some performance improvement which most probably fixes your issue. In v2.1.7 the key was loaded again for each mail.
One strange thing here:
The EdgeTtansport service should never crash because we catch all exceptions within the signer, so there may still be an issue somewhere else...
@stevemayster commented on GitHub (Nov 12, 2015):
Hello Pro.
Thanks for answer.
In log i found another error
Watson report about to be sent for process id: 12228, with parameters: E12, c-RTL-AMD64, 14.03.0158.001, edgetransport, mscorlib, S.S.C.CryptographicException.ThrowCryptogaphicException, S.S.Cryptography.CryptographicException, 202c, 02.00.50727.5477.
ErrorReportingEnabled: False
Maybe this help?
I think it's because Kaspersky AV doing something with key.
@Pro commented on GitHub (Nov 12, 2015):
@AlxVD do you also use Kaspersky AV?
@stevemayster does this happen for every email or just some random ones?
@stevemayster commented on GitHub (Nov 12, 2015):
@Pro It's random, i do everything to put key in exception in Kaspersky, but i think Kaspersky just don't care about exception and then it read this key error ocurred. Error also ocurred then backup is going on but then it's goes match softer and don't brake exchange transport, just complaints about key is locked,
@Pro commented on GitHub (Nov 12, 2015):
Can you upgrade to v2.1.8?
@stevemayster commented on GitHub (Nov 12, 2015):
Pro it's production so i can do it only on weekend.
I notify you then.
@stevemayster commented on GitHub (Nov 12, 2015):
@Pro To upgrade without Configuration.DkimSigner.exe i need to run uninstall script and then install script,right? Or i can just replace some lib?
@AlxVD commented on GitHub (Nov 12, 2015):
There is no Kaspersky AV on my server.
I'm still at 2.1.7... will try to upgrade.
@Pro commented on GitHub (Nov 12, 2015):
@stevemayster for manual update you can just replace the .dll with the one from here:
https://github.com/Pro/dkim-exchange/tree/master/Src/Exchange.DkimSigner/bin
The file is locked by the MSExchangeTransport service, so you need to stop it for this short time to overwrite it.
Then you should also update the .exe from here (download all the files):
https://github.com/Pro/dkim-exchange/tree/master/Src/Configuration.DkimSigner/bin/Release
@stevemayster commented on GitHub (Nov 12, 2015):
Pro,thanks!
@stevemayster commented on GitHub (Nov 16, 2015):
Hello @Pro!
I update to 2.1.8 in saturday.
It's quite early to say but i think issue resolved, i don't see any error in App.log.
Thank you and @gogglespisano for great work!