none
Permission denied to Team members on Project site RRS feed

  • Question

  • Hi,

    When any project manger add any team memeber and publish project,Project site has automaticaly provided permisiion to team memebr/assigned resource.

    But after publish again project manager edit the project and add the new resource,new resource cant get permisiion on project site automaticaly.

    Kindly suggest.

    Help is appricated.


    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Monday, October 28, 2013 9:43 AM

All replies

  • Hello,

    Do you automatically sync users between PWA and the Project sites? Do you see any failed jobs in the Project Server queue after the publish job?

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Monday, October 28, 2013 11:51 AM
    Moderator
  • No failed job listed.

    how to do sync users between PWA and the Project sites. see belwo image,already enabled


    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Monday, October 28, 2013 12:06 PM
  • Hello,

    So if you assign a user, say User A for now, a task on that project, not just add User A to the project team, then save and publish the project User A doesn't have access to the Project Site once all of the jobs complete successfully in the queue?

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Monday, October 28, 2013 3:17 PM
    Moderator
  • HI Paul,

    I had build the team first and then add the user according task,first time publish then all assigned resource have got access permission as read on project site.

    Problem is when i was trying to again open same project with MSP and build team with other new resource and assigned new task with new resource and then publish.that time new user cant got permission on project site.


    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Monday, October 28, 2013 7:00 PM
  • If you manually sync the site from PWA > Server Settings > Project Sites, do these users get added / access?

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Monday, October 28, 2013 8:18 PM
    Moderator
  • Thanks Paul,

    But manual is so pathetic, 200 project is on going,how to do for one by one.

    can you give me information,why its happen.


    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Monday, October 28, 2013 8:29 PM
  • I'm not suggesting this is a fix / work around at all!

    Test with one project, does this work?

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Monday, October 28, 2013 8:37 PM
    Moderator
  • Yes its working,when done manualy

    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Tuesday, October 29, 2013 5:57 AM
  • Ok, do you see this for all projects / project sites? This works fine on my 2010 test farm. What patch level is the farm?

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Tuesday, October 29, 2013 10:01 AM
    Moderator
  • Hi Paul,

    version given below.

    Microsoft SharePoint Server 2010
    14.0.6029.1000

    Microsoft Project Server 2010
    14.0.6029.1000

    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Tuesday, October 29, 2013 10:18 AM

  • Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Tuesday, October 29, 2013 10:22 AM

  • Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Tuesday, October 29, 2013 10:24 AM
  • Hello,

    I don't currently have access to a farm that is only Project Server 2010 SP1 (14.0.6029.1000) so I can't test / replicate this. My Test farm is SP2 + August 2013 CU. I would recommend that farm should also have the June 2011 CU as a minimum with SP1. There were fixes in the June 2011 CU for SP1. I don't know of any CUs that resolved an issue like the one you described, this functionality has worked since 2007 as far as I know.

    Do you see the issue with all project / projects sites / users?

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Tuesday, October 29, 2013 10:38 AM
    Moderator
  • Not yeat,I will check step by step,but same thing working fine on my UAT machine.

    My Test farm is SP2 + August 2013 CU-- can you provide link and suggest me if i will update any impact on production.


    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Tuesday, October 29, 2013 10:45 AM
  • So on your UAT farm it is works as expected, the issue only exists on the Prod farm? I would confirm if this is for all projects / projects sites/ users on the prod farm.

    I would only update the Prod farm after fully testing the Service pack and CU on a replicate Test  / UAT farm.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Tuesday, October 29, 2013 11:04 AM
    Moderator
  • Hi Paul,

    Thanks for your support and reply.

    Sorry for late reply, Now again i have face same issue,

    All project site has only unique permission and existing user has been removed, only default user is there, All user are using with contribute right before today, but today morning I find all projects site have unique permission, whom I have provided permission ,all have been removed, I don’t know why its happen,

    Truly I am so fed-up this unbehavioral experience. My mail box has full of issue regarding permission


    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Monday, November 18, 2013 11:35 AM
  • Also i have found when I am trying to give permsiion to any body,in queye find error message like below:


    General
    • Queue:
      • GeneralQueueJobFailed (26000) -
        AddSingleUserMembershipInWss.AddSingleUserMembershipInWssMessage.
        Details: id='26000' name='GeneralQueueJobFailed'
        uid='e83f8079-2831-48df-aea2-bbd304d1abd5'
        JobUID='ab759bfe-b57f-4cb5-9781-93b06b6ee496' ComputerName='WF1EPMAP10P'
        GroupType='AddSingleUserMembershipInWss'
        MessageType='AddSingleUserMembershipInWssMessage' MessageId='1' Stage=''. For
        more details, check the ULS logs on machine WF1EPMAP10P for entries with
        JobUID ab759bfe-b57f-4cb5-9781-93b06b6ee496.

    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

    Monday, November 18, 2013 11:36 AM
  • Hello,

    What do you see in the ULS logs for this error? It should give more details.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Monday, November 18, 2013 12:51 PM
    Moderator
  • Hi Paul,

    Nice to read your new bloag.

    Here I have capture USL logs by log viwear.

    I have find many critical issue like followings are

    1.Standard Information:PSI Entry Point:   Project User: Username  Correlation Id: e3b958e8-b9a1-44df-a8f2-9a43e815199d  PWA Site URL: http://*.20.*.*/PWA  SSP Name: Project Server Service Application  PSError: NoError (0) Active Directory Synchronization cannot start for the enterprise resource pool because the Active Directory Guid was not found in the Project Server Database.

    2.Standard Information:PSI Entry Point:   Project User: AD\Hasan  Correlation Id: 2b903386-fb5e-4493-aee9-6212e4cc8a95  PWA Site URL: http://project/PWA  SSP Name: Project Server Service Application  PSError: GeneralQueueJobFailed (26000) A queue job has failed. This is a general error logged by the Project Server Queue everytime a job fails - for effective troubleshooting use this error message with other more specific error messages (if any), the Operations guide (which documents more details about queued jobs) and the trace log (which could provide more detailed context). More information about the failed job follows. GUID of the failed job: 4c02a991-f7d4-48f3-87c6-306e51163dbd. Name of the computer that processed this job: WF1EPMAP10P (to debug further, you need to look at the trace log from this computer). Failed job type: AddSingleUserMembershipInWss. Failed sub-job type: AddSingleUserMembershipInWssMessage. Failed sub-job ID: 1. Stage where sub-job failed:  (this is useful when one sub-job has more than one logical processing stages).

    Help is os appricated.


    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS



    Tuesday, November 19, 2013 8:21 AM