Tags: Project 2013, Project Server 2013, PS2013, SharePoint 2013, SP2013
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.
When upgrading #ProjectServer #PS2010 to #PS2013, consider any custom project site templates #SP2013 #SharePointNovember 19, 2013 at 9:48 am | Posted in Administration, Configuration, Customisation, Functionality, Information, Installation, PowerShell, Upgrade | 3 Comments
Tags: Project 2013, Project Server 2013, PS2013, SharePoint 2013, SP2013
I have seen this posted quite often on the Project Server forums so I thought I would write a quick blog post.
When upgrading from Project Server 2010 to Project Server 2013, you will need to recreate the customised Project Site templates. Project Server 2013 doesn’t recognise the Project Server 2010 project site templates. Project Server 2013 project sites now have a template name / ID of PROJECTSITE#0, Project Server 2010 project sites use PWS#0. This can be seen below:
When recreating the new site template in 2013, start with the “Project Site” template on the Collaboration tab found on the new SharePoint site page.
How to check the #ProjectOnline database usage #ProjectServer #PS2013 #SP2013 #SharePoint #SharePointOnline #Office365November 18, 2013 at 3:07 pm | Posted in Administration, Configuration, Functionality, Information | 1 Comment
Tags: Office365, Project 2013, Project Online, Project Server 2013, SharePoint 2013, SharePoint Online
A quick blog post to detail how you can check the Project DB size in Project Online. With Project Online, each Project Web App site collection can have a 10 GB Project database:
To check Project database usage for Project Online, access your SharePoint Admin page in Office 365. On the Site Collections page, select the PWA site collection, then click Settings from the Project Web App menu as shown below:
This will display the Project Database Usage:
Should I display duration fields on the #ProjectServer PDPs? #PS2010 #PS2013 #SP2010 #SP2013 #SharePoint #ProjectOnline #MSProjectNovember 12, 2013 at 10:11 am | Posted in Administration, Configuration, Customisation, Functionality, Information | 1 Comment
Tags: Project 2010, Project 2013, Project Online, Project Server 2010, Project Server 2013, PS2010, PS2013, SharePoint 2010, SharePoint 2013, SP2010, SP2013
The answer to this question in my opinion is no. In this blog post I will explain why using an example.
Firstly I have created a new test duration field on my test Project Server 2013 environment, this is called _duration.
For the purpose of this post, I also have a new Project Detail Page (PDP) that only displays the _duration field. A new project is created, the schedule it not important here, just the value you specify in the _duration field. As you can see below, I have entered 10 days:
Save and publish this to Project Server and take a look at the project in PWA. You can see the project in PWA as shown below:
Notice the _duration field correctly shows the 10 days.
Notice the _duration field correctly shows the 10 days.
All ok at this point. Before we move on, I just want to show the project options for this project, specifically the hours per day:
Notice this is set to the default 8 hours per day. Update this to 7 hours per day. You will then notice that the _duration field correctly updates to 11.43 days:
Reset this back to 10 days then save and publish the project again.
The Project Center still display 10 days in the _duration field:
The PDP will show the incorrect duration in the _duration field:
The PDP’s assume the default 8 hours per day is used for each project. At this point the PM will probably think, lets correct the 8.75 days to 10 days. So lets do this, this is now correct in the PDP:
Great. Not quite, now take a look in the Project Center:
Notice the 11.43 days. Also check the Project Information in Project:
I was aware of this issue in Project Server 2010 but only just came across the same thing in Project Server 2013.
Hopefully that explains why I answered “no” to displaying duration fields on the Project Server PDP’s, it will save a lot of confusion with your Project Managers! As with all answers there is normally an exception to the rule and you can probably guess what that is. Displaying duration fields on PDP’s will be fine if your projects are 8 hour days
#ProjectServer #PS2013 #Project Site permission sync clarification #SP2013 #SharePoint #ProjectOnlineNovember 5, 2013 at 3:30 pm | Posted in Administration, Configuration, Functionality, Information | 1 Comment
Tags: Project 2013, Project Online, Project Server 2013, PS2013, SharePoint 2013, SP2013
Just a quick post to make you aware of a design change in the Project Server 2013 project site sync when in Project Server permission mode. The only issue is that you may find project team members without assignments are granted edit access to the associated project site rather than read access – this is now by design.
In Project Server 2010 if a user / resource was added to the project team but not assigned to any tasks they were added to the Readers (Microsoft Project Server) SharePoint group on the associated project site. This is different in Project Server 2013, when the users / resources are added to the project team but not assigned to tasks they are added to the Team Members (Project Web App Synchronized) SharePoint group rather than an equivalent Readers (Microsoft Project Web App) group. This is working as designed as there are now only two SharePoint groups on the Project Sites used in the permission sync:
Project Managers (Project Web App Synchronized)
Users who have published this project or who have Save Project permission in Microsoft Project Web App.
Team Members (Project Web App Synchronized)
Users who have assignments in this project in Microsoft Project Web App.
This could be misleading if you used 2010 and also if you view the SharePoint permission level descriptions. The Project Server 2013 Project Site permission levels can be seen below:
The “Readers (Microsoft Project Web App)” states “Users who have been added to this project in Microsoft Project Web App, but not assigned to tasks.”
Also the “Team Members (Project Web App Synchronized)” SharePoint group permission description is not quite accurate as it should states that it also includes project team members without assignments:
“Users who have assignments in this project in Microsoft Project Web App”
Hope that helps.
Changing #SharePoint Central Admin Regional Settings stops the #PowerPivot Dashboard timer job #SP2013 #PS2013November 1, 2013 at 11:22 am | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Issue, Reporting, Workarounds | 1 Comment
Tags: Project Server 2013, PS2013, SharePoint 2013, SP2013
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’ 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 #PPMOctober 14, 2013 at 8:24 pm | Posted in Administration, Configuration, Customisation, Functionality, Information, Issue | 1 Comment
Tags: Project 2013, Project Online, Project Server 2013, PS2013
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.
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.
Tags: Office 2013, Office365, Project 2013, Project Online, Project Server 2013
Following on from a post I wrote last month where I detailed creating a highlight type report for Project Online using ODATA and Excel 2013 / Power View, below details another simple example for a project cost / work dashboard with cumulative totals. The highlight report post can be seen below:
Firstly add the required ODATA feeds into the Excel workbook as described in the previous post (link above), you can see my connections below:
The two Project feeds need to contain the correct fields – the fields you wants to see on the report. As a minimum the project baseline feed should contain ProjectId, Project Name, Project Baseline Finish Date, Project Baseline Cost, Project Baseline Work and the project feed ProjectId, Project Name, Project Finish Date, Project Cost, Project Work. The TimeSet feed should look like this:
ProjectData/TimeSet()?$filter=day(TimeByDay) eq 1 and TimeByDay gt datetime’2013-01-01T00:00:00′ and TimeByDay lt datetime’2018-01-01T00:00:00′&$select=TimeByDay
The date range can be changed to suit.
The next section uses PowerPivot to create the calculated field for the TimeSet feed join – this is required for the cumulative totals. Credit goes to Andrew Lavinsky for this method. Click the PowerPivot tab then Manage. On the Projects table, add a calculated field with the formula below and rename it to Total Date:
Do the same on the ProjectBaselines table but using the following formula:
Now Click the Design Tab > Manage Relationships and set up the following relationships:
Close PowerPivot and rename the first Excel sheet to Pivottables and add another sheet, call this Charts. On the Pivottables sheet insert 2 Pivot tables as shown below:
Notice the cost, baseline cost, work and baseline work values have been added twice. Rename the duplicate values to Cumulative Work, Cost etc. as seen below:
Currently both values will show the same data as the running totals have not been set up, this is completed next using the Cumulative Cost as an example. Load the field settings and click the “Show Value As” tab:
Select “Running Total In” and choose the Total Date Field:
Click OK. Repeat this for the 3 other cumulative fields.
Now create charts from both Pivot Tables and copy the charts to the Charts sheet:
Due to the lack of data in my test instance, the charts don’t look that great but you get the idea!
With a bit of time and patience you can get the charts to look presentable (better than mine do anyway!):
As you can see above, I have also added a slicer to enable filtering, in this example we can filter by Programme.
Tags: Office365, Project 2013, Project Online, Project Server 2013, PS2013, SharePoint 2013, SP2013
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:
Create a #ProjectServer #PS2010 #PS2013 project from a template and update the EPT #SP2013 #SP2010 #PowerShellAugust 30, 2013 at 11:24 am | Posted in Add-on, Administration, Configuration, Customisation, Functionality, PowerShell, PSI | 1 Comment
Tags: PowerShell, PPM, Project 2010, Project 2013, Project Server 2010, Project Server 2013, PS2010, PS2013, SharePoint 2010, SharePoint 2013
I have been meaning to publish this PowerShell script for a few months but finally got around to it today. The PowerShell script creates a project from a template then updates the Enterprise Project Type (EPT). I did write a post over a year ago on how to create a project using PowerShell but this didn’t update the EPT:
The issue is that even if your Project Plan Template is associated to an EPT in Project Server, the project created from the CreateProjectFromTemplate method is associated to the default EPT regardless. This script will prompt for the project name, the project plan template name and the EPT name. It will create the project then update the project to associate it to the desired EPT. The script can be downloaded from the script gallery below:
Once downloaded, the script will need to be updated with the correct PWA URL, the lines that need updating are 9 and 23. These can bee seen below:
Update the http://vm753/pwa part of the URL for your PWA URL.
A walkthrough using the script is below.
Open Windows PowerShell and navigate to the PowerShell file, in this example it is on the desktop:
Press Enter and complete the details:
The new Project will be called “CPS Test Project by Paul Mather”, it will use the “PMTemp1” template and then associate the new project to the “PM TEST” EPT.
The project is created as you can see in the Project Center:
It is also associated to the specified EPT:
The default EPT on this PWA instance is “Enterprise Project”:
When using the CreateProjectFromTemplate method only, this new project would have been associated to the Enterprise Project EPT as this is the default EPT.
This is just an example of what can be done, many improvements could be made, certainly around error handling but it provides a working example for you to build on.