Brian, thank you for this very detailed explanation.
I would like to add that currently there is a bug with Project Server 2013 that blocks Project Site Permissions synchronization alltogether. After installation of September 2014 CU for Project Server and SharePoint Server, the Project Site Permissions sync fails. Queue jobs are created but the job 'Prepare Project Web App Permission Synchronization For Projects' fails for all existing Project Sites, due to a change in behavior in the September 2014 CU.
Microsoft is aware of this issue, but no date has been communicated when it will be fixed.

Hi All,

@Hans:

Could you provide more information about this issue? We are suffering the same behaviour after applying last CU's.
All existing project sites (those that were created before the update) are not found when 'Prepare Project Web App Permission Synchronization For Projects' fires. With the new ones (those that were created after the update), everything works fine.

You said that "Microsoft is aware of this issue, but no date has been communicated when it will be fixed". Where did you get this information?

@Brian Smith: Do you know anything about this issue?

Kind regards,

Hi again,

Based on log files, what is happening (on projects created before the update) is that Project Server tries to open the project site using the url http://server/myprojectsite instead of http://server/pwa/myprojectsite (note that /pwa is missing).

I've analyzed the assembly 'Microsoft.Office.Project.Server.dll' (15.0.4667.1000 - Nov 2014 CU) in order to get more details. I found some differences with the SP1 version at 'Microsoft.Office.Project.Server.BusinessLayer.PSPermissionSynchronizer.SynchronizeProjectSites(...)'.

I can't figure how is possible that this code works with new project sites but not with older ones.

@Ricardo Herrera:
I have logged a support ticket with microsoft about this issue.
If possible for you, I can only advice you to also open a support case with Microsoft. The more people that complain about this issue, the earlier it will be fixed.
You analysis of the ULS log files is correct. After the September 2014 CU, the URL used for accessing the project sites is missing a key part.

Also note that for new project, you can still have this issue if you create the project site from 'PWA Settings -> Connected SharePoint Sites' instead of automatic creation.

Based on my analysis, the root cause of this issue is that with the September 2014 CU, Microsoft changed the way the project site URL is saved in order to implement a new feature that allows project sites to be created in different site collections (already available in Project Online).

@Hans: Thanks for reply!

Sorry, but our customer can't open a ticket (:() I hope that Microsoft fixes this issue soon. Maybe in a January CU released as a Christmas gift. By the moment, we will try to find a workaround...

Kind regards,

Hi, I would like to confirm Hans observation that its not only happening for sub sites, any project site provisioned other than under root site collection is causing this issue. Until the official fix to come, resolution is to re-configure your project sites to be created under root site. (credit goes to my colleague Peter who has identified this resolution)