Article ID: 6752, created on Oct 8, 2009, last review on May 6, 2014

  • Applies to:
  • Operations Automation 2.9

Symptoms

After importing SharePoint site into new shared web application, the following task will be scheduled and will fail:

Task ID:     XXXXXX
Queue name:     ADSCTask_Provider
Task name:     Add members into group 'WSSSharedPools' (entity_id: NNNN)
Task description:     Add members into group 'WSSSharedPools' (entity_id: NNNN)
Queue status:    
Running
Start not earlier than:     Oct-08-2009 03:54
Last execution output:    
Exception during execution of MPF request: 'There is no such object on the server. [<response><errorContext description="InternalGroupAddRemove/There is no such object on the server." code="0x80072030" executeSeqNo="7"><errorSource namespace="Error Provider" procedure="SetError"/><errorSource namespace="Managed Active Directory" procedure="RethrowError_"/><errorSource namespace="SW Managed Active Directory" procedure="GroupAdd"/></errorContext></response>]'.

Cause

During import the application pool identity login name is used instead of application pool identity name. If login and name differ, the object will not be found in Active Directory.

Resolution

Changing application pool identity name to be equal to login allows to bypass the issue.

Steps to change the name:
1. Go to Domain Controller.
2. Start span-in Active Directory Users and Computers.
3. Navigate to the object of application pool identity (ex., LDAP://CN=SharePointAppPoolUser,OU=Provider,OU=Hosting,DC=mig,DC=yourdomain,DC=local).
4. In context menu choose Rename. Change the name to be same as login.
5. Press enter to apply changes. In appeared dialog click OK.
6. Restart failed task.

5356b422f65bdad1c3e9edca5d74a1ae 37e602325b9e080e0d137546b764143c 80fcf07a72a3fc2739554dff85ce8fe7 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF