Skip to main content

Problem Provisioning PWA Site after SP1

** UPDATE2:  OK so I didn't reboot before that previous note.  This has now resolved the issue.  Reboot WAS tried prior to June CU


* UPDATE:  After installing June CU2011 Server Rollups (SPF & SPS+PS) I am still seeing the same issues as before.  More research to do.....


Since my rig had Project Server 2010 SP1 packages installed I have seen PWA provisioning fail when creating a brand new PWA Site with clean DB names etc.


Note:  This is NOT a restore scenario:


Firstly I see the following, which is what I would expect:




09/19/2011 15:45:59.32 OWSTIMER.EXE (0x0C30)                   0x05C4 Project Server                 Provisioning                   6974 Information Provisioning 'zzzzzzzzzzzzzzzzz': Server versions: Primary 10.50.1600.1, Reporting 10.50.1600.1. 47871661-d3d4-46fa-9c73-f5faf328a37d





09/19/2011 15:45:59.35 OWSTIMER.EXE (0x0C30)                   0x05C4 Project Server                 Provisioning                   6975 Information Provisioning 'zzzzzzzzzzzzzzzzz': Databases specified for site 'ProjectServer' are as follows: Published: Name = 'zzzzzzzzzzzzzzzzz_Published', State = NotCreated Draft: Name = 'zzzzzzzzzzzzzzzzz_Draft', State = NotCreated Archive: Name = 'zzzzzzzzzzzzzzzzz_Archive', State = NotCreated Reporting: Name = 'zzzzzzzzzzzzzzzzz_Reporting', State = NotCreated 47871661-d3d4-46fa-9c73-f5faf328a37d

Then a little while later prior to the above job completing I see a second PWA Provisioning job is initiated, that reuses the PWA Site url configured by me and then shows the following in ULS:

09/19/2011 15:49:59.61 OWSTIMER.EXE (0x18CC)                   0x2238 Project Server                 Provisioning                   6974 Information Provisioning 'zzzzzzzzzzzzzzzzz': Server versions: Primary 10.50.1600.1, Reporting 10.50.1600.1. 27bbee07-9442-48ce-af3e-eb7dabaf80ea

09/19/2011 15:49:59.95 OWSTIMER.EXE (0x18CC)                   0x2238 Project Server                 Provisioning                   6975 Information Provisioning 'zzzzzzzzzzzzzzzzz': Databases specified for site 'ProjectServer' are as follows: Published: Name = 'zzzzzzzzzzzzzzzzz_Published', State = NotEmpty Draft: Name = 'zzzzzzzzzzzzzzzzz_Draft', State = Empty Archive: Name = 'zzzzzzzzzzzzzzzzz_Archive', State = Empty Reporting: Name = 'zzzzzzzzzzzzzzzzz_Reporting', State = Empty 27bbee07-9442-48ce-af3e-eb7dabaf80ea

Shortly after this, guess what:

09/19/2011 15:49:59.95 OWSTIMER.EXE (0x18CC)                   0x2238 Project Server                 Provisioning                   7070 Critical Provisioning 'zzzzzzzzzzzzzzzzz': One or more of the databases already contains schema. When editing or creating a Project Server instance, you may specify: * Four databases that do not exist * Four existing, blank databases * Four existing Project Server databases of the same version from the same installation. Combinations of blank, new, and existing databases are not allowed. 27bbee07-9442-48ce-af3e-eb7dabaf80ea
Subtle but important difference here... this second provisioning job that appears to have been initiated part way through the initial DB provisioning job now sees that the Published database = NotEmpty state.

Hypothesis here is that the first correct provision job has begun to build the  DB schema, and then been kicked out by the erroneous second job, which finds a mismatch set of databases and bombs out.

Resolution:

So far it appears that the June CU resolves this issue, but I am retesting this now.  be back after the break

Comments

Popular posts from this blog

#projectserver2013 VIEW FAILURE: The view failed to load. Press OK to reload this view with the default settings. Press cancel to select another view.

** UPDATE ** includes notes relating to secondary bug where Timesheet is created without Administrative tasks.

Does this ring any bells?

This has been bugging me for months, but finally I have a repro for this:

Issue Summary:  When a task is deleted from a plan that is approved into a previous or current timesheet - even when there are no actuals on the task - you can no longer view the timesheet

The following repro has been proven:
- Setup system with Single Entry Mode, with enforced Status Approval before Timesheet Approval
- Create resource as own timesheet manager
- Create new project
- Create two tasks in the same week, starting monday with 5 days duration:  1) Task to assign actuals, 2) Task to delete post submission
- Assign Resource to tasks
- publish project
- as Timesheet User, go to the appropriate timesheet period for the tasks created
- Assign actual work to one task (task 1), leaving task 2 with no actual work
- Submit timesheet
- as Project Status Manager, approve the time on task 1 …

What to do when your application server goes bang

What happens when someone kills your Application Server?
So imagine the scenario:
Three Server Solution - SQL - SharePoint 2010 and Project Server 2010 Application Server (Central Admin Host) - Wfe/ReportServer
We wake one bleary Monday morning to find that some numpty has killed the application server and the users are baying for blood.
Well surprisingly SharePoint handles this disaster recovery scenario particularly well.  Well.  Better than I thought it would to be honest.
Rough steps:
- quick SQL backup to be safe - Rebuild your application server - reinstall pre-reqs - reinstall SP, PS, SPFSP1, SPS+PSSP1, Cumulative Update and other stuff you usually put on there. - Run your configuration wizard to reattach to the Farm, and select Host CA Site
The last step was what I was VERY wary of.  Would the server simply reattach to the Farm, even when there is no CA server available?  
Bingo your back.... almost.... you are going to get errors a-gogo in your event log as things just aren't quite back…

Reporting from Project Server 2016 - multiple sites and userviews

Just a quickie...
I've been interested in how MS have handled the "multiple PWA sites in a Content DB" thing since I read that this was their new approach.  Most of my reporting is via SSRS so i am reliant (still... in 2016) on DB queries rather than OData feeds (tsk) and this "querying a PWA DB with more than one PWA site in it is unsupported" quote was worrying me.

So it looks like what is happening is this.

When you create the first PWA site in a Content DB it hard-codes the SiteID into the _Userview view design elements.  This means that your first PWA Site is the default.  All the data for subsequent sites are still held in the tables against separate SiteID's but you cannot utilise the OOTB _Userview components (see below)


SELECT        ProjectFields....
FROM            pjrep.MSP_TVF_EpmProject('FF19B767-CA6D-4C4C-B123-C0B5AE5354D6') AS MSP_EpmProject 
LEFT OUTER JOIN
                      pjrep.MSP_TVF_EpmInternalProjectHierarchies('FF19B767-CA6…