Transport Service will not start after DKIM Agent installation (Ex2010 RU19)

[tweekoeken]

Versions

• Windows Server Version: Server 2008r2
• Exchange Version: Exchange 2010 rollup 19 (transport / common dlls at v14.0.0336.000)
• Installed DKIM Exchange Version: both 3.0.13 and 3.0.12 have this issue

Description

I installed the signing agent using the install.ps1 because originally this server did not have .net 4.5.2 installed. Installation goes smoothly, the 2010 SP3 source files are placed in program files and the agent is registered. Unfortunately, the transport service won't start following this step. The event viewer registers the following error immediately and upon retries:

Watson report about to be sent for process id: 6852, with parameters: E12, c-RTL-AMD64, 14.03.0382.000, edgetransport, ExchangeDkimSigner, E.D.DkimSigningRoutingAgentFactory..ctor, S.Reflection.TargetInvocationException, 6d6d, 03.00.0013.-001. ErrorReportingEnabled: False

To be sure, I've recompiled the signing agent using the latest dlls (version noted above) and also against .net 3.5 but this did not make a difference after uninstalling/reinstalling. During troubleshooting I installed .Net 4.5.2 on this machine. The GUI now works, so that's something! I have installed the signer on Ex2016 servers without problems but these seem problematic for some reason. Anyone have suggestions or a known working Ex2010 RU19 with any version of dkim signing?

Steps to Reproduce

1. copy source zip to server
2. run install.ps1
3. enter minimal configuration (1 domain, 1 private key in the keys subfolder, freshly generated)
4. press enter, transport service should start now but crashes

Expected behavior: running agent+transport service

Actual behavior: transport service doesn't start until I disable the DKIM signing agent

[o-eazy]

The same problem applies to Windows Server 2008r2/Exchange 2010 rollup 17 as well. Event viewer error message: "Watson report about to be sent for process id: 5560, with parameters: E12, c-RTL-AMD64, 14.03.0352.000, edgetransport, ExchangeDkimSigner, E.D.DkimSigningRoutingAgentFactory..ctor, S.Reflection.TargetInvocationException, 6d6d, 03.00.0013.-001. ErrorReportingEnabled: False"

[mirzonisa]

Hi guys, just to clarify my case. I've had same problem, and after I deleted example.com and example.org settings for domains, left only my domain settings, and enabled agent, everything started fine. One thing I deleted next is message-ID option. Maybe this will help somebody.

[o-eazy]

Also some follow-up information. I used the recompiled UI configurator/installer from @Westernstandard mentioned in https://github.com/Pro/dkim-exchange/issues/198 and I was able to install the agent successfully (from within the UI), and the transport agent was starting OK after that, plus the DKIM functionality was working as well (using Exchange 2010 rollup 17). @mirzonisa I just noticed that the recompiled UI had the example.com and example.org settings deleted as well, so you might be correct that just by deleting these 2 options the problem might be corrected.

[tweekoeken]

Thanks for the responses all. I'm not a developer but I've dabbled with enough C# to recognize that TargetInvocationError is pretty generic in the context of C# exceptions. Regarding the example.org/.com: @mirzonisa is right that removing these is necessary to get the signer up and running. I've also caused this exception by adding two separate signing keys for a single domain as an experiment. I have eliminated these two factors while deploying to Ex2016 already so that isn't it. @o-eazy: I'm going to try the fix in #198, thanks for linking it.

[EgOus]

I have tried on different servers with Exch2010 RU17 and RU18, with recompiled installer from @Westernstandard and original, with removed example.com and example.org - the problem isn't solved, transport is stopped. What do I do not so?

[DRHoule]

Facing the same challenge. Has anyone been able to solve yet? Transport service will not start when the Exchange DkimSigner is enabled. Exch2010 and DkimSigner 3.0.13

[Pro]

Please use the instructions here to help me adding new versions: https://github.com/Pro/dkim-exchange/blob/master/CONTRIBUTING.md#how-to-include-support-for-newer-exchange-versions

Unfortunately I cannot test with Ex2010.

[rbfajardo]

Exchange 2010 is end of support end of 2020

Source : https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-2010-end-of-support-is-coming/ba-p/607810

Maybe deprecate DKIM-Exchange support for 2010?

[DJBenson]

Exchange 2010 is end of support end of 2020

Source : https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-2010-end-of-support-is-coming/ba-p/607810

Maybe deprecate DKIM-Exchange support for 2010?

Hi @rbfajardo

I agree that starting to deprecate older versions of Exchange is probably a good idea. Exchange 2007 has been EOL for over 3 years and 2010 is EOL at the end of the year.

I propose that as of 13/10/2020 we deprecate both 2007 and 2010 and future versions will no longer support those platforms. I will post an announcement on the front page and open a topic to discuss.

[DJBenson]

#293 created for deprecation of EX2007/EX2010.