Project Server technical bits

This has been painful Project Online reporting has been a fairly significant limitation of the Online experience for me so far.  Besides the complexity in building the oData stream, the fairly fundamental limitations of the data filtering of the URI's has been a major falling down point for me. To digress for a moment, most reports people want are timephased in some way, either Actual Work by period, planned work by period, or timesheet data by period.  All of these reports lead to a "time by day" feed.  Now the thing with timephased reports is you are usually looking for a "last three months, next three months" view (or similar).  Also the thing with the Time By Day feeds is that they are HUGE! Add these things together and you really need a way of limiting your data feed to avoid extremely lengthy refresh times. Easy enough I hear you say.  Just put a timebyday ge '2014-01-01T00:00:00' select statement in your URI before adding it into your Pow...

Event You see a queue failure - "User Synchronization for Project Web Access App Root Site and Project WSS Workspace" You may see a ULS entry that looks something like this:- 10/06/2008 17:11:37.16 Microsoft.Office.Project.Server (0x07D8) 0x0CF0 Windows SharePoint Services Database 6f8g Unexpected Unexpected query execution failure, error code 1205. Additional error information from SQL Server is included below. "Transaction (Process ID 98) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction." Query text (if available): "{?=call proc_SecAddPrincipalToRole(?,?,?,?,?,?)}" What this means Some element of PWA or Project Workspace permissions synchronisation has partially or completely failed due to a deadlock. Users may not be able to access the PWA site and/or WSS Workspaces associated to Project files Triggers The User Synchronisation of Project Workspaces and PWA ...

The scenario: You have a project workspace linked to a project That workspace has a custom document library/list or Item that requires limited user access The permissions for the document library are not inherited from the parent site Users for this document library/list are added individually The action Customer permissions are changed in PWA User Sync kicks off and re-syncs the users permissions The outcome The user permissions are removed and re-added to the site as expected Any "unique" user level permissions on the site are removed (ie if you have added additional "contributor" access as well as the Microsoft Office Project Server group permissions, etc) The users permissions on the list/item that do no inherit from the site are also removed but are not re-added It appears that the user synchronisation can remove all permissions from the site, lists and items including those where permissions are not inherited, but can only add site level and inherited permissi...