Forum Discussion
"We Couldn't Open Your Project"
Still a no-go. "Couldn't assign resource. Please try again. Correlation ID: b48ba161-17a1-44d9-9752-8ad1c6a56ec2" <-- I get that when attempting to assign her a task.
In addition, since your message, we removed and then re-added her to the project. No go.
We also created a new project in the new "Project for the Web" space (i.e. not the old Project Online world based in SharePoint) and access for that was a no, too. I can list her in the group. But when we get an error either when I try to assign her a task or when she tries to access the project itself.
John Fitch Thank you for continually checking on this. Can you check once more, we believe the issue should be mitigated. Thank you again for your patience.
- slonkakDec 08, 2020Copper Contributor
jackieduong How was this fixed? I'm having a similar issue.
- nasal8412Feb 24, 2021Microsoft
jackieduong could you please share the fix for this issue as one of my customers also facing the same issue
need to unblock this
thanks in advance
- priyankapuranikFeb 24, 2021Microsoft
nasal8412 Could you give us the details with the correlation id? (You should see if if you click on details in the error screen)
- nasal8412Feb 24, 2021Microsoft
priyankapuranik Please find the below
0cdbf6cb-93f2-482a-bdcd-3200e0fcc019
- MatsErikssonMar 05, 2021Copper ContributorAny news to this? I have the same problems, with some of my users. It may have some correlation to Sharepoint links but I am not able to solve this: Correlation ID: 7f7ec85d-e71c-41f0-b302-Bedcfbfa98c6
- faia01Mar 25, 2021Copper Contributor
MatsEriksson or anyone else. Can you share what resolved this error? I'm seeing it as well.
Thank you!
- rhahmMar 30, 2021Copper ContributorI am seeing the same error. I would like to know the resolution as well. I have a complete project that I am unable access.
- Randy DavisMar 30, 2021Microsoft
rhahm Can you give the correlation ID that you see when the project/assignment fails?
- MatsErikssonJan 27, 2022Copper ContributorIt resolved only - as fast as I can remember - with a REPAIR of Office365 which took a while. Since then we've updated to 2019 everywhere so users reporting no problems anymore. And unwieldy and cumbersome fix though.