Tried to create a new one.. doesn't help.
rgds Sven
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
I can now confirm that disabling the Disclaimer transport rule solved the transport service / poison issue for E2010 SP3 RU1. I was also able to re-enable Forefront. All looks good so far with RU1 still installed. NO poison mail and my users have started removing the pins from their admin dolls!!
I don't have time today to determine if recreating a new disclaimer is also subject to the same issue. Anyone have a thought on this?
Charlie
charlie0
↧
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
@ Sven J,
Hi - not sure if its 100% related but: http://support.kaspersky.com/9781:
"This is due to Microsoft deeply changing the component architecture and
versions in its service packs, and Kaspersky Security 8.0 for Microsoft
Exchange Servers is incompatible with Service Pack 3 for
Microsoft Exchange Server 2010."Wondering if theres a similar issue with your TrendMicro AV?
also, what was your previous version? ie from sp3 to sp3 ur1 OR from sp2 urXX to sp3 then straight to sp3 ur1?
I'm also looking ot upgrade my environment to SP3 UR1 for 2013 coexistance. Seems the exchange team fixed alot with UR1 for SP3 but may have intoduced more probs..
CurbySanPan - Learning Exchange2010, SCOM2012 and life
I must check this from my AV provider.
My upgrade scenario was SP2 RU6 -> SP3 -> SP3 RU1
My transport rule works nicely with SP2 RU6. With SP3 I don't know because I upgraded quickly to RU1
rgds Sven
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
I have the same issue with SP3-RU1.
It took me almost 6 hours of troubleshooting to find the cause of this crashing transport service.
With a disabled disclaimer transport rule the transport service is running stable again.
@Microsoft; please fix this soon!
Rene.
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Wow... Glad I am not the Lone Ranger. SP3 RU1 seemed fine for a couple of days, but only because we didn't realize certain outbound mail was getting hung up in the poison queue. It did solve iOS battery issues and soft delete problems....... Actually,
I thought the issue was Forefront, because it kept complaining about the transport service restarting unexpectedly. We disabled Forefront with no change. We do have a disclaimer rule and will disable it in the AM and re enable Forefront. Sounds like that should
do the trick until RU1 version 2 hits the street!!!!! Thank you all! I can sleep now! Charlie
charlie0
↧
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Hello.
Thank you for all your replies!
I have the problem only with RU1 on SP3 (I think that the problem isn't Trend Micro AV, because I have no problem with SP3).
I understand from your posts that the problem is the disclaimer rule (I have it!).
In your opinion there will be a RU1 version 2?
Thank you.
Regards.
Alessandro
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Quite glad I wasn't the only one with this issue after SP3 RU1. Uninstalled RU1, but we do use the disclaimer transport rule. Haven't had time to reinstall RU1 and disable the disclaimer though.
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
I have the same issue at a customer. However, I am able to reproduce this in my own lab environment:
Transport rule adds disclaimer:
- OWA/OL plain text message: no problem
- OWA/OL HTML message: problem; mail goes to Poison queue and errors in application log.
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
@ Sven J,
Hi - not sure if its 100% related but: http://support.kaspersky.com/9781:
"This is due to Microsoft deeply changing the component architecture and
versions in its service packs, and Kaspersky Security 8.0 for Microsoft
Exchange Servers is incompatible with Service Pack 3 for
Microsoft Exchange Server 2010."
Wondering if theres a similar issue with your TrendMicro AV?
also, what was your previous version? ie from sp3 to sp3 ur1 OR from sp2 urXX to sp3 then straight to sp3 ur1?
I'm also looking ot upgrade my environment to SP3 UR1 for 2013 coexistance. Seems the exchange team fixed alot with UR1 for SP3 but may have intoduced more probs..
CurbySanPan - Learning Exchange2010, SCOM2012 and life
↧
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Hi folks,
If you are seeing issues like this, pleaseraise a case with support. This is important so that we;
Know the scope and severity of the issue
Can get multiple repros
if everyone thinks that someone else will call the fire brigade, then no one does and the house burns down :(
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
I also have this issue with SP3 UR1.
Transport rule adds disclaimer:
- OWA/OL plain text message: no problem
- OWA/OL HTML message: problem; mail goes to Poison queue and errors in application log.
Martijn
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Also, call MS and let them know, may be a possible BUG.OM (MCITP) | Blog
At the moment my work schedule is bit overbooked, so I don't have a time to deal with support tickets. But if this is not solved at the end of this week I might take a call and start troubleshooting process.
rgds Sven
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Also, call MS and let them know, may be a possible BUG.
OM (MCITP) | Blog
↧
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
At the moment I disabled my only one transport rule. My transport rule was configured to append company disclaimer at the end of message. Errors are gone. I'm investigating what is wrong with my rule. It worked fine until SP3 RU1.
rgds Sven
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Have you tried disabling Antivirus\3rd party filter agent?
OM (MCITP) | Blog
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Yes. SP3 RU1 and TrendMicro ScanMail 10.2
rgds Sven
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Hi,
I'm in the same boat. Same here. At the moment I'm thinking to uninstall RU1.
Or do anyone have any other options to check out?Some logs:
The transport process failed during message processing with the following call stack: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Exchange.Data.Transport.Email.PureTnefMessage.Microsoft.Exchange.Data.Transport.Email.IBody.GetContentWriteStream(Charset charset)
at Microsoft.Exchange.Data.Transport.Email.MimeTnefMessage.Microsoft.Exchange.Data.Transport.Email.IBody.GetContentWriteStream(Charset charset)
at Microsoft.Exchange.Data.Transport.Email.EmailMessage.Body_GetContentWriteStream(Charset charset)
at Microsoft.Exchange.MessagingPolicies.Rules.ApplyHtmlDisclaimer.ConvertHtmlBody(TransportRulesEvaluationContext context, HtmlDisclaimerEntry entry, HtmlToHtml h2hConverter, Encoding bodyEncoding)
at Microsoft.Exchange.MessagingPolicies.Rules.ApplyHtmlDisclaimer.OnExecute(RulesEvaluationContext baseContext)
at Microsoft.Exchange.MessagingPolicies.Rules.RulesEvaluator.ExecuteActions()
at Microsoft.Exchange.MessagingPolicies.Rules.RulesEvaluator.Run()
at Microsoft.Exchange.MessagingPolicies.Rules.TransportRuleCollection.Run(TransportRulesEvaluationContext context)
at Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgent.OnRoutedMessageHandler(RoutedMessageEventSource source, QueuedMessageEventArgs args)
at Microsoft.Exchange.Data.Transport.Routing.RoutingAgent.Invoke(String eventTopic, Object source, Object e)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.Dispatcher.Invoke(MExSession session)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExSession.AsyncInvoke(Object state)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExSession.BeginInvoke(String topic, Object source, Object e, AsyncCallback callback, Object callbackState)
at Microsoft.Exchange.Transport.Categorizer.MExEvents.RaiseEvent(MExSession mexSession, String eventTopic, AsyncCallback callback, Object state, Object[] contexts)
at Microsoft.Exchange.Transport.Categorizer.MExEvents.RaiseOnRoutedMessage(TaskContext context, AsyncCallback callback, MailItem mailItem)
at Microsoft.Exchange.Transport.Categorizer.CategorizerComponent.Stage5OnRoutedMessage(TransportMailItem transportMailItem, TaskContext taskContext)
at Microsoft.Exchange.Transport.Categorizer.TaskContext.Invoke()
at Microsoft.Exchange.Transport.Categorizer.CatScheduler.JobThreadEntry(Object ignored)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)------------------------------------------------------
Watson report about to be sent for process id: 7832, with parameters: E12, c-RTL-AMD64, 14.03.0146.000, edgetransport, unknown, M.E.D.T.E.P.M.E.D.T.E.IBody.GetContentWriteStream, System.NullReferenceException, a79c, unknown.
ErrorReportingEnabled: True
SP3, RU1 ????
OM (MCITP) | Blog
↧
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Hello!
I have installed Rollup 1 Update on my MS Exchange 2010 SP2 server: now I have several error messages in Event Log and all the sent mails in "Poison Queue".
No problem with received mails: OWA works perfectly.
Several errors:
---> Error 10003 on MSExchangeTransport:The transport process failed during message processing with the following call stack: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Exchange.Data.Transport.Email.PureTnefMessage.Microsoft.Exchange.Data.Transport.Email.IBody.GetContentWriteStream(Charset charset)
at ............--> Error 4999 on MSExchangeCommon: Watson report about to be sent for process id: 5724, with parameters: E12, c-RTL-AMD64, 14.03.0146.000, edgetransport, unknown, M.E.D.T.E.P.M.E.D.T.E.IBody.GetContentWriteStream, System.NullReferenceException, a79c, unknown.
ErrorReportingEnabled: FalseAny ideas?
Thank you very much.
Regards.
Alessandro
Do You have any transport rule?
rgds Sven
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Hi,
I'm in the same boat. Same here. At the moment I'm thinking to uninstall RU1.
Or do anyone have any other options to check out?
Some logs:
The transport process failed during message processing with the following call stack: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Exchange.Data.Transport.Email.PureTnefMessage.Microsoft.Exchange.Data.Transport.Email.IBody.GetContentWriteStream(Charset charset)
at Microsoft.Exchange.Data.Transport.Email.MimeTnefMessage.Microsoft.Exchange.Data.Transport.Email.IBody.GetContentWriteStream(Charset charset)
at Microsoft.Exchange.Data.Transport.Email.EmailMessage.Body_GetContentWriteStream(Charset charset)
at Microsoft.Exchange.MessagingPolicies.Rules.ApplyHtmlDisclaimer.ConvertHtmlBody(TransportRulesEvaluationContext context, HtmlDisclaimerEntry entry, HtmlToHtml h2hConverter, Encoding bodyEncoding)
at Microsoft.Exchange.MessagingPolicies.Rules.ApplyHtmlDisclaimer.OnExecute(RulesEvaluationContext baseContext)
at Microsoft.Exchange.MessagingPolicies.Rules.RulesEvaluator.ExecuteActions()
at Microsoft.Exchange.MessagingPolicies.Rules.RulesEvaluator.Run()
at Microsoft.Exchange.MessagingPolicies.Rules.TransportRuleCollection.Run(TransportRulesEvaluationContext context)
at Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgent.OnRoutedMessageHandler(RoutedMessageEventSource source, QueuedMessageEventArgs args)
at Microsoft.Exchange.Data.Transport.Routing.RoutingAgent.Invoke(String eventTopic, Object source, Object e)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.Dispatcher.Invoke(MExSession session)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExSession.AsyncInvoke(Object state)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExSession.BeginInvoke(String topic, Object source, Object e, AsyncCallback callback, Object callbackState)
at Microsoft.Exchange.Transport.Categorizer.MExEvents.RaiseEvent(MExSession mexSession, String eventTopic, AsyncCallback callback, Object state, Object[] contexts)
at Microsoft.Exchange.Transport.Categorizer.MExEvents.RaiseOnRoutedMessage(TaskContext context, AsyncCallback callback, MailItem mailItem)
at Microsoft.Exchange.Transport.Categorizer.CategorizerComponent.Stage5OnRoutedMessage(TransportMailItem transportMailItem, TaskContext taskContext)
at Microsoft.Exchange.Transport.Categorizer.TaskContext.Invoke()
at Microsoft.Exchange.Transport.Categorizer.CatScheduler.JobThreadEntry(Object ignored)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
------------------------------------------------------
Watson report about to be sent for process id: 7832, with parameters: E12, c-RTL-AMD64, 14.03.0146.000, edgetransport, unknown, M.E.D.T.E.P.M.E.D.T.E.IBody.GetContentWriteStream, System.NullReferenceException, a79c, unknown.
ErrorReportingEnabled: True
↧
Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Hello.
After the uninstall of the Rollup 1, the problem is solved.
Could be a problem of the Rollup?
Or, for example, the Trend Micro AV could be not compatible with Rollup 1?
Regards.
Alessandro
↧
