Forum Discussion
XiaoqingDeng
Feb 10, 2023Copper Contributor
Sharing project failed after reaching the maximum number of retries.
Hi does anyone know how it happend? I cannot share my MS project to any group today (was able to before). Already tried many groups for few hours now. Thanks
- Feb 16, 2023
Thank you Dale_HowardMVP yes when I came back to work the next Monday, and tried again then worked. Very strange Friday it didn't allow me to share. But anyway works now. Thank you!
RaymondSantos20
Jul 03, 2024Copper Contributor
I'm still encountering this error, any fix aside from waiting it out?
Pascal_UniLu
Jul 08, 2024Copper Contributor
Hello,
I also encountered the same issue. I could narrow it down to a Security Role related issue. My context is the following:
- P4W installed in a dedicated Dataverse environment.
- Environment setting "Enable Ownership across business units" enabled.
- 1 BU per department, projects owned by those BU's (root BU does own nothing).
When you share a project with an MS Teams team, the following happens:
- A dataverse team object is created in the root BU, and assigned "Project Common" and "Project Team Member" in the root BU.
- The ownership of the project record is transferred to the newly created team.
The issue lies with the fact that the team created does not have the required security roles in the BU owning the project.
To work around it, I created the dataverse team manually, linked to the right MS Teams office group, and assigned it the needed security roles in the project owning BU. I did try sharing my project again and it worked.
It is not ideal, maybe someone has a better idea.
Hope this helps.
Pascal
I also encountered the same issue. I could narrow it down to a Security Role related issue. My context is the following:
- P4W installed in a dedicated Dataverse environment.
- Environment setting "Enable Ownership across business units" enabled.
- 1 BU per department, projects owned by those BU's (root BU does own nothing).
When you share a project with an MS Teams team, the following happens:
- A dataverse team object is created in the root BU, and assigned "Project Common" and "Project Team Member" in the root BU.
- The ownership of the project record is transferred to the newly created team.
The issue lies with the fact that the team created does not have the required security roles in the BU owning the project.
To work around it, I created the dataverse team manually, linked to the right MS Teams office group, and assigned it the needed security roles in the project owning BU. I did try sharing my project again and it worked.
It is not ideal, maybe someone has a better idea.
Hope this helps.
Pascal
- RaymondSantos20Jul 09, 2024Copper Contributor
Pascal_UniLu this worked for me. thanks!
- Pascal_UniLuJul 15, 2024Copper Contributor
Hi RaymondSantos20 ,
I eventually found the root cause and a true/cleaner solution.When you share a project with a team, the sharing is done by the Microsoft Project (or Microsoft Portoflios, depending your environment) application user. That user has Project Command and Project System security roles in the root BU, but not on others. Just grant that user those two roles in your target BU. This solves the problem for me.
Best regards,
Pascal.