Blog Post

Project Support Blog
2 MIN READ

Project Server: Project Subsite Lists Lack Essential Forms

Brian-Smith's avatar
Brian-Smith
Icon for Microsoft rankMicrosoft
Aug 08, 2023

Limited Functionality: Project Subsite Lacks Essential Forms

 

** Edit 8/9/23 Although this was initially reported with 2016, I understand the same could occur with 2019 or the Subscription Edition.  The mitigation would be the same **

 

Problem Description:  

Consider the following scenario,

  • A new site template is created.
  • The site template is associated with an Enterprise Project Type (EPT)
  • A new project is published using this EPT, for which a new SharePoint site is created.
  • While working within this new site, a user attempts to add a new list item to deliverables, issues, or risks.

In this situation, instead of seeing the new form, they may see the following error message:

        "Sorry, something went wrong. Unable to find the default new form for <list name>."

 

Root cause:  

This issue began after installing the January 2022 public update (PU) for SharePoint Server 2016. It specifically affects custom project site templates, while the out-of-the-box template functions properly. Moreover, the problem only arises when creating the Project Site automatically during project publish.

This issue can be seen if the Service Account with which the Project Server Queue Service is running is not added to the Local Built-in Administrators group on all the servers or the server where the Project Server Queue Service is running.

Solution:  

If you encounter this issue, please follow these steps to resolve it. The following changes need to be done in all server machines that runs the Project Server Queue Service,

  1. Go to the following file:  C:\inetpub\wwwroot\wss\VirtualDirectories\80\web.config

    If you have other defined web applications on other ports, then you’ll need to modify them as well. For instance, you may have a virtual directory on port 90 and so you’ll go to folder C:\inetpub\wwwroot\wss\VirtualDirectories\90 to edit the web.config file.

  2. In Explorer right click on the file to display the short-cut mention and then select Properties.
  3. Click the Security Tab, click the Edit button and click the Add button.
  4. Add your service account as new user and click Ok.
  5. Once the service account is added -> select and apply Read permissions
  6. Restart IIS and the Project Server Queue service.

 

Related document: Plan for administrative and service accounts in Project Server 2013 - Project Server | Microsoft Learn

Updated Aug 09, 2023
Version 2.0
  • Hi
    perhaps related: A customer changed the account running Queue, Event and Calculation Service to the service account running Project Server Service. The account was no local admin. But is member of wss_admin_wpg group and that has modify permissions on the web.config. 

    The effect was that the Reporting Publish jobs in the queue failed because with a 401 unauthorized error. The error was resolved by granting this account local admin permissions.

    But the default would be that the farm account runs the three services and this works without local admin permissions.

    Reporting message processor failed:

    • ReportingProjectChangeMessageFailed (24006) - Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)). Details: id='24006' 
      name='ReportingProjectChangeMessageFailed' 
      uid='b0d71dc5-1782-ee11-8a1b-005056b161d1' 
      QueueMessageBody='Project UID='d87a5344-6967-ee11-8a18-005056b161d1'. PublishType='ProjectPublish'' 
      Error='Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))'

      Regards

      Christoph

  • Adrian_Bear's avatar
    Adrian_Bear
    Copper Contributor

    Hi Brian,

     

    Thanks hugely for your post. I thought we might be the only users experiencing this issue.

     

    I am getting this exact issue with a Customer in a very locked down environment.

     

    Update: I have now tested your solution in our environment, but alas it did not resolve it.

    Do you have any further info that could lead us in the right direction?

    FYI, sites provision perfectly from PWA Settings=>Connected SharePoint sites=>Create Site

     

    Thanks

    Adrian