Forum Discussion
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
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!
16 Replies
- I'm still encountering this error, any fix aside from waiting it out?
- 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.
PascalPascal_UniLu this worked for me. thanks!
XiaoqingDeng So I got the fix identified. When you share the Project with a group i.e., the Azure AD group, the group must not have a hidden membership set. The group has to be either Public or Private but if the group has a hidden membership set, you can not assign the project to it.
Look at the attachment, I have pointed out 2 types of groups of 2 different types. Hope this helps!!
- The image and solution is not clear, could you kindly elaborate. Really appreciate your help here
aditijain1508 The Azure AD group are classified as public, private, common_public etc. FOr the MS project that you have created you have to make the group (Remember MS Teams Team is also a group)as Public for it to be shared. In the attachment, right corner, yo can see the group type
- I'm a bit confused because I guess that my Microsoft 365 group has no hidden membership set. Where can I check this ?
Nevertheless, I got the same error message when I try to assign this group to a new P4TW project :
"Sharing project '' failed after reaching the maximum number of retries. Group '' still exists, please try sharing with this group again."Nicolas_Mattioni See the attachment righ top corner. The group to which the MS project is shared shouldn't be saying HIdden Mombership, it has to be either public/privatecommon public
- I'm also having the same problem.
- Re: Sharing project failed after reaching the maximum number of retries. - Dale_HowardMVP I have found uut a fix for below topic
So I got the fix identified. When you share the Project with a group i.e., the Azure AD group, the group must not have a hidden membership set. The group has to be either Public or Private but if the group has a hidden membership set, you can not assign the project to it.
Look at the attachment, I have pointed out 2 types of groups of 2 different types. Hope this helps!!- AmarHonnungar --
Brilliant! Thanks so much for sharing the solution to this annoying problem. Much appreciated. We all learned something new today!
I am having exactly the same issue XiaoqingDeng did it completely disappear?
- I am also seeing this error since months time!!
- That is the strangest error message I have ever seen in Project for the Web. I personally have never experienced this problem. Question - Do you still have the same problem today? I know that some issues with Project for the Web go away on their own. I do not know why that happens, however! Please let us know and we will try to help you.
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!
