XADM: SendAs Diagnostic Logging in Exchange 2000 Does Not Work Correctly (322819)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q322819 SYMPTOMS
SendAs diagnostic logging may not work correctly. This problem may occur if:
- SendAs diagnostic logging is set to Maximum.
-and-
- A user (for this example, User1) has Send As permissions for another user (for this example, User2).
-and-
- The user logs on to Microsoft Outlook as User1.
-and-
- The user types User2 in the From box of a message, and then sends the message.
The following informational message may be logged:
Event Type: Information
Event Source: MSExchangeIS Mailbox Store
Event Category: Send As
Event ID: 1032
Date: 4/4/2002
Time: 7:59:57 AM
User: N/A
Computer: computer_name
Description:
/o=exrule/ou=First Administrative Group/cn=Recipients/cn=User1 sent a message as /o=exrule/ou=First Administrative Group/cn=Recipients/cn=User1.
For more information, click http://search.support.microsoft.com/search/?adv=1.
Instead, the informational message that is logged should be similar to:
Event Type: Information
Event Source: MSExchangeIS Mailbox Store
Event Category: Send As
Event ID: 1032
Date: 4/4/2002
Time: 7:59:57 AM
User: N/A
Computer: computer_name
Description:
/o=exrule/ou=First Administrative Group/cn=Recipients/cn=user1 sent a message as /o=exrule/ou=First Administrative Group/cn=Recipients/cn=user2.
For more information, click http://search.support.microsoft.com/search/?adv=1.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Component: Logging
The English version of this fix has the following file attributes or later. |
| Exmgmt.exe | 6.0.5770.97 | | Mad.exe | 6.0.5770.97 | | Store.exe | 6.0.5770.97 | | Davex.dll | 6.0.5770.97 | | Dsaccess.dll | 6.0.5770.97 | | Dscmsg.dll | 6.0.5770.97 | | Excdo.dll | 6.0.5770.97 | | Exoledb.dll | 6.0.5770.97 | | Exprox.dll | 6.0.5770.97 | | Exres.dll | 6.0.5770.97 | | Exsp.dll | 6.0.5770.97 | | Exwmi.dll | 6.0.5770.97 | | Jcb.dll | 6.0.5770.97 | | Mdbmsg.dll | 6.0.5770.97 | | Mdbsz.dll | 6.0.5770.97 | | Phatcat.dll | 6.0.5770.97 |
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
| Modification Type: | Major | Last Reviewed: | 7/17/2006 |
|---|
| Keywords: | kbbug kbExchange2000preSP3fix kbExchange2000sp3fix kbfix KB322819 |
|---|
|