Thursday, September 24, 2015

Step by Step:Upgrade Project Server 2013 to Project Server 2016

Upgrade to Project Server 2016

Pre-Upgrade Steps

1. Install SharePoint 2016 and Project Server 2016

2. Create a Web Application

3. Update 2013 environment with latest patches

Upgrade Steps:

1. Copy Project Server and Content database from the 2013 environment

a. ProjectWebApp

b. WSS_Content

** Upgrading to 2016 (Both databases will be merged to one database)

1. Select Manage content databases

Verify the Content database:

2. Restore the new database to 2016 SQL Server

The new database is restored as ProjectWebApp_PME and WSS_Content_PME:

3. Run SharePoint 2016 Powershell as administrator:

4. Mount-SPContentDatabase (WSS_Content_PME):

5. Migrate-SPProjectDatabase:

6. Upgrade Completed Successfully

Friday, February 27, 2015

PWA Navigation Made Easy - New App it helps navigating through PWA pages and connects pages directly

This app is developed by Project Made Easy, Inc. It helps in navigating through PWA pages and connects pages directly for example it connects Manage Delegates and Act As Delegates page to each other. Also it connects Timesheet page to Manage Timesheet. Additionally, this app also hides the Remove Task button of the Timesheet page.

"Manage timesheet" button on Timesheet Page

"Act as Delegate" button on Manage Delegate Page

"Add Delegate" button on Act as Delegate Page

Link to download the APP:

Friday, February 06, 2015

Project Server 2013: Error while opening Project plan in Project Web Access

Issue Description:

Getting the following error while opening the Project Plan in PWA.
An error occurred while opening your project. Give us a few minutes and try again. If this happens again, contact your administrator.


Permission denied: User i:0#.w|pmedev\proj2010 does not have category permission 'SaveProtectedBaseline' on project 5850e0f8-cdf2-4092-9cc3-577102564a24

CalcServiceManager : Communication with the worker failed while opening project guid: 6f771fcd-afad-e411-9420-00155d113d0b System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.   

02/05/2015 21:34:28.48     Microsoft.Office.Project.Server (0x06B8)  0x3900          Project Server                          Project Calculation Service (M)      ai2mx Medium         PWA:, ServiceApp:Project Server Service Application, User:i:0#.w|pmedev\proj2010, PSI: Failed to open project: 6f771fcd-afad-e411-9420-00155d113d0b, in site: b6088326-72bb-4882-b491-133e5eee2d93 Project:6f771fcd-afad-e411-9420-00155d113d0b  0cf2e69c-59f7-303c-4570-94300b0f2499

Cause: The issue occurs due to the value added for the custom field “State” in migrated environment from Project Server 2007.


To avoid the issue on the new project,

1.    Open the Enterprise Custom Fields and Lookup Tables à Click on “State” field

2.    Remove the check box “Choose a value to use as a default when adding new items”

To resolve the issue with the existing projects,

Need to remove the MD_PROP_ID='190873600' value for the projects from the table draft.MSP_PROJ_CUSTOM_FIELD_VALUES.

Note: Open support ticket with Microsoft to remove the values from the table.

Wednesday, February 04, 2015

Project Online: Issue while executing SSIS package for OData delta sync

Issue Description:

Getting the following error while executing the “OData.AssignmentsTimephased” package.

Error Message:

Exception deserializing the package "The package failed to load due to error 0xC0011008 "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.". This occurs when CPackage::LoadFromXML fails.


The package failed to load due to error 0xC0011008 "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.". This occurs when CPackage::LoadFromXML fails.

 (OData AssignmentsTimephased)

 Cause: Issue occurred due to the version conflict of Visual Studio 2010 and SQL server 2012.


Open Project à Report Properties à Change the value from True to False for the field “Run64BitRuntime”, Later execute the package.


Friday, January 23, 2015

Project Online 2013 - Webpart Error

Issue: New users get web part error in Project Online using Project Server Security Mode

Sign in as PWA Administrator > Click on  Setting button > PWA Settings > Manage User

Double click the user in question > Make sure the user has atleast team member access.

Thursday, January 15, 2015

Project Server 2013 Performance issues due to “Prepare Project Web App Permission Synchronization” job

One of my customer contacted me and stated that Project server stopped responding and resources were experiencing extremely slow response. When the resource opens Project / resource center, it takes enormous amount of time to load the data.

When I started digging, observed that the issue started after they performed a small tweak in the Project Server permission settings. I.e. Since stake holders wanted everybody in the system should be able to access all the Project sites in the PWA instance, modified the security settings to meet the business goal.

Since then on every project publish, project application service started consuming most of the CPU and memory from the server and stopped responding to the resource queries.
To meet the goal, scheduled a PowerShell script in the task scheduler to add the required resources into the Project Sites

Issue Description:

Project server responds slowly when the following jobs are stuck in Queue.

Prepare Project Web App Permission Synchronization”

“Prepare Project Web App Permission Synchronization for Projects”



Action 1: Open Project Web App, Server Settings and Manage User Sync Settings
Disable the following settings

Enable Project Web App Sync
             Enable Project Site Sync

Action 2: Add a task in the Task scheduler and schedule the action as below.

Program/Script: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Add arguments: c:\path\addperm.ps1


Add the following content and create the PS1 file in the above path.

Sample PowerShell Script: (modify based on your requirements)

add-pssnapin microsoft.sharepoint.powershell

$site = Get-SPSite http://servername/demo

Write-host "adding Authenticated Users to"

foreach ( $web in $site.allwebs )


     if ( $web.HasUniquePerm )


        Write-host `t`t`t $web.url

        New-SPUser -UserAlias "NT AUTHORITY\Authenticated Users" -Web $web.url -PermissionLevel Contribute  | Out-Null



More Info: 
Register to get free online tour:

Contact us: