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.

Role assignment with custom write scope fails in an Exchange Server 2013 environment


View products that this article applies to.

Symptoms

In a Microsoft Exchange Server 2013 environment, Exchange Web Services (EWS) impersonation fails, and you receive the following error message:
ServiceResponseException "Active Directory operation did not succeed. Try again later."

Additionally, some other cmdlets that use role assignments may fail with an error message that resembles the following:
Received a referral to ChildDomain when requesting CN=UserName,CN=Users,DC=ChildDomainName,DC=Domain,DC=com from
ServerName. You have specified the wrong server for this operation.

These issues occur if Exchange is installed in a child domain, and a custom write scope such as the CustomRecipientWriteScope or CustomAttribute1 parameter is specified in these operations.

↑ Back to the top


Resolution

To resolve this issue, install Cumulative Update 9 for Exchange Server 2013.

↑ Back to the top


Workaround

To work around this issue, do not use a custom write scope. Instead, let the scope apply to all mailboxes in the organization.

For example, run one of the following commands to remove the CustomRecipientWriteScope or CustomAttribute1 scope:
  • Set-ManagementRoleAssignment "UserName" -CustomRecipientWriteScope $null
  • Set-ManagementRoleAssignment "UserName" -CustomAttribute1 $null

↑ 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 how to configure Exchange Impersonation, go to the following Microsoft website:

↑ Back to the top


Keywords: kberrmsg, kbsurveynew, kbbug, kbtshoot, kbexpertiseadvanced, kbfix, kbqfe, kb

↑ Back to the top

Article Info
Article ID : 2988660
Revision : 1
Created on : 1/7/2017
Published on : 6/16/2015
Exists online : False
Views : 249