In my tests it does appear to need values for the final three parameters even when disabling the quota check – I’ve just put in the ones already set (apart from reducing the ReadOnlyLimit which needs to be below the MaxDbSize). Enabled:$false -ReadOnlyLimit 10200 -ReadOnlyWarningThreshold 90 -MaxDbSize 10240 To disable the quota you can use a PowerShell command executed in the SharePoint 2016 Management Shell:

Please don’t disable the timer job – it does do good stuff as well as this one bad thing… So you may not see this at the point you exceed the threshold – but the following morning when you try to access PWA. This in turn sets a flag that gets check when each page of PWA is loaded. Which runs daily, and by default between midnight and 3am. Project Server: Database Maintenance job for Project Server Service Application – The quota gets calculated as part of the timer job. It isn’t however just the content DB size as we are only counting certain project tables and certainly not the DB logs. The quota size for a PWA is set by default in Project Online to 10GB – so that is the size that will also trigger the yellow banner above. We will also be updating the upgrade instructions on TechNet to include the PowerShell script to disable the quota check. We do have a fix in the works for this issue – and it will ship in one of the first updates for Project Server 2016 so hopefully most customers will not be affected by this issue. One of the inadvertent additions is the Project Web App data quota… If you are migrating a large database to Project Server 2016 – or as your Project Server 2016 PWA content database grows you may one day see it go into read-only – with a yellow banner saying “

Thanks to Anil for this last piece of information ***Īs you may know, we have included many of the features and improvements that have been added to Project Online over the last year or two into the on-premises release of Project Server 2016. We have see where the 'read-only' banner persists and re-applying the license has resolved the problem - Enable-ProjectServerLicense -Key. *** Update - This issue was resolved in the May 2016 Public Update - and all subsequent patches (we no longer enforce quota for on-premises Project Server 2016). First published on TECHNET on Apr 07, 2016

Ms project file changes to read only