Enable-SPFeature: The Project content database has not been provisioned for this content database.

Question

Hello, I am trying to complete the initial configuration (enabling the pwasite feature) of Microsoft Project Server 2019 using the SharePoint2019 Management Shell.

To start off, this problem has been reported before in 2016, and was left with a proposed answer that didn't help me:
https://social.technet.microsoft.com/Forums/security/en-US/7fd40c4b-e6f8-4fe8-ac88-a5941460e37a/enablespfeature-the-project-content-database-extension-has-not-been-provisioned-for-this-content

The solution was that Microsoft has included the extensions, but I still receive this error when try to create my own project management site from the SharePoint 2019 Management Shell running as administrator.

I tried the commands that user Asfaw posted and got the same errors as Andrew P. reported later in that forum.

I am able to activate the 'New-SPSite' command, but not enable the 'SPFeature'.

When I try to connect to my project site, I get:

Sorry, something went wrong

An unexpected error has occurred.

In SharePoint, I've checked the Monitoring > Health Analyzer and I have no errors.

Below is an error I get from Event Viewer about there already being an IP listener, I don't know if that has to do with it.

+ System 

  - Provider 

   [ Name]  Microsoft-SharePoint Products-Project Server 
   [ Guid]  {b2178104-1b5b-4c20-8c8f-960678ced9e5} 
 
   EventID 8140 
 
   Version 16 
 
   Level 1 
 
   Task 19 
 
   Opcode 0 
 
   Keywords 0x4000000000000000 
 
  - TimeCreated 

   [ SystemTime]  2023-10-06T21:01:20.423280100Z 
 
   EventRecordID 4365 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  424 
   [ ThreadID]  9764 
 
   Channel Application 
 
   Computer WinServer130.domain130.lab 
 
  - Security 

   [ UserID]  S-1-5-21-650814884-2191095673-3849160167-500 
 

- EventData 

  string0 ProjectCalculationService16 
  string1 ProjectCalculationService16 DemoProjectServer f5213a3f-7a7e-4afe-bc93-302d1d9ed9b1 
  string2 There is already a listener on IP endpoint 0.0.0.0:16001. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations. 

Original error:

PS C:\Users\Administrator> Enable-SPFeature PWASite -url http://winserver130:15517/sites/demoproject
Enable-SPFeature : The Project content database extension has not been provisioned for this content database.
At line:1 char:1
+ Enable-SPFeature PWASite -url http://winserver130:15517/sites/demopro ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Share...etEnableFeature:SPCmdletEnableFeature) [Enable-SPFeature
   ], SPException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletEnableFeature

Answer 1

Hi @PhilAlmighty

I'm glad to hear you solve the problem ,if you have any issue about SharePoint, you are welcome to raise a ticket in this forum.

By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others." and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:

[Enable-SPFeature: The Project content database has not been provisioned for this content database.]

Issue Symptom:

+ System 

  - Provider 

   [ Name]  Microsoft-SharePoint Products-Project Server 
   [ Guid]  {b2178104-1b5b-4c20-8c8f-960678ced9e5} 
 
   EventID 8140 
 
   Version 16 
 
   Level 1 
 
   Task 19 
 
   Opcode 0 
 
   Keywords 0x4000000000000000 
 
  - TimeCreated 

   [ SystemTime]  2023-10-06T21:01:20.423280100Z 
 
   EventRecordID 4365 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  424 
   [ ThreadID]  9764 
 
   Channel Application 
 
   Computer WinServer130.domain130.lab 
 
  - Security 

   [ UserID]  S-1-5-21-650814884-2191095673-3849160167-500 
 

- EventData 

  string0 ProjectCalculationService16 
  string1 ProjectCalculationService16 DemoProjectServer f5213a3f-7a7e-4afe-bc93-302d1d9ed9b1 
  string2 There is already a listener on IP endpoint 0.0.0.0:16001. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations.

Solution:

The event viewer error was an indicator to what was going on (there already being a listener on the IP endpoint). After watching other tutorial videos on that step, I noticed the URL people would use didn't have a port number in the URL, especially one that was the same as the SharePoint site.

For example, my SharePoint site URL was http://winserver130:15517

and the bad Project Site URL I attempted to create was http://winserver130:15517/sites/project

I changed the URL to http://winserver130/sites/project and it worked.

You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best Regards

Cheng Feng

Answer 2

Hi @PhilAlmighty

I'm glad to hear you solve the problem ,if you have any issue about SharePoint, you are welcome to raise a ticket in this forum.

By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others." and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:

[Enable-SPFeature: The Project content database has not been provisioned for this content database.]

Issue Symptom:

+ System 

  - Provider 

   [ Name]  Microsoft-SharePoint Products-Project Server 
   [ Guid]  {b2178104-1b5b-4c20-8c8f-960678ced9e5} 
 
   EventID 8140 
 
   Version 16 
 
   Level 1 
 
   Task 19 
 
   Opcode 0 
 
   Keywords 0x4000000000000000 
 
  - TimeCreated 

   [ SystemTime]  2023-10-06T21:01:20.423280100Z 
 
   EventRecordID 4365 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  424 
   [ ThreadID]  9764 
 
   Channel Application 
 
   Computer WinServer130.domain130.lab 
 
  - Security 

   [ UserID]  S-1-5-21-650814884-2191095673-3849160167-500 
 

- EventData 

  string0 ProjectCalculationService16 
  string1 ProjectCalculationService16 DemoProjectServer f5213a3f-7a7e-4afe-bc93-302d1d9ed9b1 
  string2 There is already a listener on IP endpoint 0.0.0.0:16001. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations.

Solution:

The event viewer error was an indicator to what was going on (there already being a listener on the IP endpoint). After watching other tutorial videos on that step, I noticed the URL people would use didn't have a port number in the URL, especially one that was the same as the SharePoint site.

For example, my SharePoint site URL was http://winserver130:15517

and the bad Project Site URL I attempted to create was http://winserver130:15517/sites/project

I changed the URL to http://winserver130/sites/project and it worked.

You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best Regards

Cheng Feng

Answer 3

I figured it out. The event viewer error was an indicator to what was going on (there already being a listener on the IP endpoint). After watching other tutorial videos on that step, I noticed the URL people would use didn't have a port number in the URL, especially one that was the same as the SharePoint site.

For example, my SharePoint site URL was http://winserver130:15517

and the bad Project Site URL I attempted to create was http://winserver130:15517/sites/project

I changed the URL to http://winserver130/sites/project and it worked.