Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Accessing the Project Site in SharePoint RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I am an admin in PWA.  Admins have ability to access the project web site.  However, when I click on the site in Server Settings -> Operational Policies -> Project sites or directly from the projcet itself using the project site button I get an errmsg 'ACCESS DENIED'.  I am also on the team for this project.  How can I get access to the project site in SharePoint?  I deleted / re-created from the Project sites page.  I have multiple projects and cannot access any of them.  I am able to create other kinds of sites inside of sharepoint.  TIA.

    scott howes

    Friday, June 29, 2012 7:12 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    From our admin. 

    The issue came down to two Object Caching accounts not having permissions to the Project Server Web Application in SharePoint.  The SharePoint support representative was finally able to identify the accounts through the many logs sent them from our testing.  These specific accounts, according to TechNet, are used to cache user objects and increase performance while accessing web applications.  However, there is no indication in the TechNet articles of their particular use and configuration specific to Project Server.  Even though I had these accounts configured and applied to the Project Server web application anyway to better the performance, we had to remove and re-add them.  Once we did that we were able to access all the Project sites.  This was an unusual issue that the Project Server support representative had never seen whereas the SharePoint Support had seen in other areas of SharePoint but not Project Server. 

    scott howes

    • Marked as answer by scottky Tuesday, July 24, 2012 12:31 PM
    Tuesday, July 24, 2012 12:31 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
     

    Hi Scott,

    If the issue is user specific, try re-saving your account.

    PWA>>Server Settings>>Manage User

    Edit your account and click on save

    You may need to validate Automatically Synchronize project web app users is enabled or not from Project Site Provisioning settings

    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Friday, June 29, 2012 7:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Sorry, I should have mentioned that it is affecting all users, none of us can access any of the sites.  I went to the Server Settings -> Project Site Provisioning Settings and everything looks good there.  I did uncheck the project site permissions box, saved, then went back in and checkmarked the box and saved again.  Still no luck. 

    scott howes

    Friday, June 29, 2012 8:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    "User Synchronization for Project Web App App Root Site and Project Sites" queue job is responsible for synchronizing PWA permissions with project sites.

    From manage queue page, could you please check the status of "User Synchronization for Project Web App App Root Site and Project Sites"

    You may need to remove and add one user from any PWA Category or group (Except Admin) to initiate this job

    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Friday, June 29, 2012 8:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
     

    Also you may try synchronizing one site for testing purpose

    PWA>>Server Settings>>Project Sites

    Highlight any project name and click on "Synchronize"

    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Friday, June 29, 2012 8:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for responding but the issue persists.  I removed a user (inactivated) and synch'd the site.  Exited and came back in and still get error.

    scott howes

    Friday, June 29, 2012 8:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You need to add the user again to initiate the job

    did you verify the status of the job?

    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Friday, June 29, 2012 8:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I went to the user page and selected active then saved.  When I went to the manage queue jobs it was not listed so I assume it already ran.  Usually I see a list there but sometimes not if they run fast.

    scott howes

    Friday, June 29, 2012 8:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You need to remove any user from PWA category or group and add it back.

    PWA>>Server Settings>>Manage Groups

    Select any group like Team Member

    Highlight one user and remove, save the changes

    Once again edit Team Member group and add same user back into the group

    This should initiate the job

    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Friday, June 29, 2012 8:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Is this Project Server 2010?

    If so is the Project BI Center having the same problem?

    If yes, can you create another PWA instance using the same web application inc new content db (limit the sites on the current content db, create a new content db with no limit > provision a new pwa site) - does the issue occur there as well?

    If yes again, try creating a new web application with a new PWA instance - if you find this works, I would think about doing a DB Backup/Restore then create a fresh web app and point it at the restored dbs.

    I encountered this on client site and fixed it this way.

    Rob Hardy

    Saturday, June 30, 2012 8:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, BI has same issue.  I will try these suggestions and report back.  Thanks.

    scott howes

    Monday, July 2, 2012 1:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Actually the BI web form comes up, but it says Build Failure!  The Project Detail Pages give the Access Denied errmsg too. 

    scott howes

    Monday, July 2, 2012 1:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Maybe just try restoring the databases to a new web app/newly restored pwa instance and see if it at least fixes it for you.

    If the errors vary - check the ULS logs obvisouly.. Mine didn't when on a client site, just access denied errors. But all places relating to data from the content db (tho that was ok in itself)

    Let us know how you get on!

    Rob Hardy

    Monday, July 2, 2012 4:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We are still working on this, have sent the ULS logs to the vendor for review.  We are trying to determine the root cause before we re-install everything.

    scott howes

    Thursday, July 12, 2012 12:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    From our admin. 

    The issue came down to two Object Caching accounts not having permissions to the Project Server Web Application in SharePoint.  The SharePoint support representative was finally able to identify the accounts through the many logs sent them from our testing.  These specific accounts, according to TechNet, are used to cache user objects and increase performance while accessing web applications.  However, there is no indication in the TechNet articles of their particular use and configuration specific to Project Server.  Even though I had these accounts configured and applied to the Project Server web application anyway to better the performance, we had to remove and re-add them.  Once we did that we were able to access all the Project sites.  This was an unusual issue that the Project Server support representative had never seen whereas the SharePoint Support had seen in other areas of SharePoint but not Project Server. 

    scott howes

    • Marked as answer by scottky Tuesday, July 24, 2012 12:31 PM
    Tuesday, July 24, 2012 12:31 PM