Project Server : Invalid object name "pjrep.MSP_EpmProject_UserView"

Information!

---

By default, the PWA database has user views for projects, tasks, and assignments. After installing the updates, the content database stopped showing these user views. In the below screen of the content database, you can see there is no user view as “pjrep.MSP_EpmProject_UserView“, and other user views related to tasks and assignments are also missing

The Missing Views "pjrep.MSP_EpmProject_UserView" in Project Server 2016 Database and maybe there are other views which are end name with "_UserView" that are related to Tasks, Risks, TimeSheet, Resources, and Assignment ..etc as below

How to find out the issue

I have SSRS integrated mode reports that read data from the default reporting views in Project Server 2016 database, Suddenly these reports stopped working for no reason! So, After investigating the issue by checking the datasets of these reports and I found out that the "pjrep.MSP_EpmProject_UserView" is missing as below

It’s a bug in Project Server 2016, The reason one of the following

1. You may have changed for custom fields and there's an issue during the Regenerate because those views are always updated and regenerate with any change in the structure for the Assets project such as tasks Fields, resources Fields, custom fields,Risk Fields ...etc 
2.  You have configured a new Project Server 2016 farm that it’s a build number less than 16.0.4639.1001 (Jan CU 2018). 
3. You have patched the current Project Server 2016 farm with a new CU that is older than Jan CU 2018. 
4. You have performed a migration from Project Server 2013 to Project Server 2016

Solution No1 (Almost Reason)

1- Run the Repair Script below

Script!

---

Repair-SPProjectWebInstance -RepairRule 7

2- check the ULS log to debug the issue. Here’s the screen of that log:

3-Looking at the log, I found that the problem existed in the store procedure – "MSP_Epm_GenerateAllMultiValueAssociationViews".In the below screen, you can see the highlighted line causing the problem:

I changed that line in the store procedure to fix the issue. Here’s what I replaced it with-

Script!

---

CF_INDEX int IDENTITY (1,1)

I then re-run the same repair command. And as you can see, this time the status showed "Succeeded" and check the views

---

Solution No2

you have to make rollback in case if there is any update on the project structure (Custom Fields)

---

Solution No3

you have to download the last patch to keep your environment up to date and then run the Configuration Wizard

---

Notes!

---

• Run the Sharepoint Configuration Wizard after all fixes installed!
• It’s not recommended to install SharePoint update on the production environment until tested on dev/test environment.
• Perform a full backup before starting the update process because you can’t rollback the Cumulative Update Installation.