[GH-ISSUE #118] Crash with 3.0-beta and Exchange 2016 #94

New issue

Closed

opened 2026-02-26 10:35:53 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 10:35:53 +03:00

Owner

Originally created by @matbech on GitHub (Jan 2, 2016).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/118

The DKIM signer fails to install on Exchange 2016. The following error is logged:

Watson report about to be sent for process id: 15004, with parameters: E12IIS, c-RTL-AMD64, 15.01.0225.042, edgetransport, MimeKit, M.C.DkimSigner..ctor, S.Reflection.TargetInvocationException, 1bae, 01.03.0000.000.
ErrorReportingEnabled: False

followed by
The worker process crashes continuously on startup: C:\Program Files\Microsoft\Exchange Server\V15\Bin\edgetransport.exe. The service will be stopped.

Originally created by @matbech on GitHub (Jan 2, 2016). Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/118 The DKIM signer fails to install on Exchange 2016. The following error is logged: Watson report about to be sent for process id: 15004, with parameters: E12IIS, c-RTL-AMD64, 15.01.0225.042, edgetransport, MimeKit, M.C.DkimSigner..ctor, S.Reflection.TargetInvocationException, 1bae, 01.03.0000.000. ErrorReportingEnabled: False followed by The worker process crashes continuously on startup: C:\Program Files\Microsoft\Exchange Server\V15\Bin\edgetransport.exe. The service will be stopped.

kerem

2026-02-26 10:35:53 +03:00

closed this issue
added the
bug

agent
labels

kerem commented

2026-02-26 10:35:53 +03:00

Author

Owner

@semack commented on GitHub (Jan 2, 2016):

I confirm.

@semack commented on GitHub (Jan 2, 2016): I confirm.

kerem commented

2026-02-26 10:35:54 +03:00

Author

Owner

@Pro commented on GitHub (Jan 2, 2016):

Thanks for the Info. I'm currently installing Ex2016 on a Windows 2016 VM and will try to reproduce the problem.

@Pro commented on GitHub (Jan 2, 2016): Thanks for the Info. I'm currently installing Ex2016 on a Windows 2016 VM and will try to reproduce the problem.

kerem commented

2026-02-26 10:35:54 +03:00

Author

Owner

@Pro commented on GitHub (Jan 3, 2016):

The problem is that your private key isn't valid. You need to create a new one, if you upgrade from version 2.* to 3.*.
Please read: https://github.com/Pro/dkim-exchange#updating-from-version-2-to-3

I improved the error handling for invalid keys, will upload a new beta release later today

@Pro commented on GitHub (Jan 3, 2016): The problem is that your private key isn't valid. You need to create a new one, if you upgrade from version 2.\* to 3.*. Please read: https://github.com/Pro/dkim-exchange#updating-from-version-2-to-3 I improved the error handling for invalid keys, will upload a new beta release later today

kerem commented

2026-02-26 10:35:54 +03:00

Author

Owner

@matbech commented on GitHub (Jan 3, 2016):

I believe to use a correct private key. It has been created with openssl and is used in other places. Also the public key (.pub) is correctly read (using the Check function) by the DKIM configurator. Maybe the configurator should also verify the private key? See https://github.com/Pro/dkim-exchange/issues/121

I think the problem is with the line breaks at position 65 in the .pem. Whereas the private key that the DKIM configurator generates has no line breaks. The DKIM signer should support private keys with line breaks. See https://github.com/Pro/dkim-exchange/issues/120

@matbech commented on GitHub (Jan 3, 2016): I believe to use a correct private key. It has been created with openssl and is used in other places. Also the public key (.pub) is correctly read (using the Check function) by the DKIM configurator. Maybe the configurator should also verify the private key? See https://github.com/Pro/dkim-exchange/issues/121 I think the problem is with the line breaks at position 65 in the .pem. Whereas the private key that the DKIM configurator generates has no line breaks. The DKIM signer should support private keys with line breaks. See https://github.com/Pro/dkim-exchange/issues/120