none
Upgraded PWA 2019 - "Sorry, this site hasn't been shared with you" Message RRS feed

  • Question

  • Hello,

    We are upgrading a Project Server from 2010 to 2019 (retaining project permission mode).

    A user who could access the PWA in the 2010 version gets the above message when accessing the 2019 PWA.

    Few checks that we performed:

    1. The admin can access the 2019 PWA
    2. All permissions (users, security groups, security categories) were migrated to the new server (including anything related to the specific user)
    3. The new server is in a different domain than the users (the old one was in the users' domain) but firewall ports are open (admin can connect)
    4. (Don't know if it's related) When the admin opens a user in Manage Users, including her own, under the User logon account box there is a message "We couldn't find an exact match" (but still, that doesn't block her from connecting)

    Thanks,

    Barak

    Sunday, March 22, 2020 12:00 PM

Answers

  • Hello,

    Did you test user access during the migration to 2013 and to 2016 at all? What is the domain set up - one way or two way trusts? Another thing worth checking, was your Project Server 2010 application running in SharePoint Classic mode authentication? If so, did you migrate the users to the Claims based authentication? 

    Paul


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

    • Marked as answer by Barak _ Bester Thursday, April 30, 2020 12:37 PM
    Monday, March 23, 2020 8:46 AM
    Moderator

All replies

  • Hello,

    Did you test user access during the migration to 2013 and to 2016 at all? What is the domain set up - one way or two way trusts? Another thing worth checking, was your Project Server 2010 application running in SharePoint Classic mode authentication? If so, did you migrate the users to the Claims based authentication? 

    Paul


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

    • Marked as answer by Barak _ Bester Thursday, April 30, 2020 12:37 PM
    Monday, March 23, 2020 8:46 AM
    Moderator
  • Hello Paul,

    1. We didn't deploy the 2013 and 2016 environments to the users
    2. Can a one-way trust or an erroneous authentication mode result in one user being able to connect to the PWA while another user can't?

    Thanks.

    Barak

    Monday, March 23, 2020 4:24 PM
  • Hello,

    Anything helpful in the ULS logs?

    Paul


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

    Monday, March 23, 2020 5:50 PM
    Moderator
  • Are the user ID syncing?  Look in the event log and see if there are issues with 1 or more users not syncing with AD.

    My theory is the user ID is not syncing with the current resource quid, mostly because the user GUID was associated with other domain.  There are some powershell scripts floating around that clears the GUID field and the AD sync gets them populated with the right values.


    Michael Wharton, Past MVP, MBA, PMP and a Great Guy <br/> Website http://www.WhartonComputer.com <br/> Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Wednesday, March 25, 2020 4:48 AM
    Moderator
  • The problem was that authentication wasn't set to Claims based
    Thursday, April 30, 2020 12:38 PM