FluentPro Help Center

What do you need help with?

    Sorry, we didn't find any relevant articles for you.

    Send us your queries using the form below and we will get back to you with a solution.


    Common errors and warnings (Project for the web -> MS Planner)

    In this article, we will review common errors and warnings for Project for the web -> Planner migration scenario.

    Another object with the same value for property mailNickname already exists

    Error: Request_BadRequest: Another object with the same value for property mailNickname already exists.

    Cause: The error may occur at creating Microsoft 365 groups in the target tenant while migrating to Microsoft Planner. The error indicates that there is already an existing target group with the same property mailNickname, i.e. the same primary email address, and possibly name as the group that attempts to be created during the migration. As each Microsoft 365 group should have a unique mail nickname in the tenant, the creation of another group with the already used mail nickname is not allowed.

    In case the target migration account is added as a member or as an owner to the existing target group with the same mail nickname, it will be found and updated during the migration.

    If the target migration account is not an owner or a member of the existing target group and has no access to it, the group migration will fail in that case.

    Possible solution: 

    1. Check if there is an existing Microsoft 365 group in the target tenant with the same mail nickname/primary email address and name as the group that needs to be created or updated during the migration.

    2. If the existing group should be used, make sure to add the target migration user account as a member or an owner to that group in the target tenant

    3. If a new group should be created, change a bit the primary email address of the existing target group, or change the name of the source group or Plan that is used for the group creation. 

    4. Restart the uncompleted migration. 

    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option. 


    Unable to add user (user account): Authorization_RequestDenied: Insufficient privileges to complete the operation

    Error: Unable to add user (user account): Authorization_RequestDenied: Insufficient privileges to complete the operation.

    Cause: The error may occur at adding users as members and owners to the Private target Microsoft 365 group. In case the migration is performed to an existing Private Microsoft 365 group and the target migration account is not a tenant admin, it should be added to the group owners as well as members to be able to add other users to the Private group during the migration.

    In case the target migration account is a regular user and is only a member, but not an owner in the existing Private group in the target tenant, it will not have permission to add owners and members to the group, and the mentioned error will occur.
     
    Possible solution:

    1. Add the target migration user account as an owner to the necessary Private group in the target tenant or use another target account that is an owner or a member of the group.

    2. Restart the uncompleted migration. 

    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.


    Unable to add user Username (user account): Request_BadRequest: As per tenant wide policy guest users are not allowed to be owner of a unified group

    Error: Unable to add user Username (user account): Request_BadRequest: As per tenant wide policy guest users are not allowed to be owner of an unified group.

    Cause: The error occurs at adding users to the target group Owners in case the mapped users are Guests in the target Office 365 tenant. Guest users are not allowed to be owners in Microsoft 365 groups.
     

    Possible solution: 

    1. Check the target users that have been mapped to the source users that need to be added as the group owners. If their ownership should be preserved in the target groups, consider creating non-guest user accounts for them without any license in the target tenant or mapping them to other non-guest target users in the User Mapping section.

    2. Select to restart the migration and correct the mapping for the users in question in the User Mapping section. In case the group ownership should not be preserved for those users in the target group, the errors of that type may be ignored and there is no need to restart the migration. Alternatively, the corresponding target users may be removed from the mapping, however, in that case the user group membership and task assignments will not be preserved in all the migrated groups and Plans. 

    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.


    Directory_QuotaExceeded: The directory object quota limit for the Principal has been exceeded

    Error: Directory_QuotaExceeded: The directory object quota limit for the Principal has been exceeded. Please ask your administrator to increase the quota limit or delete objects to reduce the used quota.

    Cause: The error about exceeding the directory quota may occur at creating new Microsoft 365 groups in the target tenant in case the target migration account does not have the tenant admin role. Maximum 250 Microsoft 365 groups can be created with a non-admin user account in the Microsoft 365 tenant. Only that number of groups will be created during the migration that will fit the limit of total 250 groups together with the existing groups previously created by that user. Other groups that exceed the limit will fail to be created with the Directory_QuotaExceeded error.

    Possible solution: 

    Use another user account for creating the rest of the groups or use an account with the tenant admin rights as the target connection account for the migration, if it is necessary to create a great number of Microsoft 365 groups with one account during one migration.

    Alternatively, remove the groups that were created during the migration in the target tenant, and relaunch the migration, selecting another Microsoft 365 Group Creation Mode, i.e. ‘Create all Plans in one group’ or ‘Create groups with source group names and settings’, in the Migration Settings section to have a fewer number of Microsoft 365 groups created.
     
    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.


    MaximumProjectsOwnedByUser: The request exceeded allowed limits

    Error: MaximumProjectsOwnedByUser: The request exceeded allowed limits.

    Cause: The error occurs at creating a new Plan in the Microsoft 365 group that already contains 200 Plans. There is a limit of maximum 200 Plans that can be created in one Microsoft 365 group.
    If the ‘Create all Plans in one group’ migration setting is selected for the migration and the total number of projects to migrate is more than 200, only 200 projects will be created as Plans in a new Microsoft 365 group, and others will fail. If ‘Create all Plans in one group’ migration setting is selected and an existing Microsoft 365 group is specified, where there are already some Planner Plans, only that number of projects will be migrated which will fit the limit of total 200 Plans in the group together with the existing Plans. 

    Possible solution: 

    Restart the migration, selecting another Microsoft 365 Group Creation Mode that will lead to creating the rest of the Plans in different group(s), or migrate the projects to different groups in batches (in a few migrations). Make sure not to select more than 200 projects to migrate to one Microsoft 365 group.
     
    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option. 


    Unable to update task fields: The attempted changes conflicted with already accepted changes

    Error: Unable to update task fields: The attempted changes conflicted with already accepted changes. Read the latest state and resolve differences.
     

    Cause: The error may occur when there are tasks with the same names within one Bucket in the source Plan, and they have different field values set that may conflict during the migration.

    Currently, items are differentiated by name within one Bucket in the source and target Plans during the migration. Now, the tasks with the same names within one Bucket, that are migrated, are merged in the target Plan, and their field values are attempted to merge in one task as well. When the source field values are different for similar tasks, the conflict may occur that they could not be overwritten in the target task.

    The error ‘Unable to update task fields…’ indicates that the field values of the first migrated task have been set in the target task, but the field values of other tasks with the same name have not been set in the target Plan, overwriting the initial values.
     
    Possible solution: 

    1. Check if there are tasks with the same names within a Bucket in the source Plan. 

    2. Change the task names a bit (e.g. add a dot to the end), or move the tasks with the same name to different Buckets in the source Plan, if possible.

    3. Restart the migration in Project Migrator, selecting the ‘Create new and remove existing Plans before creating’ migration setting to create the target Plan and tasks from scratch. 

    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.


    Failed due to the parent group "Group Name" fail

    Error: Failed due to the parent group "Group Name" fail.

    Cause: The project migration fails with such an error in case its group creation or update has failed, as the group is a parent entity to the project.
     
    Possible solution: 

    1. Check with what error the migration of the project group has failed in the Data Migration Summary.

    2. Try to resolve the cause of the group migration failure. 

    3. Restart the migration. In case the cause of the group migration failure cannot be eliminated, try to select another Microsoft 365 group creation mode in the Migration Settings at restarting the migration.

    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.


    Unable to find plan (Plan Name) by id

    Error: Unable to find plan (Plan Name) by id.

    Cause: The error may occur in case the source project could not be found by id in the source system. 

    Possible solution:

    Check that the project with the specified name and id still exists in the corresponding group in the source system. If the project still exists, select to restart the migration for it.


    Unable to set attachments

    Error: Unable to set attachments.

    Cause: The error may occur in case there are file attachments added to an item(s) in the source project, and the source migration user account does not have access to the project files in the linked group, i.e., the account has the Admin access for reading the projects, but is neither a member nor an owner of the project group in the source tenant.

    Possible solution: 

    Add the source migration user account as a member or an owner to the necessary project group in the source tenant, or use another source account that is an owner or a member of the source project group.
     
    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.


    Skipped: project without Microsoft 365 Group

    Warning: Skipped: project without Microsoft 365 Group.

    Cause: The warning may occur in case a project(s) selected for migration is not added to any M365 group in the source system, and the ‘Create groups with source group names and settings’ Microsoft 365 Group Creation mode and the ‘Skip projects that are not added to any group’ Non-group Project Migration mode have been selected in the Migration Settings for launching the migration.

    Possible solution: 

    Restart the migration and select either the ‘Migrate Projects and create groups using project names’ option in the ‘Non-group Project Migration Mode’ drop down or select the ‘Create groups using project names’ or ‘Create all projects in one group’ option in the ‘Microsoft 365 Group Creation Mode’ drop down in the Migration Settings. 

    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option. 


    Unable to add/assign user: empty target user mapping

    Warning: Unable to add user: empty target user mapping.
     

    Cause: The warning indicates that a user has not been added as a member or/and as an owner to the target Microsoft 365 group and Plan since the source user had not been mapped to any target user in the User Mapping section before launching the migration.

    Warning: Unable to assign user (user account): empty target user mapping.

    Cause: The warning indicates that user’s item assignments have not been set in the target tasks as the user had not been mapped to any target user in the User Mapping section before launching the migration.

    Users themselves are not migrated from the source to the target system. Necessary users, that need to be added to the target groups and Plans, should already exist in the target tenant. The source users should be mapped with the target users in the User Mapping section for the correct group membership and assignment migration.
     
    Possible solution: 

    1.Make sure that all necessary users that correspond to the source users already exist in the target Office 365 tenant.

    2. In Project Migrator select to restart the uncompleted migration on the Data Migration Summary page.

    3. On the Restart Migration page check the User Mapping section. Correct the user mapping, matching all necessary source users with the corresponding target users. Please see how to perform user mapping article for more details.

    Also, the user mapping may be performed via an Excel file using the Export to/Import from Excel options.

    In case the corresponding target user does not exist, and the source user’s group membership and assignments should not be retained in the target system, such warnings may be ignored.

    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.


    N assignments have been skipped due to limit of maximum 11 user assignments per task

    Warning: 11 assignments have been added. N assignments have been skipped due to limit of maximum 11 user assignments per task.
     
     
    Cause: The warning of that type occurs if there would have been more than 11 user assignments in one task together with the already assigned users in the existing target Plan. As there is a limit of maximum 11 user assignments per task in Microsoft Planner, only users that fit the limit will be assigned to the target tasks during the migration, and others will be skipped with the warning. 

    Possible solution: 

    Check how many users are assigned to the tasks in the source Plan(s), and which users have not been assigned to the corresponding tasks in the target Plan(s). If needed, change the assignments in the target Plan(s) manually, or remove the unnecessary user assignments in the source Plan(s) and remigrate them with Project Migrator, selecting the ‘Create new and remove existing Plans before creating’ Plan creation mode in the settings.

    If the skipped user assignments should not be retained in the target Plan(s), the warning may be ignored.
     
    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.


    N attachments have been skipped due to the limit of maximum 10 attachments per task

    Warning: 10 attachments have been added. N attachments have been skipped due to the limit of maximum 10 attachments per task.

    Cause: The warning of that type occurs if there would have been more than 10 attachments in one task together with the already attached files and links in the existing target Plan. As there is a limit of maximum 10 attachments per task in Microsoft Planner, only files and links that fit the limit will be added to the target tasks during the migration, and others will be skipped with the warning.

    Possible solution: 

    Check how many attachments are added to the tasks in the source Plan(s), and which files or links have not been set to the corresponding tasks in the target Plan(s).

    If needed, replace the attachments in the target Plan(s) manually, or remove the unnecessary attachments in the source Plan(s) and remigrate them with Project Migrator, selecting the ‘Create new and remove existing Plans before creating’ Plan creation mode in the settings.

    If the skipped attachments should not be retained in the target, the warning may be ignored.

    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.


    Unable to process attachment: empty name

    Warning: Unable to process attachment: empty name.

    Cause: The warning indicates that the source task attachment, a file or a link, could not be processed and set to the target task as the attachment name is empty in the source.
     
    Possible solution: 

    1. Check the task attachments in the source Plan. Make sure that the attachment name, i.e. Text to display, is specified and that the attachment URL is valid.

    2. Restart the migration for the uncompleted Plans.

    If you need assistance or have any questions, please contact our Support Team at support@fluentpro.com or via the live chat option.
     
     

    Was this article helpful?

    Table of contents

      Still can't find what you're looking for?

      Contact Support
      Back To Top