Hello. I have seen an issue such as this occur after a recent upgrade, and it was was resolved by running a Verify and Repair on the affected project. To run the Verify, you will need to access Site Admin and select the project in the left project list. Right-click on the affected project, hover over 'Maintain Project' and select 'Verify Project' from the menu that displays. In the 'Verify Project' window, click the 'Verify Project' button in the bottom left corner. Once the Verify process has completed, click the 'Export Log' button and save the file to your desktop and close the 'Verify Report' window.

Before running the Repair on the affected project, there are a couple of things I would like to make you aware of. First, I suggest that you make a backup copy of the projects repository folder in case any unforeseen issue occurs (Default location - C:ProgramDataHPALMrepositoryqcDOMAINProject_Name). After the Repair process has completed, you can delete the project repository backup folder to save space on your server's hard drive. Second, the Repair process requires you to deactivate the project, so you will need to make any active users aware of the short window of downtime until the Repair process is complete. While in Site Admin, select the affected project once again and right-click on it. hover over 'Maintain Project' and select 'Repair Project' from the menu that displays. In the 'Repair Project' window, click the 'Repair Project' button in the bottom left corner. Once the Repair process has completed, click the 'Export Log' button and save the file to your desktop and close the 'Repair Report' window. The project will be re-activated automatically. After you have completed the Verify / Repair process, I would like for you to retest to see if the issue still occurs.