Quantcast
Channel: Errors and Poison messages after Rollup 1 on Exchange 2010 SP3
Viewing all 191 articles
Browse latest View live
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 2, 2013, 12:17 pm
$
0
0

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: False

Any ideas?

Thank you very much.

Regards.
Alessandro


↧
Search

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

August 13, 2013, 10:44 am
↧
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

July 23, 2013, 1:39 am
$
0
0

Hello,

I have the information from the microsoft support that Rollup Pack 2 for Exchange Server 2010 SP3 will come out on 13th August 2013. Rollup Pack 2 will include the Hotfix for the poison queue and HTML disclaimer problem from Rollup Pack 1 for Exchange Server 2010 SP3.

best regards

Eugen

↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

July 17, 2013, 7:30 am
$
0
0

Hi,

I hope, below method can also be applied just to overcome this issue temporarily.

Export the each message from the poison queue from Exchange 2010 SP3 RU1 (one at time) and save it in the .eml file

Copy the .eml file on to other HUB server (not Exchange 2010 SP3 RU1 installed) in to Pickup directory

The email will be delivered to the intended recipient/s

The message is poison queue is not going to deliver therefore poison queue can be emptied.

Regards

Neeraj Mehra

Neeraj Mehra

↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

July 15, 2013, 7:17 pm
$
0
0

Hi All ,

I have 2 Transport servers at each site . On site A , using Exclaimer (3rd party disclaimer) and another site B using Exchange disclaimer . There are in same exchange forest .

Last week i have updated the version of exclaimer to fix the microsoft known bugs issue , however i still hit with the poison message issue . Can anyone confirm whether i need to update on both site ? I thought my mail doesnt flow to site B transport server hence it wont be affected .

↧
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

July 2, 2013, 3:04 am
$
0
0
Yes, you have to uninstall before updating any Rollup or Service pack
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

July 2, 2013, 2:55 am
$
0
0
Does the logic behind the Interim Update's stays same? - I mean if I install this Interim Update and the next UR comes out, I must uninstall this IU before installing next UR ?

rgds Sven

↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 30, 2013, 2:59 pm
↧
Search

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 19, 2013, 2:22 pm
$
0
0

All,

SAME PROBLEM - BUT I THINK I HAVE A DECENT WORKAROUND.

We have a custom transport agent, programmed in-house, to append disclaimers. After SP3 and RU1,  GetContentWriteStream() was returning a null object (same error as original post). This stream is used to write the modified content back to the MailItem.Message.Body object.

There are two versions of GetContentWriteStream(), one with no params, and one with a string param that takes the character set of the new Stream object returned.

I decided to pass the character set from the mail item in and all of a sudden my disclaimer service started working again. In other words:

Stream newBodyContent = null;

            try

            {

                newBodyContent = e.MailItem.Message.Body.GetContentWriteStream(e.MailItem.Message.Body.CharsetName.ToString());

            }

            catch (Exception gcs)

            {

               

            }

I hope this helps. If you have a third part transport agent, perhaps this can help them fix their code too.

Thanks,

Dirk Frulla

↧
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 19, 2013, 9:11 am
$
0
0

We have the same problem with SP3 CU1. Because of the disclaimer all outbound messages end up in the poison queue. Also we have noticed that users are no longer able to open additional mailboxes from OWA when user has "Full Access for a mailbox. Server just times out. Uninstalling CU1 fixes the problem with poisoning of e-mail messages, however it doesn't fix problem with Server timing out. Some users reported Server timing out issue even before CU1 was applied, but I haven't seen real solution for this issue. If anybody knows how to fix Server timing out issue, please point me to the right direction.

↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 15, 2013, 12:03 am
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 11, 2013, 3:06 am
$
0
0
Did anyone observe that text-only mails work (have the disclaimer text appended and sent) while more "complex" mails (like with attachments or HTML formatted) don't pass the transport rule?
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 10, 2013, 9:14 am
$
0
0
I'm having the same problems after SP3 RU1 is applied. I disabled the global disclaimer and the problem went away. I have just tried Jingping's work around of adding 　 at the end of the HTML disclaimer and so far the transport service is working. Has anyone raised a support ticket with Microsoft?
↧
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 10, 2013, 6:40 am
$
0
0

Updated SP3 RU1 on last Friday.  Same issue here. We have received event ID 10003 "Poison Message".

Tim


↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 10, 2013, 3:25 am
$
0
0

Just for your information: we're experiencing the same issue with RU1 and we append disclaimer text to outgoing email using transport rule.

Removing RU1 solved the problem (for the moment).

Thanks,

Massimo

↧
Search

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 9, 2013, 11:47 pm
$
0
0
We have the same issue after applying UR1 for SP3. Both hub nodes keep crashing. And yes, we have transport rule adding disclaimers.
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 9, 2013, 11:27 pm
$
0
0
We are also experiencing this exact issue as well. We also had issues with Forefront failing to start on the hub server when disclaimers rules were enabled, presumably related. Hopefully Microsoft are giving this a high priority.
↧
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 9, 2013, 2:26 pm
$
0
0

I'm experiencing this exact issue after installing RU1, last night. I wish I would've seen this first!

Rich Text emails work, but HTML formatted emails crash the Transport Service and end up in the Poison Queue. Same as Martijn describes. My only workaround was to disable our disclaimers, which can't be a long term solution.

MS needs to address this.

↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 9, 2013, 4:46 am
$
0
0

A workaround for the common case (NOT for all cases)

Add a SBC case (double-byte) space (　) to the end of the disclaimer text. For example, if your original disclaimer text is "Hello World", then revise it as "Hello World　". Mail receivers will not notice the SBC case space unless they highlight the disclaimer text by selecting it.

If the message body contains the SBC case space as well, this workaround will not work though.

↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 7, 2013, 6:26 am
$
0
0

Please do call in and file a case# so that this issue is given the appropriate priority.

While the Product Group team are aware and are monitoring this thread, cases are also important as we can collect detailed repro data (if required).

Cheers,

Rhoderick

Microsoft Senior Exchange PFE

Blog:http://blogs.technet.com/rmilne Twitter:  LinkedIn:  Facebook:  XING:

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.


↧
Viewing all 191 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>