Link to home
Start Free TrialLog in
Avatar of nigelbeatson
nigelbeatsonFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Poison messages in exchange 2007

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.

User generated image
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 :-

User generated image
User generated image

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.

User generated image
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.
ASKER CERTIFIED SOLUTION
Avatar of VB ITS
VB ITS
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of nigelbeatson

ASKER

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
Sorry for the delay. This took a back seat due to other pressing matters, but I will check this out shortly.
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.
finally got round to dealing with this! the latest service pack for exchange fixed this for me, so thanks for your assistance.

regards