Extra.exe does not trace a single user whose legacyExchangeDN attribute contains one or more special characters in an Exchange Server 2010 environment

Article translations Article translations
Article ID: 2514700 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You enable the filtered tracing feature in Microsoft Exchange Troubleshooting Assistant (Extra.exe) to trace a user (user A) in a Microsoft Exchange Server 2010 environment.
  • User A has a legacyExchangeDN attribute that contains one or more of the following special characters:
    • dollar sign ($)
    • period (.)
    • comma (,)
    • single straight quotation mark (')
    • caret (^)
    • space ( )
In this scenario, Extra.exe traces all the users in the environment instead of only user A. Additionally, user A's legacyExchangeDN attribute is split into multiple parts in the EnabledTraces.config file. For example, user A's legacyExchangeDN attribute in the Active Directory Service Interfaces (ADSI) Edit tool is displayed as follows:

/o=CONTOSO,/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User

However, the following separated UserDN attributes are displayed in the EnableTraces.config file:

UserDN:/o=CONTOSO
UserDN:/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User

Note
 By default, the EnabledTraces.config file is located in the root of drive C.

CAUSE

This issue occurs because the trace rule for Extra.exe assumes that the special characters in the single legacyExchangeDN attribute are separators. Therefore, the single legacyExchangeDN attribute is split into two UserDN attributes.


RESOLUTION

To resolve this issue, install the following update rollup:
2685289 Description of Update Rollup 3 for Exchange Server 2010 Service Pack 2

WORKAROUND

To work around this issue, manually combine the UserDN attributes on one line, and include the special character in the EnableTraces.config file. For example, add a comma (,) to the legacyExchangeDN attribute, as shown in the following example.

The following is an example of the legacyExchangeDN attribute before you perform the workaround:
UserDN:/o=CONTOSO
UserDN:/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User

The following is an example of the legacyExchangeDN attribute after you perform the workaround:
UserDN:/o=CONTOSO,/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about KB article 967255, click the following article number to view the article in the Microsoft Knowledge Base:
967255 Only the tracing information of the last user is logged when you configure Exchange Server 2007 to trace multiple users at the same time
For more information about KB article 971878, click the following article number to view the article in the Microsoft Knowledge Base:
971878 How to troubleshoot calendar issues in Microsoft Outlook, Microsoft Exchange Server 2007, and Microsoft Exchange Server 2010


Properties

Article ID: 2514700 - Last Review: June 27, 2012 - Revision: 3.0
APPLIES TO
  • Microsoft Exchange Server 2010 Service Pack 2, when used with:
    • Microsoft Exchange Server 2010 Enterprise
    • Microsoft Exchange Server 2010 Standard
Keywords: 
kbsurveynew kbexpertiseinter kbqfe kbfix KB2514700

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com