Microsoft KB Archive/322819

= XADM: SendAs Diagnostic Logging in Exchange 2000 Does Not Work Correctly =

Article ID: 322819

Article Last Modified on 2/21/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



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:

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:

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.



RESOLUTION
To 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.

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.



STATUS
Microsoft 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.

Keywords: kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB322819

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.