#ProjectServer / #ProjectOnline error opening Enterprise Resource Pool #MSProject #Office365 #PPM

October 10, 2016 at 8:17 am | Posted in Administration, Functionality, Information, Issue, Workarounds | Comments Off on #ProjectServer / #ProjectOnline error opening Enterprise Resource Pool #MSProject #Office365 #PPM
Tags: , , , , ,

A quick post to highlight an issue and workaround for opening the Enterprise Resource Pool in Project Pro using the Open button on the Resources tab in the Resource Center:


If you try and click the Open button with no resources selected in the grid you will get the error below:

“This action couldn’t be performed because Office doesn’t recognize the command it was given” :


Select at least one resource in the grid then this command will work fine.


Error creating Project Sites from custom site template in #ProjectOnline / #SharePoint Online #PPM #Office365

September 1, 2016 at 4:30 pm | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Issue, Workarounds | Comments Off on Error creating Project Sites from custom site template in #ProjectOnline / #SharePoint Online #PPM #Office365
Tags: , , , , ,

A quick post, if you are finding that all of a sudden your project sites are failing to create with the error below:

CreateWssSiteContent: Creating project site failed! Project Uid= <site details> Microsoft.SharePoint.SPException: The site template requires that the Feature {e995e28b-9ba8-4668-9933-cf5c146d7a9f} be activated in the site collection. at Microsoft.SharePoint.Utilities.SPUtility.ThrowSPExceptionWithTraceTag

Chances are you using a custom site template and this stopped working within the last week or so. The feature ID SharePoint is complaining about is a “MobileExcelWebAccess” feature. This can’t just be enabled.

The fix is straightforward, locate the site which you used to create the site template and save that site as a template again with a different name / version then link this to the Enterprise Project Type/s. Repeat this for all custom site templates.

#SSRS native report render issue in #SharePoint #SP2013 with #IE 10 or later #PS2013 #BI #SQL

January 15, 2014 at 6:03 pm | Posted in Administration, Configuration, Customisation, Functionality, Information, Issue, Reporting | 1 Comment
Tags: , , , , ,

This post covers an the details around an issue I came across the other day and I wanted to make you aware to help in your deployments / system design. The issue is with displaying SSRS Native mode reports on a SharePoint 2013 page using a page viewer web part when using IE 10 or later. Our preference and recommendation is to usually use SSRS Integrated mode but on occasions some of our clients use SSRS 2008 R2 / 2012 Native mode. This issue doesn’t exist for SSRS Integrated mode.

****** Update ************

This issue is resolved by updating the document mode for the ReportViewer.aspx pages, updating this from <meta http-equiv=”X-UA-Compatible” content=”IE=5″>   to  <meta http-equiv=”X-UA-Compatible” content=”IE=8″> or later did resolve this issue for us. The file can be found on the report server in the following location: C:\Program Files\Microsoft SQL Server\MSRSx.InstanceName\Reporting Services\ReportServer\Pages. Please note, this will impact all the reports on that report server so test on a test server before a production server.


The issue is that the SSRS reports are not displayed correctly on the page, they are truncated:


Other standards-compliant browsers are ok, Chrome is:


IE 8 and 9 also work fine.

The page viewer web part with SSRS Native reports worked fine in SharePoint 2010 in any browser.

I have tested with the SSRS Report viewer web part (the 2008 R2 version as the SQL 2012 version doesn’t deploy to SharePoint 2013) from the RSWebParts.cab file, this has the same issue.

One of our devs had a quick look at this and it stated it was because the web part uses a table that is 3 cells wide. 2 of the cells are related to the document map while the 3rd contains the report itself. The document map cells are hidden by default.

In older versions of IE, a hidden cell in a table counted towards with width of the table, this was against the standard. Now with more standards compliant browsers, hidden cells do not count towards the width of the table.

This means that the report cell is the only cell defined for the row, so the browser forces it into the left most cell space. The end result of this is the SSRS report is truncated to the right as that is the limit of the size of that column.

So the answer going forward if your client wants to embed SSRS reports in SharePoint 2013 pages and they use IE, recommend (and use) SSRS 2012 Integrated mode.

#ProjectServer 2013 Project Center view failed to load #PS2013 #SP2013

November 20, 2013 at 10:33 am | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Issue, Workarounds | 2 Comments
Tags: , , , ,

I have seen this issue a few times now in Project Server 2013 where users see the error “View Failure The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view”


Clicking OK gives another error: “You don’t have permissions to view any projects”


This isn’t the case in this example.

There are two scenarios that I know of that cause this particular issue, these are described below:

Note: My farm is in the Project Server permission mode.

For an existing user:
•    Log in as User A, access the Project Center, access “View A” – all works great
•    Change the permissions so that User A no longer has access to “View A” or delete “View A”
•    Log in as User A, access the Project Center, User A will see the View failed to load error

For a new user – never accessed the farm before:
•    Prevent access to the default Project Center “Summary” view for the Team Members Group but allow access to other Project Center views
•    Create a new user (User B) that is only in the Team Members Group
•    Log in as User B (a new user on the farm), access the Project Center, User B will see the View failed to load error

The ULS logs gives the following error:

Error is: GeneralSecurityAccessDenied. Details: User does not have permission to this view. . Standard Information: PSI Entry Point:  Project User: i:0#.w|support\userb Correlation Id: 2f5e74c7-c751-e311-9419-00155d15d154 PWA Site URL: http://vm753/PWA SA Name: ProjectServer PSError: GeneralSecurityAccessDenied (20010), LogLevelManager Warning-ulsID:0x347A6230 has no entities explicitly specified.               ea70589c-4f64-e059-ef52-a016cf63c1ed

InitViewReportInfo ViewUid:63d3499e-df27-401c-af58-ebb9607beae8 is not found.        ea70589c-4f64-e059-ef52-a016cf63c1ed

The remote command PWAProjectGetProjectCenterProjectsForGridJsonRemoteCommand encountered an unexpected exception. ea70589c-4f64-e059-ef52-a016cf63c1ed

If you have removed the default Project Center Summary view, either removed access to it or deleted it (new user scenario), or removed any other Project Center views that users may have accessed last (existing user scenario), the known workaround at this point is as follows. Click the Projects Tab, select a view from the view menu then refresh the page. At this point the view will load and the Project Center will continue to load successfully.

Changing #SharePoint Central Admin Regional Settings stops the #PowerPivot Dashboard timer job #SP2013 #PS2013

November 1, 2013 at 11:22 am | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Issue, Reporting, Workarounds | 1 Comment
Tags: , , ,

Take care when updating the Central Admin regional settings as certain things stop working. The link to update the region settings doesn’t exist on the Site Settings menu probably for this reason but you can type the URL manually and access the page. Just add _layouts/15/regionalsetng.aspx to the URL.

Central Admin region settings were updated to English (United Kingdom), which is ID 2057.

An example of functionality that stops working is the PowerPivot Dashboard Processing Timer Job:


For the benefit of the search engines:

‘The Execute method of job definition Microsoft.AnalysisServices.SPAdding.UsageProcessingTimerJob(ID 5144359a-e86d-429f-8a5c-8c06cca109ee) threw an exception’

The following error is thrown in the URL logs:


For the benefit of the search engines:

Failed to load ‘http://sp13:15000/PowerPivot%20Management/567b4062-7a0b-4b24-a7f5-994bbed90cf1/2057/Server%20Health.xlsx&#8217; with error: ‘The workbook does not exist at the specified location’

This error lead us to the fix. Notice the 2057 in the URL. Navigating the the PowerPivot Management library, there was no 2057 folder, only a 1033 folder.

A 2057 folder doesn’t exist, on 1033 – for English (United States):


At this point you can either create a a new folder for the correct locale in this case 2057 for English (United Kingdom), then copy the 3 documents shown below from the 1033 folder to the 2057 folder:


The timer job will now run successfully and the dashboard will update. The other option is to set the regional settings for Central Admin back to English (United States) – probably the recommended fix!

The the Dashboard will update and show data:


Take care when deleting the #Project Ideas list in #ProjectServer #PS2013 #SP2013 #SharePoint #ProjectOnline #PPM

October 14, 2013 at 8:24 pm | Posted in Administration, Configuration, Customisation, Functionality, Information, Issue | 1 Comment
Tags: , , ,

Just a quick blog post to ensure you take care when deleting the project ideas list and to let you know of potential issues with deleting projects that were created via the deleted project ideas list.

This post covers the issues you will see when trying to delete a project from Project Server that was created from a project ideas list after the list was deleted.

****Update – this issue should be resolved in SP1****

Example Project Ideas list:


Project created in Project Server from the Project Ideas list above:


Delete the Project Ideas list from the “List Settings”  > “Delete this list” option.

Now try to delete the project that was initiated from the Project Ideas list, in this example delete the PM Test Project from the Delete Enterprise Objects menu in server settings. Navigate to the Project Server queue and you will notice that Project Delete job fails:


The key error is:

Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.RemoveIdeaListLinkMessage‘ messageID=’8′ stage=” blocking=’Undefined’

You will see the the project still exists in the Project Center:


But trying to access the project details gives an error:


Checking the Delete Enterprise Objects page shows that the project is not visible when selecting “Delete draft and published projects”:


Change to “Delete only published projects” shows the project:


Attempting the delete again throws the same error.

My advice at this stage is to recover the deleted Project Ideas lists if possible. In this example I still had the Project Ideas list in the PWA site recycle bin. After restoring this deleted list, the subsequent delete job for the “PM Test Project” completed successfully.

With this in mind, I would recommend that you do not delete any PWA lists that have been used to create projects in Project Server.

#ProjectServer #PS2013 / #SharePoint #SP2013 site template issue

September 4, 2013 at 10:02 am | Posted in Administration, Configuration, Customisation, Functionality, Information, Issue, Workarounds | 2 Comments
Tags: , , , , , ,

When creating new site templates in SharePoint 2013, ensure you check the box to include content. If you don’t do this, any sites created from your new template will have the “Change the look” functionality missing, it will load a blank page as shown below:


To resolve this, include the content when saving the new site template. Ensure that there is no test data on the lists / libraries etc.

Include content enabled:


After creating a site from this new template, the “Change the look” functionality will work as expected:


#ProjectServer #PS2013 #Excel Pivot Table limitation

July 4, 2013 at 11:38 am | Posted in Administration, Customisation, Functionality, Information, Issue, Reporting, Workarounds | 1 Comment
Tags: , , , , ,

Just a quick post to highlight a limitation / issue with Excel Pivot Tables that I hadn’t seen before, details below.

This particular Pivot Table uses a Data Model that contains two OData feeds from Project Server 2013, one for Project details and one for Task details. The connections can been seen below:


The relationship has been set up as follows:


I have added Programme, Project Name, Task Name and Task Start to the Pivot Table. Programme and Project Name are from the Projects table and Task Name and Task Start are from the Tasks table. The Project Name is filtered to just one project:


Looking at the Pivot Table, it looks the CPS Test project has many tasks but in fact this project only has 4 tasks:


To resolve the issue you have to add a numerical field from the Tasks table to correct the aggregation:


Hope that helps Smile

#ProjectServer #PS2010 / #PS2013 local master projects and tasks with no assignments

June 21, 2013 at 5:02 pm | Posted in Administration, Information, Issue | 1 Comment
Tags: , , , , ,

Something to be aware of when using local master projects in Project Server 2010 or 2013 when tasks in the sub projects have no assignments.

You will see random text / characters next to the Unassigned name as seen below:


The text / characters displayed will change depending on where you last clicked.

Repro steps below:

  • Open Project Pro and connect to the server
  • Create 1 project, create 3 tasks and assign an enterprise resource to all three tasks, save and publish the project.
  • Close and check-in the project
  • Create 1 other project, create 3 tasks and assign an enterprise resource to only 2 of the tasks leaving 1 task with no assignment, save and publish the project.
  • Close and check-in the project
  • Create a new project and insert both of the projects created above as read-only
  • Save the master project locally as a file, when prompted hit no to all when prompted to save changes to the two insert projects
  • Close the master project and again when prompted hit no to all when prompted to save changes to the two insert projects
  • Close Project Pro
  • Open Project Pro and connect to the server
  • Open the local master project and expand the two inserted projects
  • Switch to the Resource Usage view and notice the Unassigned resource name


  • Make changes such as expanding the Resource Name column, increase the work etc. and see the Unassigned name update.
    • After changing the Resource Name column width:


o Changing work:


o 2013:



#ProjectServer 2010 field calculation in PWA #PS2010 #MSProject #SP2010

June 18, 2013 at 3:44 pm | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Issue, Workarounds | 1 Comment
Tags: , , , ,

A quick blog post to highlight an issue and workaround for editing plans in PWA when using custom fields that use the inbuilt fields. This post uses Finish Variance as an example. The Finish Variance field doesn’t recalculate in PWA after making edits to plans, this only updates after changes in Project Pro. This post relates to the Finish Variance field but other fields will more than likely have the same issue.

In the screen shot below you will see a simple plan with 2 tasks that was created and baselined in Project Pro. There are 3 custom fields in the view:

Finish Variance RAG, the formula is IIf([Finish Variance] > 0, "Slipped", "On schedule")

Finish Variance (Calc) RAG, the formula is IIf([Task Finish Variance] > 0, "Slipped", "On schedule")

Task Finish Variance, the formula is ProjDateDiff([Baseline Finish], [Finish]) / 480


As you can see the Finish Variance and the Task Finish Variance values are currently the same and so are the 2 RAG fields.

Edit the plan in PWA and increase the task durations, for this example double the durations. Calculate the plan then save and publish the project. Refresh the page and you will see that the Finish Variance is incorrectly 0, the Finish Variance RAG is still green as this uses the Finish Variance field. The good news is that the custom field that calculates finish variance (Task Finish Variance) shows the correct values and the Finish Variance (Calc) RAG also shows the correct RAG.


To correct the Finish Variance values and the Finish Variance RAG, open the plan in Project Pro, press F9 to recalculate then save and publish. The Finish Variance default field now shows the correct values in PWA as does the Finish Variance RAG:


To get the RAGs to calculate correctly when editing in PWA you might need to create your own custom fields to replicate the calculations used on inbuilt fields. Obviously it would not be recommended to create too many task level calculated fields due to performance issues but hopefully that little workaround helps for key RAGs.

Next Page »

Create a free website or blog at WordPress.com.
Entries and comments feeds.