Skip to main content

Issue provisioning PWA on Root (HNSC or Site) in #projectserver2016

Following on from my previous 2016 PWA Setup post, I am encountering an issue with PWA on the root of a HNSC with PWA in ProjectServer Permission Mode.

 Scenario

  I want to create a pwa site on a HNSC at http://pwa.domain.com,  I don’t PWA as a pathed web under the HNSC (‘/pwa’) and I would like to avoid using a Host Header on a separate webapp with PWA provisioned at ‘/’ if poss as its horrible and ikkie

Method

  1. Create a web app on server name http://fe1
  2. Create a root Site Collection on the web app
  3. Lock Content DB down
  4. Create new Content DB for the PWA site
  5. Create a HNSC called http://pwa.domain.com pointing to the above web app using the PWA#0 template etc

    New-spsite "http://pwa.domain.com" -hostheaderwebapplication "http://fe1" -name "PWA" -Description "Project Web App" -owneralias "Domain\user" -language 1033 -template "PWA#0"
  6. Lock the content db down
  7. Enable PWASite features and all that jazz
  8. Switch to Project Server permission mode
  9. Add a user to a PWA User Group to trigger the sync


At this point adding resources returns this in the ULS

An unexpected exception occurred while processing queue messages of type PSPermissionSynchronizePWASite, Exception: System.ArgumentException: Trying to get name of an SPWeb at the root web app is not allowed. 
SPweb?  huh?  I created an SPSite surely!


And this in the queue
 GeneralQueueJobFailed (26000) - PSPermissionSynchronizePWASite.PSPermissionSynchronizePWASiteMessage. Details: id='26000' 
name='GeneralQueueJobFailed'
uid='2712a0fb-fa27-e611-80bb-00155d940402'
JobUID='2112a0fb-fa27-e611-80bb-00155d940402'
ComputerName='6ce47b31-e9bf-41c3-ae1d-0ebdf5c14dc6'
GroupType='PSPermissionSynchronizePWASite'
MessageType='PSPermissionSynchronizePWASiteMessage'
MessageId='1'
Stage=''
CorrelationUID='81e4819d-d915-3091-14dc-6f20bb3fa683'
For more details, check the ULS logs on machine 6ce47b31-e9bf-41c3-ae1d-0ebdf5c14dc6 for entries with JobUID 2112a0fb-fa27-e611-80bb-00155d940402. name='GeneralQueueJobFailed'
 uid='2712a0fb-fa27-e611-80bb-00155d940402'
 JobUID='2112a0fb-fa27-e611-80bb-00155d940402'
 ComputerName='6ce47b31-e9bf-41c3-ae1d-0ebdf5c14dc6' GroupType='PSPermissionSynchronizePWASite' MessageType='PSPermissionSynchronizePWASiteMessage'
 MessageId='1'
 Stage=''
 CorrelationUID='81e4819d-d915-3091-14dc-6f20bb3fa683'
 For more details, check the ULS logs on machine 6ce47b31-e9bf-41c3-ae1d-0ebdf5c14dc6 for entries with JobUID 2112a0fb-fa27-e611-80bb-00155d940402.

So what does work so far and what doesn't....


  1. new-SPSite on an explicit managed path ('/pwa') or under a wildcard path '/pwasites/pwa1' - OK
  2. new-SPSite on Root of a Web App with hostheader as '/'  - FAIL (expected as it seems to be SPSite on Root that the issue is
 So it seems that PWA cannot yet be on root anywhere.... YIKES!


Comments

Post a Comment

Popular posts from this blog

TPG Apps Highlights - Risk Matrix #projectonline #projectserver #risk

This post is the first of a series to highlight the apps available for Project Server and Project Online from the SharePoint store  ( https://store.office.com/search.aspx?productgroup=SharePoint&qu=tpg ) and direct via your local TPG office. The first of this series will look at the s imple plug-and-play apps that all users of Project Online can make use of quickly and easily.   T hese are: Risk Matrix  Milestone Trend Analysis (MTA) WBS Chart viewer Next we will focus on the challenge of  Resource Request Supply and Demand by demonstrating our more recent TeamLink and TeamManager apps. Team Manager App is a Resource Manager/Owner app for allocating resource supply to Projects and BAU activities and monitoring demands against commitments Team Link App is a PM tool for monitoring Project demands vs the supply provided by the Resource Managers  Finally I will highlight some of the benefits of our integration tools when used in the context of Project Online
Post a Comment
Read more

Restoring PWA Site to another Web App in the same Farm

The scenario is this: SharePoint 2016 Farm with Project Server Two Web Apps Development UAT One PWA on Development Web App. I want to copy the PWA Site on Development web app to UAT to support a testing cycle. As far as I knew there were two options: 1) Content Database Restore and Attach Process would be backup your Dev Content Database, Restore to a new Content Database for QA, then mount the database on the appropriate web app and your off.... Problem:  Although you can do this with the -AssignNewDatabaseID switch in Powershell (to avoid two content db's having the same database id) the Site Collection (PWA) in the db still retains its SiteID which means there is a duplicate SiteID in the Configuration Database.  This stops the PWA site being created and alllocated correctly and becomes essentially orphaned. This method is only any good for MOVING not COPYING Back to the drawing board... 2) Backup-SPSite / Restore-SPSite I didn't believe this w
1 comment
Read more

Migration Project Server (2010 to 2019) Issue 1 - Upgrading from 2013 to 2016 - Error encountered while migrating project data in Content database. The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users

I was intending to write a set of posts on the topic of migrating SharePoint and Project Server from 2010 on premise through 2013, 2016 to 2019 Azure, using SQL Managed Instance as the backend SQL Service.  This set of posts are still getting drafted and updated as we move through this cycle, but I came across a huge blocker this week that I wanted to post on, whilst it was fresh. Our Azure migration machines (2013 and 2016) are: - dual core 2.3ghz - 28GB Ram 2013 server is Windows Server 2012 R2 running SQL 2012 SP1 2016 server is Windows Server 2016 running SQL 2014 SP1 The Project Server dataset we are dealing with here is c.100GB (50% archive data). The uplift from SP/PS 2010 to 2013 went without a hitch over a 2.5hr period which was a huge win.  However when attempting to upgrade to 2016 we hit a hitch. Firstly some background:  When you perform the Migrate-SPProjectDatabase command, the following will happen (well it certainly did to us) - the ProjectWebApp DB fro
1 comment
Read more