SELECT permission was denied on the object 'MSP_PROJECTS'

Question

I have a SharePoint 2016 enterprise edition with Project server 2016 configured.

I am tried to run the SharePoint configuration wizard, the "psconfig.exe" didn't complete successfully and I get this error:

The SELECT permission was denied on the object 'MSP_PROJECTS', database 'WSS_Content_PWA', schema 'pjpub'

An exception of type

Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. 

Additional exception information:

Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence failed.

Exception:

The SELECT permission was denied on the object 'MSP_PROJECTS', database 'WSS_Content_PWA', schema 'pjpub'.

---

Why I get access denied for MSP_PROJECTS in Project Server 2016?

Please, help!

Answer 1

The SELECT permission was denied on the object 'MSP_PROJECTS', database 'WSS_Content_PWA', schema 'pjpub'

If you have recently updated your sharepoint 2016 farm with December 2019 Public and tried to run SharePoint 2016 Configuration wizard, you will get this issue:

The SELECT permission was denied on the object 'MSP_PROJECTS', database 'WSS_Content_PWA', schema 'pjpub'

---

Solutions
you have two workarounds to fix "Access Denied issue for MSP_PROJECTS".

1. Fix the database permissions issue for your farm account on your content database. or
2. Try to patch your farm with the latest SharePoint Cumulative update (January 2020 CU).

Fix the database permissions issue for your farm account on your content database in Project Server 2016

[Workaround 1]

• First, Get PWA Instance Details to know which content database is used for your instance.
• Open SQL Server Management > Connect to your SQL Server.
• Under the databases, check your content database.
• Expand "Security", check if the farm account is there.
  
• Right-click on the farm account, select properties.
• Set the default schema to "dbo" and press "Ok".
  
• The final result should look like
  
• Finally, try to run the SharePoint 2016 configuration wizard again that should be now completed properly.

Try to patch your farm with the latest SharePoint Cumulative update (January 2020 CU)

[Workaround 2]

If the above workaround didn't solve this issue, so you have to patch your farm with January 2020 CU that should solve this issue as per my test.

Meanwhile, you should be aware of if you have migrated from Project Server 2013 to Project Server 2016, you may face the same issue after applying SharePoint January 2020 CU.

---

Check also

• Install Project Server 2016.
• Migrate to Project Server 2016 Step By Step

Comments

Thanks for the detail answer, let me check and feedback you!

---

Awesome answer, worked like charm! thanks!

---

Glad to hear it helped you :)

---

Very helpful