Brooks White, Sr. PFE for Project Server

I am a Microsoft Premier Field Engineer supporting Project Server.

Team members receive Access Denied when accessing Project Details

Team members receive Access Denied when accessing Project Details

  • Comments 7
  • Likes

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
  • 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.

  • Thanks for your comment. Unfortunately, at this point I don't know when SP1 will be released. I am looking forward to it, though.

  • Team members receive Access Denied when accessing Project Details
    thank you

  • Dear,
    When i try to add the "My Task" Web part in My site then it will gives the below error.

    "Server Error in '/' Application.

    Object reference not set to an instance of an object.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:


    [NullReferenceException: Object reference not set to an instance of an object.]
    Microsoft.Office.Server.WorkManagement.UI.AWIOPUtilities.GetSharedComponentManagerInitializationScript(Page page) +158
    Microsoft.Office.Server.WorkManagement.UI.TaskListControl.GetTaskListInitializationScript(Page page, String clientId, String timelineDataSourceId, Boolean hidden) +30
    Microsoft.Office.Server.WorkManagement.UI.TaskListControl.OnLoad(EventArgs e) +104
    System.Web.UI.Control.LoadRecursive() +94
    System.Web.UI.Control.AddedControl(Control control, Int32 index) +728
    Microsoft.Office.Server.WorkManagement.UI.TaskListWebPart.CreateChildControls() +240
    System.Web.UI.Control.EnsureChildControls() +188
    System.Web.UI.Control.PreRenderRecursiveInternal() +72
    System.Web.UI.Control.PreRenderRecursiveInternal() +239
    System.Web.UI.Control.PreRenderRecursiveInternal() +239
    System.Web.UI.Control.PreRenderRecursiveInternal() +239
    System.Web.UI.Control.PreRenderRecursiveInternal() +239
    System.Web.UI.Control.PreRenderRecursiveInternal() +239
    System.Web.UI.Control.PreRenderRecursiveInternal() +239
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4089

    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18446"

    What the solution?

  • 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.

  • It is now May 2015, running project 2013 in sharepoint permission mode and all the latest patches are installed (in the meantime they provide updates via windows update, which is nice) and we have this issue, normal users cannot open the project on pwa.
    why the hell is this still an issue. usually i do not like workarounds like this, this should be a basic functionality which should work out of the box.
    i tried also the powershell command
    Sync-SPProjectPermissions -Url “{Enter your PWA URL here}” -Type “Full”

    But this did not help also. so now i'm trying the workaround.....

  • 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.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment