New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error #217
Comments
UP! Same error with same Exchange version. THANKS |
I'm looking for |
update. |
I also do not start the transport service after installing the agent. |
Framework 4.5 |
power shell 2.0 means |
not functioning means dkim-exchange, agree? |
unfortunately I think so |
Which exchange 2010 version are you using exactly? Show the output of |
Version 14.3(Build 123.4) |
Hello, I have exactly the same issue. |
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. |
Windows 2008 R2
Exchange 2010 SP3
The text was updated successfully, but these errors were encountered: