Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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

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

View products that this article applies to.

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.

↑ Back to the top

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.


↑ Back to the top

Resolution

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

↑ Back to the top

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

↑ Back to the top

Status

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

↑ Back to the top

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


↑ Back to the top

Keywords: kbsurveynew, kbexpertiseinter, kbqfe, kbfix, kb

↑ Back to the top

Article Info
Article ID : 2514700
Revision : 1
Created on : 1/7/2017
Published on : 6/27/2012
Exists online : False
Views : 301