Monday, February 06, 2006

Can't send mail to another server or move mailboxes...

I have spent most of the afternoon troubleshooting a weird Exchange 2000 to Exchange 2003 problem. Installed a new E2K3 server in to an E2K admin group. I could send mail from E2K to E2K3, but not from E2K3 to E2K. Outbound messages on E2K3 were sitting in the "Messages Awaiting Directory Lookup" queue and the queue went in to a retry state. Once messages would arrive in the E2K3 server from E2K, they would also go in to the "Messages Awaiting Directory Lookup" queue.

I also found that I could not move mailboxes from the E2K server to the E2K3 server. I turned Diagnostics Logging on the MSExchangeTransport's Categorizer category up to maximum and saw these two events.

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Categorizer
Event ID: 6004
Date: 2/6/2006
Time: 2:40:24 PM
User: N/A
Computer: EXCHANGE01
Description:The categorizer is unable to categorize messages due to a retryable error.

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Categorizer
Event ID: 9035
Date: 2/6/2006
Time: 2:40:24 PM
User: N/A
Computer: EXCHANGE01
Description:Categorization of the message failed with a retryable error. Either some of the admin objects were renamed recently and changes were not picked or journaling was turned on for MDB (CN=mbxXXXX,CN=XXXXXX,CN=InformationStore,CN=EXCHANGE,
CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=XXXXX,CN=Microsoft Exchange,CN=Services,
CN=Configuration,DC=XXXXX,DC=corp) and the journal recipient's mailbox is deleted.

I looked this up in the Microsoft Knowledge Base and saw a number of threads on journaling that related to having journaling configured to a mailbox or public folder that no longer existed. This was not the case, but nonetheless, I actually enabled journaling for the stores and then disabled it just be sure. No luck.

I then switched the Categorizer diagnostics logging to "Field Engineering" level (setting the registry key to "7". I came up with these errors:

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Categorizer
Event ID: 9003
Date: 2/6/2006
Time: 2:53:03 PM
User: N/A
Computer: EXCHANGE01
Description:Categorizer is temporarily unable to process a message. While processing user 'smtp:USERNAME@XXXX.com', the function 'CPhatCat::CompleteMailDrop' called 'CompleteUserMailDrop' which returned error code '0xc0040559' (The categorizer encountered an error. The operation will be restarted.). ( f:\tisp2\transmt\src\cat\sinks\phatcat\cptmaildrop.cpp@110 )

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Categorizer
Event ID: 9003
Date: 2/6/2006
Time: 2:53:03 PM
User: N/AComputer: EXCHANGE01
Description:Categorizer is temporarily unable to process a message. While processing user 'smtp:USERNAME@XXXXX.com', the function 'CompleteRecipient' called 'CompleteMailDrop' which returned error code '0xc0040559' (The categorizer encountered an error. The operation will be restarted.). ( f:\tisp2\transmt\src\cat\sinks\phatcat\cptcomplete.cpp@52 )

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Categorizer
Event ID: 9003
Date: 2/6/2006
Time: 2:53:03 PM
User: N/A
Computer: EXCHANGE01
Description:Categorizer is temporarily unable to process a message. While processing user 'smtp:USERNAME@XXXX.com', the function 'CPhatCat::CompleteUserMailDrop' called 'SetTargetServer' which returned error code '0xc0040559' (The categorizer encountered an error. The operation will be restarted.). ( f:\tisp2\transmt\src\cat\sinks\phatcat\cptmaildrop.cpp@336 )

Upon some other checking, I was still being directed to "journaling" problems and was just about ready to open up a PSS incident. However, stumbled across an obscure problem in the newsgroup archives (Abe Famoti from Microsoft had posted the answer) where the inheritiable permissions are removed from the server object. When I checked, sure enough the "Allow Inheritable Permissions From The Parent To Propagate To This Object And All Child Objects. Include These With Entries Explicitly Defined Here. Thanks Abe! I thought I was going nuts!

3 Comments:

At 4:30 AM, Blogger Volker said...

Hi Jim,

where did you find the hint from Abe Famoti?

We de also break the inheritance rights... Bad ?

Regards,
Volker

 
At 12:39 PM, Blogger Carmila said...

Jim,

I'm having the same problem. I was wondering if you could share the solution or the location of the hint from Abe Famoti.

Thanks,
Carmila

 
At 7:40 AM, Blogger Jeremy said...

Thanks for posting this. I had the same problem (permissions not inherited no the Exchange 2K server), and was also seeing tons of Journaling related troubleshooting that didn't help. This was the first page I found in searching that actually pointed out the solution.

 

Post a Comment

<< Home