mirror of
https://github.com/Pro/dkim-exchange.git
synced 2026-04-25 08:55:52 +03:00
[GH-ISSUE #97] 2013 CU9 async error #78
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 @kimurin on GitHub (Aug 28, 2015).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/97
Hi.
I'am constantly getting error in Event Viewer after upgrading to 2013 CU9 and 2.1.5:
"Agent 'Exchange DkimSigner' went async but did not call Resume on the new thread, while handling event 'OnCategorizedMessage'".
Although this had no impact on functionality.
@Pro commented on GitHub (Aug 28, 2015):
Seems to be an Exchange 2013 specific problem.
This should be fixable modifying the code by adding
AsyncAgentContext.Resume()(http://blogs.msdn.com/b/dvespa/archive/2013/02/18/exchange-2013-async-agent-resume-1057.aspx)See also: http://support.threattracksecurity.com/support/discussions/topics/1000059425
@Pro commented on GitHub (Sep 9, 2015):
@kimurin Can you please try the .dll from here:
https://github.com/Pro/dkim-exchange/tree/master/Src/Exchange.DkimSigner/bin
I tried adding the
Resume()which should eliminate the message in the event viewer?!@mrrogers75 commented on GitHub (Dec 17, 2015):
This issue is still happening in 2.1.8, but not all the time.
@mr-flibble commented on GitHub (Dec 22, 2015):
Same problem, I did update to 2.1.8 yesterday and event log is today filled with:
Agent 'Exchange DkimSigner' went async but did not call Resume on the new thread, while handling event 'OnCategorizedMessage'
Until yesterday I have 2.1.4 version without this error.
I have W 2012 R2, Exchange 2013 CU7
You can see how often is it:
@gogglespisano commented on GitHub (Dec 22, 2015):
On the surface it looks like GetAgentAsyncContext(), Resume() and Complete() should only be used if the event is handled asynchronously, which it isn't. Maybe the answer is just to remove all 3 calls?