Installing SharePoint 2016 Part 8

Creating Project Server 2016 Web App

Around 10 years ago, I was on a full time job of working as Project Server consultant and developer working with project managers and team leads in writing project plan and then creating SQL reports that helped the company making informed decision on the workforce. Project server has changed allot since then but with SharePoint 2016 a lot has changed now.


Step 1 – Download Project Server 2016 installation files. Stop! Just Kidding. Project Server 2016 is now part of SharePoint 2016 setup. You just need the License key of Project Server and a single line of PowerShell will enable the project server on the server.

You can get the SharePoint Server 2016 ISO and License keys for both Project Server and SharePoint Server from

Enabling Project Server 2016

Open PowerShell ISE as administrator – add the SharePoint snapin and run the following cmdlet.

Add-PSSnapin microsoft.sharepoint.powershell -ErrorAction SilentlyContinue
Enable-ProjectServerLicense -Key “Y2WC2-K7NFX-KWCVC-T4Q8P-4RG9W”


Creating Project Server Service Application

This is simple process using PowerShell or User Interface.

$ApplicationPool = Get-SPServiceApplicationPool “SharePoint Web Services Default”

$ProjectServiceApp = New-SPProjectServiceApplication -Name “Project Service Application” -ApplicationPool $ApplicationPool -Verbose

New-SPProjectServiceApplicationProxy -Name “Project Service Application Proxy” -ServiceApplication $ProjectServiceApp -Verbose


Creating Project Server Web App

First choose the web application where you want to create the site. We will do all the steps with PowerShell.

If you are not familiar with Project Server then you need to know that the database structure of Project Server is different than a SharePoint content database. It has its own tables and schema. Traditionally Project Server used to have 4 Databases which were later merged to single. Content database is always there to store the Project sites which store project documents.

So as a step one we will create a new content database and set it site limit to one so no one can create the site again.

$WebApplication = Get-SPWebApplication

$ProjectDB = New-SPContentDatabase -Name “WSS_Content_ProjectSite” -WebApplication $WebApplication -MaxSiteCount 1 -WarningSiteCount 0


Note: You can also create new SPSite object directly in a new content database but if you are on a heavily used SharePoint Farm it is highly likely that another site collection will be create in the same DB.

You can create the project web app like but traditionally it is created as So I will first add a new managed path as explicit inclusion.

New-SPManagedPath “PWA” -Explicit -WebApplication $WebApplication -Verbose

To create the Web app run the following cmdlet.

$Site = “”

$Template = “pwa#0”

$Name = “Project Web App”

New-SPSite -Url $Site -Template $Template -Name $Name -Description $Name -ContentDatabase $ProjectDB -OwnerAlias contoso\spadmin

Wait for few minutes to complete the process. We are not done yet. We have just created a project web app site collection. We now need to provision the database schema by running the following

Enable-SPFeature pwasite -Url $Site -Verbose

Start-Sleep 300

I also kept my ULSViewer started and filtered to see “Product” eq “Project Server”.


Wait for few minutes to see some activity in Project Server e.g. Queue etc. This will ensure that all components are project server have come online.


Let’s browse the site.


Here you go.


Moving a project server Database and pwa site collection

Project Server 2013 database is a resource intensive database becuase of having Published, Draft, Reporting and Archive Tables.  Although Microsoft had distributed them to 4 databases in past but decided to stick with one in 2013.  For high project server usage Microsoft Recommended us to move Project Server Database and PWA Site collection database to a seperate SQL Server and Seperate Drive. 

PWA Site Collection can be moved to new Content Database using Move-SPSite cmdlet.  It guess it is simple process but The PWA Database move can be done using User interface if you are a Farm admin but process is somehow resulted in access denied for me.  I am putting it down.

  • Backup the PWA Database and Restore using SQL Server management studio on 2nd SQL Box.
  • Open Central Administration –> Manage Service Application –> Project Server Service Application
  • Click on down arrow next to PWA instance and Click Edit (Note you must have DBO on PWA DB to edit)
  • Change SQL Server name and click OK.
  • Browse the PWA Site.

You can also use PowerShell. 

  • Dismount the PWA Database that will automatically dismount the instance
  • Dismount the PWA Instance
$PSA = Get-SPServiceApplication | Where{$_.TypeName –Eq “Project Server Service Application”} #Change the name if required.

Dismount-SPProjectDatabase –Name ProjectWebAppDB –ServiceApplication $PSA

or Dismont the PWA instance

#If you have a single Instance
Get-SPProjectWebInstance | Dismount-SPProjectWebInstance

#if you have multiple instances
Dismount-SPProjectWebInstance -SiteCollection ""

#You can also use Get-SPProjectWebInstance and then get the ID to remove it.

then you can

Add-PSSnapin Microsoft.SharePoint.PowerShell -ea 0 
Mount-SPProjectDatabase -Name ProjectWebAppDB -DatabaseServer ProdSQL2 -WebApplication
Mount-SPProjectWebInstance -DatabaseName ProjectWebAppDB  -DatabaseServer ProdSQL2 -SiteCollection
Get-SPProjectWebInstance | Select Url, DatabaseName, Id

Browse and Test the Site. 


Make sure you update any Reporting Services or Excel Reporting data connections on your BI Sites.  Better to publish them again.

Project 2009 Conference



Save $150 by being one of the first 500 attendees to register!  Register now at to secure your Early Bird discount rate of $699.


And, we wanted to be sure you also received this:  Your personal invitation to present at Project Conference. 


New this year! The Project Conference team has received a tremendous amount of interest from customers and partners to present content at Project Conference 2009. In response, we are formally offering customers, partners and you an opportunity to contribute to and present content at Project Conference 2009.  We encourage customers, partners and you to utilize the content submission form at to propose content ideas and speakers.  Time is limited – let your customers and partners know and act now!

Project & Project Server Infrastructure Updates

If you are looking forward to apply the infrastructure updates on Project and Project Server 2007 read the post

On July 15th, 2008 Microsoft announced the availability of the Infrastructure Update for Office Servers. The Infrastructure Update for Office Servers is a set of updates to improve platform performance and contain several customer driven fixes. The updates are applicable to Microsoft Office SharePoint Server 2007, Windows SharePoint Services 3.0, Microsoft Search Server 2008 & Microsoft Search Server 2008 Express, Microsoft Office Project Server 2007 and Microsoft Office Project 2007.

There are several noteworthy new features and fixes shipped in these updates for Project Server 2007 and Project 2007; specifically:

Read more…