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 7, 2013, 4:31 am
$
0
0

It seems this is an issue which is affecting EVERYONE running E2010 SP3 UR1 and using a disclaimer transport rule appended to all outgoing mail (A VERY common enterprise practice!).

I am curious, is anyone watching this thread using a transport disclaimer rule with Rollup 1 installed that isNOT having the problem?

If all users of disclaimers are affected, then I would think MS will address quickly with a hotfix or maybe a version 2 of the rollup (depending if anything else has surfaced). It is bothersome though that a 3rd party has already fixed their disclaimer problem with UR1  . . . . even before MS has acknowledged the problem on week later!

Charlie

charlie0

↧
Search

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 7, 2013, 4:17 am
$
0
0

I opened a ticked on the 3rd for the transport rule/disclaimer issue, let them have remote access, submitted procdump output for edgetransport.exe when it crashes, MS are investigating.

Just give them time as it seems like any fix will be a code change which will need to go through their test/QA process before being issued


↧
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 7, 2013, 1:27 am
$
0
0

Hi all - from the exchange team blog (http://blogs.technet.com/b/exchange/archive/2013/05/29/released-update-rollup-1-for-exchange-server-2010-sp3.aspx) user 'Maciej O. _' states:

"I'm afraid that all Transport Agents which use Microsoft.Exchange.Data.Transport.Email.Body.GetContentWriteStream() method are affected."

so it sounds like only transport rules that write to the message body are affected...? can anyone confirm this please?

In other news... Exclaimer have release an RC fix for the same problem that affects their transport agent, this works in the same way; to write signatures and disclaimers to the message body, so is no doubt related and proves a hotfix/patch is necessary IMO.

CurbySanPan - Learning Exchange2010, SCOM2012 and life

↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 7, 2013, 12:53 am
$
0
0

Has anyone raised a support call with MS support?

Martijn

↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 6, 2013, 11:33 pm
$
0
0
It is not the kind of mail that causes the problem, it is the transport rule that is applied. There is actually a bug check whenever the transport service crashes. Any mail that is passing through when this happens gets pushed into the Poison queue. I have heard it said that plain text gets away with this, and it is only html that causes the crash. Most of our mail is sent html, and without attachments, and I can guarantee that it is all in English.

Anthony Sheehy - MCP, MCITP

↧
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 6, 2013, 7:25 pm
$
0
0
Do you know which kind of mail will be push into poison queue? With attachment, plain text , or have non-English char? these info maybe help someone to repro this issue.
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 6, 2013, 12:58 pm
$
0
0

hi all,

sounds like its not AV related - so directly related to transport rules...

can anyone confirm if its all transport rules or only specific rules that append text? - i guess your using the 'append disclaimer text and fallback to action if unable to apply' rule?

FYI: we use exclaimer disclaimer signature and disclaimer software who have also confirmed that there are issues with the disclaimer/signatures when used with SP3 UR1 -- so assume its related

CurbySanPan - Learning Exchange2010, SCOM2012 and life

Yes can anyone confirm this only affects rules that append text?  And not for example affect a max message size transport rule?
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 4, 2013, 5:45 am
$
0
0

I have reported this to Microsoft. Even if you do not have a support contract, it is possible to use site feedback to send this information to Microsoft (So I am told.)

The problem occurs because of a fault with the sink that is used to run transport rules. Disable the transport rule and your emails will immediately come out of the poison queue and get sent. You may also find that your anti-virus is also working after removing the transport rule.

Disabling the Transport Rule is a workaround, not a solution, until Microsoft fix the problem.

Anthony Sheehy - MCP, MCITP

↧
Search

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 4, 2013, 4:55 am
$
0
0

hi all,

sounds like its not AV related - so directly related to transport rules...

can anyone confirm if its all transport rules or only specific rules that append text? - i guess your using the 'append disclaimer text and fallback to action if unable to apply' rule?

FYI: we use exclaimer disclaimer signature and disclaimer software who have also confirmed that there are issues with the disclaimer/signatures when used with SP3 UR1 -- so assume its related

CurbySanPan - Learning Exchange2010, SCOM2012 and life

↧
↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 4, 2013, 4:13 am
$
0
0
Figures that doesn't work. Something must be malformed in RU1 Sure hope M/S jumps on this. I also hope nothing else pops up. If it were not for the 30% PLUS improved iPhone battery life and soft delete fix, we would have uninstalled RU1!!!

charlie0

↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 4, 2013, 4:09 am
$
0
0
Tried to create a new one.. doesn't help.

rgds Sven

↧

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 4, 2013, 3:32 am
$
0
0

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

June 3, 2013, 11:33 pm
$
0
0

@ 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

June 3, 2013, 10:38 pm
$
0
0

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

June 3, 2013, 9:42 pm
$
0
0
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

↧
Search

Errors and Poison messages after Rollup 1 on Exchange 2010 SP3

June 3, 2013, 8:03 am
$
0
0

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

June 3, 2013, 5:24 am
$
0
0
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

June 3, 2013, 5:19 am
$
0
0

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

June 3, 2013, 5:18 am
$
0
0

@ 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

June 3, 2013, 5:16 am
$
0
0

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