error

[vane1980]

Windows 2008 R2 Exchange 2010 SP3

[alovalvo]

UP! Same error with same Exchange version. Any solution?

THANKS

[vane1980]

I'm looking for

[alovalvo]

update. I manually unblocked mentioned files in the script. Now, the "MSExchangeTransport" service failed to start due to continuous crashes. As I can see in the event viewer (error event id 1016). Note also error event 4999 MSExchange Common: "Watson report about to be sent for process id: 7224, with parameters: E12, c-RTL-AMD64, 14.03.0319.002, edgetransport, ExchangeDkimSigner, E.D.DkimSigningRoutingAgentFactory..ctor, S.Reflection.TargetInvocationException, 6d6d, 03.00.0013.-001. ErrorReportingEnabled: False"

[vane1980]

I also do not start the transport service after installing the agent. do you have a power shell version?

[alovalvo]

Framework 4.5

[vane1980]

power shell 2.0 means

[vane1980]

not functioning means dkim-exchange, agree?

[alovalvo]

unfortunately I think so

[Pro]

Which exchange 2010 version are you using exactly?

Show the output of Get-ExchangeServer

[vane1980]

Version 14.3(Build 123.4)

[marcwaz]

Hello, I have exactly the same issue. I mean after the installation, the transport service is not restarting (unless I disable the Exchange DkimSigner). In the event log I have also the same watson error: Le rapport Watson est prêt à être envoyé pour l'ID de processus : 13516, avec les paramètres : E12, c-RTL-AMD64, 14.01.0438.000, edgetransport, ExchangeDkimSigner, E.D.DkimSigningRoutingAgentFactory..ctor, S.Reflection.TargetInvocationException, 6d6d, 03.02.0000.-001. ErrorReportingEnabled : False

[ramon-garcia]

Here it works prefectly.

The first issue, the error of unblock-file missing, is caused by the powershell version used in the Exchange shell. The exchange shell icon starts powershell version 2.0. One has to create a new shortcut with Powershell versión 5.1, and then one has the unblock-command.

The issue mentioned by @marcwaz and @alovalvo (ExchangeDkimSigner, E.D.DkimSigningRoutingAgentFactory..ctor, S.Reflection.TargetInvocationException) is caused by having DLLs for .NET runtime 4, but Exchange 2010 is based on .NET runtime 2.0. Probably the installation script copied DLLS from the configuration utility and overwrote DLLS like mimekit.dll used by the signer.

This problem can be detected by running from Powershell 2.0, for instance, from Exchange shell

Add-Type [path to mimekit.dll]

if you see an error reporting that mimekit.dll is for a different version of the .net runtime, then this is your problem.

The solution: copy DLLs from the directory with ExchangeDkimSigner.dll to the installation directory. Check that these DLLs can be loaded from .NET 2.0 with the command Add-Type above.