When you try to move business units in Microsoft CRM, you receive an error message (839157)


The information in this article applies to:

  • Microsoft CRM 1.2
  • Microsoft Business Solutions CRM 1.0
CRM SE:782CRM SE:783CRM SE:953

SYMPTOMS

When you try to move Microsoft CRM business units in your organization, you receive one of the following error messages.

  • If you have applied hotfix 835292, you receive the following error message: Error Message: An object with the specified name already exists in the Active Directory.
  • If you have not applied hotfix 835292, you receive the following error message:
    Error Message: An unexpected error occurred. Microsoft CRM users who have a custom Microsoft CRM Security role that has Parent:Child business unit access to read or write to records may not be able to re-parent a Business unit.
The following information is logged in the Microsoft CRM Server Application event log: MSCRM Platform Error Report: -------------------------------------------------------------------------------------------------------- Error: The server is unwilling to process the request. Error Message: The server is unwilling to process the request.
Error Details: Details on this error have not been provided by the platform. Source File: Not available
Line Number: Not available
Stack Trace Info: at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain() at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.CallHandlerExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) This problem occurs when the following conditions are true:
  • You made changes to parent-child business unit privileges in a default Microsoft CRM security role that did not previously have these privileges.
  • You reassigned a business unit.
For more information about the conditions that exist when this problem occurs, see the "Steps to reproduce the problem" section.

RESOLUTION

Microsoft CRM has a fix for this problem that is part of a cumulative update. The cumulative update information is described in the following Microsoft Knowledge Base article:

904435 Update Rollup 2 is available for Microsoft CRM 1.2

STATUS

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

MORE INFORMATION

Steps to reproduce the problem

Note These steps have been created by using Adventure Works Cycle, a Microsoft CRM sample company. These steps are for illustration. Do not add these new business units to a production Microsoft CRM server. They cannot be removed after they are added.
  1. Log on to the Microsoft CRM Web client as a user who has administrative privileges.
  2. Create a top-level business unit by following these steps:
    1. On the GoTo menu, point to Home, and then click Settings.
    2. On the Settings menu, click Business Unit Settings.
    3. On the Business Unit Settings page, click Business Units.
    4. On the Business Units page, click New Business Unit.
    5. In the Name box, type Top Level. Leave Parent Business Unit as the default setting.

      Note Adventure Works Cycle is the parent business unit if you are using the CRM sample company.
    6. Click the Save and Close button.
  3. Create several additional business units by following these steps:
    1. On the Business Units page, click New Business Unit.
    2. In the Name box, type Business Unit A.
    3. Click the lookup button that is next to the Parent Business Unit field. This will open the Look Up Records dialog box.
    4. Click Go to display all the parent business units that are available.
    5. Click to select Top Level, and then click OK.
    6. Click the Save and Close button.
    7. On the Business Units page, click New Business Unit.
    8. In the Name box, type Business Unit B.
    9. Click the lookup button that is next to the Parent Business Unit field. This will open the Look Up Records dialog box.
    10. Click Go to display all the parent business units that are available.
    11. Click to select Business Unit A, and then click OK.
    12. Click the Save and Close button.
    13. Repeat steps d through f to create business units C, D, and F with parent business units B, A, and B, respectively.
    The following table represents the Business Unit structure:
    Adventure WorksTop LevelBusiness Unit ABusiness Unit D
    Business Unit BBusiness Unit C
    Business Unit F
    Business Unit E
  4. Make changes to the Salesperson default security role by following these steps:
    1. On the GoTo menu, point to Home, and then click Settings.
    2. On the Settings page, click Business Unit Settings.
    3. On the Business Unit Settings menu, click Security Roles.
    4. In the Business Unit list, click Business Unit A.
    5. Double-click Salesperson to open the default salesperson security role.
    6. In the Role Name text box, type SalespersonChange.
    7. On the Core Records tab, in the Delete column of the Note row, click the circle repeatedly until the access level changes to Parent: Child Business Units.
    8. Click the Save and Close button.
  5. Change the parent business unit of Business Unit A by following these steps:
    1. On the GoTo menu, point to Home, and then click Settings.
    2. On the Settings menu, click Business Unit Settings.
    3. On the Business Unit Settings page, click Business Units.
    4. Double-click Business Unit A.
    5. On the Actions menu, click Change Parent Business.
    6. Click the lookup button that is next to New parent business.
    7. Click Go to display the available business units.
    8. Click Adventure Works Cycle, and then click OK to close the Look Up Records dialog box.
    9. Click OK to close the Confirm Change Parent Business dialog box.
    10. Click the Save and Close button.
    The new business unit structure is represented by the following table:
    Adventure WorksTop Level Business Unit
    Business Unit ABusiness Unit D
    Business Unit BBusiness Unit C
    Business Unit F
    Business Unit E
For more information about the terminology that is used to describe Microsoft product updates, see the following articles in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

887283 Microsoft Business Solutions CRM software hotfix and update package naming standards

REFERENCES

838986 Microsoft Business Solutions CRM version 1.2 published updates and hotfixes

Modification Type:MinorLast Reviewed:9/8/2006
Keywords:kbMBSadministration kbQFE kbprb kberrmsg kbMBSMigrate KB839157 kbAudDeveloper kbAudITPRO kbAudKnowledgeWorker kbAudEndUser
©2004 Microsoft Corporation. All rights reserved.