When anyone sends to these lists on any exchange server, the same result occurs.
 
Messages stay in the directory lookup queue for hours.
 
Inetinfo.exe process goes through the roof in terms of cpu time and mem usage.
 
sometimes smtp while still in a running state, seems to not process anything and everyone on that server complains of mail latency.
 
the server has 1 gig of ram. Exchange is on a raid 5 with the edb/stm/trans logs on a seperate logical drive from the OS and binaries.
 
AV is Sybari Antigen.
 
When diag logging is turned up, I get no further errors from the CAT.
Exchange Transport logs a bunch of errors pretaining to NDR's.
 
 
 
The email causing this issue is an email sent to about 15 private Outlook DL's which all contain single internal members. Anywhere from 2 to 100, depending on the DL.
No groups or nestd groups in the DL's. All recipients are internal. No external.
 
Most DSAcess counters in perfmon are at 0.
 
Out of SMTP server CAT:address lookups not found, the number is more than half of the CAT:Address Lookups in general.
 
 
 
Tell me if you need more info or what else I should give you to adequately help in leading me in the right direction.
 
Thank you


 
On 5/4/06, joe <[EMAIL PROTECTED]> wrote:
That would have been my logical response too; googling your error against the support site pulls that exact KB and you didn't mention it in your initial post...  So what else have you done and discounted before a bunch of other responses come through?
 
Some additional questions to make the brain juices flow a little... Is cat logging cranked up to 7? What other cat messages are coming through? Have you looked at the perms on the server objects to make sure they aren't incorrect? What is the disk config in that machine (physical and logical levels) and where is everything at ( i.e. bins, logs, dbs, page files, etc)? How is the overall perf of the machine? What is the io load in iops and how does that stack up against the theoretical max of your disk layout? How do your dsaccess counters look? How does it compare with the normal baselines?  Are there any "Special" IDs in the list? Can anyone else send to that list and not get the error? Is there anything odd about the list or the user in terms of permissions or settings? How long has the issue been going on? Has the user or anyone ever been able to send to that list and not have a problem?
 
 joe
 
--
O'Reilly Active Directory Third Edition - http://www.joeware.net/win/ad3e.htm 
 
 


From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Tom Kern
Sent: Thursday, May 04, 2006 4:19 PM
To: [email protected]
Subject: Re: [ActiveDir] Exchange queue(OT)

 
No, I spent about 2 secs before finding that.
Alas, it doesn't apply to my enviorment.
 
I sometims have an itchy send finger but, I try not to waste your guys time fi I can help it.
 
Thanks

 
On 5/4/06, Katherine Coombs <[EMAIL PROTECTED] > wrote:
Hi Tom,
 
I'm sure that you've spent more than the 5 seconds that I did trying to find a solution, but I came across this article:  http://support.microsoft.com/default.aspx?kbid=884996
 
HTH,
Katherine


From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Tom Kern
Sent: 04 May 2006 20:35

To: activedirectory
Subject: [ActiveDir] Exchange queue(OT)

 
I have an issue where a user sends an email to about 1800 recipients using Outlook DL's.
 
The email always gets stuck in the "messages awaiting directory lookup" queue for hours(sometimes days).
 
The only thing logged in the app log is-
 

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Categorizer
Event ID: 6004
Date:  5/4/2006
Time:  3:21:02 PM
User:  N/A
Computer: EXNYC01
Description:
The categorizer is unable to categorize messages due to a retryable error. There is not enough space on the disk.
 

For more information, click http://www.microsoft.com/contentredirect.asp.
Data:
0000: 70 00 00 00               p...   

 

The server has about 80gig of free space.

 

I tried moving the user's mailbox to another server but she still gets the same issue.

 

Has anyone had experience with this error?

 

I'm running Exchange 2k in mixed mode ina AD 2000 native mode enviorment.

 

Thanks



Reply via email to