Solved

Poison messages in exchange 2007

Posted on 2015-01-23
5
32 Views
Last Modified: 2016-03-08
We have a single Microsoft SBS 2008 server running exchange 2007

On the 10th November last year we had 55 poison messages hit our server which caused warnings in our server application event log, and a queue in the exchange queue viewer showing 55 messages too.

poison-messages.jpg
On trying to view or delete the queue viewer crashes.

I also tried the commandlet :-

Try this cmdlet from the Exchange shell:

get-message -Queue:Poison | remove-message -withndr $false

but that too crashes.

The event log shows :-

poison-event-1.jpg
poison-event-2.jpg

I did not manage to get anywhere with this, so just left them there.

However, on 1ot November 2014, 13th November 2014, 20th November 2014, 9th December 2014, 23rd January 2015 we see the same 55 warnings in our server application event log, and the posion messages remain in the poison message queue in our queue viewer.

queue-viewer.jpg
Now being old school, I dont particulalry like to see returning events, so thought I would ask what everyone else thought.

Is it possible to clear these down from the queue viewer, and should the fact that this seems to keep re occuring be of concern to us?

If anyone can throw any light on this, I would be much obliged.
0
Comment
Question by:nigelbeatson
  • 4
5 Comments
 
LVL 24

Accepted Solution

by:
VB ITS earned 500 total points
ID: 40569278
Poisoned messages don't actually expire so you have to manually remove them from the poison queue one way or another.

It sounds like you may have some issues with .NET on your Exchange server if both EMC and EMS are crashing when you go to remove the poisoned messages. Is your server currently up to date in terms of Service Packs for Exchange and Windows patches?
0
 

Author Comment

by:nigelbeatson
ID: 40573058
Sorry for the delay.

I will check tha patch/update status on the server during my next visit in a couple of days. I am not at this site all of the time.

Many thanks
0
 

Author Comment

by:nigelbeatson
ID: 40671054
Sorry for the delay. This took a back seat due to other pressing matters, but I will check this out shortly.
0
 

Author Comment

by:nigelbeatson
ID: 41373160
sorry for the delay, but we have found another issue with this server, in as much as the automatic update, in fact any update run, does not complete. I suspect this is the root cause, and will be addressing this shortly.

I will keep you posted.
0
 

Author Closing Comment

by:nigelbeatson
ID: 41498418
finally got round to dealing with this! the latest service pack for exchange fixed this for me, so thanks for your assistance.

regards
0

Featured Post

Too many email signature changes to deal with?

Are you constantly being asked to update your organization's email signatures? Do they take up too much of your time? Wouldn't you love to be able to manage all signatures from one central location, easily design them and deploy them quickly to users. Well, you can!

Join & Write a Comment

"Migrate" an SMTP relay receive connector to a new server using info from an old server.
Easy CSR creation in Exchange 2007,2010 and 2013
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
This video discusses moving either the default database or any database to a new volume.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now