McCoyIT
asked on
Exchange 2007 Event ID 9213 - Categorization failed.
I have several messages stuck in the exchange 2007 queue that have no "from address" and are in a failed retry state due to "Categorization failed. This message will be deferred and retried because it was marked for retry if rejected".
I do have journaling setup on this machine, an the one common denominator I see is that all of these messages are coming from my Exchange 2003 server.
Prior to this starting I had moved my queue to a new partition (ran out of space), re-created a completely new queue...and have restarted the server. I am going to restart again tonight, but I can't seem to find much info on this problem. It does log an event ID 9213 as well.
I do have journaling setup on this machine, an the one common denominator I see is that all of these messages are coming from my Exchange 2003 server.
Prior to this starting I had moved my queue to a new partition (ran out of space), re-created a completely new queue...and have restarted the server. I am going to restart again tonight, but I can't seem to find much info on this problem. It does log an event ID 9213 as well.
ASKER
there is nothing else on the machine except exchange...all of our spam filtering is done through a 3rd party. The machine does have a Trend Micro antivirus client installed, but its been installed since day 1 and never had any issues.
I can find nothing on the error code or this error message.
The queue might be the cause of it, as moving that is not something that is done very often.
Journaling could be the issue. Do you have journaling enabled on the older server? Exchange tags the message to indicate that it has already been journaled, if something is happening to that tag then that could cause something like this.
-M
The queue might be the cause of it, as moving that is not something that is done very often.
Journaling could be the issue. Do you have journaling enabled on the older server? Exchange tags the message to indicate that it has already been journaled, if something is happening to that tag then that could cause something like this.
-M
ASKER
journaling is the problem for sure, I just can't seem to get it to tag properly since moving the queue even though I've disabled and re-enabled journaling. Even though the queue moved physical disks, that shouldn't affect journaling....as they are just sending reports to an account. In the past I've even moved the journal account to another storage group and that didn't cause any problems either and this is only happening from the 2003 server. The other 2 2007 servers are journaling just fine. Damn that 03 box!
What else is on the Exchange 2003 server?
Anything that could be scanning the SMTP traffic? If you have other servers that journal correctly then it would point the finger at something happening to the traffic coming off the Exchange 2003 server.
-M
Anything that could be scanning the SMTP traffic? If you have other servers that journal correctly then it would point the finger at something happening to the traffic coming off the Exchange 2003 server.
-M
ASKER
no it's only an exchange server as well. I have disabled journaling at the database level on all server, and now I've created a global journaling rule. I'll report back.
I have the exact same issue on my Exchange server. The only solution I found was to:
1. Stop Microsoft Exchange Transport Service
2. Rename the Queue folder in C:\Program Files\Microsoft\Exchange Server\Transport Roles\data\
3. Start the Microsoft Exchange Transport Service
4. The Queue folder should be recreated without the messages stuck in the Submission queue.
Were you ever able to find the root cause of the problem?
Thanks
1. Stop Microsoft Exchange Transport Service
2. Rename the Queue folder in C:\Program Files\Microsoft\Exchange Server\Transport Roles\data\
3. Start the Microsoft Exchange Transport Service
4. The Queue folder should be recreated without the messages stuck in the Submission queue.
Were you ever able to find the root cause of the problem?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you used the Queue viewer on the Exchange Management Console to examine the Submission queue? When I did on the same event ID, I found that the message stuck in the queue was >10MB, and our archiver appliance was rejecting it because of that...
Go to the Exchange Management Console->Tools->Queue Viewer, and look at the Submission queue. Double click the message. Go to the Recipient Information tab, and look at the "Last Error" field on any of the message stuck in the queue. In my case, the bounce message was:
"400: 4.4.7 The server responded with: 500 5.3.4 ROUTING: SizeLimit; message exceeds maximum fixed size for route. The failure was replaced by a retry response because the message was marked for retry if rejected."
Go to the Exchange Management Console->Tools->Queue Viewer, and look at the Submission queue. Double click the message. Go to the Recipient Information tab, and look at the "Last Error" field on any of the message stuck in the queue. In my case, the bounce message was:
"400: 4.4.7 The server responded with: 500 5.3.4 ROUTING: SizeLimit; message exceeds maximum fixed size for route. The failure was replaced by a retry response because the message was marked for retry if rejected."
In reference to my previous comment,
it turns out it was the route to the e-mail archiver appliance (defined under organization->hub transport-> Send Connectors tab on the Exchange Management Console) that had the message size limitation. When I bumped the maximum message size for that connector (by right clicking on the connector and choosing "properties") to a limit higher than the size of the message caught in the queue, the message cleared out of the queue by being sent to our e-mail archiver.
it turns out it was the route to the e-mail archiver appliance (defined under organization->hub transport-> Send Connectors tab on the Exchange Management Console) that had the message size limitation. When I bumped the maximum message size for that connector (by right clicking on the connector and choosing "properties") to a limit higher than the size of the message caught in the queue, the message cleared out of the queue by being sent to our e-mail archiver.
ASKER
please close this issue...I have resolved myself as stated in my post.
Categorizer is also where AV and Antispam usually does its thing.
-M