次の方法で共有

Team members receive Access Denied when accessing Project Details

  • [アーティクル]

Problem:

Team member with My Tasks set by Team Members template and the same for Global Permissions.

Team member user goes to PWA > Project Center and clicks on a project name to open the Project Detail Pages.

Receives message:

         Workflow Status 

         Access Denied  

         Basic Info 

         Details

          

To work around:

Go to PWA > Server Settings > Manage Groups.

Click Team Members group.

Click My Tasks in Selected Categories.

Add "Open Project" to My Tasks for Team Members as in the screenshot below.

         

(If you save now and attempt to reproduce the Access Denied message as a team member, you will see this message: This Web Part was unable to load, as below.)

         

Back in Team Member permissions, scroll down to Global Permissions.

Add New Project under Project.

Save and close Team Member permissions.

Have the team member user access the project in Project Center by clicking the project name.  The Project Details will now appear as below

 

         

Comments

  • Anonymous
    January 01, 2003
    Thanks for your comment. Unfortunately, at this point I don't know when SP1 will be released. I am looking forward to it, though.
  • Anonymous
    January 01, 2003
    Najeeb, troubleshooting by using the comments on a blog can be a frustrating exercise for you and for me. Can I recommend you please contact Customer Support? You will be much more satisfied with the response times and time to resolution. You could start here http://support.microsoft.com/gp/contactus81?Audience=Commercial.
  • Anonymous
    January 01, 2003
    Team members receive Access Denied when accessing Project Details
    thank you
  • Anonymous
    January 01, 2003
    Markus, thank you for posting a comment on my blog!

    Problems with the SharePoint or Project Server functionality are all entered into a sort of master list and the product groups work to determine which fixes have the most impact with the least risk for customers. Because Microsoft has limited resources in terms of developers and testers, the product groups have to make informed decisions about which problems have the most impact on customers. Problems that have a workaround get a lower priority simply because they HAVE a workaround and I feel this is especially true for workarounds that can be handled in the GUI.
  • Anonymous
    February 05, 2014
    I have a PWA in SharePoint mode. In SP mode, I get the ugly "This Web Part was unable to load." Unfortunately, this work around only works for PWA in Project Server mode. Hopefully this bug is resolved in Project Server 2013 SP1.
  • Anonymous
    August 13, 2014
    The comment has been removed
  • Anonymous
    May 20, 2015
    The comment has been removed