New blog articles in Project

February Project Update Blog

Microsoft Project Team — Mon, 01 Mar 2021 23:57:50 GMT

Microsoft Project Trivia!

We’re starting trivia this month to help people learn more about Microsoft Project & its history. Leave your guesses to these questions in the comments & check back next month to see if you were right!

Question: What year was Microsoft Project first released?

Bonus: How many Windows applications did Microsoft release before Project?

Reimagine Project Management with Microsoft

Microsoft Project is hosting a free digital event to help our users learn more about how to leverage Project, Microsoft Planner, and Dynamics 365 Project Operations to best manage your projects – both big and small!

This includes 6+ hours of on-demand demos and product walkthroughs to help you discover and leverage new features and learn best practices to keep your projects on track. Get tailored guidance directly from the engineering teams behind these products.

This event goes live on March 18^th, 2021. You can learn more here.

New Features

Flexible Deployment for Project for the web ~ This feature is now available to all users! Create different environments for Project for the web based on organization, business unit, or team needs. Check out our blog post to learn more about this new experience
Filter on Project Home ~ Use a search bar to easily find your projects on Project Home.

Upcoming Features

Export Timeline to PDF ~ Print your timeline information to a PDF so you can share your project schedule with external stakeholders.
Project Accelerator ~ The Project Accelerator allows users to leverage Power Apps to manage the entire lifecycle of your projects, including demand management, financial goals, team development, and artifact tracking.
Assign tasks to non-group members ~ Assign a task to someone without automatically adding them to your project group.
Effort in the Project details pane ~ See overall effort on your project directly in the Project details pane, including the total effort, completed effort for your project, and remaining effort on your whole project.

FAQ:

This section includes questions we see frequently, either through the in-app Feedback button or from the comments of last month’s blog.

Q: What dependencies are supported in Project for the web?

A: Project for the web currently only supports Finish-to-Start dependencies. If you need additional dependencies, please submit feedback using our in-app “Feedback” button in the top-right corner of the product. This best helps us keep track of customer needs.

Q: Where are attachments stored in Project?

A: You can find all your attached files in your Team’s SharePoint library.

Note that you can't attach files to tasks in Project unless you have already shared your project to a group. You can do this by using the “Group members” button in the top-right corner of the product.

You can attach links to your tasks even before you add a group to your project.

We want to hear from you! If you have feedback, submit it by using the “Feedback” button in Project for the web. Make sure to include your email address so we can contact you directly with any follow up questions or comments. Your comments on our blog posts are also monitored, so let us know what you think about this or other articles.

For those Microsoft 365 changes that need a project to implement

Brian Smith — Mon, 22 Feb 2021 23:02:33 GMT

This blog post grew out of a conversation with one of my Microsoft colleagues about how one would push a Planner task to Azure DevOps - and the scenario was that they are very happy with the Message Center to Planner integration as a means to triage changes as they come through - but to actually execute on the changes they would normally use Azure DevOps. So I got my thinking cap on and took a look at what was available in Power Automate.

Planner is somewhat limited in direct actions and triggers, but of course you can use the Graph API too once you get a Flow started - but the trigger is what you need here and I wanted to avoid a timer job just looking in Planner. The "On completed" trigger seemed like the best approach, as if you were carrying out the work in Azure DevOps (or Project) then the plan task could be closed. Then with the number of supported labels increasing in the very near future I thought that, combined with a complete task, would get me started.

Power Automate then has an action to read the Planner labels, so I could check if the task needed to go to Azure DevOps - and if so use the "Create a work item" action.

In this example I decided to create as a Feature - and in the description I crafted a link that would navigate back to the Planner task to get the full information. A proper job here would probably involve a few more steps to read the information and populate it into Azure DevOps, but as a quick proof of concept it worked for what I needed.

And here is my newly created Azure DevOps feature.

My next thought was - that nice - but what if I want to use Project Online or the new Project to manage a Microsoft 365 change? (The eagle eyed may have already seen the :Send to Project Online and Send to PfW in my labels list) so I extended my Flow to also look at those labels and react accordingly.

It is important to mention here that I am creating these as projects in Project Online and Project for the web - and not as tasks - as the assumption is that you would use this when you needed more than just a task (otherwise why not leave in Planner?). Likewise for Azure DevOps - I created a feature but there may well be other entities added to deliver the change.

For the examples I've used I'll admit that these could probably just have been handled in Planner - as I can't imagine our adding of text predictions justifies a complete project plan to ready users...

And in the new Project we see the other task turned to a plan - in this case in a different environment than the default using the new flexible deployments option.

The Flow was pretty basic adding these two too - just a condition driven by the label that was applied, then the Create a new Project for Project Online (as the description doesn't support HTML I didn't create the href):

and for the new Project in the Dataverse environment I used the following:

The tricky piece here was working out what the GUIDs needed to be, and I used the option to open the datasets in Excel to get a good look at the GUIDs so I could test out and confirm what these needed to be. You can do this (permissions allowing) by going to make.powerapps.com, selecting the environment, then under Data, Tables select the table of interest (set filter to "All") then use the "Edit data in Excel option (don't get too excited - you can't really edit the data for this Project stuff in Excel).

Calendar Id can be found from the Calendar column of the Work template table – in my case I only had one work template, the default – so not problem using just this one – you might need to have some way to choose if your config is more complex.

Contracting Unit can be found as the Contracting Unit column in the Project table – and again I just had one so ok to hard code – your mileage may vary (Don’t confuse it with the Contracting Unit (Lookup) field…).

Project Manager comes from the Project Manager column in the Project table, and has its origins in the User table and the User column. It is NOT the same as the AAD GUID.

Like the Azure DevOps example you'd probably want to add a few more steps to pull more information in - and I did skip a big "gotcha" on the Project Online side - as Project Online does not allow certain characters in a Project name I chose my example carefully. You'd need to swap out any occurenace of the following characters - : .(period) \ " / : ; | ? ' < > * # ~ % { } +.

Finally - a screenshot of the whole Flow:

Let me know what you think - and what would make managing Microsoft 365 changes easier?

Flexible Deployment for Project for the web is here!

Microsoft Project Team — Thu, 18 Feb 2021 05:47:45 GMT

We are pleased to announce the availability of Flexible Deployment for Project for the web. As a part of the Microsoft Dataverse (formerly known as Common Data Service (CDS)) platform, Flexible Deployment enables you to create different environments based on organizational, business unit, or teams needs.

In addition to the existing Default environment, you now have more choices to spin up different kinds of Dataverse environments for the Project for the web: Production and Sandbox. With Production, your organization can create specific environments such as limiting access to data for the HR department, deploying different customizations for different sets of users, or staying compliant on data residency requirements if your users and tenant are not located in the same country. The Sandbox environment allows for Application Lifecycle Management to develop and test customized solutions for Project before rolling out to production.

You can use Flexible Deployment with Project Plan 1, Project Plan 3, and Project Plan 5. Each subscription comes with a certain amount of storage.

The choice of deployment gives you the flexibility and extensibility to stay on top of business needs while reducing complexity for your IT group. Please refer to the links below to find out more.

Learn how to get started in Deploying Project.
Help end users learn how to get started with the Project Power App.
Learn about the new Project for the Web Security Roles.
If you have additional questions, check out Frequently Asked Questions.

January Project Update Blog

Microsoft Project Team — Mon, 01 Feb 2021 17:44:06 GMT

Many features requested through Microsoft UserVoice appear on the Microsoft 365 Public Roadmap when they are in development, rolling out, or being launched. If you follow UserVoice, submit suggestions for new capabilities, continue to vote on other users’ feature requests, or track which submissions receive the most votes.  If you don’t follow this forum, come join and help us make Project better.

Feedback on existing features is also welcomed! If you have feedback, submit it by using the ‘Feedback’ button in Project for the web. Make sure to include your email so we can contact you directly with any follow up questions or comments. Your comments on our blog posts are also monitored, so let us know what you think about this or other articles.

New features:

Deploy Project to different environments: Coming soon, organizations now have more flexibility on how they deploy Project for the web. You can use multiple environments, not just the Default one.
Task attachments: All Project users can add file and link attachments to their tasks in Project for the web.

Upcoming features:

Email notifications: Switch on notifications to see changes about your projects. Get updates when you have a new project, roadmap, or task so you never miss any work.
Export Timeline to PDF: Share your schedule with outside stakeholders by exporting your timeline to PDF.

2020 Review:

The new year is a great time to check out all the features that Project for the web added in 2020! Here’s a list of our favorite features that came out last year:

Task-Level Custom Fields ~ Store custom information about your projects effectively by adding custom fields! For more information, check out our blog post on this feature.
Export to Excel ~ Export your task grid information to an Excel spreadsheet. Share your information with colleagues and analyze Project data using the power of Excel! Learn more by checking out our blog post on this feature.
Project and Roadmap in Teams ~ Add your project or roadmap as a tab in Teams. You can use this to more effectively collaborate with teammates and keep all your work in one place. Check out our blog post on this feature to learn more.
Group by Assigned to ~ Organize your tasks by assignee while on the Board view. Get insight into what each teammates is working on and see all your project tasks in one place.
Office 365 Users viewing Project ~ All Office 365 users can access Project and Roadmap as read-only users. Share your project with stakeholders, even if they don’t have a Project license.

Dynamics 365 Project Operations ~ Our team partnered with Dynamics to help launch Project Operations, a new application that has everything you need to run your service business. For more information on this product, check out the Project Operations overview page.

Import Project Desktop files to Project for the web API

Microsoft Project Team — Mon, 04 Jan 2021 23:56:42 GMT

You can now use an API through Powershell to import .mpp files into Project for the web!

The instructions below will use your credentials to create a project from the .mpp file.

Instructions:

1.Download these files (link) and put them under one folder
2.Open Powershell and navigate to that folder

3* .Run this command Import-Module .\ProjectImport.psm1

4**.Run this command ImportProject -InstanceId your instance ID -FilePath "Your full filepath” *

When Project has finished importing your .mpp file, you will see a success message with a URL to your new project. From here, your imported project will behave exactly like any other project in Project for the web.

*See the FAQ, Tips, & Tricks section below if you have an issue with these steps!

**To find your Instance ID:

a. In the Dynamics 365 Administration Center, select the default instance, and then click Open.

b. On the PowerApps setting page, look at the first part of the URL to determine your Instance ID value. In the graphic below, the Instance ID value would be https://orgde6d15d8.crm.dynamics.com.

FAQ, Tips, & Tricks

Q: Can I import tasks from my .mpp file into an existing project?

A: We do not currently support project updates through .mpp import. Importing a .mpp file will create a new project.

Q: Are there any limits on what .mpp files I can import through the API?

A: The normal Project for the web limits apply to imported .mpp files. If you attempt to import a .mpp file that violates these limits, you will see an error when importing. You can find these limits here.

Q: I’m seeing an error when I try to run the first Powershell instruction. What should I do?

A: If you’re seeing an error, try unblocking the dll files then run this instruction again.

To unblock a file:

Right-click the file and open the Properties pane
Scroll to the bottom of the pane to the Security section
Toggle the ‘Unblock’ toggle in this section
Click Apply

Once you’ve unblocked both files, you should re-attempt to import your project.

Q: Some of my data wasn’t there when I opened my imported project. What’s going on?

A: Project for the web has does not support all features included in Project Desktop. To make it possible to import .mpp files into Project for the web, some data must be dropped to fit into the new environment.

Unsupported features include (but are not limited to):

Baseline

Project-level custom fields
Cross-project dependencies
Links
Schedule from setting
Sub Projects

Constraints
Deadlines
Formulas
Null tasks
Inactive tasks

Manual tasks
Recurring tasks
Resources

Please let us know what you think in the comments!

Project for the web - December Update

Microsoft Project Team — Mon, 04 Jan 2021 16:22:30 GMT

Happy Holidays & Happy New Year from the Microsoft Project team!

We are very excited for 2021 and all the new features we will be rolling out for you to use.

As always, we love your feedback! If you have feedback, submit it using the ‘Feedback’ button in Project for the web. Make sure to include your email so we can contact you directly with any follow up questions or comments. We also read all the comments on our blog posts, so let us know what you think about this and other articles.

New features:

Task attachments: Starting in January, you can add file and link attachments to your tasks in Project for the web.
API for importing .mpp files into Project for the web: Starting in January, you can use an API to import your Project Desktop files into Project for the web. Easily import and start working online quickly.

“Quick look” column: A new column in the Grid will show you additional information about your tasks.

Upcoming features:

Deploy Project to different environments: Organizations will have more flexibility in how they deploy Project for the web. You will be able to use multiple environments, not just the Default one.
Email notifications: Turn on notifications to see when you are assigned new tasks or alert you when a task’s due date is coming up.

Export timeline to PDF: Export your timeline to a PDF file so you can share it with non-Project users and external stakeholders.

Project for the web - November Update

Microsoft Project Team — Thu, 03 Dec 2020 16:40:28 GMT

Many features requested through Microsoft UserVoice appear on the Microsoft 365 Public Roadmap when they are in development, rolling out, or being launched. If you follow UserVoice, submit suggestions for new capabilities, continue to vote on other users’ feature requests, or track which submissions receive the most votes. If you don’t follow this forum, come join and help us make Project better.

Your feedback is especially important now, as we look back on all we’ve done in 2020 and look forward to what we can build in 2021. Your feedback is so important to help us decide what we do moving forward.

New Features:

Export to Excel: Starting this month, you can export your project grid into an Excel spreadsheet. Share information with colleagues and analyze Project data using the power of Excel. This feature should be available to everyone now!
Quick Look Column: A new column in the grid will allow you to see more information about your tasks without opening task details. This will start being available in December!
Customization in Project: Now, all users with a Project for the web license can customize their app without the need to purchase an additional Power Apps license. Check out our blog post on this to learn more.

Upcoming Features:

Task Attachments: Link your tasks to the relevant documents! Upload a file directly from your computer or link your tasks to documents stored in SharePoint. Working online? Add a link as an attachment so teammates can view relevant information directly from your project.
Email Notifications: Coming soon, configure custom notifications to send you an email every time something important happens in your projects.

Answers to top questions:

Q: Is the ability to add Projects to private channels in Teams on the roadmap?

A: There are no present plans to complete this work. However, we would love to hear from you about how this impacts your workflow so we can understand your needs in Teams.

Q: Are there license requirements to use the Project & Roadmap apps in Teams?

A: Users with an active Project subscription (Project Plan 1, Project Plan 3, or Project Plan 5) can create and edit projects. A Project Plan 3 or Project Plan 5 subscription users can create or edit roadmaps. All Office 365 users should be able to view Projects/Roadmaps shared within Teams in a read-only mode.

Enterprise Global not loading after migration to Project Server 2019

Brian Smith — Wed, 02 Dec 2020 23:30:15 GMT

Great to see so many people upgrading to the latest - but one issue we have heard is that the Enterprise Global template (EGT) cannot be opened in Project Server 2019 after the migration. The problem appears to be that the Project UID for the EGT is changed - then it cannot be found under its new GUID. Often this is seen to be happening when migrations start at an earlier release - like 2010 or 2013, but from the reports we have the problem only occurs at the final stage - and the EGT opened just fine in 2016.

The solution requires a bit of work in SQL Server, so if you are not comfortable working in SQL then either work with the database administrator for Project Server - or of course open a support ticket. Always best too - if you either take a SQL backup before making any changes - or make the changes just after your normal backups occur - in case you need to revert.

To detect the issue you would first run a query like this one - substituting your content database name for dbname:

use dbname

select PROJ_UID, PROJ_NAME from pjpub.msp_projects where proj_name like '%eglobal%'

This may return a result similar to the following:

PROJ_UID PROJ_NAME

75CDD7DB-1B68-4B70-A8D6-2FE52DA83ACD EGlobal

87537CC3-5AF6-421E-A42F-A27CB2A2EFA2 EGlobal-20150320041555

Here, the EGlobal has the proper association to PROJ_UID = 75CDD7DB-1B68-4B70-A8D6-2FE52DA83ACD (this is the static GUID) and an older version of the EGlobal is shown here (the second row).

If the EGlobal has a different UID, then it’ll need to be updated to use the proper one.

For example, suppose the returned result looks like this:

PROJ_UID PROJ_NAME

DF59652B-073D-4FB1-A16E-1F7233C439AE EGlobal

87537CC3-5AF6-421E-A42F-A27CB2A2EFA2 EGlobal-20150320041555

You’d need to run an update query that looks similar to this:

use dbname

Update pjpub.msp_projects

Set PROJ_UID = '75CDD7DB-1B68-4B70-A8D6-2FE52DA83ACD'

where PROJ_UID = 'DF59652B-073D-4FB1-A16E-1F7233C439AE'

Use the GUID (in this example starting 'DF59,,,' that is the incorrect GUID returned from the previous select statement.

If this doesn't solve the problem - or if the GUID looks to be ok, then you have a different problem and would need to open a support ticket.

Thanks to Adrian and Ajith for help with putting these details together - and Dale and Paul for alerting us to the issue.

My suspicion is that this is a 2019 client issue - as just changing the GUID to try and repro the issue in 2016 does not give any problems - the EGT opens just fine whatever GUID it has...

Export your entire project to Excel

Madhuri Jain — Wed, 02 Dec 2020 09:32:18 GMT

Project for the web comes with some great out-of-the-box tools for keeping your team on track. App features like orange and red highlights for late and overdue tasks provide you with visual cues for quickly finding tasks that need attention. There’s also Power BI reporting, which gives you visually rich report pages for your portfolio, resource and and project overviews.

And now we have added Export to Excel as it was one of your top requests we have received over the months. You can now export your project to Microsoft Excel where you can customize the data in whatever way your team finds most useful.

To export a project, simply click on the overflow menu at the top right corner and then click the Export to Excel button.

This feature is also available in Project Teams app.

When to export a project to Excel

There are multiple scenarios for Export to Excel, here are some to help you get started:

For reporting: You will now be able to use the data you export from Project to create charts, pivot tables and more in Excel. You can quickly sort the task by their finish dates or filter information to find out the completed tasks. You can then share this information with your team or drop into presentations. Some snapshots of the charts created on top of Excel are:

For sharing: Use Export to Excel to share your project status with guest users, vendors, or your clients who do not have access to Project. Easily delete information you do not wish to share with others such as providing high-level executive summaries without unnecessary details.
For Archiving: Archive your completed projects in Excel to quickly share your compliance and maintain an external record of your work.
For Printing: Print your project in Excel in a format that makes it easier for senior management to consume.

These are just a few of our ideas of how Export to Excel can help you get more out of Project—but we want to hear how you are using it! Leave us a comment below on your experiences so far. Please let us know the ideas for future integration capabilities or enhancements to current ones, like adding the ability to import items from Excel back into Project, through our User Voice site.

App + User authentication and Project Online development

Brian Smith — Mon, 23 Nov 2020 22:43:50 GMT

With the most recent updates to the SharePoint client object model (CSOM) libraries it is now possible to authenticate to SharePoint and Project Online with the MSAL libraries rather than ADAL - and this opens up the use of .NET Standard rather than needing the .NET Framework. This DOES NOT however mean that Project Online supports App ID only authentication. SharePoint Online does support app only - but the additional authorisation level in Project to understand who the user is and what they can do requires app + user. See more information here - https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/using-csom-for-dotnet-standard and the API permissions you can choose are shown here. Im my example I've just selecting the Project.Write which allows me to create and update a project.

API Permission Options for Project Online

You application would need to reference the Application (Client) ID associated with these permissions when requesting token - but would also need to pass in the credentials of a user with permissions and license to Project Online. This could be an interactive login - or using a securely stored username and password (not recommended) or using a stored token that is refreshed periodically. Attempting to connect by with the application ID will fail with an "unauthorized" response.

As an example, the following code would get the token and set for project context to make further CSOM calls:

string domainName = "brismith.onmicrosoft.com"; string PJOAccount = "brismith@brismith.onmicrosoft.com"; string scope = "https://brismith.sharepoint.com/Project.Write"; string redirectUri = "http://localhost"; string pwaInstanceUrl = "https://brismith.sharepoint.com/sites/pwa/"; // your pwa url int DEFAULTTIMEOUTSECONDS = 300; HttpClient Client = new HttpClient(); var TenantId = ((dynamic)JsonConvert.DeserializeObject(Client.GetAsync("https://login.microsoftonline.com/" + domainName + "/v2.0/.well-known/openid-configuration") .Result.Content.ReadAsStringAsync().Result)) .authorization_endpoint.ToString().Split('/')[3]; // This client ID just has project.write PublicClientApplicationBuilder pcaConfig = PublicClientApplicationBuilder.Create("87edf46a-466d-4241-8afc-b9650d7fb0d7") .WithTenantId(TenantId); pcaConfig.WithRedirectUri(redirectUri); // This section uses the interactive flow for auth var TokenResult = pcaConfig.Build().AcquireTokenInteractive(new[] { scope }) .WithPrompt(Prompt.NoPrompt) .WithLoginHint(PJOAccount).ExecuteAsync().Result; //The following section uses the username and password - this would be best pulled from Azure Key Vault or use another auth flow //This also requires the app registration to be set as a public client //SampleConfiguration config = SampleConfiguration.ReadFromJsonFile("appsettings.json"); //string text1 = config.Text1; //var sc = new SecureString(); //foreach (char c in text1) sc.AppendChar(c); //var TokenResult = pcaConfig.Build().AcquireTokenByUsernamePassword(new[] { scope }, PJOAccount, sc).ExecuteAsync().Result; // Load ps context csom.ProjectContext psCtx = new csom.ProjectContext(pwaInstanceUrl); psCtx.ExecutingWebRequest += (s, e) => { e.WebRequestExecutor.RequestHeaders["Authorization"] = "Bearer " + TokenResult.AccessToken; };

- using the latest MSAL (Microsoft.Identity.Client v4.22) and Microsoft.ProjectServer.Client from Microsoft.SharePointOnline.CSOM 16.1.20616.12000 at the time of writing. These will also work with legacy auth disabled which is a setting that may break some existing custom applications.

To check if legacy auth is disabled you can open the SharePoint Online Management shell, connect to your admin Url and run Get-SPOTenent. Look in the returned properties for:

LegacyAuthProtocolsEnabled : False

which in my case shows that legacy auth is disabled.

Hopefully we will get the sample on Github updated with this latest information.

Customizing and extending the Project app just became more convenient!

Microsoft Project Team — Thu, 19 Nov 2020 00:06:20 GMT

In response to your feedback on UserVoice, we are pleased to announce a change to the Project for the web licensing to allow you to customize and extend the Project app without the need to purchase additional Power Apps licenses. For many scenarios, this change makes it easier for your organization to tailor Project Plan 5, Project Plan 3, and Project Plan 1 to meet unique business needs. The table below outlines what you can do with your subscription. The change to licensing is effective immediately.

The table below only outlines these changes. Please review the Project Service Description for further details.

¹Understand model-driven app components

Project for the web - October 2020 Update

Microsoft Project Team — Mon, 02 Nov 2020 17:01:14 GMT

Many features that are requested through Microsoft UserVoice appear on the Microsoft 365 Public Roadmap when they are in development and within months of being rolled out. If you follow UserVoice, submit suggestions for new capabilities, continue to vote on other user’s feature requests, or track which submissions receive the most votes. If you don’t follow this forum, come join and help us make Project better.

New Features:

Project & Roadmap in Microsoft Teams: Add your project or roadmap as a tab in Teams! Learn more about this feature by checking out our blog post.
Share projects with groups you don’t own: You can see all your groups when you add a group to your project. Easily share your work with the people who are import to your project without creating new groups.
Scroll to date in Timeline: Starting in November, you can automatically jump to any date on the timeline using our Go to date button on the Timeline view.

Upcoming Features:

Export to Excel: Export your project grid into an Excel spreadsheet. Share this information with colleagues and analyze Project data using the power of Excel!

Answers to top questions:

Thanks for all your comments on last month’s blog!

Q: I cannot change the Microsoft 365 group assigned to my project once I've set the group. Is this correct?

A: Right now, you can’t change the project group once it has been set. This is known functionality, and there are no present plans to change it.

However, when you copy a project, your group is not copied. If you need to assign a new group to a project, the best way to do that is to copy the project & assign the new group.

Q: Can I add projects to private channels in Teams?

A: Currently, you cannot add projects to private channels as private channels are not integrated with M365 groups.

Announcing Project and Roadmap apps for Microsoft Teams

Madhuri Jain — Tue, 17 Nov 2020 16:18:50 GMT

We are pleased to announce the release of the Project and Roadmap apps in Microsoft Teams. Connecting directly to Project from within Teams has been one of the major requests from Project users, and these apps will make it easy to manage, track, and collaborate on all aspects of a team’s project in one place. This brings content and conversation side-by-side in one integrated experience.

Team members can create new projects or roadmaps, or open existing ones, in Microsoft Teams and keep communications within the context of work and collaboration within Office 365. The Project and Roadmap apps can be added as tabs in any channel by selecting the “+” icon at the top of a channel. Anyone who has access to that channel can also access that tab.

Microsoft Teams ♥ Microsoft Project

Today, each one of us has become a project manager. To stay on top of the ever-shifting requirements of our jobs, we need tools that are simple yet robust enough to support any requirement, flexible enough to support any project type, and, most importantly, easy enough to collaborate with anyone no matter where they are or what device they are using.

The Project app in Teams helps you tackle anything from small projects to large initiatives and is designed for just about any role, skill level, or project type. You can do almost everything you can do in Project for the web experience such as the automated scheduling engine to set effort, duration, and resources from inside Teams.

Microsoft Teams ♥ Roadmap

If your group runs multiple projects at the same time and needs visibility across all the work being done, Roadmap provides a visual and interactive way to connect these projects and show their status in a transparent way across the organization.

The Roadmap - Microsoft Project app will give you a cross-functional, big picture view of the work that is most important to you. You can create a consolidated timeline view of projects from Microsoft Project and Azure Boards and plan larger initiatives across all of them - complete with key dates and milestones - so that all the work is visible.

Note: All Office 365 users will be able to view Projects/Roadmaps shared within Teams in a read-only mode. Users with appropriate Project for the Web licenses to create and edit Projects/Roadmaps will be able to do the same from within Teams as well. Learn more about Office 365 User view access here and Project for the Web licenses here.

If you want to learn more, see Use Project or Roadmap in Microsoft Teams. Next, notifications in Teams will be added so that users can see what’s important to them within Project and Roadmap in their team's activity feed. We’d love to learn more about what type of scenarios you would like notifications to fulfill. Provide your feedback here .

Frequently asked questions:

Q: What type of Projects can I add through the Project app in Teams?

A: Project app integrates with Project for the Web and hence allows you to add projects created using Project for the Web as a tab. It does not support projects created on PWA (Project Web App) or Project client (MPP files).

Q: Which projects show up in the existing list of the Project app?

A: When you add a Project to a Team's Channel tab, you can find all the Project for the web projects in the existing list which are shared with the Team (i.e the underlying Office 365 group).

Feedback!

We love hearing from you. Please tell us how we can improve your Project experience in Teams through our UserVoice site. You can also leave a comment below to engage with us directly to provide feedback.

Keep checking our Tech Community site for the latest feature releases and Project news.

Project for the web - September 2020 Update

Microsoft Project Team — Wed, 30 Sep 2020 19:15:34 GMT

Our team recently updated the items on the Microsoft 365 Public Roadmap. You can see our upcoming features and when those features will be available!

You can let us know what you think about these new features on Microsoft UserVoice. Join an existing thread or create a new one to tell us how to make Project better.

We also love feedback on existing features! If you have feedback, submit it by using the ‘Feedback’ button in Project for the web. Make sure to include your email so we can contact you directly with any follow up questions or comments. We also monitor the comments on all blog posts, so let us know what you think about this or other articles!

New Features:

Task Custom Fields: Store custom information about your projects efficiently by adding custom fields! For more information, check out the blog post on this feature.
Dynamics 365 Project Operations: Our team partnered with Dynamics to help launch Project Operations, a new application that has everything you need to run your service business. Check out our new features and capabilities released as part of wave 2 on October 1st. For more information on this product, check out the Project Operations overview page
Group by Assigned to: You can organize your tasks by assignee in the Board view. Get insight into what each person is working on! This feature should now be available to all Project users.

Self-Service Onboarding: Customers can make a self-service purchase online. New users can try out Project and other Microsoft solutions on their own! Check out the FAQ page for this feature to learn more.

Upcoming Features:

Project & Roadmap in Microsoft Teams: Starting in October, you’ll be able to add a project or roadmap as a tab in Teams. Chat with your teammates while viewing and updating your work.
Export to Excel: Export your project grid into an Excel spreadsheet. Share this information with colleagues and analyze Project data using the power of Excel!

Share projects with groups you don’t own: You can see all your added groups when you add a group to your project. Easily share your work with all the important people without creating new groups.

Answers to top questions:

Q: I was not able to attend Ignite this year, but I still want to watch some sessions! How can I do that?

Microsoft has several recorded sessions from Ignite that you can watch. Here are links to some of our favorites:

Also, we have some post-Ignite opportunities for customer connection. These conversations will run through October and cover a range of topics. You can find more information on these expert connects, including the list of events & the sign up page, on this site. The sign up form for these events can be found here.

Announcing Custom Fields for your tasks

Alexander Lahuerta — Thu, 24 Sep 2020 21:31:07 GMT

You can now personalize your tasks with custom fields in Project for the web! Select the “New field” button under the Add column menu to get started.

Create up to ten new fields to help you keep track of important information specific to your projects and workflows. Choose from four types:

Track important deadlines with Date fields
Use Yes/No fields to flag tasks that need follow up
Use Number fields to manage details such as quantities
Take short notes about status with Text fields (tip: hold the Windows key and tap semi-colon to open the emoji picker to add the colored circles)

Filter tasks using the contents of fields. If you have limited screen real estate, manage the fields in the task details pane. Give them a try, and let us know what you think in our UserVoice forum.

How to create custom fields

Select the “Add column” button to see the “New field” option. This button will open the menu to create a new custom field.

From here, select the type of custom field you would like to create.

Give your field a name select ‘Create’ to create your new custom field.

Your new custom field will appear in your project and you can start using it.

Like any other field, custom fields can be hidden from the Grid view. You can also use the column header to reach the edit pane where you can edit your fields.

The Edit field dialog box allows you to rename or delete that field.

Custom fields also have their own section in the task details pane. This is a great view if you have limited space on your screen.

Frequently asked questions

Q: How can I create the same custom fields on all my projects?

A: If you want to use the same set of custom fields in all your projects, you can create a template project, and then copy it. All your fields and values will be copied over. Take a look at our article on copying projects.

Q: Can I create formulas in Project for the web?

A: Not today. We’d love to learn more about what kinds of things you’d use formulas for. Provide your feedback in our User Voice forum.

Q: Can I include these fields in PowerBI reports or in PowerApps built on Project for the web?

No. These fields are local to your projects.

Q: How many custom fields can I create in one project?

A: Each project can support up to 10 custom fields

Feedback!

Microsoft Project loves your feedback!

We monitor the comments on all blog posts, so please let us know what you think about this feature in the comments section below. Additionally, the feedback you provide through the “Feedback” button in the product plays a vital role in our product decisions. Please let us know what you think. We read every submission and try to respond as needed; be sure to provide an email address so we can reach out for further information.

The feedback you provide through UserVoice for Project for the web gives us new ideas on how to improve your experience with Project. Join an ongoing discussion, or start your own conversation. We love to read what people think on making Project even better.

Project for the web - August 2020 Update

Microsoft Project Team — Mon, 31 Aug 2020 21:26:39 GMT

The Project team has been focused on big features, which you can see listed here, or track in the Microsoft 365 Public Roadmap. You can let us know any new features you need on Microsoft UserVoice. Join an existing thread or create a new one to tell us how to make Project for the web better.

We love feedback! If you have feedback, submit it by using the ‘Feedback’ button in Project for the web. Make sure to include your email so we can contact you directly with any follow up questions or comments. We also monitor comments on all blog posts so let us know what you think about this or other articles!

New features:

Group by Assigned: Starting this month, you can organize your tasks by assignee in the Board view. Get insight into what each person is working on!

Upcoming features:

Share Projects with groups you don’t own: Starting next month, you can see all your added groups when you add a group to your project. Easily share your work with all the important people without creating new groups.
Task Custom Fields: Use custom fields in Project for the web to ensure that all your information can live in one place.
Project & Roadmap in Microsoft Teams: Coming soon, Project & Roadmap will have their own applications in Microsoft Teams. Chat with your teammates while viewing and updating your work. All features available in the web experience will be available in the Teams.
Email notifications: Stay ahead of your work by creating email notifications for yourself and your teammates.
Export to Excel: Leverage the power of Microsoft Project & Microsoft Excel together by exporting your project data into spreadsheets.

Answers to top questions:

Q: How can I share project information with non-project users?

A: Users that are assigned certain Office 365 licenses can access Project for the web and Roadmap in read-only mode. For a full list of licenses with read-only access to Project for the web, check out our documentation.

As noted above, we have an export feature planned for release in the fall.

Project for the web - July 2020 Update

Microsoft Project Team — Mon, 03 Aug 2020 03:53:51 GMT

Our team is focusing on some bigger features that will be released in the next few months. In the meantime, we appreciate your continuous feedback through the “Feedback” button in the product and on UserVoice for Project for the web. Your input helps us focus on developing features that are helpful and improve the experience in Project for everyone!

The new features called out below may look familiar if you follow Project on the Microsoft 365 Public Roadmap, which gives advanced notice on pending releases of larger features. Additionally, other new capabilities mentioned in both this blog and future blogs will be appearing in the monthly “What’s new in Project" article, which will list out new larger and smaller features that already have rolled out.

What’s the Latest?

Project Operations ~ The Project team has been working with Dynamics 365 to build Microsoft Dynamics 365 Project Operations. This product aims to help teams predict, adapt, and rapidly respond to change across their projects and organizations. Announced at the end of June, the Project Operations public preview program is meant to collect feedback and ideas on this product and help us improve it before the product’s general release later this year. If you’re interested in our work with Dynamics 365, be sure to check out their blog post.
Documentation ~ The materials to help you leverage Project for the web for your team have been updated. Check out our blog post on Calendars in Project for the web. If you have feedback, feel free to leave comments, and we’ll do our best to get back with you as quickly as we can.
Scheduling Changes ~ Our scheduling changes to effort and duration are now available to all organizations using Project for the web. New projects should be scheduled with these changes. We’re working on converting old projects to this new scheme for the next month.

What’s coming next?

Teams Integration for Project and Roadmap ~ The native application to add Projects and Roadmaps in Teams is being developed. Keep an eye out for more information on this new feature!
Custom Fields at the Task level ~ Create custom fields in Project for the web to allow you to store custom information about your projects!

Answers to top questions:

Q: Any chance of an export feature coming up?

A: A new feature that allows users with an Office 365 license to view a project in read-only mode was rolled out last month. Additionally, we are planning on improving our export capabilities soon. You can follow that development, and let us know what you think here.

How to use calendars in Project?

Microsoft Project Team — Fri, 17 Jul 2020 23:46:17 GMT

As a project manager, your job is to schedule tasks accurately to ensure everything happens at the right time. However, before you begin to schedule, you need to determine the number of the working hours and days it will take to complete these tasks.

Project for the web comes with a default work template that can be automatically applied to all projects. This template is based on the average work schedule: it specifies work hours of 9AM through 5PM from Monday through Friday. If your work does not follow this schedule, you can create a new work template to suit your project’s needs. This blog post will walk you through the steps of changing the working hours and days of a project in Microsoft Project.

Project for the web is built on the Microsoft Power Platform. Because of this, some aspects of calendar and assignment setup needs to be done in Power Apps.

To access Dynamics 365:

While signed in to Office 365, open a browser window and go to https://web.powerapps.com
On the PowerApps page, select Apps.
On the Apps page, in the Org Apps tab, select Project.

From here, you can make changes to your projects and resources, implementing behind-the-scenes capabilities that can help you with project planning.

Note: For the purposes of this article, we will refer to assignees as resources. This is the term used by Dynamics 365 to refer to people assigned to complete tasks, but this term is not generally used in Project for the web.

Creating a work hours template

A work hour template (WHT) is a template that defines working days and hours and can later be applied to a project or resource. For example, a user might have a “Night Shift” WHT defined as Monday-Sunday 8PM-7AM, or a “Weekend Shift” WHT defined as Thursday-Sunday, 8AM-5PM.

There are several ways you can create a work hours template; however, all work templates are based off the calendars of bookable resources. A bookable resource is anything that can be scheduled. You can create a bookable resource in Dynamics 365 and configure its working hours. These working hours will define when the resource can be assigned work.

Note: You will not be able to create new bookable resources or work hours templates if you are not an Dynamics admin. If you follow these steps and do NOT see the buttons discussed here, talk to your Office 365 admin to help you with this work.

To create a bookable resource:

From the Project Power Apps page, select Resources.
Select New.
Add a resource type, user, and a name to your bookable resource, then select Save and Close. This will bring you back to the resources page Note: To learn more about bookable resources, check out the Set up bookable resources article. In summary, “Resource type” indicates who and what the resource is, “User” indicates who owns the bookable resource, and “Name” is the name of the bookable resource.
Select the name of your newly created resource.
On the top ribbon, select Show Work Hours
Select one of the working days. This should open a new view with options to ‘Edit’ and ‘Delete’ the working hours
Select ‘Edit’ and ‘All events in the series’
From this pane, select your desired working days and working hours
Select ‘Save’ on the Hours pane
Select Save and Close until you get back to your resource page.

Once you’ve configured a Bookable Resource’s calendar, you can create a work hours template based on this resource. You can do this in one of the following two ways.

To create a work template from the Active Work Hour Templates page:

From the Project Power Apps page, select the Projects menu on the bottom of the left pane, and then select Settings.
On the Project Settings Parameters page, select Calendar Templates.
On the Active Work Hour Templates page, select New.
Name your work template and (optionally) add a description
Use the drop-down menu to select the Template Resource that you would like to base the work hours on.
Select Save and Close. Your new work hours template will display on the Active Work Hour Templates page.

To create a work template from the Resources page:

On the Resources page, select the resource you want to base your work hours on.
Select Save Calendar As, enter a name for the work hours template, and then select Save.
When you’re done changing options, select Save and Close.

Applying a calendar to a project

Once you’ve created a work hours template, you can apply that template directly to a project.

To apply a work hours template to a project:

In your project, open the Project Settings pane.
Select the Calendar drop-down menu and select the work hours template you want to apply to the project.

If you do not see the Calendar field in Project details, this means you only have one available work hours template.

Once you have configured the calendar field to the right WHT, your work should only be scheduled during the working hours defined on the template.

FAQ

Q: Where can I find out more?

A: Check out our article: Create and apply work calendars in Project for the web

Q: Can I configure a resource calendar?

A: You can apply a calendar to a resource from the Resources page on PowerApps. From the Resources page, select the resources that you want to apply a calendar for and select Set Calendar. In the Work Template window, select the work template that you want to apply to your resource.

You can learn more about applying a calendar to a resource.

Q: Who has access to this functionality?

A: Dynamics 365 admins have the ability to create and apply calendars. If you follow these steps and do not see the mentioned buttons, then you do not have admin access to Project. You should contact your admin for help with calendar issues.

Project for the web - June 2020 Update

Microsoft Project Team — Mon, 06 Jul 2020 15:22:27 GMT

Welcome to the June update for Project for the web!

The feedback you provide through the “Feedback” button in the product or UserVoice on Project for the web (or maybe both!) plays a vital role on how we approach new features. Please keep this feedback coming! We read every submission we get and try to respond as needed. Be sure to provide an email address so we can reach out for further information.

What’s the latest?

Copy Project ~ You can copy an existing project and use it to create a new project. This feature should now be available to all Project for the web users. To find more information on this feature, please check out our Copy Project blog post!
View persistence ~ Collapsing summary tasks and custom column width in Grid view will remain the same when you reload or reopen your projects.
Office 365 user view to Project and Roadmap ~ All O365 users should be able to access Project and Roadmap as guests.

What’s coming next?

Custom Fields at the Task Level ~ Create custom fields in Project for the web to allow you to store custom information about your projects!
Add Roadmap reports to the PowerBI template ~ Starting very soon, you will be able to export data from roadmaps to PowerBI. Keep an eye out for future announcements and blog posts about this new functionality!
Teams Integration for Project and Roadmap~ Right now, you can add Roadmaps and Projects as Web tabs in Teams. However, you soon will be able to add Projects and Roadmaps as an app in Teams.

Answers to top questions

Q: What admin permissions level is required to change working hours for a project calendar?

A: Dynamics 365 admins should have the permissions level to change working hours for project or resource calendars. If you need help with permissions for changing the project calendar, contact your systems admin.

Copying projects in Project for the web

jackieduong — Tue, 23 Jun 2020 17:10:15 GMT

We are pleased to share that we've added the ability to copy projects in Microsoft Project for the web. We built this feature to address your feedback to allow you to reuse projects and repeat workflows. With Copy Project, you can now easily duplicate projects to get started even faster.

Copy existing projects

It takes a lot of time to build the perfect project plan. This is especially true when a project includes a lot of tasks or are part of a repeated process. Manually recreating projects can be tedious and takes time away from actually doing the work. With copy project, you can now create a new project by duplicating an existing one. From the project, you can click on the title of the project to open up the details pane. From there, you can select “Copy project” from under the “…” menu.

Click on the title of the project to open the project’s details pane

Click on the “…” from the project’s details pane to open up the drop-down

Click on “Copy project”

Your new project will be created with the same original project name with “- Copy” added to it so you can easily track the copied project. You can update the name of your newly copied project through the Project Details Pane.

The overall project structure and tasks get copied over. Copying a project does not copy over task assignments or the connected O365 group. However, you can always re-assign the project to the same group (or a different one!). Tasks are also reset to 0% complete, so you can start your new project with a clean slate.

Tips and Tricks

Getting started with your new project: Don’t forget to rename your project in the project’s details pane! You can also share this newly copied project to a new or existing group, by clicking on “Group members” in the top right corner, so you and your team can quickly get working on the new project.

Moving your project dates: When you copy a project, the dates will copy over – and you may end up with a lot of “late” tasks! To quickly adjust the project to your new deadlines, you can update the Start Date of the project to push all of the tasks out. That way, you keep the relative dates, durations, and dependencies of all the tasks.

Update the Project Start Date through the Project Details Pane to change the period of your project.

Templatizing your projects: You can deactivate a project and use it as a template, so that others can reuse the project but not make edits to it. You can deactivate a project through the Dynamics interface, which will make the project read-only.

First, go to the Dynamics app via the O365 Waffle

Select the “Project” module, where you will see a list of your projects – select the project you’d like to deactivate.

Once you select your project that you want to deactivate, you can click the “Deactivate” button.

In the Project for the web interface, you will see that this project is not editable, but can be copied. You can now use this as a non-editable template!

Feedback

If you have any questions, comments, or feedback on the Copy Project experience, please let us know! We love hearing from you, so please continue to tell us how we can improve your Project experience by commenting directly on this post, through the “Feedback” button in the product, or UserVoice for Project for the web. We read every submission and try to respond as needed -- be sure to provide an email address so we can reach out to you for further

Project for the web - May 2020 Update

Microsoft Project Team — Fri, 29 May 2020 23:04:12 GMT

We recognize that work has changed drastically in the last few months and want to continue in giving you modern tools that support you and your teams. The feedback you provide through the “Feedback” button in the product or UserVoice for Project for the web helps us make decisions on future features. We read every submission and try to respond as needed -- be sure to provide an email address so we can reach out to you for further information!

The new features called out below may look familiar if you follow Project on the Microsoft 365 Public Roadmap, which gives our users notice of pending releases. Additionally, new features are announced on our monthly “What’s new in Project” article, which lists large and small features that already have been rolled out each month.

What’s the latest?

Copy Project - You can copy an existing project and use it to create a new project. This feature is being rolled out incrementally and will be available to all users soon.
Office 365 E5 user read only - Office 365 E5 users can now view Projects/Roadmaps that are shared with them in a read-only mode. Read-only access will be rolled out to other Office users incrementally in the near future.
Task scheduling changes - Starting this month, new projects that have tasks with resources can be scheduled by using a fixed duration behavior model.

What’s coming next?

Add Roadmap reports to the PowerBI template - Starting this summer, you will be able to export data from roadmaps to PowerBI. Then, you can report on Roadmaps using PowerBI templates, reports, and dashboards!
View persistence - Collapsing summary tasks and custom column width in Grid view will remain the same when you reload or reopen your projects. Find important information faster and get started quickly when returning to your work.

Answers to top questions

Q: Can I change the working hours for my project?

A: Yes! We have an article on how to do that here. Remember, you need to have admin permissions to do this, so check with your systems administrator if you need help with this.

Q: How do I set a milestone/deadline in Project?

A: You can set a milestone in Project by setting the duration of a task to 0. Milestones will appear as diamonds in the timeline but are not visually different from other tasks in the Grid and Board views.

New Flow Templates for Project for the web

jackieduong — Thu, 14 May 2020 03:17:48 GMT

You can use Power Automate to create automated workflows for Project for the web. Project for the web is built on the Microsoft Power Platform, and its data is stored in CDS (Common Data Service). You can access Project data in Power Automate through the Common Data Service connector.

We have released two new Power Automate Flow templates for Project Managers and Team Members in the Flow Template Gallery to help you be more productive with Project for the web. You can also use these templates to explore how to build more Flows with Project for the web data.

New Templates

You can leverage templates today by clicking on the link to the template and clicking “Create Flow”.

Send an email notification for tasks you assign to people in your projects – This template is designed for Project Managers. It will send a notification email to anyone you assign tasks to in projects that you’re the Project Manager of, so the assignees are reminded of their new task.

Daily email reminder of late and upcoming tasks in Project – This template sends a daily email of all late and upcoming tasks due in the next 7 days that are assigned to you.

Additional Notes:

By default, the Environment field in the Flows are set to “Current” in the Common Data Service actions. The environment that you are in must be “Default” since Project for the web runs in the default org. If you need to update the Environment you are currently in Flow for, you can click the “Environments” button in the top right corner of the ribbon, and select “Default”
You will need an appropriate license to run flows in Power Automate. You can learn more about Power Automate licensing here.

Feedback

Your feedback is invaluable in helping us make future product decisions. Please continue to give us your input by using the “Feedback” button in the product or UserVoice for Project for the web. We read every submission we get and try to respond as needed. Be sure to provide an email address so we can reach out to you for further information!

If you have any questions about the new templates, building Flows with Power Automate and Project for the web data, or other template ideas, please let us know in the comments!

Project for the web – April 2020 Update

Microsoft Project Team — Fri, 01 May 2020 23:58:42 GMT

Some features announced below may look familiar if you follow the Project on the Microsoft 365 Public Roadmap or read the March 2020 Update on this blog. The Public Roadmap provides advanced notice of upcoming features that are typically bigger in scope and/or highly anticipated. Another new feature resource to bookmark is the monthly ‘What’s new in Project’ article. The “Project for the web” tab in this article highlights both big and small features that are already available to use.

What’s the latest?

Support for all Geographies – Project for the web and Roadmap now have worldwide support. If you still cannot access Project for the web and Roadmap, contact your Office 365 admin.
Project for the web for Education – Project for the web and Roadmap are officially available for our education customers!
Project for the web and Roadmap on/off toggle – The ability to disable Project for the web or Roadmap in an entire tenant is available for all geographies. To learn more, please review the "Turn Project for the web or Roadmap on or off for users in your organization" article.
Task filtering Use the filter toggle in the top right corner of the Project screen to filter your tasks in the Grid view. Enter in your keyword, and Project will search the (task) Name, Assigned to, and Bucket fields.
Project Percent Complete – Many of you need to know how much work has been done on your projects. Now, your project details will display the percent complete to give you better visibility into the overall work already completed against your entire project.
Copy Project – You can copy an existing project and use it to create your new project. Copying a project means all the tasks, dependencies, durations, and efforts are included. This feature is being rolled out incrementally and will be available to all users soon.
Task scheduling change for unassigned tasks– You can set Effort and Duration independently of each other for unassigned tasks. When Effort is set, Duration will not change.

What’s coming next?

View Persistence – Collapsing summary tasks or changing column width in the Grid view will stay the same when you reload or reopen your projects. This update will make it easier for you to find important information faster when opening a project!
Add Roadmap reports to the Power BI template – You will be able to use Roadmap reports in the Project report templates on Power BI.
Office 365 user view to Project for the web and Roadmap – Share your projects & roadmaps with Office 365 users! These users can only see the tasks in your projects but not make changes to your work. This functionality will be available first to Office 365 E5 users and will slowly roll out to users with other Office 365 licenses.
Task scheduling change for tasks with assignments - You will be able to set the Effort and Duration to be independent of each other for tasks with assignments. When Effort is set, Duration will not change. We will let you know when this update becomes available.

Answers to top questions

Q: Will filtering work in the Board and Timeline views?

A: Filtering is only available in the Grid view.

Q: How can I share Power BI reports with my clients?

A: If you have a Project Plan 3 or Plan 5 license, you can use the Project Power BI template to import, analyze, and share data from Project for the Web. There are a variety of “out-of-the-box” reports available to help you easily understand your data. For example, our Portfolio Dashboard gives you a roll-up of all projects, while the “My Work” report lets an individual team member see their own work across projects.

For more information, check out our help article on using Power BI with Project for the Web data here.

Project for the web – March 2020 Update

Microsoft Project Team — Thu, 30 Apr 2020 21:13:38 GMT

Welcome to the first blog focused on new key features for Project for the web. Our intent is to highlight the latest and greatest, so we will provide updates periodically. The new features called out below may look familiar if you follow Project on the Microsoft 365 Public Roadmap, which gives advanced notice on pending releases of larger features. Additionally, other new capabilities mentioned in both this blog and future blogs will be appearing in the monthly “What’s new in Project" article, which will list out new larger and smaller features on an ongoing basis.

The feedback you provide through either the “Feedback” button in the product or UserVoice on Project for the web (or maybe both!) plays a vital role on how we approach new features. Thank you to everyone for taking the time to comment or suggest ways on how to improve and evolve the product. Please keep your feedback coming! We read every submission we get and try to respond as needed. Be sure to provide an email address so we can reach out to you for further information – it’s very helpful for us!

What’s the latest?

Many of the new, or recently new, features for Project for the web and Roadmap are based on your input. Again, please continue to provide us your feedback!

Copy link to task – Using the the right-click menu, you can copy a link to a task. This link, when clicked, will take you back to the project with the details opened for that specific task. If someone wants more details on the task, they can click the link you shared to open the task and see what you are referencing.
More Roadmap Zoom levels – One top request for Roadmap was for users to zoom out to see a longer timeframe on the screen. We heard you and added three new zoom stops so you can see as much as 6 years at a time.
Many bug fixes – Like any v1 experience, we’ve received a lot of feedback and have been fixing a number of bugs. One interesting bug was how a user's screen would start shaking for no apparent reason. It took us a moment for us to figure out what this feedback meant, but we were able to reproduce the issue and have since fixed it. Another common bug fix was on the “Today” and yellow late task highlighting that appeared incorrectly in the Grid and Board views. This issue came up when your time zone was different from the project’s time zone.
Power BI report template including Project Online and Project for the web – As you may have projects in both Project Online and Project for the web, you now can use the updated Power BI report template to include reports that connect to both data sources. Please reference the "Connect to Project data through Power BI Desktop" article to learn more.

What’s coming next?

We will be launching the following in April.

Support for all Geographies – Starting April 7, 2020, Project for the web and Roadmap will have worldwide support. If you haven't been able to see both service and capability, it could be because your region hasn't been supported up until now. After mid to late April, if you are still unable to access Project for the web and Roadmap, you may need to contact your Office 365 admin.
Toggle on/off - You will have the ability to disable Project for the web or Roadmap for your entire tenant. This feature will be available for all geographies. For more details, please review the "Turn Project for the web or Roadmap on or off for users in your organization" article.
Project for the web & Roadmap for Education – Great news for our education customers! You will have access to Project for the web and Roadmap as the roll out begins on April 7, 2020.
Copy project – You may have a project that is like a previous project you’ve completed. To make it easier to get started quickly, you can copy the existing project and use it as the basis for a new project. When copying the project, you’ll get all the tasks, dependencies, and other scheduling information, which you can then update as needed.
Task filtering – As your project grows, you may need to see only a subset of the project at one time. You can soon filter your list of tasks in the Grid view. Just click the filter button on the top right of the page and enter the value you want to query on. Project will search the (task) Name, Assigned to and Bucket fields.
Task scheduling change – In response to your feedback, you can now set Effort and Duration independently of each other for unassigned tasks. When Effort is set, Duration will not change. For tasks with assignments, our plan is to also update Effort and Duration to be independent of each other. We will let you know when this update becomes available.

Answers to top questions

We want to share the two most commonly asked questions with their respective answers below.

Q. How do I delete a project?

A Click the project’s name. In the side pane that pops out, click the … in the upper right corner, and you’ll see the Delete project command.

Q. How do I create a milestone?

A. Set the task duration to 0 days for any task, and you now have a milestone. Milestones are represented by diamonds in the Timeline view, and our plan is to update their styling for the Grid view, too.

Project Online: Adding tasks where you want them with Power Automate

Brian Smith — Mon, 03 Feb 2020 18:46:37 GMT

This is a guest post from Daniel Partridge - who answered an internal enquiry at Microsoft, for a colleague who needed to add a task under a summary using Power Automate (Flow). Great timing as Daniel was also looking at the same challenge.

In Daniel's words and pictures:

In order to accomplish this, I used the “Send and HTTP Request to SharePoint” action in my Power Automate flow, and the end result appears in the schedule as shown in this image:

The flow process would be as follows (*IMPORTANT: The REST API to use for this would be ProjectServer vs. ProjectData in the URL). ProjectData is used for reporting - OData.

Get the Project Id (GUID)
Get the Id (GUID) of the Summary task
Checkout Project - Power Automate Project Online Action
Send HTTP Request to SharePoint - Power Automate SharePoint Action

HTTP POST: _api/ /Draft/Update()/Projects('ProjectGUID')/Draft/Tasks/Add()

Header JSON

{

"Accept": "application/json;odata=nometadata",

"Content-Type": "application/json"

}

Body JSON

{

"parameters":

{

"Name": "task title",

"Notes": "task notes",

"Duration": "2d",

"ParentId": "summaryTaskGUID"

}

Send HTTP Request to SharePoint - Power Automate SharePoint Action

HTTP POST: _api/ProjectServer/Projects('ProjectGUID')/Draft/Update()

Header JSON

{

"Accept": "application/json;odata=nometadata",

"Content-Type": "application/json"

}

Body JSON

Leave blank

Check-in and publish Project - Power Automate Project Online Action

The images below show an example using the Power Automate Project Online Action for “Creates new task” which is unnecessary if you are using the Project Summary task or some other task that already exists to link to as the parent task:

Thanks Daniel for sharing, and I hope this helps other people using Power Automate and Project Online to get their tasks flowing into their projects just where they want them!

My holiday gift to you - update posts are up to date!

Brian Smith — Fri, 27 Dec 2019 22:01:28 GMT

I'd let these slip a bit - but I just updated the Project 2016, Project Server 2016 and Project Server 2019 posts with the updates through to December 2019. For the 2019 client - the updates can be found at https://docs.microsoft.com/en-us/officeupdates/monthly-channel-2019 or https://docs.microsoft.com/en-us/officeupdates/semi-annual-channel-2019 depending on the channel you get Office through (Monthly or Semi Annual - other channels are available)

Project 2016

Project Server 2016

Project Server 2019

Project for the web - some users not resolving in the assigned to field

Brian Smith — Mon, 11 Nov 2019 17:00:49 GMT

If you have had your Office 365 tenant for some time (since before Guests were a thing - so 6 years or so ago) and migrated accounts in from on-premises active directory - then you might run in to this issue where these users are not being resolved. In some cases this might be expected, as you can't use external users yet - but if these are accounts in the same Office 365 tenant and real members then read on.

This is a known issue where the UserType of these specific users who were added a while back via AD is NULL - and see https://docs.microsoft.com/en-us/dynamics365/talent/people-picker-user-not-found for details. You can look on the Users blade of Azure Active directory to see this value for a user - my screenshot shows what they SHOULD look like - I don't have a user in a bad state.

You can see here that Alex is a member - he can be assigned ok.

You can also use PowerShell to resolve this - either the AzureAD account or Msol Account:

Have someone who is an admin on the tenant do the following steps:

Run Windows Powershell as an admin
Enter Install-Module -Name MSOnline
Say Yes to the prompts around if you want to install the module
Enter Connect-MsolService
Enter the tenant admin credentials when prompted
Set-MsolUser -UserPrincipalName firstname.lastname@yourtenant.onmicrosoft.com -UserType Member
Wait 30 minutes or so
Go back to Project and try searching for the user in a project where he isn't a member of the group but you are a group owner

You should replace the UserPrincipalName with each account in turn that currently has a NULL UserType. You could also choose to use Outlook and add members to the Group - they will then soon become available for assignment in Project for the web.

Another way to see if a user is affected is to use Graph Explorer https://developer.microsoft.com/en-us/graph/graph-explorer and a Url similar to the following. with the user's display name replacing First and Last:

https://graph.microsoft.com/beta/users?$filter=startswith(displayName,%27First%20Last%27)&$select=id,displayName,userType,onPremisesSyncEnabled

A working user will return the expected data (and don't get confused like I did by the null against userType - this isn't the issue:

{
"@odata.context": "https://graph.microsoft.com/beta/$metadata#users(id,displayName,userType,onPremisesSyncEnabled)",
"value": [
{
"id": "ded29fcd-46cc-432b-9965-06e43d48ada0",
"displayName": "Patti Fernandez",
"userType": null,
"onPremisesSyncEnabled": null
}
]
}

A broken user will not be able to resolve from Graph - and will return an empty array:

{
"@odata.context": "https://graph.microsoft.com/beta/$metadata#users(id,displayName,userType,onPremisesSyncEnabled)",
"value": []
}

The new Project is rolling out!

Microsoft Project Team — Wed, 16 Oct 2019 16:19:48 GMT

Introducing Project, or Project for the web

We are pleased to announce the beginning of the rollout of Project, also known as Project for the web and formerly known as Project service. As announced at Ignite 2018, the release of Project for the web marks the next chapter for Microsoft Project. If you are an existing Project customer with either Project Online Professional or Project Online Premium subscriptions, Project for the web will be available in your Office 365 tenant, starting in October 2019. Any user with one of these subscriptions will get access to this new product.

For more information, check out What is Project for the web? and Customizing Project for the web.

Subscriptions, Pricing, and Plans

Project for the web is available through two subscriptions: Project Online Professional and Project Online Premium. Each of these subscriptions also includes Project Online and Project Online desktop client. To understand which applications are provided in each of the available Project subscriptions and what capabilities each application offers see the Microsoft Project Service Description.

In the table above the number of checks () indicates the general level of capabilities provided by a plan. For example, for Project Online Premium provides more capabilities then Project Online Professional.

We will continue to offer Project Online Professional and Project Online Premium subscriptions at their current prices. All the new capabilities in our initial Project for the web release are available in both subscriptions so current subscribers can take advantage of the new capabilities at no additional cost.

Note that Project for the web is only available through Project subscriptions.

Capabilities & Features

Please go see the list of capabilities and features for Project for the web

Questions and answers

What is the roadmap for Project for the web?

We will be providing the latest updates to Project products on the Microsoft 365 Roadmap. If you filter on "Project," you will easily be able to find upcoming and released features and capabilities. We will be carefully tracking user feedback and usage. You can be part of the conversation by participating in our Project Feedback Forum.

In this age of agile software development, rather than setting a specific date for specific features, we will regularly assess customer feedback and usage data for Project for the web to ensure we are delivering features that meet customer needs.

Will Project for the web be available in the Office 365 Government Community Cloud (GCC)?

We are committed to offering Project for the web in GCC. You can contact your Microsoft representative for more information.

What are the benefits of Project for the web for Microsoft Partners?

Existing Project partners, and any other Microsoft partners interested in expanding their business will benefit from this new platform for Project for the web. The adoption of the Microsoft Power Platform as the new platform moving forward opens a new set of opportunities enabled by Power BI, PowerApps, Microsoft Flow, and the Common Data Service. We’re excited about the expansion of opportunities for partners, including training, app development, configuration services, adoption programs, and the ability to offer custom applications on AppSource, etc. We expect to see our Project Partner community transforming their current IP in the light of the new platform. You can learn more by joining our Yammer “Project Partners WW” group.

For existing customers

Project Online desktop client

Read Project for the web and Project Online desktop client.

Project Online

Read Project for the web and Project Online.

Project Server

We recognize that many customers are using Project Server and many need to continue to use it for some users or geographies due to compliance and other requirements. We released Project Server 2019 at the end of 2018.

Here is the product lifecycle for Project Server:

At this point, we do not have information to share about future on-prem releases of Project.

Roadmap - have you disabled some necessary services?

Brian Smith — Tue, 24 Nov 2020 21:45:23 GMT

The new Roadmap feature for Project Online uses the Common Data Service for storage of the Roadmaps and items, and also uses Flow to synchronize the data periodically. If you have certain services disabled then either the infrastructure for Roadmap can't get provisioned when you first go to use it - or it might just stop working.

If you go to the App Launcher and Admin, and go to the Azure Active Directory Admin page - then Enterprise Applications the usual suspect will be ~~Dynamics CRM Online~~ Common Data Service (Application ID = 00000007-0000-0000-c000-000000000000). If I look at the properties on my system (which I broke on purpose) then I can see that users cannot access the application. (Dynamics CRM Online now has the better name - Common Data Service)

As you can see above - the Name for this item is Common Data Service. To resolve the issue and get things working again I need to set the Enabled for users to sign-in to Yes, and then Save.

Other Enterprise Applications may also cause a similar issue, but tend to not be present for tenants who just have Project Online. But if you see these applications - check them too:

Microsoft PowerApps - Application ID = 475226c6-020e-4fb2-8a90-7a972cbfc1d4
CRM Admin API - Application ID = 637fcc9f-4a9b-4aaa-8713-a2a3cfda1505

All of these (if they are present) need to be enabled for user login. If they aren't then you should check with the other work stream owners as to why they had been disabled and alert them to the fact they are required for Roadmap to function.

*** Update 11/24/2020 The current app dependencies for Project for the web and Roadmap are:

Common Data Service – Application ID 00000007-0000-0000-c000-000000000000
Microsoft PowerApps - Application ID = 475226c6-020e-4fb2-8a90-7a972cbfc1d4
CRM Admin API - Application ID = 637fcc9f-4a9b-4aaa-8713-a2a3cfda1505
Microsoft Flow - Application ID 7df0a125-d3be-4c96-aa54-591f83ff541c
Dynamics Provision – Application ID 39e6ea5b-4aa4-4df2-808b-b6b5fb8ada6f

***

Other symptoms you might see if you are running F12 Dev tools in your browser is that a call to GetRoadmapCdsEndpoint either times out or fails with an http 400 response. You may see a spinning 'Almost Ready!' message, rather than the 'Sorry...' one.

Related to this type of failure could be some other block on the required services - such as a Conditional Access rule blocking functionality such as Flow. If Roadmap links to Azure DevOps (ADO) stop working then maybe a Conditional Access rule is blocking the Flow calls to ADO.

Of course it is always worth checking the Service Health Dashboard in case the problem is at the service level too.

Once things are running OK then I can either start or continue to use Roadmap!

More information on Roadmap if you are not familiar with it - here - https://techcommunity.microsoft.com/t5/Project-Blog/Announcing-Project-Roadmaps/ba-p/268466

For those who prefer to use PowerShell rather than the UI - then you can run the following in an AzureAD PowerShell window:

Connect-AzureAD
$cds = Get-AzureADServicePrincipal -Filter "AppId eq '00000007-0000-0000-c000-000000000000'"
$cds.DisplayName
$cds.AccountEnabled

And this should return:

Common Data Service
True

Project Online or Project Server - best leave the master pages alone!

Brian Smith — Thu, 11 Jul 2019 16:42:05 GMT

Because some customizations can break Project Web App pages we have always blocked SharePoint Designer from editing/changing a PWA master page - and in the 2007 version I even blogged about it. Time moves on and there are now new ways to play about with master pages, and new ways to break PWA! Design Manager was released a couple of years ago to allow easy branding of SharePoint pages, and this isn't something we can block for PWA so it is possible to break our pages - so for the best experience do not update the master pages on a PWA site.

As with any 'unsupported' change that doesn't always mean you shouldn't do it - but just be prepared that it might break something, so test thoroughly and then if you do find a break you will need to either fix it by reverting or further modification. We can't help you from support to troubleshoot the break - our support only extends to reverting to the original master page.

The most recent issue I've heard of where a master page caused problems affected some of the charts in the Resource Center - but I'm sure there are many different ways that things might break.

We have added this unsupported scenario to our software boundaries and limits documentation at https://docs.microsoft.com/en-us/projectonline/project-online-software-boundaries-and-limits

Just for reference - the documentation for Design Manager can be found here - https://docs.microsoft.com/en-us/sharepoint/dev/general-development/overview-of-design-manager-in-sharepoint

Project Professional not working on Windows 7?

Brian Smith — Tue, 09 Jul 2019 21:41:23 GMT

*** Updated info 7/9/2019

If you moved to the Standard release no action needed - but you could now move back to targeted
If you did get a replacement NAMEEXT.DLL then no action needed, either "Update Now" or when the next update and the new DLL will replace the temporary one.
If you used some other workaround based on the DLL in the error - then "Update Now" to fix it
If you are seeing this error for the first time - then "Update Now" to get the latest version

After updating Project Pro – customers with the fixed versions should be on builds at or greater than 16.0.11727.20244

For the background to the issue read on ***

There is an issue with a recent update (June 2019) of the Project Professional click to run client for those in the targeted channels (Project Online Desktop client) that gives an error for Windows 7 users when connecting to Project Web App, either by opening the application and trying to connect to PWA, or if taking an action that would start Project, such as opening a plan from the Project Center into Project:

Error message - full text below

“The program can't start because api-ms-win-core-version-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.”

This affects customers on targeted releases and only on Windows 7 - and can be overcome by reverting to the standard release for now, and if you understand that then go for it - if not then read on for other options...

We have a couple of workarounds for this issue and I'd suggest number 2 might be the best one to choose, as it keeps you at the same release level just in case you are benefiting from a recent fix for any of the Office products:

As this only affects the targeted channel you can revert to the standard release and then uninstall and re-install to get things working. To make these changes get your administrator to go to Office 365 Admin Center, then Settings, Organizational Profile and change release preferences to Standard Release under the Release track.
Contact support and we can supply a fixed NAMEEXT.DLL that will overcome the issue. Quote SP183696 to help identify the issue you are having.

Once we release the fix (hopefully we will make the July updates) then no action is needed - the right new DLL will be installed. If you take option 1 above then after the July updates you could change back to targeted release.

We have issued a Service Health Dashboard announcement, but only to customers who have opened cases - SP183696.

And again, this only affects Windows 7, and as a reminder, support for Windows 7 ends on January 14th 2020.

Project and Project Online - multi factor authentication

Brian Smith — Mon, 17 Jun 2019 16:00:43 GMT

When planning the last blog posting on the old MSDN site before migration to the TechCommunity blog sites for Project, Planner and Project Support I asked on Twitter what the last post should be. Didier Maignan suggested an article on MFA for PWA and Pro. I then found I was too late - so instead I'm posting on the new home of Project Support blogs – so here goes!

This is my Office 365 tenant, brismith365, and I have enabled MFA for my user though the Admin portal – and I already have a phone associated with this user account. The login when I go to PWA looks like the following (and I also have the custom Office 365 background – in this case Puponga, New Zealand):

Scrren shot of O365 Login - custom backgroundI choose my account:

Multi factor authentication (MFA) promptAnd after clicking Next I see the following, and I chose to have a text message sent:

Choice for MFAI get a message, then enter in the screen:

Request for security verification codeI’m then presented with an app password that I can use for applications that don’t support the phone authentication.

App password if requiredI’m then authenticated (I don’t need the app password for PWA) and can get to SharePoint and PWA.

SharePoint via MFA

PWA via MFAFor the Project Online desktop client this would be the experience. I open Project and choose my brismith365 connection to get to the same PWA as above:

Project client login

Clicking OK takes me to the page to enter my login:

Account login for Project client

This recognizes that I have MFA configured and send me a text message, which I enter and click verify:

MFA prompt as it recognizes it needs a codeAnd I’m in! The account top right has my Microsoft account – as I have several accounts associated with my Project client, but I am connected and authenticated to the same PWA as above.

Authenticated and connected

Multi factor authentication for Project Web App and Project Online desktop client!

Project Server 2019 Public Updates

Brian Smith — Fri, 12 Feb 2021 14:48:10 GMT

Here are all the articles for fixes released for Project Server 2019 from its launch to date. The DB Version at release was 16.0.10337.12109. Some months there is more than 1 package for updating SharePoint Server 2019.

February 2021

https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-office-online-server-february-9-2021-kb4493192-4930dbe2-17f9-42d1-4174-3e281a746c84

https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-sharepoint-server-2019-february-9-2021-kb4493194-c3347c2c-5ace-7079-54c9-15dd4980ade7

https://support.microsoft.com/en-us/office/february-9-2021-update-for-sharepoint-server-2019-language-pack-kb4493193-10e07a5e-3559-85c9-9518-3d61c60c0c96

DB Version 16.0.10371.20043

Fixes accessibility issues in the Pick Resource feature (also seen in Project Web App as Choose User) dialog box because of an incorrect focus on the OK button. After you apply this update, the focus is set on the Search Text Edit field.
The date range of the timescale on the Project Web App (PWA) Approvals page is off by one day if the user's time zone is set to a zone east of UTC. For example, UTC+2.
In some situations, the Project Calculation Service (PCS) crashes while it opens a given project. The crash details that are logged in the SharePoint Unified Logging System (ULS) logs or in the Windows event logs resemble the following entry:
"The worker encountered a very serious error and will shutdown. Exception code was: 0xc0000005 (EXCEPTION_ACCESS_VIOLATION)."
Ribbon buttons in the task management section (View,Edit, Delete item) in the task list are disabled for the tasks that are listed beyond the first page.

January 2021

https://support.microsoft.com/en-gb/help/4493160/security-update-for-office-online-server-january-12-2021
https://support.microsoft.com/en-gb/help/4493162/security-update-for-sharepoint-server-2019-january-12-2021
https://support.microsoft.com/en-gb/help/4493161/security-update-for-sharepoint-server-2019-language-pack-jan-12-2021

DB Version 16.0.10370.20001

Users cannot open the Project server admin page (ServerConfig.aspx), and you receive an error message that resembles the following:
"System.ArgumentException: Culture ID 4096 (0x1000) is a neutral culture; a region cannot be created from it."
When you view a timeline in Project Web App, the day portion of a date label is repeated. For example, if the language and locale are set to Portuguese, and you have a task that is scheduled to begin on November 13, the label on the timescale shows "13 13e Novembro" instead of the expected "13 Novembro."

December 2020

https://support.microsoft.com/en-nz/help/4486750/security-update-for-office-online-server-december-8-2020
https://support.microsoft.com/en-nz/help/4486751/security-update-for-sharepoint-server-2019-dec-8-2020
https://support.microsoft.com/en-nz/help/4486752/security-update-for-sharepoint-server-2019-language-pack-dec-8-2020

DB Version 16.0.10369.20000

No Project Server 2019 updates

November 2020

https://support.microsoft.com/en-nz/help/4486713/security-update-for-office-online-server-november-10-2020

https://support.microsoft.com/en-nz/help/4486714/security-update-for-sharepoint-server-2019-nov-10-2020

https://support.microsoft.com/en-nz/help/4486715/november-10-2020-update-for-sharepoint-server-2019-language-pack

DB Version 16.0.10368.20022

Fixes a scheduling engine crash, and adds additional logging to help identify possible future crashes.
Fixes an issue in which the "Reporting (Timesheet Save)" queue job runs very slowly. This job is created when timesheets are submitted. This issue creates a backup of queue jobs and causes other slow performance problems.
Fixes an issue in which grouping in a task list that's in a project site breaks the quick edit experience.
Fixes an issue in which a resource's availability or maximum units information is lost after the resource is updated through the Client Side Object Model (CSOM) or the Project Web App user interface (UI).

October 2020

https://support.microsoft.com/en-ie/help/4486674/security-update-for-office-online-server-october-13-2020

https://support.microsoft.com/en-ie/help/4486676/security-update-for-sharepoint-server-2019-october-13-2020

https://support.microsoft.com/en-ie/help/4486675/october-13-2020-update-for-sharepoint-server-2019-language-pack-kb4486

DB Version 16.0.10367.20000

Sometimes, when you open a project, the % Complete value on a Fixed Duration task that's 100 percent complete changes to a lesser value.
On a portfolio cost analysis, the picker control that enables you to choose "Forced-in," "Forced-out," or "Auto" is unavailable. Therefore, you can't change projects that you want to force in or out of the analysis. This occurs on Project Web App instances that have been defined as host-named site collections.

September 2020

https://support.microsoft.com/en-us/help/4484505/security-update-for-sharepoint-server-2019-sept-8-2020

https://support.microsoft.com/en-us/help/4484504/security-update-for-sharepoint-server-2019-language-pack-sept-8-2020

No Project Server 2019 updates

August 2020

https://support.microsoft.com/en-us/help/4484472/security-update-for-sharepoint-server-2019-august-11-2020

https://support.microsoft.com/en-us/help/4484471/security-update-for-sharepoint-2019-language-pack-august-11-2020

DB Version 16.0.10364.20001

Sites that have many timesheets or timesheet views may experience a time-out when you create or modify timesheet views. This may make it impossible to create timesheets or open existing timesheets.
When you follow a procedure to link a project task to an Issue or Risk within the Asset Picker table, items such as Issues, Documents, Tasks, and Deliverables are missing.

July 2020

https://support.microsoft.com/en-us/help/4484453/security-update-for-sharepoint-server-2019-july-14-2020

https://support.microsoft.com/en-us/help/4484452/security-update-for-sharepoint-server-2019-language-pack-july-14-2020

DB Version 16.0.10362.20025 (language dependent) 16.0.10363.12107 (language independent)

It is now possible to update task custom field values through the REST API.
Editing a project in Project Web App or approving status updates uses the Project Calculation Service (PCS). In some situations, PCS crashes when it closes a project. The crash details as seen when viewed in the Unified Logging Service (ULS) log (or in the Windows event logs) resembles the following:
"The worker encountered a very serious error and will shutdown. Exception code was: 0xc0000005 (EXCEPTION_ACCESS_VIOLATION)."

June 2020

https://support.microsoft.com/en-us/help/4484400/security-update-for-sharepoint-server-2019-june-9-2020

https://support.microsoft.com/en-us/help/4484404/june-9-2020-update-for-sharepoint-server-2019-language-pack-kb4484404

DB Version 16.0.10360.20000 (language dependent) 16.0.10361.12114 (language independent)

In the Google Chrome and Microsoft Edge Chromium browsers, when you leave pages such as the Project and Resource Center, changes that you made (such as adjusting column widths) are not saved.
Note For this fix to work, you have to first install Chrome or Chromium browser version 81 or a later version.
The Resource Request page may unexpectedly display engagements from other resources.
In the Google Chrome and Microsoft Edge Chromium browsers, even if you select Cancel in the Edit Resource page, the resources remain checked out.
Note For this fix to work, you have to install Chrome or Chromium browser version 81 or a later version.
Consider the following scenario:
- You create a user from Manage Users. You do not select the User can be assigned as a resource option.
- Later, you edit the user account and you enable the option.
- You go to the Resource Center and select Capacity Planning button or go to Capacity Planning page with the page URL.
  In this situation, a dialog box appears and states "There is no availability data for the resources you have selected. This commonly occurs for cost and material resources without enterprise resource calendars."

May 2020

https://support.microsoft.com/en-us/help/4484332/security-update-for-sharepoint-server-2019-may-12-2020

https://support.microsoft.com/en-us/help/4484331/may-12-2020-update-for-sharepoint-server-2019-language-pack-kb4484331

DB Version 16.0.10359.20000

No Project Server 2019 updates

April 2020

https://support.microsoft.com/en-us/help/4484292/security-update-for-sharepoint-server-2019-april-14

https://support.microsoft.com/en-us/help/4484291/security-update-for-sharepoint-server-2019-language-pack

DB Version 16.0.10358.20000

Querying for a task dependency through the client-side object model (CSOM) returns a non-elapsed LinkLagDuration string for elapsed values. For example, you have a dependency that says 2FS+1ed. Instead of returning the expected 1ed, it returns 3d.
When accessing certain projects through the client-side object model (CSOM) or REST, the process fails because of overflow in the Schedule Variance Percentage (SVP) or Cost Variance Percentage (CVP) fields.
Consider the following scenario:
- You have server event code on the publishing event that extracts data from a project through the client-side object model (CSOM).
- You open a project by using Project or Project Web App.
- You make changes in the project.
- You publish the project.

In this scenario, the publishing event code that reads the project data runs for more than a minute and then times out. Therefore, the event unexpectedly cancels the publishing job.

If you apply a filter to a Tasks list, you don't see the expected result for those items (which are on the second and subsequent pages).

March 2020

https://support.microsoft.com/en-us/help/4484271/security-update-for-sharepoint-server-2019-march-10

DB Version 16.0.10357.20002

After you edit a project in Project Web App, it may take a long time to save the project. This is especially true if there are many custom field values. This causes slower publishing, check-in jobs, and other related actions.
Editing a project in Project Web App or approving status updates uses the Project Calculation Service (PCS). In some situations, PCS crashes while it closes the given project. The crash detail is logged in the Unified Logging System (ULS) logs, and it resembles the following:
"The worker encountered a very serious error and will shut down. Exception code was: 0xc0000005 (EXCEPTION_ACCESS_VIOLATION)."
Consider the following scenario:
- You have an enterprise resource custom field.
- You edit a resource and assign a value to the field.
- You delete the enterprise resource field.
- You edit the resource, and save your changes.

In this scenario, the process fails, and you receive the following error message:
"Unknown error has occurred"

February 2020

https://support.microsoft.com/en-us/help/4484259/security-update-for-sharepoint-server-2019-february-11

https://support.microsoft.com/en-us/help/4484225/february-11-2020-update-for-sharepoint-server-2019-language-pack-kb448

DB Version 16.0.10355.20000

Adds support for the SameSite cookie attribute to remain compatible with changes in how web browsers such as Chrome handle cookies.

January 2020

https://support.microsoft.com/en-us/help/4484224/january-14-2020-update-for-sharepoint-server-2019-kb4484224

This update fixes the following issues in Project Server 2019:

Loading a timesheet takes a long time and may time out.
Resource calendars aren't updated correctly when a base calendar changes. This may cause the timephased actual work reported by a team member to appear on different days from where it was entered.
You are unable to set the assignment Actual Cost field either as a timephased or scalar value through the client-side object model (CSOM).

December 2019

https://support.microsoft.com/en-us/help/4484177/december-10-2019-update-for-sharepoint-server-2019-kb4484177

https://support.microsoft.com/en-us/help/4484176/december-10-2019-update-for-sharepoint-server-2019-language-pack-kb448

DB Version 16.0.10353.20001

This update fixes the following issues in Project Server 2019:

When a SharePoint update is applied and the SharePoint Products configuration wizard is run, the reporting association views are dropped but not re-created.
After you upgrade from Project Server 2010 to 2019, if you edit a project in PWA and delete an inactive task, after you save the project, you may be unable to reopen it.
You are unable to update and clear local Duration and Outline Code field lookup values through the client-side object model (CSOM).
Consider the following scenario:

You create a project with a single task and large number of resources.
You add all resources to the task.
You save and publish the project.
You edit the project in PWA.
You click the drop down for the Resource Names column.

In this case, you will see that some resources are no longer assigned to the task.

November 2019

https://support.microsoft.com/en-us/help/4484149/security-update-for-sharepoint-server-2019-language-pack-november-12

https://support.microsoft.com/en-us/help/4484142/security-update-for-sharepoint-server-2019-november-12-2019

DB Version 16.0.10352.20000

When the Schedule Variance Percentage (SVP) or Cost Variance Percentage (CVP) earned value becomes very large, an overflow condition occurs. This causes the client-side object model (CSOM) or REST calls that are made while accessing the project to fail. The SVP and CVP values now have a lower limit of -100% and upper limit of 100%.
After this update is installed, you can receive information about any type kind of completed queue jobs for a project when you use the new GetAll() method from a REST call.
Consider the following scenario:
- You create a new project in Project Web App.
- When the schedule project detail page appears, the Project Summary Task is visible.

In this situation, you cannot type in the Task Name field to create a new task.

Consider the following scenario:
- As a timesheet user, you open your timesheet.
- On an assignment that has no actual work, you enter actual work on a given date.
- You save the timesheet.
- You change your mind, and you remove the actual work that you previously entered.
- You send the timesheet or status update for approval.
- The status manager approves the update.
In this scenario, when the assignment is viewed in Project Professional, it has an actual start date set even though you removed the actual work in the timesheet, and this also removed the actual start date. This fix correctly removes the assignment's actual start date in this situation.

October 2019

https://support.microsoft.com/en-us/help/4484110/security-update-for-sharepoint-server-2019-october-8-2019

https://support.microsoft.com/en-us/help/4484109/october-8-2019-update-for-sharepoint-server-2019-language-pack-kb44841

DB Version - 16.0.10351.20000

When you select View Installed Updates in the Windows Control Panel, you see the most recently installed SharePoint Server 2019 Public Updates listed. However, the version number of these updates isn't displayed in the Version column. After you install this update, the version number of these updates will be displayed.
Makes changes to display the new Japanese era name for date format samples in Date Format in Project Web App (PWA) sites.
You can now update a task dependency lead and lag time by using the LinkLagDuration property through the client-side object model (CSOM). Similar to other duration properties (such as the Task.Duration property in the Task Object), it excepts either a string or an integer value. For example, either 1d or 480 is acceptable to indicate one day of work.
The CalendarException.RecurrenceWeek property returns wrong values for calendar exceptions through the client-side object model (CSOM).
When the Schedule Variance Percentage (SVP) earned value becomes very large, an overflow condition occurs. This may cause either abnormal SVP values within Project Web App (PWA) project views or the view may fail to load. The SVP value now has a lower limit of "-100%" and upper limit of "100%".

September 2019

https://support.microsoft.com/en-us/help/4475596/security-update-for-sharepoint-server-2019-september-10

https://support.microsoft.com/en-us/help/4464557/security-update-for-sharepoint-server-2019-language-pack

DB Version 16.0.10350.20000

Through the client-side object model (CSOM), the TaskLink ProjUid property for an external task returns the ID of its own project instead of the ID of the project that the task refers to. This update adds the ExternalProjectUid and ExternalTaskUid properties to the Task class to fix this issue.
Loading a timesheet is very slow and may take one minute or more.
Project Server Interface (PSI) API calls that require the permission of a farm administrator fail for users who are farm administrators but not server administrators.

August 2019

https://support.microsoft.com/en-us/help/4475555/security-update-for-sharepoint-server-2019

DB Version 16.0.10349.20000

Fix: When the Schedule Variance Percentage (SVP) earned value field becomes very large, an overflow condition occurs and prevents PWA project views from loading.
Fix: When you click the Export to Excel button to export data on pages such as from the Project Center, you receive the following error message:

Sorry, something went wrong. An unexpected error has occurred.

July 2019

https://support.microsoft.com/en-us/help/4475529/security-update-for-sharepoint-server-2019-july-9-2019

DB Version 16.0.10348.12104

Adds the ProjectIdMinDigit, ProjectIdSeed, ProjectIdPostfix and ProjectIdPrefix properties in the EnterpriseProjectTypeCreationInformation class. You can now use these properties to update the Project Identifier information of an enterprise project type (EPT) through the client-side object model (CSOM).
Adds the ProjectQueuePublishSummary method for the ProjectCollection class in the client-side object model (CSOM) so that project-level fields on a project can be published independently from the entire project. For example, if you use a workflow in your project creation process, you can use this new method to publish the stage summaries.
Updating a fixed duration task assignment from a timesheet may unexpectedly change the assignment’s finish date to an earlier date.

June 2019

https://support.microsoft.com/en-us/help/4475512/security-update-for-sharepoint-server-2019-june-11-2019

DB Version ?

Contains fixes for the following nonsecurity issues:

In some circumstances, if you delete a few views that are associated with custom fields that support multi-value selection from a lookup table in the database, and then you run the Repair-SPProjectWebInstance cmdlet, you find that the first view isn’t generated in the database.

May 2019

https://support.microsoft.com/en-us/help/4464556/description-of-the-security-update-for-sharepoint-server-2019-may-14

DB Version - 16.0.10345.12101

Contains the following improvements:

Adds support for the new Japanese era in the timeline portion of the Project Summary web part in Project 2019.
Adds the GraphicalIndicator property to the CustomField class in the Client-Side Object Model (CSOM). You can now set and get a Graphical Indicator for a custom field.

For the complete list of SharePoint fixes see the article above

April 2019

https://support.microsoft.com/en-us/help/4462221/april-9-2019-update-for-sharepoint-server-2019-language-pack-kb4462221

https://support.microsoft.com/en-us/help/4464518/description-of-the-security-update-for-sharepoint-server-2019-april-9

DB Version - 16.0.10343.20000

In an environment that uses the Japanese new era calendar, date formats that contain year aren't applied on the Timeline view for dates that occur after May 1, 2019.

For full details of the SharePoint Server 2019 fixes see the articles above.

March 2019

https://support.microsoft.com/en-us/help/4462199/description-of-the-security-update-for-sharepoint-server-2019-march-12

DB Version - 16.0.10342.12113

Contains the following improvement and fixes:

Adds support for the new Japan era in SharePoint Server 2019.
Editing a project-level custom field while on a project detail page (PDP) cuases lost task-level calculated custom field values if the field formula includes the task's Unique ID.
When you upload content to a document library, selecting a destination folder doesn't work. This issue occurs when you open the SharePoint site by using the Microsoft Edge browser.

February 2019

https://support.microsoft.com/en-us/help/4462170/february-12-2019-update-for-sharepoint-server-2019-language-pack-kb446

https://support.microsoft.com/en-us/help/4462171/february-12-2019-security-update-for-sharepoint-server-2019

DB Version - 16.0.10341.20000

his update adds the ability to change a task's duration type through the client-side object model (CSOM) after the task is created.
You can't set the description of a lookup table value to blank through the client-side object model (CSOM).
You can't get all the details of a dependency link, such as the lag duration and project UID properties, through the client-side object model (CSOM).

For full details of the SharePoint Server 2019 fixes see the articles above.

January 2019

https://support.microsoft.com/en-us/help/4461514/january-8-2019-update-for-sharepoint-server-2019-language-pack-kb44615

https://support.microsoft.com/en-us/help/4461634/description-of-the-security-update-for-sharepoint-server-2019-january

DB Version - 16.0.10340.12101

When the Missing server side dependencies health analyzer rule runs on a server that's not running the SPWebService service, an error message that states that some web parts are missing in the system is displayed in the health analysis report.

Note To fix the issue, you need to install both fixes together with this update.

For full details of the SharePoint Server 2019 fixes see the articles above.

December 2018

https://support.microsoft.com/en-us/help/4461548/descriptionofthesecurityupdateforsharepointserver2019december112018

DB Version - 16.0.10339.12102

For full details of the SharePoint Server 2019 fixes see the articles above.

November 2018

https://support.microsoft.com/en-us/help/4461513/description-of-the-security-update-for-sharepoint-server-2019-november

DB Version - 16.0.10338.12107

This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user opens a specially crafted Office file. To learn more about these vulnerabilities, see Microsoft Common Vulnerabilities and Exposures CVE-2018-8568 and Microsoft Common Vulnerabilities and Exposures CVE-2018-8572.

Note To apply this security update, you must have the release version of Microsoft SharePoint Server 2019 installed on the computer.

Where did that old MSDN/TechNet post go?

Brian Smith — Sun, 14 Feb 2021 02:27:08 GMT

You may be landing here on a redirect from our MSDN or TechNet blogs. Most of the content of the Project Support blog is here now, and some of the BriSmith MSDN blog is split between this blog, or the Project and Planner blogs in this community . If you search for the old document title you should find it - or in the migrated content we also show the original post date - which is in the full Url from MSDN/TechNet. In the unlikely event that the content you want didn't make the journey - please leave a comment and I'll see if I can find it!

Planner blog - https://techcommunity.microsoft.com/t5/Planner-Blog/bg-p/PlannerBlog

Project blog - https://techcommunity.microsoft.com/t5/Project-Blog/bg-p/ProjectBlog

Also you can look for some missing ones on my personal blog as I've added them as an archive of Project Support posts

Screenshot of new blog

All the 2010, 2013 and 2016 Project and Project Server Updates

Brian Smith — Wed, 14 Oct 2020 05:36:49 GMT

I'm moved over and updated the pages of Public Updates for each of the Products - some have had to be split due to post size limitations - all the pages are listed here!

Project Server 2019

https://techcommunity.microsoft.com/t5/project-support-blog/project-server-2019-public-updates/ba-p/627952

Project 2016

https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-2016-Updates-RTM-to-December-2016/ba-p/390785

https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-2016-Public-Updates-January-2017-to-date/ba-p/387755

Project Server 2016

https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-Server-2016-Public-Updates/ba-p/387845

Project 2013

https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-2013-Cumulative-Update-RTM-to-the-end-of-2015/ba-p/387488

https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-2013-Cumulative-Updates-2016-to-Date/ba-p/387508

Project Server 2013

https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-Server-2013-Cumulative-Updates-RTM-to-Dec-2015/ba-p/387372

https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-Server-2013-Cumulative-Updates-from-2016-to-Date/ba-p/387411

Project 2010

https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-2010-Cumulative-Updates/ba-p/386863

Project Server 2010

https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-Server-2010-Cumulative-Updates-RTM-to-June-2012/ba-p/387714

https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-Server-2010-Cumulative-Updates-from-August-2012-to-date/ba-p/387671

Project 2016 Updates (RTM to December 2016)

Brian Smith — Fri, 29 Mar 2019 13:31:54 GMT

December 2016

December 6, 2016, update for Project 2016 (KB3127994)

https://support.microsoft.com/en-us/kb/3127994

WinProj.exe version: 16.0.4471.1000

Fixes the following issues:

Updates the translation of the check in confirm dialog box in Ukrainian when you close a changed project.
Fixes the following issues:

When you view a custom field lookup table within the Project Information dialog box, you may find that some expected values don't appear.
When you open and save a Project 2003 project to a server, resource enterprise custom field values may be lost.
Consider the following scenario:

In a project, you go to the Resource Sheet view where you have resources defined.
You insert one of the local Outline Code fields.
From the outline code field on a resource or on resources, you select a value from the values that you have defined.
You save the project to Project Server.
Later, you set the outline code values to something else.
You save, close and reopen the project.

In this situation, the new values that you set into the outline code field on the resources are lost.

After you save a baseline, timephased work and cost values aren't displayed as expected. For example, you may see work and cost during periods where no work or cost exists.
When you open certain XML files in Project, assignment delay is ignored. Therefore, the start and finish of some assignments on a task may be different. This can also cause the given task to schedule differently.
In a master project, when you view the finish date of an inserted project summary task (this is the task that represents a subproject), you may find that it doesn't reflect the latest finish date of the tasks in the subproject.

To fix the following issue, install December 6, 2016, update for Office 2016 (KB3115278).

Consider the following scenario:

You create a new report. For example, you create a new report that's based on the default Project Overview report.
In a field list, you add more than one level of sorting.
You save your project.
You open your project.

In this situation, all the elements on the report are lost and all that you see is a blank screen.

November 2016

November 1, 2016, update for Project 2016 (KB3127960)

https://support.microsoft.com/en-us/kb/3127960

WinProj.exe version: 16.0.4456.1003

Fixes the following issues:

In some cases, you can't open a saved project that you worked with previously. Instead, you may see the file open progress indicator appears as if the project is opening, but the project doesn't open.
Assume that you start Project Professional and connect to a server, and that you have selected to load summary resource assignments. In this situation, when you go to a resource usage view, a given resource that should be shown as overallocated appears to be underallocated during a certain period, for example, daily.
When you open certain XML files, the start date of some assignments may be ignored, which means tasks are scheduled incorrectly. You may also notice that the assignment on a task has an actual start date yet the task doesn't.
When you level a project on a week-by-week basis, Project may freeze. After the leveling is complete, you may find that the tasks are scheduled out to the end of time, which is December 31, 2149.
When you use the JavaScript Office API against Project 2016, querying task start dates and finish dates always returns the automatically scheduled start dates and finish dates instead of the manually scheduled start dates and finish dates.
When you open a project from a SharePoint site and then click the Edit Project button from the banner, you may see an error message that resembles the following:

You have made changes to '<project name>'.
Another user has also made changes. What would you like to do?
Click Discard to discard your changes and edit the latest version.
Click Save as to save your changes to a different file and open the latest version.

This issue occurs with projects that were stored in Project Server.

After you save and publish a project plan, upon close and check it in, you receive the following error message:

The following job failed to complete.
Job Type: Checking
Error ID: 9000(0x2328)
Could not checkin project. Please contact your system administrator to force checkin this project.

When you open an XML file, resource assignments may have trailing zero work values in a usage view. For example, the work contour may resemble the following:

8h, 8h, 2h, 4h, 0h, 0h, 0h

It should appear as the following:

8h, 8h, 2h, 4h

Consider the following scenario:

You have a master project.
You have several sub projects in the master project.
The sub projects are set to read-only.
You open the master project.
You select the Edit Project button from the banner.

In this situation, the sub projects are opened with the read/write permission even though they are set to read-only.

Assume that you change the name of an enterprise calendar. When you open projects that use that calendar, Project 2016 may crash.
Assume that have a task that has a duration of four elapsed months or longer. When you save the task to the XML file format, Project 2016 freezes.
When you open certain XML files, you receive the following error message:

The actual finish date is before some of the previously entered timephased actual work values. If you continue with this operation, Project will truncate some of the previously entered timephased actual work values.

Additionally, when you open some XML files, you may find that the Gantt bars for fixed or elapsed duration tasks show an unexpected trailing split.

If an inserted subproject has a task that is 100% complete and has an ALAP constraint, the summary tasks within the subproject may have an incorrectly calculated start, finish, and duration.
Assume that a project contains a local resource whose name is the same as an enterprise resource, and the local resource is assigned to an incomplete task and a task that is 100% complete. When you save the project on a server, the local resource is assigned to the completed task, and the enterprise resource is assigned to the incomplete task.

October 2016

October 11, 2016, update for Project 2016 (KB3118342)

https://support.microsoft.com/en-us/kb/3118342

16.0.4432.1003

Fixes the following issues:

When you open projects from an XML file and some tasks in the file are defined as manually scheduled, the duration of these tasks may change to the default of 1d instead of the value that's defined in the file.
If a task is updated to be 100% complete and the cost resource for the task is more than $83.33, the duration is reset unexpectedly.
Consider the following scenario:

You have an enterprise calendar.
You set the enterprise calendar as the base calendar for some projects in the project server.
In preparation to delete the enterprise calendar, you go to the projects that are using the calendar and select a different calendar for them.
In Project Web App settings, you go to the Enterprise Calendars page and try to delete the calendar.

In this situation, you can't delete the calendar because you are told that it is in use. After you install this update, you can now go to the projects in which the calendar is used, and use the organizer to delete it. After the calendar is deleted from the individual project that uses it, you will then be able to go to PWA and delete the calendar.

Consider the following scenario:

You have a master project in which you have at least one sub project.
The master and sub projects have been saved to Project Server.
You unlink the sub project from the master project.
You save the sub project back to Project Server.

In this situation, the assignments in the sub project are lost.

Consider the following scenario:

You have a task in a project that has a resource assigned.
The resource assignment has 80h of work.
The resource assignment has split work wherein it works the first week, and it has a zero work split for the second week and finally has work on the last week.
The assignment is 50% complete and the first week is completed.

On the Task Usage view, the actual work details of the assignment resembles the following:

8h, 8h, 8h, 8h, 8h, 0h, 0h, 0h, 0h, 0h

You view the stop date and also notice that it's the same as the resume date. After you install the update, the trailing zero actual work values no longer appear and the stop date corresponds to where the last timephased actual work value that's more than zero is ended, and it's not the resume date which starts at the beginning of the third week.

When you publish a project from Project 2016 to PWA, resource enterprise custom field values may be lost.
When you publish a project to Project Server, formulas associated with a custom field that use the Current Date function will display the correct values. However, the published data for the same field may display a different value. For example, you have a custom task field with a formula that displays the current date. Then, you publish a project and you see the expected values on tasks in the custom field in PWA. Two days later, you open the same project in Project 2016, you see the correct values and publish the project. However, when you see the published values within the custom field in PWA, you see the same value from two days earlier.
When status updates are applied, trailing time phased actual work values are created. This causes finish dates are later than expected.

September 2016

https://support.microsoft.com/en-us/kb/3118266

16.0.4432.1000 (Remember - you need to look at winproj.exe, we don't show the specific Project version under File, Account - just the MSO version).

Assume that you create an .mpp file in a SharePoint document library and then synchronize the library to the local computer by using OneDrive, and the file path is longer than 130 characters. In this situation, the .mpp file can’t be opened in Project 2016.
Assume that you create a project from a template in Project Web App. When you try to enter timephased cost date or actual cost date for a cost resource in Project 2016, the values that you enter can't be applied, and Project 2016 may crash.
When you merge or append a tab-delimited text document into an existing project, merged changes can't be saved in Project 2016.

August 2016

https://support.microsoft.com/en-us/kb/3115424

16.0.4417.1000

Translates some terms in multiple languages to make sure that the meaning is accurate.
When you try to import and merge an XML format into an existing project, and the XML project has tasks that have dependencies among them, Project 2016 may crash.
Consider the following scenario:

You have at least two projects and the projects have task-level cross project dependencies.
The projects are included in a master project.
The master project is open and you are looking at the Gantt view.
In this situation, you experience the following issues:

The dependency lines between the tasks in the inserted projects aren't displayed.
Dragging and dropping to create links between tasks that are in a sub-project or across sub-projects doesn't create a link as expected.
The Link the selected tasks and Unlink tasks buttons in the schedule grouping of the Task ribbon don't function on cross project tasks.

When you try to edit or create a new Network Diagram data template, you receive the following error message:

The field "<Unavailable>" does not exist. Click a field name in the list, and then press Enter.

When you work in a usage view within the context of a master, Project 2016 may crash. This issue may occur when you level resources or delete tasks.
Assume that you have a Project .MPP file that's stored in a SharePoint document library. When you click the file name, the project opens but you don't see a banner that offers you the ability to edit or check out the project. Instead, the project may keep in a read-only state and you can't save or check in changes.
When you set the date of a task to a value that's greater than the year 2099 in Project 2016, the date is displayed incorrectly in the date picker control. For example, if you have tasks that are scheduled on May 12, 2110, the year is displayed as 2010 in the date picker.
In the printout or print preview of a Gantt chart in Project 2016, the Resource Names column displays the same information as the Predecessors column. This issue occurs if you set Windows Regional Settings to a right-to-left language.

July 2016

https://support.microsoft.com/en-us/kb/3115284

16.0.4405.1000

Fixes the following issues:

When you open and then save a project file to a Project server, the task finish date and duration are changed. This issue occurs if the assignment finish date doesn't match the task finish date. This can be the case with fixed duration tasks.
The Last Modified and Last Published timestamps are not converted to your timezone.
When you save a project, some baseline information may be lost if you don't have the permission to save a baseline.
When you save a project for sharing, and then save it back to the server, the baseline data is deleted from the project if you don't have the Save Protected Baseline permission.
When you add a resource or do a Save As operation to the MPP format on a project that's connected to Project Web App, Project 2016 may crash.
When you go to a view such as the Gantt chart and then click the auto filter on a date field such as the Start field, dates that are later than 2099 aren't displayed. Therefore, you can't filter days that are later than 2099 by using the auto filter.
Assume that you set the primary language to simplified Chinese and the secondary language to English. When you try to synchronize projects with a SharePoint task list, the process fails.
If you set % Work Complete progress on a summary task in Project 2016, work and actual work may incorrectly be added to subtasks that don't have a resource assigned.
Assume that you select to load summary resource assignments to start Project 2016. When you go to a Resource Usage view and scroll through the resource, Project 2016 may crash. This issue occurs after you install March 8, 2016, update for Project 2016 (KB3114865).

June 2016

https://support.microsoft.com/en-us/kb/3115149

16.0.4393.1000

Updates the translation in the project check in dialog box for French to make sure that the meaning is accurate.
When you try to unlink a subproject from a master project that has a custom field with a lookup table defined, Project 2016 crashes if the subproject doesn't have the same lookup table definition as in the master project yet the custom field has values.
When you try to open a large project in Project 2016, you receive the following error message:

This operation cannot be completed because the source file contains invalid project data or the total number of rows would exceed the limit of 1,048,000 rows in a project. Validate the data in the source file, insert fewer rows, delete some rows, or consider dividing your project into subprojects to provide more space for tasks and resources.

This issue occurs if the assignment maximum unique ID of 1048576 is exceeded.

Project 2016 may freeze when you print or preview certain projects.
Consider this scenario:

You have an enterprise resource custom field.
The field has a lookup table applied to it, and multiple values can be selected.
You have a resource that has a value in the field that's longer than 255 characters.
You open a project in Project Professional that uses this resource.

In this situation, you receive the following error message:

The value you entered does not exist in the lookup table of this code. All values must be predefined in the code lookup table. Contact your server administrator to get new values added.

You also find that the list of values in the field is truncated or has disappeared completely.

When you try to print a specified number of pages and select to have the timescale fit to the end of the page, the timescale doesn't horizontally fill the entire page.
Assume that you change a date by using the date picker, and the date is not in the current year. In this situation, the day and month are changed but the year isn't changed. This issue occurs when the date format is set to 4/W04.
When you save subprojects in the context of a master project, Project 2016 may crash. This issue may occur if the subprojects have Visual Basic Applications code in them.
When you set a finish date for a fixed duration task in which assignments on the task have actual work entered on non-working times, the finish date is changed to a different date from what you entered, and the assignment finish date is changed to the task finish date even though the assignment doesn't share the task's finish date.
When you open a project that has many cross project links in Project 2016, Project 2016 may freeze and eventually crashes when the computer runs out of memory.
Assume that you open a master project that has many subprojects in Project 2016. When you press ESC to cancel the loading, Project 2016 may crash.
Consider the following scenario:

You have a task in your project.
You have two resources that are assigned to the task.
On one of the assignments, delay has been added.
You publish the project to a server where protected actual work is enabled.
The resource who owns the assignment where delay doesn't exist reports work and the status update is applied to the task. The other assignment still has no actual work.
As the project manager, you set the work value to zero on the assignment that has no actual work.

In this situation, the actual start and actual finish dates are set on the assignment even though these dates weren't reported by the team member. Later, when the project manager adds work back to the assignment and tries to reschedule it, the operation fails because Project tells that the change would change work entered by a team member.

Project 2016 may freeze when you create a recurring task.
If you try to reset the work breakdown structure (WBS) for a selection of tasks, the entire project is updated instead.
When you scale a printout to fit to one page in Project 2016, the printed output is unreadable.
When you submit a Physical % Complete value for a task that is synchronized to a SharePoint task list in Project 2016, an incorrect value is displayed. For example, the value of 100% appears as 1000%.
When you open projects, Project 2016 may crash. This issue occurs for some projects in which certain calendars in that project were duplicated.
Consider this scenario:

A task has an eight-hour assignment and it has been published to a team member.
The team member opens their timesheet and enters multiple time-phased actual work values. For example, 8h on one day and 3h on a second day.
The team member changes their mind and zeros out the last time-phased value. In this case, the 3h turns to 0h.
The team member submits their timesheet and the status manager approves the update which is then applied to the project.

When the task and assignment are viewed in Project Professional, the task ends on the second day and the assignment ends on the first day. The expectation is that the task ends at the same time as the assignment.

The Office.ProjectProjectFields.ProjectServerUrl property that is used in Office Application solutions returns an integer instead of a URL string.
When you use the Project Import Wizard, you receive an incorrect merge result if the merge key is set to a custom field.
When you set the % Work Complete value for summary tasks in Project 2016, Project 2016 may crash. This issue occurs if Project is connected to a Project server where the Only allow task updates via Tasks and Timesheets setting is enabled.
When you synchronize a project in Microsoft Project 2016 to a SharePoint task list, some assignment data is lost if there are more than 50 rows.Note To fix this issue, you need to install June 7, 2016, update for Office 2016 (KB3114709).

May 2016

https://support.microsoft.com/en-us/kb/3115105

16.0.4378.1000

A better translation of the following messages is now available for the Japanese language. These messages appear when a user tries to edit the name of an enterprise resource within their project:

Changes to enterprise resources will be lost.
You can modify an enterprise resource in a project for modeling purposes and publishing the project will include any changes. Your changes will be overwritten when the project is next opened.

A user with security permission can modify the attributes of this resource by checking out the resource with the Open Enterprise Resource Pool command.

Fixes the following issues:

Assume that you use a task template that has cost resources assigned to create a project in Project Web App. When you open the project in Project 2016, Project 2016 crashes.
In some cases, a task's % Complete displays 99% even though the % Work Complete on all the assignments on the task shows 100%.
When you apply a group to a checked-out enterprise view in Project 2016, Project 2016 may crash.
Consider the following scenario:

You have an enterprise resource that's assigned to a project.
You change the booking type for the resource.
You save and then open the project again.

In this situation, the booking type property isn't saved.

The ZoomTimescale Visual Basic Applications method ignores the duration parameter for the Timeline view in Project 2016. Therefore, you can't force the timeline view to zoom to a specific range.
Consider the following scenario:

A team member is assigned to a task that begins on Monday.
The task is published to the team member.
The team member opens their timesheet and enters actual work on Wednesday.
The team member submits their timesheet.
The project manager approves the status update from the team member.

In this situation, the task still shows that it begins on Monday instead of Wednesday.

When a summary task is viewed in the task inspector, the subtasks aren't listed.
Consider the following scenario:

A user enters time phased actual work on an assignment and submits the work for approval.
The status manager approves the update.
The user changes the assignment start date and then submits the change.
The status manager approves the update.

In this scenario, the time phased actual work may move to another date.

If you use the Assign Resources dialog box to replace one resource with another resource, the total work value displayed in the Resource Usage view isn't always updated correctly.
Setting actual cost for cost assignments on tasks doesn't always calculate the correct progress as expected. This issue occurs when the assignment is the only resource on the task.
When you delete a resource from a split task, the split task is deleted unexpectedly.
When you import a project from an XML file, timephased baseline work isn't imported correctly. For example, on an assignment, the baseline cost values over a 10-day period are as follows:

2h, 3h, 4h, 5h, 6h, 8h, 8h, 8h, 8h, 8h.

When it's imported, the values change to 2h, 6h, 6h, 6h, 6h, 6h, 6h, 6h, 6h.

April 2016

https://support.microsoft.com/en-us/kb/3114973

16.0.4366.1000

After you apply status updates to project schedules, the actual work contours on some assignments unexpectedly display zero for actual work values in various time periods.
When you try to update budget costs on resources in Project 2016, Project 2016 may crash.
When you use an auto filter on a text type field, such as the task name, and the field contains many varied values, Project 2016 may crash.
Assume that you add the compliant field to a view and find something isn't compliant. When you make the item compliant, the field isn't updated until you leave the view and then come back again.
If you have the option to clear leveling values before leveling or you click the Clear Leveling button within the Resource Leveling dialog box, it doesn't always work correctly. Instead, tasks may be leveled to unexpected dates or values may still be found in the Leveling Delay field.
You can't create a project from a SharePoint task list if the list has data validation rules set.
When a resource is overallocated by a combination of actual work and remaining work, the work doesn't appear in red (overallocated) in that period when it's leveled on a day-by-day basis.
Microsoft Project doesn't always calculate the finish dates of some tasks that causes them to finish later than expected. This can occur in a scheduled from finish project where implied dependencies from a summary task to the sub tasks aren't always respected.
Assume that you have a summary task that contains one or more subtasks. Then, you make the summary task become a non-summary task either by outdenting all subtasks or by deleting all subtasks. In this scenario, the internal property on the task that specifies the duration format (minutes, hours, days, weeks, and months) may not be set correctly. Therefore, when you publish the project, the reporting data is inaccurate, and the duration of the given task isn't correct.
When you open a master project that has cross project links, Project 2016 may crash.
When you try to connect to a Project Web App instance in Project 2016 on a computer in which you have not recently connected to the PWA instance, the connection may fail.
When you select multiple tasks and try to replace a resource, the replace action doesn't work if the initial resource that you are replacing isn't assigned to all the selected tasks.

March 2016

https://support.microsoft.com/en-us/kb/3114865

16.0.4351.1000

When you merge an Excel workbook into an existing project where there's more than one assignment on a given task, only the actual work on the first assignment is updated.
When you use Microsoft Visual Basic for Applications (VBA) macros to edit project data within the Project.BeforeSave event handler, the edits to the project may not be saved if the project is saved to Project Server.
After status updates are accepted and applied to tasks in a project, the total actual work on the assignments may become larger, and the new actual work appears in time periods where the user didn't report it. For example, you report 8h on Monday and 3h on Tuesday. When you view the assignment in the project after the update is applied, besides the 8h on Monday and 3h on Tuesday, you may also see 8h on Thursday and Friday.
You can't remove remaining work from a manually scheduled task in Project 2016 when the task is published to Project Server. This issue occurs when the Only allow task updates via Tasks and Timesheets task settings and display options are enabled.
After you level resources by using the week-by-week or month-by-month basis in Project 2016, the resources remain overallocated.
When you use Project 2016 with certain Windows region date and time formats (for example, Spanish (Mexico)), baseline bars aren't displayed in the Gantt chart.
When you apply a grouping to a task type view, baseline finish type fields may not show the expected value on the grouping summary row tasks. Instead of showing the latest finish date as expected, the field shows Not Available if at least one of the grouped tasks doesn't have a baseline finish date.
Consider the following scenario:

A user enters time phased actual work on an assignment and submits the work for approval.
The status manager approves the update.
The user changes the assignment start date and then submits the change.
The status manager approves the update.

In this scenario, the time phased actual work may move to another date.

When you open a project from a server, it may take a long time if the project doesn't exist in the user's local active cache.
Consider the following scenario:

You add some Visual Basic Applications (VBA) code to a project in Project Professional 2016.
You save and publish the project to Project Server, and then you check in the project.
You edit the project on the schedule project detail page in Project Server.
You change and save the project.
You open the project again in Project Professional 2016.

In this situation, the VBA code is missing.

Assume that you have a series of related tasks (they have dependencies between them) and you now make one of the tasks inactive. In this situation, the successor tasks to the inactive task may be scheduled later than expected.
Macros that exist in the local global template don't work if they are invoked from the ribbon. This issue occurs when Project 2016 is connected to Project Server.
When a plan is opened for edit in Project 2016 or in Project Web App, in some cases, additional actual work may appear on an assignment.
If you save an incremental baseline that rolls up baseline values from a task to summary tasks, the timephased baseline values of the summary tasks are deleted from the dbo.MSP_EpmTaskBaselineByDay table in the reporting database.
If you update a sheet view to show the notes field, you may see redraw issues.
If you have a project that's saved to Project Server, you can't access project level properties.
When Project 2016 connects to Project Server, Project 2016 may crash if there are enterprise templates but you don't have the permission to access them.
It may take a long time to open multiple projects from Project Server in Project 2016.
You can't publish a project in Project Web App and receive an error message that looks something like the following:

Cannot insert duplicate key in object 'pub.MSP_PROJECT_RESOURCES'

It takes a long time to close and check-in a master project if Summary Resource Assignments (SRA) are loaded.
When you print a timeline in Project 2016, the last letter can sometimes be wrapped to the next line.
If you delete data by using the delete or backspace key in Project 2016, the BeforeTaskChange, BeforeResourceChange, and BeforeAssignmentChange events are not triggered.
When you open a Project file from a SharePoint document library, the file is sometimes opened as read-only when it should be read and write. In other cases, the project is sometimes opened as read and write but you can't save changes.Note To fix this issue, you also need to install March 8, 2016, update for Office 2016 (KB3114857).
After you set the Default Assignment Owner field for an enterprise resource and then create a project that uses the resource, the Default Assignment Owner field is blank.
If you enable the Only allow task updates via Tasks and Timesheets option, you can't set tasks to 100% complete if the task has an assignment with zero work.
When you level resources for projects in Project 2016, Project 2016 may crash.
When you select to merge data from Excel and use the task name as the key in Project 2016, you receive an error message.

February 2016

https://support.microsoft.com/en-us/kb/3114714

16.0.4339.1000

Enables add-in developer to receive a list of API requirement sets.
Fixes the following issues:

When you try to import an Excel workbook into a project in Project 2016, some assignment information is lost.
When you try to save a project from an earlier version of Project Server in Project 2016, you receive the following error message:

Error 9000
Save job cancelled in the queue: Root element is missing.

If you save a project as an .xml file in Project 2016, custom calendar information may not be saved. Therefore, when you open the .xml file, the calendar information is not found.
When you open the Assign Resources dialog box in Project Standard 2016, Project Standard 2016 may crash.
Assume that you display the Hyperlink field in Project Professional 2016. On a task, you enter an address in the Hyperlink field to a document that's stored on a SharePoint site, and then you click the link. Sometimes in this situation, the document doesn't open, and you're redirected to the root site where the document is stored.
When you open an XML file and select the New project option, it's much slower than merging the XML file into an existing or blank project.
When you import timephased data by using XML files in Project 2016, the <WorkContour> tags are ignored. This issue occurs when the timephased actual work values exist but the remaining work timephased values aren't complete in the XML file.
When you open a SharePoint task list in Project 2016 and close it without saving, the %Complete fields of tasks are updated to incorrect values.
When you start a task before the project start date, certain time scale labels in a Gantt view such as those that work from a project's start, for example, the "W1, W2, W3, W4… (From Start)" label, show the week starting at the beginning of the task instead of at the beginning of the project.
In some cases, the font control shown on the Tasks tab in the ribbon within the Font group is empty and the font size is 0. When you try to select a font or size, Project 2016 may crash.
When you try to print preview or pint the Team Planner view of a project in Project 2016, Project 2016 may crash or the view isn't displayed correctly. This issue occurs if the project is connected to a resource pool that has more than 20 resources.
When you try to save a project to the Project 2007 format in Project 2016, Project 2016 crashes. This issue occurs if the project has a table defined, and the Lock first column option is enabled in the table and the locked column has a title associated with it.
Consider the following scenario:

A project is displayed in a time scaled view, such as the Gantt Chart view, in Project 2016.
The timescale is formatted to display either years or half years on the top and a minor timescale of quarters or less on the bottom.

In this situation, the tick marks of the yearly or half-yearly timescale don't match with the minor timescale. For example, the year starts from December instead of January.

When you save a password protected file by using the Save As function in Project 2016, the file may become corrupted and then can't be opened.
When you scroll horizontally across the timescale in a Gantt type view, the nonworking time shading might not be displayed correctly. This issue occurs if you have chosen to display the shading in front of the bars.
When you import data from an Excel workbook in Project 2016, text data that is mapped into text type fields is truncated to 128 characters. For example, a task name is truncated.

January 2016

https://support.microsoft.com/en-us/kb/3114538

16.0.4324.1000

Some additional properties on existing Visual Basic Application methods were added. However, in some cases, their inclusion breaks backwards compatibility with macros from earlier versions.

December 2015

https://support.microsoft.com/en-us/kb/3114393

16.0.4312.1000

In some cases, when you save a project to Project Server, you receive a 9000 error code.

November 2015

https://support.microsoft.com/en-us/kb/3108456

16.0.4266.1001

10/22/2015 Initial Release

Project Server 2013 - Which Public Update do you have? At least April 2018 I hope!

Brian Smith — Tue, 26 Mar 2019 16:06:01 GMT

As we no longer have Service Packs but just regular Public Updates the servicing model changed for various products - including SharePoint and Project Server. If you are still running Project Server 2013 then you should already know you are out of mainstream support - but next month sees an important date - 4/10/2019 - at which point you need to have at least the April 2018 Public Update to be supported at all. https://docs.microsoft.com/en-us/SharePoint/product-servicing-policy/updated-product-servicing-policy-for-sharepoint-2013

All updates for SharePoint/Project Server 2013 can be found at https://docs.microsoft.com/en-us/officeupdates/sharepoint-updates Please choose the most recent available rather than April 2018 - there have been quite a few updates since then!

Project Server 2016 Public Updates

Brian Smith — Fri, 12 Feb 2021 14:53:14 GMT

This page lists the updates for Project Server 2016. Initial release was 1/5/2016 and the DB Version was 16.0.4327.1000

February 2021

https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-sharepoint-enterprise-server-2016-february-9-2021-kb4493195-bb99570c-8cb0-c006-17b9-217dfeb560ee

DB Version 16.0.5122.1000

This update also contains a fix for the following nonsecurity issue in Project Server 2016:

No error message prompt is seen when a duplicated view is created in Project Web App.
The start/finish date for a task is wrong after the task's assignment work is increased to > 0 and where the task is a milestone (duration is 0). This problem occurs after you install KB 4486753.

January 2021

https://support.microsoft.com/en-gb/help/4493163/security-update-for-sharepoint-enterprise-server-2016-jan-12-2021
https://support.microsoft.com/en-gb/help/4493167/security-update-for-sharepoint-enterprise-server-2016-jan-12-2020

DB Version 16.0.5110.1000

This update also contains a fix for the following nonsecurity issue in Project Server 2016:

If you delete many thousands of timesheets, the process might be slow.

December 2020

https://support.microsoft.com/en-nz/help/4486753/security-update-for-sharepoint-enterprise-server-2016-dec-8-2020
https://support.microsoft.com/en-nz/help/4486721/security-update-for-sharepoint-enterprise-server-2016-dec-8-2020

DB Version 16.0.5095.1000

This security update also fixes the following issues in Project Server 2016:

Improves performance on timesheet actions, such as saving and submitting.
Fix: When a cost resource is assigned to a milestone task and the project is scheduled through a REST or client-side object model (CSOM) call, the calculation fails and generates an error message that includes the text, "Cannot extend beyond minimum date."

November 2020

https://support.microsoft.com/en-nz/help/4486717/security-update-for-sharepoint-server-2016-nov-10-2020

DB Version 16.0.5083.1000

This security update also fixes the following issues in Project Server 2016:

When timesheets are submitted, the "Reporting (Timesheet Save)" queue job is created. However, this job may run very slowly. This creates a backup of queue jobs and causes other slow performance problems.
Project Web App instances that have many timesheets or timesheet views may experience a time-out when you create timesheet views or modify existing timesheet views. This can prevent you from creating timesheets or opening existing timesheets.

October 2020

https://support.microsoft.com/en-us/help/4486677/security-update-for-sharepoint-server-2016-october-13-2020

https://support.microsoft.com/en-ie/help/4486681/october-13-2020-update-for-sharepoint-enterprise-server-2016-kb4486681

DB Version 16.0.5071.1000

This security update contains fixes for the following issues in Project Server 2016:

Opening the approvals page or submitting timesheets is very slow.
Sometimes, when you open a project, the % Complete value on a Fixed Duration task that's 100 percent complete changes to a lesser value.

September 2020

https://support.microsoft.com/en-us/help/4484506/security-update-for-sharepoint-server-2016-sept-8-2020

https://support.microsoft.com/en-us/help/4484512/security-update-for-sharepoint-server-2016-sept-8-2020

No updates for Project Server 2016

August 2020

https://support.microsoft.com/en-us/help/4484473/security-update-for-sharepoint-server-2016-august-11-2020

https://support.microsoft.com/en-us/help/4484476/security-update-for-sharepoint-enterprise-server-2016-august-11-2020

DB Version 16.0.5044.1001

This security update contains a fix for the following nonsecurity issue in Project Server 2016:

Buttons on the Tasks ribbon tab are disabled for the tasks that are listed beyond the first page.

July 2020

https://support.microsoft.com/en-us/help/4484440/security-update-for-sharepoint-server-2016-july-14-2020

https://support.microsoft.com/en-us/help/4484436/security-update-for-sharepoint-server-2016-july-14-2020

DB Version 16.0.5032.1001

This security update contains fixes for the following nonsecurity issues in Project Server 2016:

When you use either the Google Chrome or Microsoft Edge Chromium browser, even if you select Cancel in the Edit Resource or in Enterprise Custom Fields and Lookup Tables pages, the resource, enterprise field or lookup table remains checked out. For this fix to work, you have to install Chrome or Chromium browser version 81 or later.
When you use either the Google Chrome or Microsoft Edge Chromium browser, if you change a View setting such as a column width or order, the changes do not persist if the view, filter, or grouping is applied to pages such as the Project Center, Resource Center, Approvals, Tasks, or Timesheets. For example, after you change View from Summary to Cost, and then you refresh the page, the View value remains as Summary. For this fix to work, you have to install the Chrome or Chromium browser version 81 or later.

June 2020

https://support.microsoft.com/en-us/help/4484402/security-update-for-sharepoint-server-2016-june-9-2020

https://support.microsoft.com/en-us/help/4484344/june-9-2020-update-for-sharepoint-enterprise-server-2016-kb4484344

No updates for Project Server 2016

May 2020

https://support.microsoft.com/en-us/help/4484336/security-update-for-sharepoint-server-2016-may-12-2020

No updates for Project Server 2016

April 2020

https://support.microsoft.com/en-us/help/4484299/security-update-for-sharepoint-server-2016-april-14-2020

https://support.microsoft.com/en-us/help/4484301/security-update-for-sharepoint-server-2016-april-14-2020

No updates for Project Server 2016

March 2020

https://support.microsoft.com/en-us/help/4484272/security-update-for-sharepoint-server-2016-march-10-2020

https://support.microsoft.com/en-us/help/4484275/security-update-for-sharepoint-server-2016-march-10-2020

DB Version 16.0.4978.1000

This security update contains fixes for the following nonsecurity issues in Project Server 2016:

In Project Web App (PWA), you can't edit in a lookup table's Value and Description columns while you use the Chrome browser.
You edit a resource in Project Web App and use the Chrome browser. In this situation, although initials may exist for a work resource that's tied to a Windows user account, the Initials field isn't populated and appears blank. Therefore, if the resource is saved, the blank initials are saved over the correct initials.
You can't navigate through the tables on the Approvals and Resource pages by using a keyboard.

February 2020

https://support.microsoft.com/en-us/help/4484255/security-update-for-sharepoint-enterprise-server-2016-february-11

https://support.microsoft.com/en-us/help/4484257/february-11-2020-update-for-sharepoint-enterprise-server-2016-kb448425

DB Version 16.0.4966.1000

This security update contains fixes for the following nonsecurity issues in Project Server 2016:

You receive the following error message when you save or submit a timesheet that has has a newly locked task:

"An error occurred while communicating with the server. Check connectivity with your administrator to determine whether further action is necessary."

Consider the following scenario:
- You have server event code on the publishing event that extracts data from a project through the client-side object model (CSOM).
- You open a project by using Project or Project Web App.
- You make changes in the project.
- You publish the project.

In this scenario, the publishing event code that reads the project data runs for more than a minute and then times out. As a result, the event unexpectedly cancels the publishing job.

January 2020

https://support.microsoft.com/en-us/help/4484220/january-14-2020-update-for-sharepoint-enterprise-server-2016-kb4484220

https://support.microsoft.com/en-us/help/4484215/january-14-2020-update-for-sharepoint-enterprise-server-2016-kb4484215

This update also fixes the following issues in Project Server 2016:

Fixes performance problems when you perform actions such as connecting Project to the server, trying to see a list of projects from the server, going to the Project Center page and so on.
When the Schedule Variance Percentage (SVP) or Cost Variance Percentage (CVP) earned value becomes very large, this causes an overflow condition. It causes the client-side object model (CSOM) or REST calls to fail when you access the project. The SVP and CVP values now have a lower limit of "-100%" and upper limit of "100%".

December 2019

https://support.microsoft.com/en-us/help/4484178/december-10-2019-update-for-sharepoint-enterprise-server-2016-kb448417

https://support.microsoft.com/en-us/help/4484181/december-10-2019-update-for-sharepoint-enterprise-server-2016-kb448418

DB Version 16.0.4939.1000

This update contains the following improvement and fix in Project Server 2016:

Adds the ProjectLastPublishedDate field to Project Server OData Projects entity so you can, for example, do a REST call to get a project's last published data.
You are unable to update and clear local Duration and Outline Code field lookup values through the client-side object model (CSOM).

November 2019

https://support.microsoft.com/en-us/help/4484147/november-12-2019-update-for-sharepoint-enterprise-server-2016-kb448414

DB Version 16.0.4927.1000

This security update contains a fix for the following nonsecurity issue in Project Server 2016:

In a Project Web App (PWA) project in which a proposed resource is replaced by a committed resource (or vice versa), existing assignments aren't replaced by the new resource. Instead, the assignments are lost.

October 2019

https://support.microsoft.com/en-us/help/4484111/security-update-for-sharepoint-enterprise-server-2016

https://support.microsoft.com/en-us/help/4484115/october-8-2019-update-for-sharepoint-enterprise-server-2016-kb4484115

DB Version 16.0.4912.1000

This security update contains improvements and fixes for the following nonsecurity issues in Project Server 2016:

Makes changes to display the new Japanese era name for date format samples in Date Format in Project Web App (PWA) sites.
The OwnerId property is now available to update the project owner through a REST call. The type of this property is String, but it accepts only the user's numeric ID.
You cannot delete resource calendar exceptions through the client-side object model (CSOM). This issue occurs after you install update 4464594.
If the stage status information text contains special characters such as an ampersand (&), workflows fail.
When the Schedule Variance Percentage (SVP) or Cost Variance Percentage (CVP) earned value becomes very large, this creates an overflow condition. This causes the client-side object model (CSOM) or REST calls that are made while accessing the project to fail. The SVP and CVP values now have a lower limit of "-100%" and upper limit of "100%."

September 2019

https://support.microsoft.com/en-us/help/4475590/security-update-for-sharepoint-enterprise-server-2016

https://support.microsoft.com/en-us/help/4475594/security-update-for-sharepoint-server-2016

This security update contains improvements and fixes for the following nonsecurity issues in Project Server 2016:

Users can now add tasks while editing a project in the Schedule view when the Project Summary Task option is selected.
You can now receive information about any type kind of completed queue jobs for a project when you use the new GetAll() method from a REST call.
When the Schedule Variance Percentage (SVP) earned value becomes very large, it causes an overflow condition that prevents Project Web App (PWA) project views from loading. The SVP value now has a lower limit of -100% and upper limit of 100%.

August 2019

https://support.microsoft.com/en-us/help/4475549/security-update-for-sharepoint-enterprise-server-2016

https://support.microsoft.com/en-us/help/4464553/august-13-2019-update-for-sharepoint-enterprise-server-2016-kb4464553

This security update contains improvements and fixes for the following nonsecurity issues in Project Server 2016:

Through the client-side object model (CSOM), the TaskLink ProjUid property for an external task returns the ID of its own project instead of the ID of the project that the task refers to. This update adds the ExternalProjectUid and ExternalTaskUid properties to the Task class to fix this issue.
Fix: When the database upgrade sequence of the SharePoint Server 2016 Products Configuration Wizard runs, the Central Admin Database is unexpectedly added to the Project Server database schema. This may cause reporting issues and violations to health rules to run against the Central Admin Database.
Fix: When you view the resource engagements Resource Requests page that is formatted to show timephased data, it may take several minutes for the page to render, depending on the number and complexity of the engagements.
Fix: The CalendarException.RecurrenceWeek property returns the wrong value through the client-side object model (CSOM).
Fix: When the Schedule Variance Percentage (SVP) earned value field becomes very large, an overflow condition occurs that prevents PWA project views from loading.
Fix: The project Start Date that is displayed in Project Detail Pages (PDPs) in Project Web App (PWA) doesn't match what is displayed in the Project Information dialog box in Project Professional 2016.

July 2019

https://support.microsoft.com/en-us/help/4475520/security-update-for-sharepoint-enterprise-server-2016

Contains the following improvements and fixes for nonsecurity issues in Project Server 2016:

Makes changes so that the first year of an era in Japanese dates on a timeline view shows as the special Kanji character (元). The Japanese date format is now consistent between the calendar date picker and the timeline view.
You can now update a task dependency lead and lag time by using the LinkLagDuration property through the client-side object model (CSOM). Similar to other duration properties (such as the Task.Duration property in the Task Object), LinkLagDuration accepts either a string or an integer value, such as "1d" or "480" to indicate one day of work.
After you change actual work values in a timesheet, you find that the columnar Total work values in the time-phased grid part of the view does not sum correctly.
When you query project-level information through the client-side object model (CSOM), read performance is slow if the Project Owner field is included.

June 2019

https://support.microsoft.com/en-us/help/4464594/description-of-the-security-update-for-sharepoint-enterprise-server

Contains fixes for the following nonsecurity issues in Project Server 2016:

Adds the PublishSummary method for the ProjectCollection class in the client-side object model (CSOM) so that project-level fields on a project can be published independently from the entire project.
Updating resources through the client-side object model (CSOM) takes a long time or causes a time-out.
When you update a task in a timesheet, after the status update is applied to the project, in Project you may observe unexpected results to the resource assignment. For example, the custom remaining work contour has changed to Flat. Or, the finished date of the assignment on a fixed duration task is earlier than expected.

May 2019

https://support.microsoft.com/en-us/help/4464549/description-of-the-security-update-for-sharepoint-enterprise-server

DB Version - Content DB 16.0.4849.1000

This update contains a fix for the following nonsecurity issue in Project Server 2016:

Updating a local custom field lookup table values through the client-side object model (CSOM) may cause Project to crash.

See full article for SharePoint fixes.

April 2019

https://support.microsoft.com/en-us/help/4464510/description-of-the-security-update-for-sharepoint-enterprise-server

https://support.microsoft.com/en-us/help/4461507/april-9-2019-update-for-sharepoint-enterprise-server-2016-kb4461507

DB Version 16.0.4834.1000

Contains fixes for the following nonsecurity issues in Project Server 2016:

When you query many projects in batches through the client-side object model (CSOM), the project custom fields values are returned as "null."
In an environment that uses the Japanese new era calendar, date formats that contain year aren't applied on the Timeline view for dates after 1 May 2019.
When you query a project by using a Representational State Transfer (REST) call, not all of the expected project related properties are returned.
When you update a single resource through the client-side object model (CSOM), a Reporting (Resource Sync) job is unexpectedly invoked for all resources and the process takes much longer than expected.
If you directly publish a project without first doing an explicit save operation, you won't receive an email notification for new or changed assignments.
Consider the following scenario:
You migrate your Project Server 2010 or 2013 data to Project Server 2016.
You open a project for editing from Project Web App.
You delete tasks in the project. You save the project.

In this situation, when the project is reopened, you may find that the tasks that were deleted previously reappear or that the project can't be reopened.

In an environment that uses the Japanese new era calendar, date formats that contain year aren't applied on the Timeline view for dates that occur after May 1, 2019.

This update improves translations of a PowerShell warning message for multiple languages versions of SharePoint Server 2016.

March 2019

https://support.microsoft.com/en-za/help/4462211/description-of-the-security-update-for-sharepoint-enterprise-server

DB Version - Content DB 16.0.4822.1000

Improvements and fixes

Makes the following improvement in SharePoint Server 2016:

Adds support for the new Japan era in SharePoint Server 2016

Contains a fix for the following non security issue in Project Server 2016:

Editing a project-level custom field while on a project detail page (PDP) causes lost task-level calculated custom field values if the field formula includes the task's Unique ID.

February 2019

https://support.microsoft.com/en-us/help/4462155/description-of-the-security-update-for-sharepoint-enterprise-server

DB Version - Content DB 16.0.4807.1000

This security update contains the following improvement in Project Server 2016:

This update adds support in the client-side object model (CSOM) for setting the EnterpriseProjectType of a project by using the REpresentational State Transfer (REST) Application Programming Interface (API)..

January 2019

https://support.microsoft.com/en-us/help/4461598/description-of-the-security-update-for-sharepoint-enterprise-server DB Version - Content DB 16.0.4795.100

This security update contains fixes for the following nonsecurity issues in Project Server 2016:

If you update both a task's name and Actual Cost value through the Client-Side Object Model (CSOM), the task name is lost. Additionally, other fields that were set during the same update are lost.
You can't get all the details of a dependency link, such as the lag duration and project UID properties, through the Client-Side Object Model (CSOM).
Assume that you have selected PEN, AED, or other values in the Currency Settings section on the Additional Server Settings page. When you create a project from Project Web App (PWA), you experience a "ProjectOptCurrencySymbolInvalid" error, and the project is not successfully created.

December 2018

https://support.microsoft.com/en-us/help/4461541/descriptionofthesecurityupdateforsharepointenterpriseserver2016decembe DB Version - Content DB 16.0.4783.100

This security update contains improvements and fixes for the following nonsecurity issues for Project Server 2016:

This update provides the UpdateCreatePDP method so that you can set the "New Project Page" Project Detail Page (PDP) for an enterprise project type (EPT) through the Client-Side Object Model (CSOM).
While on the Timesheet Adjustment page, you click the Filter button and then you manually enter a Custom Date Range date that is outside of the allowable range for the project (such as between 1/1/1984 and 12/31/2149). When you then click the Apply button, the page fails to load and becomes unrecoverable. You see the following error message:“Sorry, something went wrong. Your request has failed for an undetectable reason; you may need to contact your system or database administrator."

November 2018

https://support.microsoft.com/en-us/help/4461501/description-of-the-security-update-for-sharepoint-enterprise-server

DB Version - Content DB 16.0.4771.100

This security update contains improvements and fixes for the following nonsecurity issues for Project Server 2016:

When multiple user and group synchronization jobs run in parallel, SQL deadlocks may occur. This issue may cause orphaned records in the MSP_WEB_SECURITY_PSMODE_PERMISSION_SYNC_STATES table that may also cause poor synchronization performance and large amounts of disk space consumed by the orphaned rows.
When an automatic approval rule is used to process status updates, for a given task, the Process Status field on the Tasks page is not changed from "Manager updated" to "Completed" even though the task is completed.
This update enables the ScheduledFromStart property to be set in the DraftProject class in the Client-Side Object Model (CSOM). You can now specify at creation of a new project whether it should be scheduled from the start date or the finish date.
This update adds the GraphicalIndicator property to the CustomField class in the Client-Side Object Model (CSOM). You can now set and get a Graphical Indicator for a custom field.
Approving status updates leads to an internal failure. The Info column in the Status updates history says that there was an internal error, and the Status says "Pending." This problem can occur when a team member adds notes to their task status.
This update adds a UseForMatching property to the CustomField class in the Client-Side Object Model (CSOM). Through this property, you can set whether a field is used for matching generic resources.
Assume that you change the Week starts on setting for a project and save the project as a template in Project 2016. Then, you associate the template to an Enterprise Project Type (EPT) in Project Web App. When you create a new project from the Project Center by using the EPT, you find that the Week starts on setting doesn't match the setting in the template.
Approving status updates leads to an internal failure. The Info column in the Status updates history says that there was an internal error, and the Status says "Pending." This problem may occur when an internal services timeout occurs even though the Project Calculation Service RequestTimeLimits is set to an appropriate value.
In the Capacity Planning report, the Resource Center, Resource Assignments and Resource requests buttons on the Ribbon are not working.
This update adds the Departments property for the EnterpriseProjectType class in the Client-Side Object Model (CSOM). You can now set and get the department for an Enterprise Project Type.
The Current Max. Units (%) value of a resource that's shown in Project Web App doesn't match the current Max. Units value that's seen in Project 2016.
A project's or task's calendar can't be set through the Client-Side Object Model (CSOM). Instead, you see the error message: "Column "TASK_CAL_UID' is read only."

October 2018

https://support.microsoft.com/en-us/help/4461447/description-of-the-security-update-for-sharepoint-enterprise-server DB Version - Content DB 16.0.4756.100 This security update contains improvements and fixes for the following non security issues for Project Server 2016:

This update adds support for cost resources in the Client-Side Object Model (CSOM) in Project Server 2016. Now, you can create or get a cost resource through CSOM.
This update adds the ability to set the LookupAllowMultiSelect property on the CustomField class in the Client-Side Object Model (CSOM).
This update adds support for the HyperlinkURL and HyperlinkName properties to the EnterpriseResource class in the Client-Side Object Model (CSOM).
This update adds a IsLeafOnly property to the CustomField class in the Client-Side Object Model (CSOM). Through this property, you can get or set a value that indicates whether the custom field value must be a leaf node in the lookup table.
The data of an inactive resource assignment incorrectly affects availability on Capacity Planning reports.

September 2018

https://support.microsoft.com/en-us/help/4459402/september-2018-updates-for-microsoft-office

DB Version - Content DB 16.0.4744.1000

This security update contains improvements and fixes for the following non security issues for Project Server 2016:

You can't update the Status Manager field for a task through the Client-Side Object Model (CSOM).
When you create and insert a new task into a collapsed task outline in a project through the Client-Side Object Model (CSOM), the new task may be inserted at the wrong location in the project.
When you assign a resource to a task through the Client-Side Object Model (CSOM), this is done based on the resource name instead of pairing the resource and task GUID fields. As a result, the resource that is assigned to the task is not the one that is specified through CSOM.
When the scheduled Backup and Restore Timer job runs, SQL Server deadlocks occur when an archived version of the project has to be deleted before a new version can be written.
If a task link is created between two tasks, the dependency type of the task link can't be changed through the Client-Side Object Model (CSOM).
The Task IsLockedByManager property can't be set through the Client-Side Object Model (CSOM).
You can't get the department that is associated with a custom field through the Client-Side Object Model (CSOM).
When you try to get an enterprise resource through the Client-Side Object Model (CSOM), the RES_ID property (the Unique ID of an enterprise resource), isn't returned in the same manner as it is through the Project Server Interface (PSI).
You can't return a list of template projects by using the Client-Side Object Model (CSOM) ProjectCollection.
You can't update a Lookup Table mask through the Client-Side Object Model (CSOM). Therefore, you can't programmatically add a value to the Lookup Table at the level that is not defined in the mask.

August 2018

https://support.microsoft.com/en-us/help/4032256/description-of-the-security-update-for-sharepoint-enterprise-server DB Version - Content DB 16.0.4732.1000

This security update contains improvements and fixes for the following nonsecurity issues for Project Server 2016:

When a SharePoint Server 2013 content database that contains Project Server sites is mounted on a SharePoint Server 2016 farm that was set up by using PowerShell cmdlets, Project Server-related database tables are not created. Therefore, the Project Server related sites cannot be opened.
When you restore Enterprise custom fields by using the Administrative Backup and Administrative Restore features in SharePoint Server 2016 Central Administration, you experience a "ForeignKeyViolationError."
If you set a long Duration or Work value for a task in a project and then try to achieve the value of the WorkTimeSpan property by using the Project Server 2016 client-side object model (CSOM), an overflow occurs in the WorkTimeSpan property. For example, when you set the Duration value to 75 days, the DurationTimeSpan property displays 36000. However, the WorkTimeSpan property displays -35791.3941333333.
You receive an unknown error when you set a lookup table value for a local custom field through the Project Server 2016 client-side object model (CSOM).
When you enter 1d in the Committed Work field for a resource engagement, the Committed Work field always displays the default 8h for 1 day instead of the project calendar setting from the Enterprise Global.
This update makes the Task Type field and Task.IsEffortDriven property updatable through the Project Server 2016 client-side object model (CSOM).
When you create an enterprise resource through Project Server 2016 client-side object model (CSOM), you are unable to set values for required custom fields. Therefore, you can’t create the enterprise resource.

July 2018

https://support.microsoft.com/en-us/help/4022228/description-of-the-security-update-for-sharepoint-server-2016

DB Version - Content DB 16.0.4717.1000

This security update contains improvements and fixes for the following nonsecurity issues in Project Server 2016:

The ReadResourcePlan API is now available even if the Resource Engagements feature is enabled.
It takes a long time to process tasks in a project through the client-side object model (CSOM) APIs in Project 2016.
Local custom date type fields that have a formula and have the calculation for the task and group summary rows option set to minimum or maximum are not rolled up correctly to summary tasks when you update a project in Project Web App.
It takes a long time to load entities such as tasks, resources, and assignments through the client-side object model (CSOM) APIs if custom fields exist.
When you use the Chrome browser to open a project from the Project Center where the project name includes spaces, you receive the following error message:

Project Web App was unable to find the specified Project.

Additionally, you receive the following error message:

Sorry, we were unable to open your project. Please try again. If this happens again, contact your ADMINISTRATOR.

June 2018

https://support.microsoft.com/en-us/help/4022173/description-of-the-security-update-for-sharepoint-enterprise-server-20 https://support.microsoft.com/en-us/help/4022178/june-12-2018-update-for-sharepoint-enterprise-server-2016-kb4022178 DB Version - Content DB 16.0.4705.1000

This update contains fixes for the following issues for Project Server 2016:

It takes a long time to load tasks from a project through client-side object model (CSOM) if custom field lookup table data is also loaded.
It takes a long time to load a project in a Project client that has a large number of long-running resource engagements.
After the migration from Project Server 2013 to Project Server 2016 and SQL Server 2014 to SQL Server 2016, the performance of a custom SQL reporting query is slow.
When you select multiple resource in Project Web App and select to open them in Project Professional 2016, you receive the "Undefined" error message. You should receive an error message that resembles the following:
Your selection exceeds the limit for the number of resources we can open at a time from Project Web App. We opened the enterprise resource pool with the supported number of resources.
If you use the on-premises version of CSOM, the EnterpriseResourceCostRate classes are not available. Therefore, you cannot update resource rates.
Even if a status manager has never touched or owned a given assignment, the Status Update History page still shows the assignment. For example, the status history in the approval center shows a status manager approved an assignment even if the status manager did not approve it.

May 2018

https://support.microsoft.com/en-us/help/4018381/description-of-the-security-update-for-sharepoint-enterprise-server-20 https://support.microsoft.com/en-us/help/4018386/may-8-2018-update-for-sharepoint-enterprise-server-2016-kb4018386 DB Version - Content DB 16.0.4690.1000

This update contains fixes for the following issues for Project Server 2016:

If the proxy for the Project Service Application services already exists when you create a new Project Service application by using Install-SPService –Verbose command, an additional proxy for the service is created.
Consider the following scenario:
- As a team member, you open your timesheet and enter work for two adjacent days.
- On the first day, you set the actual work value back to zero.
- On the first day, you set 8 hours of non-working time on an administrator task (for example, vacation)
- You send a status update for approval.
- You open the previous week timesheet.
- You enter actual work values.
- You send the timesheet for approval, and the status manager approves it.
In this case, the actual work that was entered on the second of the two days moves to the first day. The actual work should not move when the status update is applied to the project.
When you publish a project in which the process updates the Summary Resource Assignment to a later date, the publish fails if the server is configured to use a date format other than MM-DD-YY.
This security update contains improvements and fixes for the following nonsecurity issues in SharePoint Server 2016:
- When an item is deleted from the usage analytics caches, the item is now also deleted from the analytics reporting database.
- If you don't have sufficient permission to mount a content database to a farm by using the Mount-SPContentDatabase cmdlet, the cmdlet fails and the database is dropped unexpectedly.
- This update introduces the "My Site creation default to OneDrive in Office 365" hybrid feature in SharePoint Server 2016. After you install this update and enable this feature, hybrid-enabled users can have their OneDrive personal sites provisioned in the cloud instead of on-premises. On-premise only users can still have their OneDrive personal sites provisioned on-premises.
- You cannot use the SharePoint Term Store Management UI in browsers other than Internet Explorer.
- The WebPart.ZoneID property is unavailable in the Web Part information.
- SharePoint emails that are longer than 1,000 characters could become corrupted at the 1,000-character position. Depending on what content happens to be at that position, the corruption could be minor (corrupted text) or severe (broken HTML markup).
- This update fixes the following three issues with the SharePoint Properties Panel:
  - When you save a SharePoint properties panel with required properties for the first time, you cannot find the properties.
  - The DateTime format is assumed to MM/DD/YY.
  - Drop-down of lookup type is set to nil when the label is selected.

April 2018

https://support.microsoft.com/en-us/help/4018336/description-of-the-security-update-for-sps-2016 https://support.microsoft.com/en-us/help/4018340/april-10-2018-update-for-sharepoint-enterprise-server-2016-kb4018340 DB Version - Content DB 16.0.4678.1001

This update contains fixes for the following issues for Project Server 2016:

Portfolio Analysis View displays incorrect availability and requirements information in certain conditions, depending on data and planning horizon settings.
You cannot see Queue Job status because duplicated Project Publish reporting causes the Manage Queue page not to be loaded. In addition, you receive the following error message:
Sorry, something went wrong An unexpected error has occurred
The Capacity Planning Views don’t always display project assignments for each selected resource.
When you change the definition of the Task Status field in the Task content type, the “In Progress” value that was deleted previously still appears occasionally.
When the assignment actual work is missing in the published database, the timesheets pages don’t load in single entry mode. In addition, you receive the following error message:
The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.
When you create resource engagements from Project Web App(PWA), the PWA always uses 8 hours for one day instead of the expected setting from Enterprise Global.
When you open projects from Project Center in Project Web App by using Internet Explorer 11 in Windows 7, you receive the following error message in the browser:
Action Not available -Project Professional needs to be installed to open the project. Install project and try again
The title of Project Detail Pages displays encoded Unicode characters unexpectedly. For example, the character “&” in the title becomes “&amp”.
You cannot create customer views that are based on filtering and grouping in Project Web App.

March 2018

https://support.microsoft.com/en-us/help/4018293/description-of-the-security-update-for-sharepoint-enterprise-server-20 https://support.microsoft.com/en-us/help/4011687/march-13-2018-update-for-sharepoint-enterprise-server-2016-kb4011687 DB Version - Content DB 16.0.4666.1000

This update contains fixes for the following issues for Project Server 2016:

When the Project permission “View the Project Schedule Details in Project Web App” is enabled, you may see views and data that you don’t have permission to see.
Actual work that’s applied as a part of a status updates approval doesn't always appear in the given project.
When you open and edit a project, and then save back to Project Server 2016, you may see an error message in the Unified Logging System (ULS) logs that resembles the following:

[PS_AC][Number] Invalid bool pid 188745088 (B400580) for container Task
- When you open and edit a project, and then save it in Project Server 2016, you may receive an error message that has some of the following elements in it:
  
  ActiveCacheQueuedMessageExecutionError error="System.InvalidCastException: Specified cast is not valid”
- Consider the following scenario:
  - You have a Project Web App (PWA) site and Project Server 2016 in your organization.
  - You log on to a PWA instance, and then create an enterprise custom field for the resource entity and another enterprise custom field for the project entity.
  - You start Project Professional 2016 and connect to Project Server 2016. Then, you add a resource and set a value for the custom field of the resource.
  - You save the project and check it in.
  - In PWA, you locate the Project Center, drill into the project, and then select a Project Details Page (PDP), if you have not already selected it.
  - You make a change to the project custom field, and then you save the project from the PDP.
  - In Project Professional 2016, you open the project and view the custom field value.
  In this situation, the value of the resource custom field is missing.

February 2018

https://support.microsoft.com/en-us/help/4011680/descriptionofthesecurityupdateforsharepointentserver2016february13-201 DB Version - Content DB 16.0.4651.1000

This update contains fixes for the following issues for Project Server 2016:

Assume that a Project Web App site is configured to use Host Headers for the site collection. In this case, the drop-down menus on the Force in/out field for the project selection in portfolio analyzer views don't work correctly.
In some cases, the timesheet status is displayed as "Not Approved" even though the timesheet has been approved.
Consider the following scenario:
- You have a Project Server 2016 and a Project Web App instance provisioned.
- You have at least one resource defined.
- You log on the Project Web App site instance, locate the Resource Center view, select a resource, open the Resource tab in the ribbon, and then select the Capacity Planning button.
- In Capacity Planning views, you look for the Export to Excel button to export the details table.
In this situation, the Export to Excel functionality is missing because the button does not exist.
Consider the following scenario:
- You have a task that has a resource assigned.
- The task has a split in it. For example, there's a week of work, a week with no work, and then a final week that has work.
- In the timesheet for this task, you enter hours on the task so that the work is completed up to the date where the split begins.
- The timesheet is submitted and then the status update is approved.
- After that, the project is opened in Project Web App, and the task finish date is adjusted to a date that’s after the actual work is completed. For example, the actual finish date is set to the middle of the week where there is no work.
In this situation, the actual work is spread over the whole duration.

January 2018

https://support.microsoft.com/en-us/help/4011642/descriptionofthesecurityupdateforsharepointenterpriseserver2016january https://support.microsoft.com/en-us/help/4011645/january-9-2018-update-for-sharepoint-enterprise-server-2016-kb4011645 DB Version - Content DB 16.0.4639.1002

This update contains fixes for the following issues for Project Server 2016:

You cannot create projects by using the Project Server 2016 client-side object model (CSOM) if some required fields are missing.
Actual work that has been reported by team members in a project inadvertently gets spread differently than what was reported. For example, the actual work hours of 2, 2, 2, 2 are changed to 1.78, 1.78, 1.78, 2.45. The totals stay the same, but the time-phased work appears differently across the days. This issue occurs in certain situations when the project is edited in Project Web App even though the task setting and display server option Only allow task updates via Tasks and Timesheets are enabled.
SharePoint security groups may not be populated with the correct users when the Project Server Active Directory synchronization process runs. As a result, users may not be able to log on to Project Server or may have the wrong permissions.
Consider the following scenario:
- You have an Administrative category that enables multiple lines.
- You create a timesheet and add a new non-project line that uses the category in the timesheet.
- You change the default name or description for the non-project line to a new name and then save the timesheet.
- After that, you go to the next timesheet period, and then check the administrative task.
In this situation, you see the task in the next timesheet period, but the task name or description doesn’t carry over.
After you install the updates Description of the security update for SharePoint Enterprise Server 2016: October 10, 2017 and October 10, 2017, update for SharePoint Enterprise Server 2016 (KB4011161), views in the pjrep schema, which are used for reporting, are lost.

December 2017

https://support.microsoft.com/en-us/help/4011576/descriptionofthesecurityupdateforsharepointserver2016december12-2017 https://support.microsoft.com/en-us/help/4011578/december-12-2017-update-sharepoint-enterprise-server-2016-kb4011578 DB Version - Content DB 16.0.4624.1000

This update contains fixes for the following issues for Project Server 2016:

Assume that you have an enterprise resource that is a part of a team assignment pool. When you go to the Resource Center, select the resource and then click the Capacity Planning button, the resource is not displayed, and in some cases you see the error “Sorry, something went wrong.”
Consider the following scenario:
- A project manager publishes a task to a team member.
- The team member goes to their timesheet and enters actual work on the task.
- The timesheet is submitted and then approved.
- The project in which the task exists is deleted.
- The team member goes back to their timesheet.
- In this situation, the task on which the actual work was submitted is no longer there.
When you delete a value from a custom field that's configured to display a graphical indicator, the record in the database is not deleted, but instead the value is set to NULL, and the indicator value is preserved in reporting.

November 2017

https://support.microsoft.com/en-us/help/4011244/descriptionofthesecurityupdateforsharepointserver2016november14-2017 https://support.microsoft.com/en-us/help/4011243/november-14-2017-update-sharepoint-enterprise-server-2016-kb4011243 DB Version - Content DB 16.0.4615.1000

This update contains fixes for the following issues for Project Server 2016:

When a Project Server lookup table is created and details are added, nothing is displayed for the resource in Resource Center > Capacity Planning.
After you change the SharePoint farm authentication realm, Project Server workflows stop progressing and go into suspended mode.
If the previous publish is failed, the publishing of the master project is blocked.

October 2017

https://support.microsoft.com/en-us/help/4011217/security-update-for-sharepoint-enterprise-server-2016 https://support.microsoft.com/en-us/help/4011161/october-10-2017-update-for-sharepoint-server-2016-kb4011161 DB Version - Content DB 16.0.4600.1001

This update contains fixes for the following issues for Project Server 2016:

Some summary resource assignment work or actual work values may have large negative numbers. This issue may cause the project publish process to fail.
After you add yourself to a task by using the Add yourself to a task option for a timesheet, the new assignment request is sent to the project owner instead of to the task manager for the task.

September 2017

https://support.microsoft.com/en-us/help/4011127/descriptionofthesecurityupdateforsharepointserver2016september12-2017 https://support.microsoft.com/en-us/help/4011112/september-12-2017-update-for-sharepoint-server-2016-kb4011112 DB Version - Content DB 16.0.4588.1000

This update contains fixes for the following issues for Project Server 2016:

Consider the following scenario:
- You create a Gantt Chart format and then select to display at least one of the custom duration bars.
- You edit a Project view and then set the Gantt Chart format to one that has custom duration bars.
- You edit a project in Project Web App.
- You apply the project view.
In this situation, the view doesn't load, and you receive the following error message:

The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.
When you edit a task and select the Show More button, the focus isn't set on the first uncovered field.
When you call the GetTimePhase method on the StatusAssignmentCollection that's exposed on an EnterpriseResource object in CSOM, the Status Broker permission is ignored.

August 2017

https://support.microsoft.com/en-us/help/4011049/august-8-2017-update-for-sharepoint-server-2016-kb4011049 https://support.microsoft.com/en-us/help/4011053/august-8-2017-update-for-sharepoint-server-2016-kb4011053 DB Version - Content DB 16.0.4573.1000

This update contains fixes for the following issues for Project Server 2016:

When you try to rename a project that has a required project level custom field in Project Professional 2016, you may receive the following error message:
Renaming project failed with error code hr = 0x80020009
When you try to rename a project to a name that contains the ampersand character, you receive the following error message:
Renaming project failed with error code hr = 0x80020009
After you drill into a project and open the Project Detail page in the Project Center, you may receive the following error message:
Sorry, something went wrong An unexpected error has occurred. Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator.
This error occurs if you don't have the Open Project permission.
The Name column in a Gantt view in a document library does not display the expected values.

July 2017

https://support.microsoft.com/en-us/help/3213544/descriptionofthesecurityupdateforsharepointserver2016july11,2017 https://support.microsoft.com/en-us/help/3213543/july-11-2017-update-for-sharepoint-server-2016-kb3213543 DB Version - Content DB 16.0.4561.1000

This security update contains fixes for the following nonsecurity issues for Project Server 2016:

Reliability and functionality issues when a SharePoint Server 2013 content farm is consuming a UPA service application from a SharePoint Server 2016 farm.
A user cannot edit summary tasks lock field in the Project Center while using Project Web App.
You can't edit items in quick edit mode in a document library that has more than two pages of files when the Edit function (the link to edit items) is enabled. This issue occurs after you move to a different page of items.
Sub projects may become normal projects sporadically in Project 2016.

June 2017

https://support.microsoft.com/en-us/help/3203432/descriptionofthesecurityupdateforsharepointserver2016june13,2017 https://support.microsoft.com/en-us/help/3203433/june-13-2017-update-for-sharepoint-server-2016-kb3203433 DB Version - Content DB 16.0.4549.1001 This security update contains improvements and fixes for the following nonsecurity issues in Project Server 2016:

Improve the performance of the Reporting (Project Publish) queue jobs.
Fixes the following issues:
- Consider the following scenario:
  - A project manager publishes a task to a team member.
  - The team member in either a timesheet or in tasks within Project Web App reports work that's earlier than what was scheduled. For example, 8 hours‚ of work was scheduled on Wednesday but 8 hours of actual work was reported and submitted for Monday.
  - The status manager approves the update.
  - The team member zeros out the actual work and moves it to a later date.
  - The status manager approves the update.
  - The project is opened in Microsoft Project Server.

In this situation, the task's actual start date still reflects the earlier update instead of the new update where the actual start date is later.

The Reporting (Project Publish) job takes longer than expected in Project Server 2016.
Suppose you go to the Project Center page in the Project Web app and select many projects. When you click the Open In Microsoft Project option, nothing seems to happen, and the expected master project isn't created in Project Professional. Now, when you've selected more projects than can be used to create a master project via this method, you'll see a message similar to this:

Your selection exceeds the limit for the number of projects we can open at a time from Project Web App. We created a master project with the supported number of projects. You can then add additional projects by going through Insert Subproject.

Resources from approved engagements become local resources in Project Professional if the project manager doesn't have sufficient permissions to that resource.
When you add new tasks to a project while editing a project in PWA, formulas that use the Now() or CurrentDate() functions calculate incorrect results.
An assignment's Finish Date, Work, and Remaining Work values are wrong when team members enter material units in PWA Tasks or Timesheets views.
User-generated (ad hoc) custom filters that are applied to PWA views don't display data values. For example, you open a custom filter dialog box in Project Center to add a filter on a date column. After you save, close, and then reopen the dialog box, the date you set isn't displayed.
When you submit a status update, task-level baseline data disappears from the Tasks view for the given task assignments.
Improves the translation of Project Server 2016 in multiple languages

May 2017

https://support.microsoft.com/en-us/help/3191880/description-of-the-security-update-for-sharepoint-server-2016-may-9-20 and https://support.microsoft.com/en-us/help/3191884/may-9-2017-update-for-sharepoint-server-2016-kb3191884 DB Version - Content DB 16.0.4534.1000 These are the Project fixes - see the full articles linked above for the complete list of SharePoint fixes and the new SharePoint features in this release: This security update fixes the following nonsecurity issues for Project Server 2016:

The March 2017 public update provided the necessary WSDL files in order to programmatically access the Project Server Interface (PSI). However, the WDSL files were not completely correct. Therefore, even after the update is installed, it wasn't possible to access the various PSI end points.
When you run an administrative backup and an administrative restore of Enterprise custom fields, the restore fails at 29 percent completion. You also see a DatabaseForeignKeyViolationError (50002) queue error.

April 2017

https://support.microsoft.com/help/3178721 and https://support.microsoft.com/help/3178718 DB Version - Content DB - 16.0.4522.1000 This update contains the following improvements and fixes for Microsoft Project Server 2016:

When you browse PWA pages that have HTML grids either in Internet Explorer standards or enterprise mode, you can't scroll pages because the scroll bars don't appear.
Screen readers don't identify that the Delegate Name and the User Name fields on the Add Delegation page are required.

This public update delivers the first feature pack (Feature Pack 1) for SharePoint Server 2016 that contains the following features:

Administrative Actions Logging
MinRole enhancements
SharePoint Custom Tiles
Hybrid Auditing (preview)
Hybrid Taxonomy
OneDrive API for SharePoint on-premises
OneDrive for Business modern experience (available to Software Assurance customers)

March 2017

https://support.microsoft.com/help/3178675 and https://support.microsoft.com/help/3178672 DB Version - Content DB - 16.0.4507.1000

SharePoint updates:

Adds the Web Service Definition Language (WSDL) proxy files for Project Server 2016.
Adds translations for several group membership strings in multiple languages.
Adds error messages for the exceptions of taxonomy replication and migration.

This update fixes the following issues:

Some database views in the reporting schema such as the pjrep.MSP_EpmProject_UserView are missing and they can't be recreated.
Spelling check does not provide suggestions or correct misspelled words in a calendar app.
You can't add dimensions or measures to an OLAP cube definition if there is more than one PWA instance defined in a given web app.
OLAP cube builds times don't follow the requested pattern. For example, if you set a cube to be built hourly, there are some hours where the cube isn't built.
If you apply a filter that uses the Does not Contain filter test to a project that you are editing in Project Web App, tasks that have the filtered characters are still displayed.
Administrative tasks should not be auto approved if the timesheet owner has the Adjust Timesheet permission.
On the OLAP Database Management page, you can't set a new default OLAP database, or enable or disable existing databases if you have more than one PWA instance on the server.
Previously, files are copied side-by-side if the EnableSideBySide setting is true. Now, files are copied side-by-side regardless of the EnableSideBySide setting.
An issue that occurs when you pipe Set-SPContentDatabase with Get-SPContentDatabase.
Adds more logs to diagnose the issue in which a farm server turns to the Upgrade Required status after a successful run of psconfig with the No Action Required server status.
It's difficult for a screen reader to understand the structure between sections on a discussion board. This is because there is only one heading. This update adds h2 and h3 labels to the discussion board for better screen reading.
Updates the translations to make sure that the meaning of the word "Drivers" is correct in Project Server.

February 2017

https://support.microsoft.com/kb/3141515 and https://support.microsoft.com/kb/3141517 DB Version - Content DB - 16.0.4498.1000 This update fixes the following issues in Project Server 2016:

Timephased data on material resources may be incorrect if updates come from PWA. For example, you have a material contour that resembles the following:

10,10,10,10

In PWA, the team member reports the following:

5,10

When the update is displayed in Project Professional, the material contour resembles the following:

5,10,25

Instead, the contour should be like:

5,10,12.5,12.5

After you edit a project in PWA, formulas that rely on the Now() function and the [Current Date] property aren't calculated.

January 2017

https://support.microsoft.com/en-us/kb/3141486 and https://support.microsoft.com/en-us/kb/3141487 DB Version - Content DB - 16.0.4483.1000 This update includes the following improvements and fixes in Project Server 2016:

You can't use the CSOM API to set the BookingType property for enterprise resources in projects.
When you apply status updates in PWA, actual work is added to some assignments unexpectedly. For example, you have an assignment that has 35 hours total work, and the status update is to apply 9 hours. When you view the results in Project Professional, you find that the assignment is unexpectedly completed. Meanwhile, the total work and the actual work have increased to 400 hours.
Translates some terms in multiple languages to make sure that the meaning is accurate.
Translates some terms in Brazilian for Project Online.

December 2016

https://support.microsoft.com/en-us/kb/3128017 and https://support.microsoft.com/en-us/kb/3128014 DB Version (C0ntent DB - 16.0.4471.1000) This update includes the following improvements and fixes in Project Server 2016:

If you apply a new site theme, the timeline which is a part of the tasks app, may continue to use the default theme. For example, suppose that the new site theme displays a blue background. In this case, the timeline would still be displayed with the default white background.
An Active Directory group that's used to synchronize users in Project Web App and that includes disabled accounts does not inactivate those users in Project Web App. Additionally, the Active Directory Sync job may show that it partly failed.
When you edit a project in Project Web App, the filter that has been associated to the view that you have applied doesn't work if the filter uses the "Begins with" test.
Consider the following scenario:
- In Project Professional, you have several tasks, some of which are summary tasks.
- You have collapsed some detail tasks so that you only see the related summary tasks.
- You save, publish, close, and check in the project.
- In Project Web App, you go to the Project Center.
- You drill into the project so that you can see the details.
- You choose to edit the project in Project Web App.
In this situation, you see the expected summary tasks but you can't expand them in order to see the sub tasks under them.

November 2016

https://support.microsoft.com/en-us/kb/3127940 and https://support.microsoft.com/en-us/kb/3127942 One public fix in this release: Self-assigned timesheet lines may display an incorrect TASKUID in the OData feed.

October 2016

https://support.microsoft.com/en-us/kb/3118376 and https://support.microsoft.com/en-us/kb/3118372 DB Version (C0ntent DB - 16.0.4432.1003) The Project Server specific fixes are not in the public articles for this update. The fixes will be posted here when information is made public.

September 2016

https://support.microsoft.com/en-us/kb/3118289 and https://support.microsoft.com/en-us/kb/3118295 DB Version (C0ntent DB - 16.0.4432.1003) In 3118289 Known Issues

If you install the September 2016 public update for SharePoint Server 2016 and then perform a license upgrade from Standard to Enterprise, the license upgrade will time out before completing. This causes the license upgrade operation to fail.If you want or need to perform a SharePoint 2016 license upgrade, you must complete the license upgrade before installing the September 2016 public update.This issue will be fixed in a future public update.Patching and upgrading the September 2016 public update for SharePoint Server 2016 may take three times longer than in previous public updates. Please be patient while the patching and upgrading operations are completing.

Fixes (The Project Server ones)

When you use a template to create a project in Project Web App, the duration of a fixed duration task is changed unexpectedly.
For a task that displays in a timeline on a SharePoint site, when you edit the task's date range from the callout, the timeline disappears.
When you use Internet Explorer or Microsoft Edge, the focus is lost unexpectedly when you move bars up or down from one timeline to another.
When you publish certain projects that include timelines in Project Web App, the Schedule Project Detail Page doesn't load so that you can't see the schedule view.
For tasks that display in a timeline on a SharePoint site, when you click the Edit Date Range button for a task on the timeline, you receive an error that resembles the following:

Error message "Sorry, something went wrong" Correlation ID: xxxxx Date and Time: xxxx.
If you use the keyboard to select parts of the Project Summary web part, the visual focus may be stuck on the timeline section of the web part when at the same time the focus appears elsewhere. This causes screen readers not to work correctly.
When the focus is given to a check box on the Project Web App Resource Center page, nothing is ready by a reader because the column does not have a header.
On the Manage Timesheets page, a screen reader can't determine which cell is selected and therefore it can't read out the information in the cell to the user.
If project sites are created on a different site collection than Project Web App, the Web Admins group is created but user accounts are never synchronized to the group.
Consider the following scenario:
- You have an Administrative Time category that allows multiple lines.
- You create a timesheet.
- On the timesheet, you create a new non-project line that uses the category.
- You save the timesheet.
- You go to the next timesheet period.
In this situation, the page fails to load and stays forever on the loading state.
You can't use keyboard to expand or collapse groupings in the grid on the Resource Center page.
Assume that you press the Tab key to move the focus on a column header on the Manage Timesheets page. Then, you press the Enter key in order to sort by this field. In this situation, the focus is lost from the column header, and you have to press the Tab key many times in order to return to the column header.
In a task list, when you click the Add button to add a new option from the Predecessors section and use the Tab key to navigate away from the Add button, visual focus disappears and you can't make selections from the Priority or the Task Status drop-down lists.
You can't use the keyboard to move the focus to the column headers in the grid for the Resource Center page. Therefore, you can't sort the grid by using the keyboard. After you install this update, you can tab to the column header and then press CTRL + SPACE to open the drop-down list. You can also press CTRL + Y to shift the focus to the column header for a grid cell.
You don't have the permission to create a project in Project Web App even if you are a project manager.
A server-side correlation cancelation on a save job causes deferred jobs to be canceled. For example, a team member submits time against a task and the status manager approves the update. Then, the project is checked out and the Status Update job state is listed as Skipped for Optimization. If a future save on the given project is canceled for whatever reason, the Skipped for Optimization status update job is also canceled.
After you delete a value from a custom field on the My Tasks page, the change isn't saved and the value comes back when you go to the My Tasks page again.

August 2016

https://support.microsoft.com/en-us/kb/3115437 and https://support.microsoft.com/en-us/kb/3115441 DB Version (Content DB) - 16.0.4417.1000 In 3115424:

Translates some terms in multiple languages to make sure that the meaning is accurate.

This update includes the following improvements and fixes for Project Server 2016:

Improves performance for the CSOM API GetByUser method from the Enterprise Resource Collection when there are thousands resources in Project Server.
In the SharePoint Central Administration Health Analyzer, the Missing server side dependencies Configuration rule shows multiple errors that should not be listed. For example, on the Configuration category, the explanation says:

[Upgrade] The number of column pool tables exceeds the database limit. The tables that exceed this limit and should be dropped.

Assume that the Single Entry Mode timesheet setting is enabled. When a timesheet user receives status notifications, the link in the received email navigates to the My Tasks page instead of the Timesheet page.
SQL Lock escalation is disabled by default for SharePoint content databases. This causes large databases to fail during the migration from Project Server 2013 to Project Server 2016 because of memory constraints.
After earned values are calculated in PWA from the schedule project detail page, the values may not be saved. This means the published views of the earned values may not be accurate.

In 3115441:

Translates some terms in multiple languages to make sure that the meaning is accurate.
This update will allow to remove search results from the index until the next incremental crawl.
When you run the SharePoint Products Configuration Wizard (PSConfig), an error occurs. The error message on the result summary page or in the result summary command line output is generic and doesn't provide enough information to help fix the problem. This update now presents detailed error messages to identify which failures affect critical configuration tasks and which failures affect noncritical configuration tasks in the PSConfig summary. Error messages about missing SharePoint features now include the feature title instead of just the feature GUID. Error messages are displayed when the upgrading or updating has been improved. Finally, the summary message includes instructions for how to retry the configuration tasks that failed.
When some products or updates are installed on a SharePoint Server 2016 based computer, the SharePoint configuration database may be unaware of the installed product or update. This can cause a failure when the SharePoint Products Configuration Wizard (PSConfig) is running to do an upgrade. PSConfig will now automatically update the product and update state for the local server in the configuration database to avoid the failure.
When you run the PSConfig command tool in GUI or cmdlet mode, informative error messages aren't provided. After you install this update, you can understand the error easily.

July 2016

https://support.microsoft.com/en-us/kb/3115304 and https://support.microsoft.com/en-us/kb/3115299 DB Version (Content DB) - 16.0.4405.1000 In 3115304:

Translates some terms in multiple languages to make sure that the meaning is accurate.

In 3115299: This security update contains improvements and fixes for the following non-security issues:

Add new CSOM APIs for getting term set names of all languages, and for getting and setting group managers and contributors.
The setCustomFieldValue method can't set a custom field through Java scripts.
Changes in resource properties aren't propagated to OData until a Reporting Refresh job is started.
The planned work is incorrect on the Approval page.
When you reduce the work of a fixed work task while editing in Project in the Schedule Web Part, the duration of the task may be reduced unexpectedly.
If you have an enterprise custom field that has a formula that references a custom field with a lookup table, the value may not be set correctly.
Assume that you are in edit mode of a project with an unassigned task. When you switch from a task view to an assignment view that has a task ID, the view is stuck in loading and you have to refresh the page to get it to work again.
You can't load timesheet if the ASSN_RESPONSE_PENDING field is set to NULL for one of the assignments.
When you change the start date and a multiline text custom field on a project detail page, the multiline text custom field can't be saved and updated.
When you save a project detail page, you receive the CustomFieldRowDoesNotMatchCorrespondingDefinitionInDB error.
When you change the start date of an assignment through the My Tasks page, or through the Timesheet page in Single Entry mode, the actual work of the assignment may be changed.

June 2016

https://support.microsoft.com/en-us/kb/3115184 and https://support.microsoft.com/en-us/kb/3115181 DB Version (Content DB) - 16.0.4393.1000 In 3115184

When you're denied the permissions to open a project, you receive a generic error message instead of the access denied message. This issue also occurs when you have the access to the project but no view is available to the category in which you are added.
Exporting resource assignments to Excel fails.

In 3115181

The Resource Plan button is removed from the schedule Web Part and Project Center. Project Server 2016 now offers the Resource Engagements and Capacity Planning features to replace resource plans.
You can't set a Resource Assignment view to be filtered by a custom field, and you receive the following error message:

An unknown error has occurred.
When you try to add or delete a user from a project server security group, you experience an error if the project site is a root web and the host header configuration is enabled.
After a project manager rejects a task update, you don't receive an email notification that informs you of the task rejection.
When you're denied permissions to open a project or view a project schedule in Project Center, you receive the generic "An error occurred while opening your project" error message instead of the more specific access denied message.
Assume that you save time for a timesheet without submitting. Then, a project manager deletes it from the project of the tasks on which you saved within your timesheet. When you go to submit the timesheet or a status update for that timesheet, it fails and you receive the following error message:

An error occurred while communicating with the server. Check connectivity with your administrator to determine whether further action is necessary.
If the timesheet unit settings are set to weeks, planned work isn't displayed in timesheets.
A summary task may not correctly compute the rollup value of a custom field if the field is configured with the following properties:
- A date type
- A minimum rollup
- A formula where the value may be null (N/A)
You can't edit and save changes to enterprise resources in Project 2016.
When an administrator edits the Proposal Summary Project Detail page, the following error message appears on the page:

Sorry, something went wrong.
Assume that a project server administrator creates an enterprise project template. Then, project managers create a project by using the template and specify an owner for the project. When the project is saved, Project Web App ignores the owner information.
It takes a long time for the initial project publish and user synchronization jobs to complete. The end result is that a project manager who creates a project in Project Web App waits for a long time before being able to move to other Project Web App pages.
Consider the following scenario:
- You have a project-level enterprise field that's linked to a lookup table.
- The custom field is exposed on a project detail page (PDP).
- You edit a project on the PDP.
- You change the value of the custom field as well as other fields such as the project description field.
- You save the project.
In this situation, you receive the following error message:

An error has occurred while saving your project to the server. Please contact your administrator for assistance.

In addition, the queue job error details state GeneralItemDoesNotExist.
After you change the booking type of a resource in a project, the booking type of the resource's assignments aren't updated to reflect the new booking type.
The status update process fails to update actual work on a project when a custom field formula calculation in the project fails.
Cost values are displayed incorrectly when you edit a project in Project Web App. For example, 100$ is displayed as 10.000$.
Assume that the Project Web App project editing session of a project has timed out. After you select OK to the "Your session has timed out because of inactivity. To continue editing this project, click OK" message and save the changes, the changes aren't applied to the project.
Enterprise Flag fields don't save a No value unless you explicitly select the value. Therefore, if you're looking at this value as you move from one Project Detail Page to another, you may find that the value is displayed as blank or NULL instead of the No value that you expect.
The Approvals page doesn't roll up totals on grouping rows for the timephased data.

May 2016

https://support.microsoft.com/en-us/kb/3115088 DB Version (Content DB) - 16.0.4378.1000

When you change a resource in the resource center in Project 2016, you receive the following error message if the resource has an email language set:

The e-mail language for this resource is not valid.
Consider the following scenario:
- A project in which tasks have been published to team members is checked out.
- As a team member, you assign yourself to a task from the project.
- You add actual work to the task.
- You submit the task and work for approval.
- The new task is approved.
- The task on which the assignment was made, and it's deleted from the project and the project is then saved, and checked in.
In this situation, the update transaction is listed as successful even though the update isn't applied.
When you add an assignment to an existing task on a timesheet, you receive the following error message:

error loading.

This issue occurs if the project name has the "&" character.
Within the schedule web part, if you apply a filter on an enterprise field that has a lookup, no tasks are displayed for the project.
When a team member submits time against an administrative task and the task requires approval, an e-mail notification intended for the approver is sent to the team member.
When you switch to a different filter type on the Manage Queue Jobs page, you may receive the following error message if many jobs are present:

Sorry, something went wrong.
Incorrect availability or capacity is displayed on the Capacity Planning page. For example, 7.5h becomes 8h.
Resource Engagement data is deleted after a full publish of a project.
After you upgrade Project Server 2013 to Project Server 2016, large PWA sites become read-only.

Project 2016 Public Updates (January 2017 to date)

Brian Smith — Fri, 12 Feb 2021 14:50:30 GMT

This page lists all of the released Public Updates (PU) and Service Packs (SP) for Microsoft Project 2016, both Standard and Professional, and Project for Office 365.

From April 2016 the Office client updates are shipped 1st Tuesday.

Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack). I have noticed that in 2016 we don’t do a good job of displaying the version and in File, Account, About Project we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe – in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you are running a click to run installation - such as Project Pro for Office 365 see http://support2.microsoft.com/gp/office-2013-365-update for details of the update schedules - but the version numbers and fixes should be roughly in line with the CU releases below.

February 2021

No updates for Project

January 2021

https://support.microsoft.com/en-gb/help/4493159/january-5-2021-update-for-project-2016-kb4493159

Version 16.0.5110.1000

Consider the following scenario.

You have a project that has several thousand tasks.
You try to enter text into the task name field or edit the existing task name.

In this situation, you may notice a long pause, even as long as several seconds, before the text that you type begins to appear in the name.

December 2020

https://support.microsoft.com/en-nz/help/4486749/december-1-2020-update-for-project-2016-kb4486749

Version 16.0.5095.1000

When you use the ConsolidateProjects method with enterprise projects, and the AttachToSources parameter is set to False, if the code tries to insert the same project multiple times, it fails to run and the following error occurs:
"The file format is not valid.
Use a different file for this situation."
The value of the actual cost of work performed (ACWP) field for a given task may not update accordingly when the Status Date is changed.

November 2020

https://support.microsoft.com/en-nz/help/4486712/november-3-2020-update-for-project-2016-kb4486712

Version 16.0.5083.1000

In some cases when you view tasks, you may see a resource named Unassigned resource even though no resources are assigned to the task.
If you have a resource that has multiple cost rates, when you assign the resource to a fixed work task, the cost values, both scalar and timephased, are different from those if the resource doesn't have multiple cost rates.
Fixes an issue where Project may crash if you apply a Group by to a Resource Usage or Resource Sheet view and then insert the Can Level field to it.

October 2020

https://support.microsoft.com/en-ie/help/4484502/october-6-2020-update-for-project-2016-kb4484502

Version 16.0.5065.1000

On occasion, when you open the project, the % Complete on a Fixed Duration task that is 100% percent complete changes to a lesser value .
When a custom crafted Project XML file that contains assignment, but not accompanying TimephasedData data is opened, the associated task % Complete isn't set as expected.

September 2020

No updates for Project

August 2020

https://support.microsoft.com/en-us/help/4484477/august-4-2020-update-for-project-2016-kb4484477

Version 16.0.5044.1000

There's no warning information when you select the Refresh button under the Engagements tab, and you have new engagements that have not been saved. You should see the message "You have unsaved changes to some engagements. Refreshing will cause you to lose these changes. Do you want to continue refreshing the engagements?".
The TaskDependencies.Add method fails when the following conditions are true:

Project is connected to the server.
You define comma (,) as the decimal separator in locale settings and you have Project's display language set to, for example, German.
The project is saved to the server.
The Lag parameter of the method is specified, and its value doesn't equal a whole number. For example, 2,5 vs. 2.

From within Project Web App, when you open a project in Project Professional, you see an error message like the following:

"Project Professional must be running online before your project can be opened. Configure Project to connect to Project Web App and try again."

This problem occurs when your Project Web App URL ends with ".com" that's similar to "http://pwa.contoso.com".
After you save a project as a PDF or XPS file to a document library, the PDF or XPS file doesn't exist in the document library.

July 2020

https://support.microsoft.com/en-us/help/4484441/security-update-for-project-2016-july-14-2020

When the Predecessor or Successor field is edited in a Form view, an extra ProjectBeforeTaskChange event is fired.
When you change the project start and finish dates in the Project Information dialog box, the ProjectBeforeTaskChange event doesn't capture this property change.
Project may crash when you open a project .xml file.

June 2020

https://support.microsoft.com/en-us/help/4484399/security-update-for-project-2016-june-9-2020

Resetting or updating a baseline may change timephased Baseline Budget Cost or Work fields, and the baseline may not reflect the correct budget values.

May 2020

https://support.microsoft.com/en-us/help/4484345/may-5-2020-update-for-project-2016-kb4484345

Version 16.0.5002.1000

Changes to a task's timephased baseline work values are incorrectly blocked when the Only allow task updates via Tasks and Timesheets feature is turned on in the server. This update fixes this problem.

April 2020

https://support.microsoft.com/en-us/help/4484269/security-update-for-project-2016-april-14-2020

Users can't create external task dependencies in the Japanese version of Project 2016. For example, creating a predecessor from a task in one project to a task in a different project.
The OnUndoOrRedo event within a COM Add-in doesn't fire without first enabling a transaction.
Assume that the timescale is set up to have a middle and bottom timescale set to Quarters over Months. When you print the timescale together with the Hriji calendar, the ending month in the quarter may get clipped. For example, the "Oct" month is moved into the third quarter, and "Sep" is skipped completely.
The ProjectBeforeTaskChange event doesn't fire when you select the Inactivate button in the Scheduling group on the Tasks tab.
Consider the following scenario:
- A project is saved to Project Server.
- The project has a local custom field that has a lookup table.
- The CustomFieldGetValueListGetItem method is invoked on a local custom field that doesn’t have a lookup table.
- The project is closed, saved, and checked in.

In this scenario, the values that are in the local custom field on which the method is run may be lost.

March 2020

https://support.microsoft.com/en-us/help/3085454/march-10-2020-update-for-project-2016-kb3085454

Version 16.0.4978.1000

Project may take a long time to save projects. This is especially true of projects that have many custom field values. This causes delays in publishing, check-in jobs, and other related actions.

February 2020

https://support.microsoft.com/en-us/help/4484253/february-4-2020-update-for-project-2016-kb4484253

Version 16.0.4966.1000

Consider the following scenario:

You have a project that's saved to a server.
You have VBA code that is invoked from a custom ribbon button.
The code changes the project.
The code invokes the Save() method.
The code closes the project.
The project is opened later.

In this scenario, you find that the changes are not saved.

January 2020

https://support.microsoft.com/en-us/help/4484140/january-7-2020-update-for-project-2016-kb4484140

Version 16.0.4954.1000

When more than one cost rate exists on a resource, even if the cost rate is the same, cost values on assignments may be incorrect because of rounding. For example, a resource has a current rate of $1 per hour and assignment units that are set at 85 percent. Also, the assignment also has 25 hours of work, but the cost on the assignment shows $24.99 instead of the expected $25.00.
Consider the following scenario:

You have a project on Project Server that has server-based custom fields that have lookup table values, and you save the project as an MPP file.
You start Project while you are disconnected from the server profile, and you open the MPP file.

In this scenario, you see lookup values that are not expected. Because lookup table values are not stored in the MPP file, no lookup values should be displayed.

December 2019

https://support.microsoft.com/en-us/help/4484170/december-3-2019-update-for-project-2016-kb4484170

When you connect Microsoft Project to Project Server online, you receive the following error message:

"The server you are trying to access is using an authentication protocol not supported by this version of Office."

This update fixes the issue. After you install this update, you will be able to sign in to Project successfully.

November 2019

No updates for Project

October 2019

https://support.microsoft.com/en-us/help/4484116/october-1-2019-update-for-project-2016-kb4484116

Version 16.0.4912.1000

This update improves translations of timeline date formats in the Finnish language of Project 2016.

It also fixes the following issues:

If you type notes on the Notes page which is accessed through the Update Tasks form, the notes aren't saved.
Consider the following scenario:

A user goes to Windows Explorer and clicks on a file in order to directly open it in Project.
While the first user has the file open, another user opens the same project.

In this situation, the subsequent user sees a message that states "<File Name> is locked for editing by ' '. " The user name that already has the file opened should appear in the message but does not.

The Wrap Text function doesn't always automatically adjust row heights to enlarge cells as expected.
Importing resources to Project Server fails with an "An error occurred during import" error message. In some cases, you also see an "An enterprise calendar must be chosen for this resource" message for certain resources in the "Errors" column on the Validation Resources page of the import wizard.
After you replace a completed enterprise resource with a local resource, Project crashes while you save the project.

September 2019

https://support.microsoft.com/en-us/help/4475589/security-update-for-project-2016-september-10-2019

Version 16.0.4900.1000

This security update contains fixes for the following nonsecurity issues:

When you access various pane-based wizards in Project, such as Import Resources to Enterprise, Import Project, Task Inspector and Deliverables, you see an error message that resembles the following:

An add-on for this website failed to run. Check the security settings in Internet Options for potential conflicts.

This problem occurs when the ActiveX controls and plug-ins > Run ActiveX controls and plug-ins setting is set to Disable in the Internet security zone.
Consider the following scenario:
You have a test Project Web App site in your test environment and a production site in your production environment.
The two sites have the same site ID.
In Project, you have server profiles that point to both instances.

In this scenario, when you edit an enterprise calendar in PWA, Project starts. But you may find that the wrong calendar has been edited.

Note To fix this issue completely, you must install KB 3114852 together with this update.

August 2019

https://support.microsoft.com/en-us/help/4475544/august-6-2019-update-for-project-2016-kb4475544

Version 16.0.4888.1000

This update fixes the following issues:

Consider the following scenario:

You open a given project by using the Microsoft Installer edition of Project 2016.
You switch to a Task Usage type view.
The view in the timephased portion includes the ACWP and BCWP earned value fields.
On a summary task for a given period, you note the ACWP and BCWP values.
You open the same project with a subscription version of Project 2016 (also known as a click-to-run edition).
You view the same timephased ACWP and BCWP values during the same period.

In this situation, you notice that the subscription version shows correct values. For example, you view the timephased values on the project summary task for the period and in the MSI edition, you see:

$154.96, $0.00, $0.00

In the subscription version, you see:

$154.96, $9,660,884.17, $10,123,596.17

Consider the following scenario:

You have a test Project Web App site in your test environment and a production site in your production environment.
The two sites have the same site ID.
In Project, you have server profiles that point to both instances.

In this case, when you select to edit an enterprise calendar in PWA, Project starts. But you may find that the wrong calendar has been edited.

Note To fix this issue completely, you also need to install 3114852 together with this update.

July 2019

https://support.microsoft.com/en-us/help/4475518/july-2-2019-update-for-project-2016-kb4475518

Version 16.0.4873.1000

This update fixes the following issues:

When you assign a resource to tasks in several projects at less than 100% and the resource assignments share common dates, if you open all the projects at the same time, you find that the resource is overallocated.
When Project is connected to a server, the Visual Basic for Applications TaskDependencies.Add method fails if the Lag parameter is set to a non-integer value and the Decimal symbol on the local computer is set to a comma.

June 2019

https://support.microsoft.com/en-us/help/4464589/june-4-2019-update-for-project-2016-kb4464589

Version 16.0.4861.1000

This update fixes the following issues:

In projects that have many sub tasks under summary tasks and the sub tasks have a lot of work, you may find that the % Complete and Actual Duration values on summary tasks are not displayed correctly. For example, a project summary task that should show 88% complete shows 94% instead.
When projects are opened from XML files, custom lookup field values may be read-only.

May 2019

https://support.microsoft.com/en-us/help/4464541/may-7-2019-update-for-project-2016-kb4464541

Winproj Version 16.0.4849.1000

This update fixes the following issues:

Assume that the Flag1 field on a task is changed from Yes to No before the project is saved. The field value still displays Yes when you reopen the project.
You have selected the Japanese calendar format in the Label dropdown menu in the Gantt Chart timescale. However, the era is shown in English instead of Japanese.
Consider the following scenario:

You have a master project that has at least one sub project.
You have published both the master and the sub project.
You open the published version of the master project.
You view the sub project from the master project.

In this case, the sub project is the draft version of the project instead of the expected published version.

April 2019

https://support.microsoft.com/en-us/help/4464503/april-2-2019-update-for-project-2016-kb4464503

Winproj Version 16.0.4834.1000

This update contains the following fixes:

When you drag an assignment from one task to another in the Task Usage view, the assignment GUID (ASSN_UID) doesn't change accordingly. This could lead to a project publish failure if there is unapproved status pending.
After you add tasks to the Timeline view in a project, when you try to open the project in Project 2010 that you previously saved in Project 2016, you may receive the following error message, depending on how you manipulate the Timeline view:
Unsupported File. This file cannot be opened because it was created by a newer version of Project and may contain data not supported by Project 2010.

March 2019

https://support.microsoft.com/en-us/help/4462198/march-5-2019-update-for-project-2016-kb4462198

Winproj Version 16.0.4822.1000

This update contains the following improvements and fixes:

Adds support for the new Venezuelan currency symbol in Project 2016.
When you synchronize projects from Project 2016 to a SharePoint site, Project crashes. The crash occurs when a given task predecessor or successor field has 255 characters.
If you try to change the actual work value on a summary task when protected actual work is enabled, Project 2016 may freeze or crash.
If you enter a timephased actual work value for a material resource that is assigned to a fixed duration task, the Work and Assignment Units on the assignment don't display correct values. For example, assume that resource units (work) equals 100 and you enter the timephased actual work value as 23.27. The Work and Assignment Units display 99.94 instead of staying at the expected value of 100.
When you open projects in Project 2016, you receive the following message:
The operation cannot be completed because the source file contains invalid project data or the total number of rows would exceed the limit of 1,048,000 rows in a project. Validate the data in the source file, insert fewer rows, delete some rows, or consider dividing your project into subprojects to provide more space for tasks and resources.

February 2019

https://support.microsoft.com/en-us/help/4462134/february-5-2019-update-for-project-2016-kb4462134

Winproj Version - 16.0.4810.1000

This update fixes the following issues:

Assume that you open a project from a Project Server, that and you insert a project, and that during the insertion process, you deselect the Link to project option. Also assume that the project that you insert has custom fields. After you save, close and check in the master project, custom fields values that were previously associated with the inserted project may be missing.
Consider the following scenario:

You have a manually scheduled task where the duration is greater than zero.
The task is partially complete.
The Mark task as milestone property of the task is set.
You save the project in the XML format.
You open the XML version of the project.

In this case, the task displays a zero day duration and the task finish date equals the start date.

January 2019

https://support.microsoft.com/en-us/help/4461587/january-2-2019-update-for-project-2016-kb4461587

Winproj.exe version 16.0.4795.1000

Improvements and fixes

This update contains the following improvements and fixes:
- You assign a resource to a task.
- In the Task Usage view, you display the Actual Work and Actual Overtime Work fields.
- On the assignment, you type 2.33h in the Actual Work field and type 3.33h in the Actual Overtime Work field.

After you edit and save a project, the values for some Enterprise Resource Custom fields on the project are lost.
Consider the following scenario:

When you compare the actual work on the task with the actual work on the assignment, the values are inconsistent. For example, the task shows 5.66h and the resource assignment shows 5.67h.

In some situations where your project is saved to Project Server and where user updates are protected, you may not be able to indent or outdent a task. Instead, you receive the following error message:

Change would modify work entered by a team member. We can’t make that change because Project Web App is set to only allow actual work to be entered by team members through Timesheets or My Work.

When you edit resource properties on local resources while editing from a master project, changes are not saved successfully.
You can't create recurring daily exceptions whose periods are more than 1 day and the intervals overlap. As an example, you create a recurring exception that begins on the first day of the month, is scheduled every 28 days and ends after three months. If you try to create another recurring exception that begins the second day of the month, is scheduled every 28 days and ends after three months, the action is blocked.
In the Czech language, a corrected translation for Committed Work is made.

December 2018

https://support.microsoft.com/en-us/help/4461540/december42018updateforproject2016kb4461540

Winproj.exe version 16.0.4783.1000

Improvements and fixes

This update fixes the following issue:Consider the following scenario:

You make changes to a project.
You save the project.
You look at the progress indicator in the lower-right part of the screen to determine the progress.

In this situation, the indicator starts by saying that it is "Saving" the project. Then, it says that it is "Synchronizing data to server...". After this, however, the expected progress and final "Save completed successfully" details are not displayed

November 2018

https://support.microsoft.com/en-us/help/4461478/description-of-the-security-update-for-project-2016-november-13-2018

Winproj.exe version 16.0.4771.1000

Improvements and fixes

This security update contains improvements and fixes for the following nonsecurity issues:

When you save a project as an XML file, Project 2016 may crash. This issue can occur after you install the April 3, 2018, update for Project 2016 (KB 4018320).
When you make changes in a project and then save it, the custom field lookup table values are also saved even though they have not been changed. Therefore, it takes longer to publish the project. And while the publishing processes, other actions such as viewing the tasks view in Project Web App may be slow.
Assume that you update cost or work data for a subtask in Project 2016. When you save a baseline on the task and choose the option to roll up the baseline data to all summary tasks, the baseline data for task summary tasks within the sub project is rolled up but not to the inserted project summary tasks and summary tasks in the master project.

Consider the following scenario:

You have a SharePoint document library.
The document library list experience is set to the new "modern" experience.
The document library versioning settings require checkout.
You have a Project file stored in the library. You open the file from the library by using Project 2016.

In this situation, you find that the expected "check out required" prompt isn't displayed, and therefore you can't respond. This means that if you make changes to the project and save, Project tells you that the changes can't be saved because checkout is required.

October 2018

https://support.microsoft.com/en-us/help/4461443/october-2-2018-update-for-project-2016-kb4461443

Winproj.exe version 16.0.4756.1000

Improvements and fixes

This update makes sure that the Japanese era name in Project 2016 is displayed correctly when a new era begins.

September 2018

No package

August 2018

https://support.microsoft.com/en-us/help/4032238/august-7-2018-update-for-project-2016-kb4032238

Winproj.exe version 16.0.4732.1000

Improvements and fixes

Assume that you open a project from Project Server. You change a local custom field's lookup table, then you save, close and reopen the project. In this case, values from the lookup table that were previously entered for various tasks may be lost even though the values aren't deleted from the lookup table. Additionally, some parts of the lookup table definition may be missing.

July 2018

https://support.microsoft.com/en-us/help/4022217/july-3-2018-update-for-project-2016-kb4022217

Winproj.exe version 16.0.4717.1000

Improvements and fixes

Assume that you apply a different view (such as the Gantt Chart view) to a project that has the Network Diagram view applied. When you apply the Network Diagram view again to the project, the nodes are lost and the dependency lines are drawn to random places. In some cases, Project may crash.
The actual work values of a task and the assigned resource are inconsistent. For example, the task shows actual work as 5.66 hours and the assignments shows actual work as 5.67 hours.
Task EAC value is not calculated as expected for a project in Project 2016. For example, when you compare the EAC field in a project that's opened in Project 2010, there is a value difference of anywhere from a few cents to several thousand dollars (assuming the dollar currency).
When you select the Open button from the Project Web App resource center without any resource selected, you see the message "To perform this action, you need to have Project Professional 2016 installed." In this case, if you dismiss the message, you cannot edit enterprise resources.
If you use a 32-bit version of Project and you use the Update Project function to reschedule uncompleted work, you may not see an expected Planning Wizard page that tells you that Project did not reschedule certain unscheduled tasks because of a constraint that's applied to them.
The actual finish date that you enter is ignored for a task if the task has a Finish No Earlier Than (FNET) constraint and the actual finish date is earlier than the FNET constraint.

June 2018

https://support.microsoft.com/en-us/help/4022164/june-5-2018-update-for-project-2016-kb4022164

Winproj.exe version 16.0.4705.1000

Improvements and fixes

Consider the following scenario:

You create a project template that has a task and resource assigned to it where the Assignment Units value is set to 0%.
You create a project in Project Web App in which the template is associated with the selected enterprise project type.

In this situation, the assignment on the task shows the Assignment Units value as 100% instead of 0%.

When you insert a project into a master project and clear the link to project check box, you may receive the following error message:

These tasks can't be linked because they're already linked through another task chain.

After the insertion process is complete, for a given task, it displays the same predecessor or successor for two times.

If you save a project that's created by Project 2002 or Project 2003 to a project server, the MSP_TASK_CUSTOM_FIELD_VALUES_SHADOW database table grows large.
Assume that you have a task that has a cost resource assigned and there is no work or material resource. When you split the task, the remaining cost is lost.
When a Project based COM add-in executes the FileSave method, Project 2016 may crash.
When you try to open an enterprise calendar while it is connected to a Project Web App instance by using Google Chrome, you receive the following error message:

Sorry, we were unable to open your project. Please try again. If this happens again, contact your administrator.

Assume that you add a resource to your project where the default booking type for the enterprise resource is set to Proposed. When you change the booking type of the resource in the project to Committed, and then save, close and reopen the plan again, the booking type is reverted to Proposed.
When you delete a Gantt chart type view that has a drawing in Project 2016, Project 2016 may crash. Related to this, when you delete a drawing in a Gantt view, you may see the drawing is deleted from another view.

May 2018

https://support.microsoft.com/en-us/help/4018373/may-1-2018-update-for-project-2016-kb4018373

Winproj.exe version 16.0.4690.1000

Improvements and fixes

When you try to perform an action, for example, applying a font or a background format to a cell, Project may crash.
Consider the following scenario:

You create a fixed duration task that is 100% complete.
You create a custom calendar and add a one-day exception in the range of task duration.
You change the task calendar to the custom calendar, and then you see that the duration reduces by one day.
You save and then close the project.
You reopen and recalculate the project, and then check the finish date.

In this situation, the actual finish date is shifted to one day later.

When projects are opened from a server, resources names aren't always seen. In addition, when you use the Build Team dialog box, you see the same thing where some resources don't have names. After you apply this update, the Resource Names are visible to the user.
Consider the following scenario:

You create a local project with some tasks and save it as a file.
You create a second project, you have the first project share resources from it and you save it as a local file.
You assign the resource to the tasks.
You save the projects.
You upload the project file and shared resource file to a SharePoint Online document library.
You open the project file from the document library, and you receive the message:

This file shares resources from a resource pool

After you select OK, the shared resource file is also opened.
You add a new task to the project file and assign it to a resource.
You save the project file and close both files.

In this situation, when you reopen the project file, the link to the shared resource file is lost.

Consider the following scenario:

As a team member, you open your timesheet and enter work for two adjacent days.
On the first day, you set the actual work value back to zero.
On the first day, you set 8 hours of non-working time on an administrator task (for example, vacation).
You send a status update for approval.
You open the previous week timesheet.
You enter actual work values.
You send the timesheet for approval and the status manager approves it.

In this case, the actual work that's entered on the second day of the two days moves to the first day. The actual work should not move when the status update is applied to the project.

April 2018

https://support.microsoft.com/en-us/help/4018320/april-3-2018-update-for-project-2016-kb4018320

Winproj.exe version 16.0.4678.1000

Improvements and fixes

When a task custom field formula is applied, and it also uses the formula for summary and grouping rows, the summary row displays "#ERROR". In addition, the grouping row displays incorrect values.
The Change Working Time dialog box enables you to select a date and to see the working shifts for that day listed in the Working times section. For example, a date shows working shifts of 8:00 AM to 12:00 PM and 1:00 PM to 5:00 PM. In some cases, you may be unable to see all the defined shifts for the given date because it's hidden behind the text that tells you the date's base calendar.
You open a project from the Project Center while using the Google Chrome browser. Then you see the following error message:

Sorry, we were unable to open your project. Please try again. If this happens again, contact your administrator.

Consider the following scenario:

You have a project plan that has many tasks with long durations.
You may have some baselines established.
You save the project plan to an XML file.
You open the XML file.

In this case, if you use the 32-bit version of Project, it may crash. If you use the 64-bit version of Project, you notice that it takes a long time to open the file and Project uses many gigabytes of memory. When you look at the size of the XML file, you'll also notice that it is hundreds of megabytes in size.

Note To fix this issue, you also have to set the value of the registry key XmlDisableTimephasedSplitByDay to 1. See Registry information for more information.

This update also contains the following improvement:
- The build number of Project that created the XML file.
- Project, task, resource and assignment GUIDs.
- Names of views.
- Names of tables.
- Names of filters.
- Names of groups.
- Names of data import and export maps.
- Names of reports.
- Names of drawings.

When you save a project to the XML format, the following pieces of new information are exported:

Project exports these pieces of information but does not read them when you open or merge an XML file. Therefore, you can't, for example, add or change view names within an XML file, and have Project read and understood the information.

Note If you do not want your XML files to have this new information, you can set the following registry key:

Location: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\MS Project\Options\Save\
Type: DWORD
Name: SimpleXmlexport
Value: 1

March 2018

https://support.microsoft.com/en-us/help/4011734/march-6-2018-update-for-project-2016-kb4011734

Winproj.exe version 16.0.4666.1000

Improvements and fixes

If your project has manually scheduled tasks, and server notifications and reminders are turned on, you may receive unnecessary modified task notifications.
After actual work from a status update is applied to a task, the work values may not appear in Project as expected. For example, you report 4 hours on a day, but when you open the project, you don't see the time-phased actual work value. This issue may occur when you assign a new resource to a task that is completed.
When the Status field is referenced in a task custom field formula, other calculations may go slowly. For example, when you enter time-phased work data, it takes several seconds before you take back control.
When you add a resource to a project, the Booking Type field of the resource is ignored. For example, if the default booking type for the resource is set to "Proposed", when you add the resource to your project, the booking type is displayed as "Committed".
When you manipulate Views and other elements within the ProjectBeforeSaveBaseline event code in Project VBA, Project may crash after you save a baseline.
When you open and edit a project, then save back to Project Server 2016, you may see an error message that has some of the following elements in it:

ActiveCacheQueuedMessageExecutionError

error="System.InvalidCastException: Specified cast is not valid”

When you open an XML file that has time-phased baseline data in Project 2016, the time-phased data on assignments may be incorrect. For example, the time-phased work hours that you entered are 2, 2, 2, 2. However, they are displayed as 2, 0, 0.58, 1.42, 0. The totals stay the same.
When a task custom field formula is applied and it also uses the formula for summary and group rows, the summary row displays “#ERROR”. In addition, the grouping row displays incorrect values.
Consider the following scenario:

You save a baseline in your project, and then you save the project.
You save another baseline and you save the project, close it, and check it in.
You query the database and view the MOD_DATE property for the given baselines.
Another user opens the project and saves a different baseline.
You query the database and check the MOD_DATE property for the three baselines.

In this situation, you find that the values of the MOD_DATE property for the baselines are the same. They should be different and reflect the date and time when you saved the baselines.

February 2018

https://support.microsoft.com/en-us/help/4011672/february-6-2018-update-for-project-2016-kb4011672

Winproj.exe version 16.0.4654.1000

Improvements and fixes

You cannot assign a cost value to a cost resource through the Assign Resource dialog box if the Windows regional setting is set to Norwegian. Instead, you see the following error message:

This field only supports numbers.

If you’ve only typed numbers, try entering a smaller number with up to two decimal places.

Consider the following scenario:

You are using the German version of Project 2016.
You set the date format to use Weeks. For example, “3/W05".
You create an automatically scheduled task.
You modify either the Start or Finish field to change the date.

In this scenario, you receive the following error message:

The date you entered isn't supported for this field. Dates must be between January 1, 1984, through December 31, 2149.

Enter the date in the correct format, eg., 15/06/00 or 15 June 2000

Consider the following scenario:

You have a Project Web App site and Project Professional 2016 in your organization.
You create some custom project fields and add them to your project detail pages (PDPs).
In Project Web App, you create a new project and add values to these custom fields.
You open the project in Project Professional 2016, make a change and then save the project.
You open the project in Project Web App and view the custom field values on the PDPs.

In this situation, the values for these custom fields may be lost.

Consider the following scenario:

You have a task that has a resource assigned.
The task has a split in it. For example, there's a week of work, a week where no work exists and then a final week that has work.
In the timesheet for this task, you enter hours on the task so that the work is completed up to the date where the split begins.
The timesheet is submitted and then the status update is approved.
After that, the project is opened in Project Web App and the task finish date is adjusted to a date that's after where the actual work is completed. For example, the actual finish date is set to the middle of the week where there's no work.

In this situation, the actual work is spread over the whole duration.

January 2018

https://support.microsoft.com/en-us/help/4011633/january-2-2018-update-for-project-2016-kb4011633

Winproj.exe version 16.0.4639.1000

Improvements and fixes

The grouping rows that are applied to Gantt views in projects may not display values for given fields that have formula calculations.
Consider the following scenario:

You have two projects.
You assign two tasks from the two projects to a same resource.
You use the Capacity Planning tool to check the two projects, and you see that a red over allocation icon shows in the indication column.
You change the duration to a longer period.

In this scenario, the over allocation icon in the indication column stops working.

When you operate on a project in Project 2016, you receive the following error message:

This issue occurs if the assignment maximum unique ID of 1048576 is exceeded.

The progress point shape (the point on the progress bar) for some tasks may not be drawn at an expected position in Project 2016.

December 2017

https://support.microsoft.com/en-us/help/4011573/december-5-2017-update-for-project-2016-kb4011573

Winproj.exe version 16.0.4627.1000

Improvements and fixes

In the Chinese version, Project 2016 crashes when you open the Change Work Time dialog and scroll the calendar to date between 1995 and 2011.
When system events such as Group Policy updates are applied, Project 2016 may flicker.
When visual reports are generated from the context of a master project, the results are inconsistent and may fail completely in certain cases. For example, if you select the Earned Value Over Time Report chart, you may find that not all the costs from the sub projects are included in the pivot chart, and you may receive the following error message when you create a visual report:An unknown error has occurred. An error occurred and the requested action could not be completed at this time.
Consider the following scenario:

You open a project from Project Server.
You save the project by using the Save for Sharing functionality.
You delete data from the project. For example, you delete an assignment on a task.
You save the project back to the server.

In this situation, you may find that there is still data for the deleted element in reporting database. For instance, you still see actual work in the project.

November 2017

https://support.microsoft.com/en-us/help/4011227/november-7-2017-update-for-project-2016-kb4011227

Winproj.exe version 16.0.4615.1000

Improvements and fixes

When you save changes to a master project that's stored in a SharePoint document library, subprojects switch to read-only mode and aren't saved accordingly.
If you have Task Path feature enabled, Project 2016 may freeze when you select a task within your project.
After you set a timescale label to None in a timescaled view such as the Gantt chart, all labels for other timescale tiers disappear, and the label for the tier that you have selected to hide does not disappear.
Consider the following scenario:

You have a task in Project 2016 that is set to fixed duration and is effort-driven.
You have a resource assigned to the task.
Within a Task Form type view, you assign an additional resource to the task and specify the units for the resource to any value other than 100 percent.

In this scenario, the unit setting for the additional resource is 100 percent, and the name disappears.

Consider the following scenario:

You save a baseline in your project.
You query the database and check the MOD_DATE property for the given baseline.
You open the project and save a different baseline.
You query the database and check the MOD_DATE property for the two baselines.

In this scenario, you find that the values of the MOD_DATE property for the two baselines are the same. They should be different and reflect the dates on which you save the baselines.

October 2017

https://support.microsoft.com/en-us/help/4011141/october-3-2017-update-for-project-2016-kb4011141

Winproj.exe version 16.0.4600.1000

Improvements and fixes

Consider the following scenario:

You decide to edit a project in Project Web App or Project 2016.
You enter time-phased Actual or Actual Overtime work on an assignment and notice that it's no longer scheduled the way that you expect it should be.
You adjust the assignment start dates and finish dates to reflect the schedule that you have expected.

In this situation, additional actual work that you don't enter may be applied to the assignment unexpectedly.

Assume that you have a Project Server 2016 and Project Professional 2016, when you save a project that's connected to the Project Server, you may receive the following error message:

Change would modify work entered by a team member

We can't make that change because Project Web App is set to only allow actual work to be entered by team members through Timesheets or My Work.

This issue occurs after the July 5, 2017, update for Project 2016 (KB3203476) is installed.

September 2017

https://support.microsoft.com/en-us/help/4011101/september-5-2017-update-for-project-2016-kb4011101

Winproj.exe version 16.0.4588.1000

Improvements and fixes

When you open certain XML files, Project 2016 may crash. Additionally, in some cases, the durations of tasks may differ from those in the earlier versions of Microsoft Project.

August 2017

https://support.microsoft.com/en-us/help/4011034/august-1-2017-update-for-project-2016-kb4011034

Winproj.exe version 16.0.4573.1000

Improvements and fixes

Changes the word Level to the word Equalize in resource leveling scenarios for the Danish version of Project 2016.

This update fixes the following issues:

When you use the Save Baseline feature to copy a baseline from one to another (for example, from baseline 1 to baseline 5), the time phased cost and work values for budget resources are not copied.
The Status value may be incorrect at the summary task level. For example, a summary task's status is displayed as Late even though all of its subtasks are calculated as Complete, Future Task, or On Schedule.

July 2017

https://support.microsoft.com/en-us/help/3203476/july-5-2017-update-for-project-2016-kb3203476

Winproj.exe version 16.0.4561.1000

Improvements and fixes

Assume that you create a SharePoint Tasks List in Project Online. After you change the indent of the tasks in Project 2016 and synchronize the tasks with SharePoint, the indent setting isn't synchronized correctly.

If the task finish date is changed in the schedule web part, the actual work is spread unexpectedly.
After you replace a local resource with an enterprise resource, the actual work is transferred to the enterprise resource even though it's a protected work.
When you select a task in the Task Name column in Project 2016, Project 2016 crashes if the first column that's locked of the table is Task Name, and one or more tasks are indented.
After you import task, resource, and assignment information from an Excel worksheet in Project 2016, the work value is ignored.
When you open an XML file that has comma decimal characters for numeric values in Project 2016, the numeric values is lost because the numeric values are read incorrectly if Project 2016 uses dot decimal characters.
Cost precision is lost after you copy and paste a task in a project. For example, if the cost on the source task is $76.85, it will become $76.65 on the pasted task.

June 2017

https://support.microsoft.com/en-us/help/3191934/june-6-2017-update-for-project-2016-kb3191934

Winproj.exe version 16.0.4549.1000

Improvements and fixes

Improves the translation of Project 2016 in multiple languages.
Pasting into the Resource Namesfield within the Task Usage view allows you to paste the same resource name more than once. This creates a duplicate and causes problems when you apply status updates from Project Server.
Improves translation for the French version of Project 2016.
This update fixes the following issues:
- A project manager publishes a task to a team member.
- The team member in either a timesheet or in tasks within Project Web App reports work that's earlier than what was scheduled. For example, 8h of work was scheduled on Wednesday but 8h of actual work was reported and submitted for Monday.
- The status manager approves the update.
- The team member zeros out the actual work and moves it to a later date.
- The status manager approves the update.
- The project is opened in Project Server.

Consider the following:

In this situation, the task's actual start date still reflects the set with the earlier update instead of the new update where the actual start date is later.

When you open a project from Project Server, you incorrectly see the following error message:

This project cannot be opened in read-write mode because a previous project checkin for this project is not complete.

Assume that you open a project in Project Professional 2016, and you are prompted to apply status updates. If you select to apply status updates, the process never finishes, and the project remains in a temporarily unusable state.
When you open an XML file that has timephased baseline data in Project 2016, the timephased data appears incorrectly. For example, on Saturday, the timephased baseline work should appear as 0.9h, but it instead appears as 0.88h.

May 2017

https://support.microsoft.com/en-us/help/3191870/may-2-2017-update-for-project-2016-kb3191870

Winproj.exe version 16.0.4534.1000

This update fixes the following issues:

After you change the Physical % Complete value on a subtask, the value is not calculated as expected on the related summary task.
When you open a project from a SharePoint list, Project 2016 may crash as the synchronization process begins.
When you print review project data, you may find the text that is wrapping in a cell appears differently than it does in the view. For example, text may be missing or the location where the text breaks from one line to the next is different.
If a cost and a work resource are assigned to the same task, you may not be able to change the task's status manager.

April 2017

https://support.microsoft.com/help/3178708

WinProj.exe version 16.0.4522.1000

This update includes the following improvements and fixes:

In some circumstances, leveling on a week-by-week basis pushes tasks to the end of time (12/31/2149). Meanwhile, the leveling operation takes a long time to complete, and Project 2016 is unresponsive during that time.
After you upgrade from Project 2013 to Project 2016, manually scheduled tasks are not updated correctly. For example, you create a project that has a manually scheduled task by using Project 2013 and open it from your server by using Project 2016. Then you update the task's duration and save the project. However, the change does not appear in PWA or when it's opened again in Project 2013.
The Links Between Project dialog box incorrectly displays "File Not Found" in the Differences column for projects that exist and are available on your Project Server.
Consider the following scenario:
- October 2016 security monthly quality rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
- October 2016 Security Only Quality Update for Windows 7 SP1 and Windows Server 2008 R2 SP1
- Task Inspector
- Import Project Wizard
- Import Resources Wizard
- Deliverables

You install either of the following updates that target Internet Explorer.
After this, you use one of the following features in Project:

In this situation, the given feature pane isn't displayed as expected.

When you use the Copy Timeline function in Project 2016, the timescale doesn't align correctly with where the bars are scheduled and shown. For example, you have a task that begins January 23, 2017. However, the timescale marker that shows January 21, 2017 appears later than the start of the task.
Removing the start date from a resource assignment may cause the start date of the task to reschedule to "as soon as possible", and this may cause huge leading splits on the assignment.
When you open the Build Team dialog box in Project 2016 and enable the Online status next to name display option, Project may crash.
When you assign a task to a resource with a max units 0, the assignment units is unexpectedly assigned as 100%.
When you edit an assignment finish date from a Task From type view, Project 2016 may crash.
When you open a project file from a SharePoint site through the Recent menu in Project 2016, the file is opened with read/write permission, and you are not prompted to check out the project even though the Require documents to be checked out before they can be edited? SharePoint option is enabled.

March 2017

https://support.microsoft.com/help/3178669

WinProj.exe version 16.0.4510.1000

This update fixes the following issues:

The Visual Basic Applications ScreenUpdating property does not work as expected in Project 2016. Instead of freezing the screen content when the code runs, the screen continues to update. This produces screen flicker and causes the code to run slower.
Assume that a project manager opens a project in Project 2016 that has been successfully used with Project 2013. In this situation, when actual work values are observed in the Task Usage view, it is found that, for some resources, the actual work has been moved from the dates on which it was entered.
In the Progress Lines dialog box, you select to display progress lines in relation to the baseline plan instead of the default actual plan. In this situation, the progress line does not draw as expected.
When you open an .xml file within the Import Wizard and select the As a new project option, Project 2016 may crash.
Assume that you open a project plan, and transfer local resource custom field lookup table values to an enterprise resource enterprise field. Then you save the project plan to a Project server. In this situation, some custom enterprise resource lookup table values may be lost.
In some cases, enterprise custom field data may be lost from a project after a status update has been applied, and the project is then opened in Project Professional 2016.

February 2017

https://support.microsoft.com/help/3141514

Winproj.exe version 16.0.4498.1002

This update fixes the following issues:

When you open a project that has a milestone task, an actual start date may be added unexpectedly even though it did not have a date the last time it was saved.
A task's % Complete value is also updated unexpectedly after you update the % Work Complete value.
The Cost Performance Index (CPI) value on a summary task may incorrectly display a value that's similar to -99999999999999.
When you print a project view such as the Gantt chart one by one page in Project 2016, you may find that the row heights are taller than expected, that column widths are narrower than expected, and that font sizes are smaller than expected.
When you open a project and save it, the project ownership may unexpectedly change to you.
Consider the following scenario:

You are a user who edits projects in Project Professional or Project Web app.
You have been denied the Save Protected Baseline permission.
You open a project from Project Server.
You copy and paste a task to another location in the project.

In this situation, the protected baseline (baseline 0 – baseline 5) data is pasted. Because you don't have permissions to create baseline data, the paste process should not replicate this detail from the copied task and its assignments.

January 2017

https://support.microsoft.com/en-us/kb/3141459

Winproj.exe version - 16.0.4483.1000

Fixes the following issues:

Assume that you create and apply a grouping in a sheet type of view such as the Gantt Chart view in Project 2016. When you print the project, the horizontal bands appear. However, the vertical parts that tie together the top and bottom of the band don't appear.
In Project Professional, you can now add the Locked field to a task view to facilitate closing tasks to update.In Microsoft Project Server, team members have project tasks assigned to them and they report their status (the work that they have performed) on these tasks. In some cases, a project manager may want to close these tasks to update so that team members are prevented from submitting status but still have visibility to the tasks.To achieve this, previously the project manager had to edit the project in Project Web App and set the Locked field on the given tasks in the project. Now, in order to lock or close tasks to update, the project manager can open their project in Project Professional and insert the Locked field into a task view where they can set the value to Yes or No as appropriate.
The Last Modified date in the Project Professional Open dialog box does not reflect the current time zone. For example, your time zone is Pacific Time (UTC-08:00) and the Last Modified date shows 09:15 instead of the expected 01:15.
Assume that you save a project that has timephased baseline data to the XML format. When you open the XML file, the timephased baseline data is incorrect.
When you save a baseline for a selected task, the task or assignment baseline values may be incorrectly rolled-up to and displayed on the related resources.
When you apply status updates in PWA, actual work is added to some assignments unexpectedly. For example, suppose that you have an assignment that has 35 hours total work and the status update is to apply 9 hours. When you view the results in Project Professional, you find that the assignment is unexpectedly completed. Meanwhile, the total work and the actual work have increased to 400 hours.
When you open a project from a SharePoint document library through a direct URL, the project is opened as checked-out even though the Require documents to be checked out before they can be edited? setting is enabled.

Project Server 2010 Cumulative Updates RTM to June 2012

Brian Smith — Mon, 25 Mar 2019 21:42:49 GMT

This page lists all of the released Cumulative Updates (CU), Service Packs (SP) and infrastructure update for Project Server 2010 from RTM to June 2012. From February 2015 onwards all fixes are shipped in Public Updates PU). From March 2015 client updates available via Windows Update and Download Center, server updates only via Download Center. They are listed in reverse date order - newest at the top. The CUs are normally available in a 'rollup' package that also includes the SharePoint Server and SharePoint Foundation CUs as well as one (sometimes two) 'Individual' packages which just contain the Project Server fixes. Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack). In some months a rollup package did not get released. I have also recorded the version you will see in the dbo.Versions table in the Project Server database after applying each update and running the configuration wizard. In some months this does not get incremented if there were no database changes.

June 2012

Rollup - http://support.microsoft.com/kb/2598355 Individual - http://support.microsoft.com/kb/2598375 and http://support.microsoft.com/kb/2598376 Database Version - 14.0.6122.5000

Consider the following scenario:
- You create a user account in Project Web Access (PWA), and you enable Exchange Synchronization for the user account.

- You create a new plan that contains many tasks in Project 2010.

- You assign the user account to all the tasks.

- You save and then publish the plan in Project Server 2010.

- You log on to the mailbox of the user account that you created to see whether the task list is synchronized.

In this scenario, duplicate tasks are created in the task list in Microsoft Outlook.

You cannot edit security categories that contain more than 1000 projects when one or more projects in the security categories are archived and then renamed.
You cannot submit a project to the next stage of a demand management workflow in Project Server 2010.
When a team resource tries to self-assign a task, the task is still displayed in the task list and is not assigned correctly to the team resource.
When you change a project summary task in Project Server 2010, the timephased budget cost information for cost resources is lost.
When Active Directory Domain Services (AD DS) contains an inactive user, the Project Server security group synchronization process fails.
Timephased remaining costs and actual costs are calculated incorrectly in the report database in Project Server 2010.
When you set a custom date field to NA in Project Server 2010, the date 1/3/84 is displayed unexpectedly in the field.
Values in a custom field are not displayed in Project Professional 2010 or in Project Web App (PWA). This issue occurs when the custom field can contain multiple values. However, the values are displayed in Project Professional 2010 or in PWA after you clear the local project cache.
After you save a value in the cost formula field on a Project Detail Page (PDP), an incorrect value is displayed. This issue also occurs in the percentage formula field.
After you accept status updates for a project in Project Server 2010, the project displays actual work that is submitted through PWA as an incorrect decimal value. For example, a project displays .48h as the actual work even though you submitted .5h as the actual work.
Assume that you self-assign a task in Project Server 2010, and then you open a new timesheet that contains an assignment without any planned work. In this situation, the task enterprise custom field does not populate values as expected.
Assume that you edit a task by using the Schedule Web Part in the Project Center. When you try to close and update the task, you receive the following message:
This project is currently checked out. No edits can be made to it while it is checked out.
When you update the status of certain projects, the status update job fails. Additionally, you receive the following error message:

Status approval internal error: StatusingInternalError (3116)
When you publish a Project Detail Page (PDP) in Project Server 2010, the values in an enterprise custom field are lost. This issue occurs even when you do not change the project schedule in the PDP.
Buttons on the ribbon are disabled for certain tasks in the Approval Center. This issue is caused by a script error that occurs on the Approval Center page.

April 2012

Rollup - http://support.microsoft.com/kb/2598152 Individual - http://support.microsoft.com/kb/2598272 Database Version 14.0.6119.5000

When a project manager approves status updates, and then publishes a project plan from Project Web App (PWA), the field that is calculated based on a cost rate table contains an incorrect value.
Assume that you configure an auto-publish rule for projects in Project Server 2010. When a project is checked out, the auto-publish rule does not publish the project as expected. Additionally, all successive auto-publish jobs are skipped, and other projects that meet the auto-publish rule are not published.
You cannot change the user logon account information to an account that does not exist in the Manage Users page. Additionally, you receive the following error message:

The NT account specified is invalid. Check the spelling of the user name, verify that a valid domain name was included, and check that a duplicate domain was not used.

Note If the user account is inactive, the user account validation should not occur, and you should not receive the error message.
It takes a long time to create a portfolio analysis in Project Server 2010 when the Analyze time-phased project resource requirements against organizational resource capacity check box is selected.It takes a long time to display the Resource Availability page when you click the Resource Availability button on the Resource Center view.
When you try to access a Project Center view that has a filter which filters by a value field of a custom lookup table, you receive the following error message:

Unknown Error

When you visit a project detail page in PWA, you see duplicate values in fields that are associated with a lookup table.
Assume that you back up a project that contains a resource plan. After you restore the project, the resource plan disappears.
Project Server 2010 deletes resources and assignments from projects unexpectedly.

February 2012

Rollup - http://support.microsoft.com/kb/2597152 Individual - http://support.microsoft.com/kb/2597138 Database Version - 14.0.

Consider the following scenario: When you use the Project Server Interface (PSI) to update an enterprise custom field on a local resource, the values in the enterprise custom field that are associated with the local resource are lost.
- You set the system time zone to a setting between UTC and UTC +12:00 on a Project Server 2010 server.
- You set a date period for a project in the Date Range dialog box by using Project Web App (PWA). For example, you set the Date Range when you edit a resource plan.
- You view the date value on the Date Range group on the ribbon.
In this scenario, the date value that is displayed does not match the date value that you set. Additionally, the date period is one day earlier than the date period that you set.
Assume that you create a timesheet that contains a task. The task has a Flag enterprise custom field that is set to Roll down. In this situation, the timesheet is not created successfully. Additionally, you receive the following error message:

The Timesheet creation failed, because of problems with the project server or with data validations, such as resources not being valid work resources or users. Check your environment, and then try again.

Then, you delete the timesheet. In this situation, you receive error 24011 for the Reporting (Timesheet Delete) queue job.
When you add a task to a timesheet in a project whose name contains an ampersand (&), you receive the following error message:

An unknown error has occurred.
Assume that a status manager rejects some updates to a user's timesheet and publishes the project plan. Then, the user resubmits the rejected values. In this situation, the timesheet is displayed as approved. However, the re-submitted updates do not appear in the approval center or in the project plan.
When a resource pool is resynchronized with Active Directory, the Exchange Server Synchronize Tasks property flag for users is reset. Therefore, users are not synchronized with the Exchange Server until the Synchronize Tasks settings are re-enabled.
When you try to set actual work for a manually scheduled task on a nonworking day, the actual work values that are displayed in PWA, such as in My Tasks, may not appear. For example, five hours of actual work entered on Sunday may be displayed as zero hours in My Tasks.
The Task Hierarchy field in a timesheet view is not populated until the timesheet is saved. This issue occurs when one of the following conditions is true: Assume that you have a fixed duration task that has more than one enterprise resource assigned. Then, a user updates the actual work of a resource in the task by using Project Web Access (PWA). In this case, the task-level % Complete and Actual Duration values are not updated correctly when you view the task in Project Professional.
- An existing task that is assigned to a resource has no planned or actual work during the period of a newly created timesheet.
- A new task is assigned to a resource, and a user opens an existing timesheet period that contains the new assignment.
When you publish projects, you receive the following error message in the queue:

Queue Error: General Microsoft.Office.Project.Server.BusinessLayer.Queue.Message: ProjectPublishFailure (23000). Details: id='23000' name='ProjectPublishFailure' uid='<uid>' projectuid='<projectuid>' messagetype='Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.UpdateSRAMessage: projectUid = <projectuid>' messageID='179' stage='' blocking='Block'. Queue: GeneralQueueJobFailed (26000) - ProjectPublish.UpdateSRAMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='<uid>' JobUID='<jobuid>' ComputerName='<computername>' GroupType='ProjectPublish' MessageType='UpdateSRAMessage' MessageId='179' Stage=''. For more details, check the ULS logs on machine <computername> for entries with JobUID <jobuid>.
Assume that you have a multiple-value custom field that is referred from a formula in an enterprise project custom field. In this situation, when the formula is recalculated on the server, you do not receive a list of all selected values. Instead, you receive only the last value. For example, a multiple-value custom field displays the values A1, A1.1, C, C1.1, and C1.2. However, the formula on the server returns the value C1.2 only.

December 2011

Rollup - http://support.microsoft.com/kb/2597015 Individual - http://support.microsoft.com/kb/2596997 Database Version - 14.0.6114.5000

Consider the following scenario: Assume a PWA site administrator disables the Allow future time reporting setting on a Project Server 2010 server that has single entry mode enabled. In this situation, when you submit a timesheet, an error occurs.
- You create a Project Web App (PWA) site on a Project Server 2010 server that has single entry mode enabled.
- You recall a timesheet through the PWA site.
- You review the timesheet on the PWA site.
In this scenario, the actual work values in the timesheet are updated unexpectedly.
When you create a project template that contains a custom calendar, you cannot use Project Server Interface (PSI) to create a project from the project template.
When a timesheet approval job fails, the timesheet appears in the approval list. Then, when you approve the timesheet for the second time, a TimesheetIncorrectMode error occurs. Additionally, you receive the following detailed information about the error:

There has been an error processing a timesheet for which you are/were responsible. Check your approvals list to locate the offending timesheet if one exists. The error condition may be related to the fact that Timesheets are a state driven feature; therefore, the allowable values for processing are dependent upon the existing value which for this transaction was 3.
Consider the following scenario:
- You apply Service Pack 1 for a non-English language pack on a Project Server 2010 server.
- You create a PWA site that uses the same non-English language.
- You apply the hotfix package that is described in Microsoft Knowledge Base (KB) article 2536600.
- You log on to the PWA site.
In this scenario, the column headers on the Project Center page, My Tasks page and Resource Center page are displayed in English instead of the non-English language that you used to create the site.
Consider the following scenario: Assume that you specify a minimum version level required by Project clients to connect to a Project server in Project Server 2010. When you use a Project client that does not meet the minimum version level required to connect to the Project server, the client connects to the server successfully. However, the client should be unable to connect to the server.
- You add an enterprise custom field that includes a formula to a project.
- The formula references a baseline field that is set to NA.
- You save the project from a Project Detail page.
- You review the project through PWA.
In this scenario, the data in the enterprise custom field is lost.
When you try to save a project to a Project Server 2010 server, you receive the following error message:

The following job failed to complete. Job Type: Save Error ID: 9000(0x2328) Error Description: The project could not be saved to the server. Please retry saving the project. If the problem persists, save the project as a MPP file and contact your system administrator.
Assume that you set the Publish field to No for a task that is already published in a project. After you publish the project to a Project Server 2010 server, all the pending status approval items are rejected on the Approval Center page.Note This hotfix package does not change the rejection behavior for reassigned, self-assigned, or newly created tasks. In these cases, if you set the Publish field to No, all the pending approval items are still rejected on the Approval Center page.
Assume that a workflow for a project is successfully completed. When you try to open the project by using PWA after 60 days, you receive the following error message:

Unable to open the project. The workflow associated with the project has been terminated unexpectedly.

October 2011

Rollup - http://support.microsoft.com/kb/2596506

Individual - http://support.microsoft.com/kb/2596498

Database Version - 14.0.6112.5000

When you use the TimesheetCreated event to customize a timesheet in Project Server 2010, the timesheet does not display the correct data.
When you accept updates for a task in Project Web App (PWA), the duration and actual work values for certain tasks are lost.
Consider the following scenario:
- You add an enterprise custom field which is based on a lookup table to a timesheet in Project Server 2010.
- You update the timesheet.
- You submit the timesheet.
- You view the Approval Center.
In this scenario, the Approval Center displays two items that have to be approved. However, the Approval Center should only display one item.
Consider the following scenario: Assume that you close a task to prevent that task from being updated in a timesheet in Project Server 2010. When you recall a timesheet to which the task was previously added, the task disappears from the timesheet.
- You set yourself as the assignment owner of a material resource in the Assignment Owner field in Project Server 2010.
- You assign the material resource to a new task in a project.
- You save and publish the project.
- You view the new task on the My Tasks page in PWA.
In this scenario, the My Tasks page does not display the new task. Additionally, the reminder does not display the correct number of new tasks.
When you group by projects in the Timesheet view in PWA, PWA displays duplicate project names.
Consider the following scenario: Consider the following scenario. You add a Task Hierarchy field to the Timesheet view in PWA. Then, you add a new assignment to the timesheet. In this situation, the Task Hierarchy field does not display the task hierarchy details. However, the Task Hierarchy field displays the task hierarchy details after you save the timesheet.
- You create custom fields that are associated with tasks in PWA.
- You update a task together with the custom field information on the My Timesheets page.
- You import the results into the My Tasks page.
In this scenario, the Timesheet view does not display the custom field value. Additionally, the Timesheet view does not display the custom field value when you create additional timesheets.
Consider the following scenario. You log on to PWA as a project manager. You approve a task and enter many characters into the comments text box in the Approval Center. In this scenario, you receive the following error message:

An Error occurred while processing one or more items. This was caused by one of the following: A timesheet job is failed and blocking correlation in the queue. The approval item no longer exists or has already been approved. The host server is unreachable.
This hotfix configures the Approval Center to highlight task updates when a task is updated in Project Server 2010.

August 2011

Rollup - http://support.microsoft.com/kb/2553049 Individual - http://support.microsoft.com/kb/2553047 Database Version - 14.0.6105.5000 (Not updated - so same as June)

When you apply updates on a completed task that does not have an actual start date, task scheduling fails in Project Server 2010.
Assume that you first set a large value for the actual work on a material assignment in Project Server 2010. Then, youreduce the value. In this case, the actual work is saved incorrectly for the material resource.
Assume that you click Send to submit a timesheet in Project Server 2010. You click Send again when the timesheet is being processed in the queue. In this case, a TimesheetIncorrectMode error occurs.
Task scheduling fails in Project Server 2010 if a project contains links to tasks that do not exist.
Consider the following scenario: The scheduling feature changes a task’s start date to an earlier date under certain conditions. This issue may cause task scheduling to fail in Project Server 2010.
- You have a project that has a material resource.
- The material resource is assigned to a task.
- The material resource has no cost.
- The cost accrual is set to the start of the assignment.
In this scenario, task scheduling fails in Project Server 2010.
Assume that you open a timesheet for a future period of time. Then, you click Save. In this case, additional lines are added into the timesheet.
You may experience one or more of the following issues in Project Server 2010: When a project manager makes a change to an assignment in Project Server 2010, resources receive an email message notification even if the assignment is completed.
- When you update a timesheet line, you may receive the following error message:
  
  An unhandled exception occurred in Microsoft.Office.Project.Server.BusinessLayer.Statuing.StatusingSendGridUpdatesForNodeConsistency.
- When you save a timesheet, the queue job fails. Additionally, the following message is logged in the Unified Logging Service (ULS) log:
  
  assert - resume_computation error.
The reporting database update job fails in Project Server 2010. Therefore, other jobs that are marked with "waiting to be processed" that follow the update job in the queue are auto canceled.
When you click the This is an Enterprise Project. Click this icon to open the Project for editing in Project Professional icon to open a project in read/write mode in the Project Center, the project opens in read-only mode.
You cannot use the QueueUpdateProject project server interface (PSI) to change a project owner if you do not have Save permission in Project Server 2010.

June 2011

Rollup - http://support.microsoft.com/kb/2536600 Individual - http://support.microsoft.com/kb/2536586 Database Version - 14.0.6105.5000

Assume that you edit a project plan through a Project Web App (PWA) site that is hosted in Microsoft Project Server 2010. When you try to calculate the project plan, you receive the following error message:

An error occurred while scheduling the project. Try to schedule the project again in a moment. If the problem persists, contact your administrator.
No cancellation feedback message displays when you perform a cancel operation in a PWA site that is hosted on Project Server 2010.
Assume that you perform a cancel operation for the Project Publishing event, the Project Summary Publishing event, or the Project Updating Scheduling Project event in a project detail page (PDP) in Project Server 2010. In this situation, no cancellation notification message is displayed.
An exception occurs when you synchronize users from a domain that does not contain a Project Server 2010 server.
You cannot create timesheets when you migrate databases from Office Project Server 2007 to Project Server 2010.Note This issue occurs because the Project Name field is removed from the My Timesheet view when an Office Project Server 2007 instance is configured.
When you enable Single Entry Mode on a Project Server 2010 server, resources can remove themselves from a task through PWA even though they have added actual work to the task. Therefore, the approved actual work is deleted from the Project server.
You edit a project plan that contains a custom field in a project detail page in Project Server 2010. Additionally, the custom field includes a formula. You save and check in the project plan, and then you visit another page before the save and check in request is completed. In this situation, the project plan may remain in a checked-out state.
Assume that you try to approve a task that has a summary task as its predecessor or successor in Project Server 2010. When you preview the task’s status update in the Status Update Preview page, you receive the following error message:

The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.
You cannot open multiple projects from the PWA that is hosted on a Project Server 2010 server when the list separator is not a comma.
The PSI returns incorrect results when lots of Project Server Interface (PSI) calls are sent to the ASMX interface in Project Server 2010.
Consider the following scenario: You cannot sort your assignments on the My Timesheet page in Project Server 2010.
- You log on to the My Timesheets page through PWA.
- You open an already approved timesheet in the My Timesheets page.
- You recall your timesheet.
- You change actual work on a task in the timesheet.
- You add actual work to a nonworking administrative time category.
- You save the timesheet, and then you submit it.
- You open the project plan in a Project 2010 client after actual work is synchronized with the project plan.
In this scenario, the actual work contour is incorrect. For example, a value that displayed as 0.5d before, now displays as 0.51d.
When you log on to a project site through PWA, and then you try to view an issue that links to a deleted project task, you receive one of the following error messages:

An error has occurred in the script on this page.

Or

An unexpected error has occurred.
When you enable the Use this field for matching generic resources option in PWA, the Roll down, unless manually specified optionin the Calculation for Assignment rows section is disabled unexpectedly.
Assume that you delete values in the Enterprise Custom Field (ECF) of a task through PWA. In this situation, any following update for the task cannot be saved. Additionally, there is no message that indicates the save operation failed.
The OnUpdatingScheduledProject event handler method that cancels updates for a project does not work in Project Server 2010.
Assume that you try to manage users on the Manage Users page in Project Server 2010. When you try to deactivate a user who is not listed on the first page, you receive an error message.
The NullRefrenceException exception may occur when you create a project by using the PSI in Project Server 2010.
Consider the following scenario: Assume that you perform a cube building operation on a PWA site that uses Claims based authentication. In this situation, Windows NT accounts are not automatically added to the Online Analytical Processing (OLAP) cube role.
- A project manager accesses the Approval Center page by using PWA.
- The project manager accepts task status updates from a team member.
- The project manager verifies that the status update queue job is finished successfully.
- The project manager opens the project plan, and then views the updated task status.
In this scenario, the task status updates are not applied to the project plan.
The user delegation feature does not work for pages that directly call Windows Communication Foundation (WCF) in a Claims based authentication PWA site.
When a status manager accepts updates for tasks in Project Server 2010, the status of the update job is listed as processing on the Manage Queue page and never finishes.
Consider the following scenario:
- You enableSingle Entry Mode in a PWA site.
- You create a delegation for a user.
- You start a delegation session as the user’s delegation.
- You create a timesheet, and then you save it.
In this scenario, the user or you as the delegation cannot open the timesheet. Additionally, you receive the following error message:

Timesheet has already been created by either the timesheet owner or a delegate. Refresh this page to get an up-to-date list of timesheets.
Consider the following scenario:
- You create a user account in a PWA site.
- You add the user account to a group that only has the permission to see a project's details, but not to open the project.
- You use the account to log on to the PWA site to see the project’s details.
In this scenario, you cannot see the projects details. Additionally, you receive the following error message:

Error: Access Denied.
Consider the following scenario. You edit a project through PWA. The edit operation starts a server-side scheduling process. In this scenario, you cannot save the project successfully. Additionally, you receive the following error message in the Unified Logging Service (ULS) log:

GeneralProject:ProjectSchedulingEngineException (9133). Details: id='9133' name='ProjectSchedulingEngineException' uid='a610edbc-b5ad-448b-8b35-3895e09441b8' exception='Microsoft.Office.Project.Scheduling.EventHorizonFinishException: Error in the application.

Service Pack 1 (SP1)

Due to some known issues found at release it was also recommended to update to June 2011 CU

Download - http://www.microsoft.com/downloads/details.aspx?FamilyId=B9FCDC42-EEA4-4C08-9169-A9A73E55B8D4 List of fixes - http://download.microsoft.com/download/B/0/D/B0D1540B-6CF6-4674-9C8E-7A45FD91C163/Microsoft%20SharePoint%202010%20and%20Office%20servers%20Service%20Pack%201%20Changes.xlsx Database Version 14.0.6027.1000

April 2011

Rollup - http://support.microsoft.com/kb/2512801 Individual - http://support.microsoft.com/kb/2516483 Database Version - 14.0.5137.5000

Assume that a master project has a subproject that contains more than 100 tasks in Microsoft Project Server 2010. You try to view the master project tasks from Project Detail Pages. In this situation, not all the tasks are visible. Additionally, the subproject tasks collapse unexpectedly.
Consider the following scenario: You try to select certain time periods on the My Tasks page through Project Web App (PWA). You click the Next button multiple times on the My Tasks page. In this situation, a time period start date is a day earlier than what it should be.
- You have a single entry mode in Project Server 2010.
- You update the timesheet line for a task assignment.
- You submit the task status and the timesheet.
- You try to delete the project that contains the task after the timesheet is approved.
In this scenario, the project cannot be deleted. Additionally, you receive an error message.

February 2011

Rollup - http://support.microsoft.com/kb/2475879 Individual - http://support.microsoft.com/kb/2479792 Database Version - 14.0.5130.5000 (Not updated - same as December)

You enable Single Entry Mode on a Microsoft Project Server 2010 server, and then you send a timesheet. In this situation, the task status manager does not receive an email message notification for status updates.
Consider the following scenario: When many users try to create timesheets on a Project Server 2010 server at the same time, the user who first submits a timesheet creation request receives an error message. In this situation, the rest of users can create timesheets successfully. However, the timesheets that are created do not contain administrative line items.
- You create a custom field in a Project Web App site.
- The site is hosted on a Project Server 2010 server and has a non-English locale.
- The custom field contains a graphical indicator that is based on formulas.
- You save the custom field, and then you open it again.
In this scenario, the formulas displays in English instead of non-English. Additionally, you cannot save the custom field again.
You assign a resource to an existing project plan in Project Server 2010. Then, the resource inserts a row in a timesheet. In this situation, there is no top-level summary task that is listed for the plan in the menu of the row.
When lots of users try to create timesheets at the same time on a Project Server 2010 server, the following issues occur: Assume that you edit a project in a project detail page (PDP) in Project Server 2010. When you select to save and check in the project, then you visit another page before the save and check in request is completed. In this situation, the project may be left in a checked out state.
Certain users cannot create timesheets successfully. Additionally they receive an error message.
The timesheets that are created do not contain administrative lines. In this situation, users cannot add time to the timesheets.
When you try to save a project in Project Server 2010, you receive the following error message:

Cannot insert duplicate key row in object 'dbo.MSP_ASSN_CUSTOM_FIELD_VALUES_SHADOW' with unique index 'UQ_MSP_ASSN_CUSTOM_FIELD_VALUES_SHADOW'

December 2010

Rollup - http://support.microsoft.com/kb/2459258

Individual - http://support.microsoft.com/kb/2459112 and http://support.microsoft.com/kb/2459113 Database Version - 14.0.5130.5000

In Project Web App (PWA), you cannot change the value in the Actual Start field on the My Work Tasks page.
Consider the following scenario:In Project Professional 2010 you save the baselines for a project. Then, you use the Update Tasks command to update the tasks in the project. In this situation, the baseline values that you previously saved are lost.
- You are a team member of a project in Project Server 2010.
- You only have permissions to view projects in PWA.
- You drill into the project.
In this scenario, you receive the following error message:

An unexpected error has occurred.
In Project Server 2010, you try to change the owner for a project in the Project Information Project Detail Page (PDP). However, you cannot change the project owner in the Owner field when the new owner does not have the Save permission on the project.
In Project Server 2010, you cannot create a PWA site that uses a host header name. Instead, the site can only use the server name.
Consider the following scenario. In Project Server 2010 you create a site by using the Microsoft Project Site template. Then, you try to access the Cost column in the Risks page of the new project site. In this scenario, you receive the following error message:

An unexpected error has occurred.

October 2010

Rollup - http://support.microsoft.com/kb/2394322 Individual - http://support.microsoft.com/kb/2413667 Database Version - 14.0.5114.5000 (Not updated - unchanged from June 2010)

Assume that you create a custom field together with a formula that uses the semicolon separator. When you create another custom field together with a formula that refers to the first custom field, you receive the following error message:

Unknown Error.

August 2010

Rollup - http://support.microsoft.com/kb/2352345 Individual - http://support.microsoft.com/kb/2276341 (There was also a reliance on the SharePoint Foundation patch for a jsgrid fix - http://support.microsoft.com/kb/2266423 Database Version - 14.0.5114.5000 (Not updated - unchanged from June 2010)

The New-SPProjectWebInstance cmdlet does not work together with the host header when a site collection already exists.
Project Server administrators now can resolve user names by using email addresses. For example, depending on how the claims providers are configured, the user logon account can be entered and validated as an email address such as username@live.com
(mailto:username@live.com)
on the Edit User page.
After you provision a Project Web Access (PWA) site, the queue service process restarts unexpectedly. This causes the interruption of the queue on other PWA sites.
The queue service may consume large amounts of memory, such as several gigabytes (GB), when there are hundreds of PWA sites in a farm.
If users cannot be resolved in Active Directory because of intermittent connectivity issues, the users are deactivated.
Consider the following scenario. You apply the hotfix package that is described in Microsoft Knowledge Base article 2075990. You connect the Project client to Project Server 2010 and use manually scheduled tasks. Then, you update the % complete column on a manually scheduled task in the project. In this scenario, the baseline work value is cleared from other manually scheduled tasks unexpectedly.

June 2010

No Rollup Individual - http://support.microsoft.com/kb/2075990 Database Version - 14.0.5114.5000

The tracking GUID that is specified in the Project Server Interface (PSI) headers is not honored as the Job Group ID of the resulting queue jobs.
If the project uses a Force-in alias or a Force-out alias, you cannot switch a project to automatic scheduling. Additionally, recalculation fails, and you receive the following error message:

An unknown error has occurred.
You set a baseline to the NA status for any project task. However, this baseline is not updated when you publish the project from the client.
You cannot create enterprise projects or templates on the server from certain Microsoft Office Project 2007 templates.
If the value of the ChangeXML parameter is a large number, the UpdateStatus PSI method requires a long time to update many tasks that apply to different users. This behavior blocks the Team Foundation Server (TFS).
When you attach some databases and then provision a site, the upgrade fails if you load a language pack that is not supported by Project Server 2010.

RTM Initial Release Database Version 14.0.4750.1000

Project Server 2010 Cumulative Updates from August 2012 to date.

Brian Smith — Fri, 29 Mar 2019 13:41:17 GMT

This page lists all of the released Cumulative Updates (CU), Service Packs (SP) and infrastructure update for Project Server 2010 from August 2012 to date. From February 2015 onwards all fixes are shipped in Public Updates PU). From March 2015 client updates available via Windows Update and Download Center, server updates only via Download Center. They are listed in reverse date order - newest at the top. The CUs are normally available in a 'rollup' package that also includes the SharePoint Server and SharePoint Foundation CUs as well as one (sometimes two) 'Individual' packages which just contain the Project Server fixes. Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack). In some months a rollup package did not get released. I have also recorded the version you will see in the dbo.Versions table in the Project Server database after applying each update and running the configuration wizard. In some months this does not get incremented if there were no database changes.

March 2019

No specific Project Server 2010 updates - but the roll up for SharePoint - https://support.microsoft.com/en-us/help/4462227/march-12-2019-cumulative-update-for-project-server-2010-kb4462227

December 2016

NOTE: There are no Project Server specific updates in the Project Server roll-up for December 2016. The released rollup package contains security updates for SharePoint 2010, but no specific fixes for Project Server 2010 service application. Project Server roll-up package Rollup - https://support.microsoft.com/en-us/kb/3128033 No database change - so 14.0.7156.5000

November 2016

NOTE: There are no Project Server specific updates in the Project Server roll-up for November 2016. The released rollup package contains security updates for SharePoint 2010, but no specific fixes for Project Server 2010 service application. Project Server roll-up package Rollup - https://support.microsoft.com/en-us/kb/3127952 No database change - so 14.0.7156.5000

October 2016

NOTE: There are no Project Server specific updates in the Project Server roll-up for October 2016. The released rollup package contains security updates for SharePoint 2010, but no specific fixes for Project Server 2010 service application. Rollup - https://support.microsoft.com/en-us/kb/3118383 No database change - so 14.0.7156.5000

September 2016 NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package). This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch. Rollup - https://support.microsoft.com/en-us/kb/3115470 No database change - so 14.0.7156.5000

August 2016 There are no updates for Project 2010 for August 2016.

July 2016 NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package). This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch. Rollup - https://support.microsoft.com/en-us/kb/3115242 No database change - so 14.0.7156.5000

June 2016 NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package). This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch. Rollup - https://support.microsoft.com/en-us/kb/3115316 No database change - so 14.0.7156.5000

May 2016 NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package). This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch. Rollup - https://support.microsoft.com/en-us/kb/3115122 No database change - so 14.0.7156.5000

April 2016 NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package). This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch. Rollup - https://support.microsoft.com/en-us/kb/3114992 No database change - so 14.0.7156.5000

March 2016 NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package). This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch. Rollup - https://support.microsoft.com/en-us/kb/3114876 No database change - so 14.0.7156.5000

February 2016 NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package). This does however contain all the updates shipped up to the January update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch. Rollup - https://support.microsoft.com/en-us/kb/3114754 No database change - so 14.0.7156.5000

January 2016

Rollup - https://support.microsoft.com/en-us/kb/3114556 Individual - https://support.microsoft.com/en-us/kb/3085610 No database change - so 14.0.7156.5000

When you change the project description on a project detail page and then save it, the description isn't saved as expected. This issue occurs after you install August 11, 2015, update for Project Server 2010 (KB3055046).

December 2015

NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package). This does however contain all the updates shipped up to the September update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch. Rollup - https://support.microsoft.com/en-us/kb/3114405 No database change - so 14.0.7156.5000 November 2015 No individual Project Server 2010 package this month NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package). This does however contain all the updates shipped up to the September update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch. Rollup - https://support.microsoft.com/en-us/kb/3101530 No database change - so 14.0.7156.5000

October 2015

No individual Project Server 2010 package this month NOTE: Although this patch is called an update for Project Server – and is what we would normally consider the ‘roll-up’ patch – there are no new fixes for Project Server (hence no individual package). This does however contain all the updates shipped up to the September update – so can be used to bring you right up to date with Project Server 2010 and the other products included in the roll-up patch. Rollup - https://support.microsoft.com/en-us/kb/3085598 No database change - so 14.0.7156.5000

September 2015

Rollup - https://support.microsoft.com/en-us/kb/3085517 Individual - https://support.microsoft.com/en-us/kb/3085527 Database Version - 14.0.7156.5000

When you approve multiple status updates at one time, all remaining updates fail if a single update fails.
When you open a resource plan that contains many resources and customer fields in Project 2010, it takes a long time to load up the resource plan.

August 2015

Rollup - https://support.microsoft.com/en-us/kb/3055038 Individual - https://support.microsoft.com/en-us/kb/3055046 Database Version - 14.0.7151.5000 (Not updated this month)

When you use a Project Server Interface (PSI) application to update a project-level custom field of a project, values of calculated custom fields are blank on tasks when viewed in Project Web App.

July 2015

Rollup - https://support.microsoft.com/en-us/kb/3054972 Individual - https://support.microsoft.com/en-us/kb/3054982 Database Version - 14.0.7151.5000 (Not updated this month)

When you change the view for a Project Center or Project Schedule view and apply a different filter or grouping, the filter option and the grouping option do not change as expected, and the view may still be filtered or grouped based on the previous view.
When you try to run the Deficit and Surplus report on the Analyze Resources page in Microsoft Project Web App, you experience a time-out issue.
When you create deliverables directly in a SharePoint site that has the Project Web App Connectivity feature enabled, you cannot see the deliverables in Microsoft Project Professional 2010.

June 2015

Rollup - https://support.microsoft.com/en-us/kb/3054877 Individual - https://support.microsoft.com/en-us/kb/3054887 Database Version - 14.0.7151.5000

When you try to edit a resource in Project Web App, you receive an unknown error that resembles the following in the ULS logs:

Exception occurred in method Microsoft.Office.Project.Server.BusinessLayer.Project.ProjectQueueUpdatePDPProjectCF System.Data.SqlClient.SqlException: The EXECUTE permission was denied on the object 'MSP_ReadLocalAndEnterpriseLookupTableInfoByUIDs', database 'ProjectServer_Published_PWA', schema 'dbo'.

For more information, see Project Server 2010: After applying the March CU resources can't be saved in PWA.

May 2015

Rollup - https://support.microsoft.com/en-us/kb/2999496/ Individual - https://support.microsoft.com/en-us/kb/2965314/ Database Version - 14.0.7145.5000 (not updated)

When you try to insert a task for a project in the Schedule Web Part in Project Web App, you receive the following error message:

This edit is unsupported in Project Web App.

This issue occurs if the project has a particular structure of outline levels or task indentations and if you are using Internet Explorer 11.
When you export or print a resource plan for a project in Project Web App, the work or full-time equivalent is incorrect. For example, suppose that you enter the values 1d, 2d, and 3d. The print may show the values as 0.63d, 1.75d, and 2.63d.
When you publish a project in Project Web App in which tasks contain formulas that use the ProjDateDiff function, incorrect calculations may be made. This issue occurs if your project calendar does not use the default calendar configuration (08:00-12:00 and 13:00-17:00).

April 2015

Rollup - https://support.microsoft.com/en-us/kb/2965293/ Individual - https://support.microsoft.com/en-us/kb/2965302/ Database Version - 14.0.7145.5000 (not updated) No Project Server feature fixes this month, but a security patch: This update resolves vulnerabilities that could allow elevation of privilege if an attacker sends a specially crafted request to an affected Microsoft Project Server 2010. The attacker who successfully exploited these vulnerabilities could then perform cross-site scripting attacks on affected systems and run script in the security context of the current user. An attacker who successfully exploited the vulnerabilities could read content that the attacker is not authorized to read, use the victim's identity to take actions on behalf of the victim, such as change permissions, delete content, and insert malicious content in the victim’s browser.

March 2015

Rollup - http://support.microsoft.com/KB/2956198 Individual - http://support.microsoft.com/kb/2553480 Database Version - 14.0.7145.5000

You cannot update a local custom field by using Project Server Interface (PSI) if the field is associated with a lookup table. Additionally, you may receive a "GeneralUnhandledException" exception.
Assume that you change the working time of the enterprise calendar associated with your project to a nondefault working time such as 9:00-17:00. Then you publish a task and open the Tasks page in Project Web App (PWA). Then you change the finish date and the duration of the task and save the change. In this situation, both the finish hour and the task duration are incorrect.

February 2015

Rollup - http://support.microsoft.com/KB/2899557 Individual - http://support.microsoft.com/KB/2881024 Database Version - 14.0.7137.5000 (Not updated - so same as November 2014)

Assume that you browse to a Project Web App (PWA) site on a computer where the time zone setting differs from the server that hosts the PWA site. When you browse to the Tasks page, the active time period may be incorrect.
Assume that you create a new Enterprise custom field, and then you enter a formula that refers to the Task Calendar field. When you save the Enterprise custom field, you receive the following error message:

The custom field could not be saved due to the following reason(s): This formula contains references to one or more fields that do not exist in the system. Correct the formula and try again.
Consider the following scenario:
- You link two tasks by using a Start-to-Start (SS) dependency. In this case, the predecessor is a summary task and the successor is an ordinary task.
- You make some changes to the project plan by using a Project Server Interface (PSI) application.
- You publish the project plan to a Project server.
In this scenario, the start date of the successor tasks may be earlier than expected.

December 2014

Rollup - http://support.microsoft.com/KB/2910889 Individual - http://support.microsoft.com/KB/2899587 Database Version - 14.0.7137.5000 (Not updated - so same as November 2014)

When you change the view of the Project Center page and apply a different filter or grouping, the filter option and the grouping option do not change as expected, and the view may still be filtered or grouped based on the previous view.
Assume that you have a resource whose Latest Available date is set, and the resource’s calendar has exceptions. When you call the Resource.UpdateResources method, you may receive the "CalendarUnusedCalendarException" error message.

November 2014

Rollup - http://support.microsoft.com/kb/2899479 Individual - http://support.microsoft.com/kb/2899537 and http://support.microsoft.com/kb/2899549 Database Version - 14.0.7137.5000 Consider the following scenario:

You create a project in Project Professional 2010.
In the new project, you disable the Actual cost are always calculated by Project calculation option under Project Options in the Schedule section.
You create a task that has a duration value of 20d, and then you assign the task to an Enterprise resource.
You insert the Cost and Actual Cost columns into the view, and then you update the values for the two columns.
You save and publish the project to Project Server 2010.
You create a report that is based on an OLAP cube that is generated from the server reporting data.

In this scenario, the task costs for this project are incorrect in the report because an additional cost for unassigned resources is added. Consider the following scenario:

In Project Server 2010, you create a custom field that uses a lookup table, and then you enable multiple values to be selected.
You insert several tasks into a project, and then you select values from the custom field for the tasks.
You save and publish the project.
You change the value of the custom field for one of the tasks, and then you save the project.
You change the value of the custom field for the other tasks, and then you save the project.
You publish the project.

In this scenario, the value of the custom field for the tasks may be incorrect when you query the value from the reporting database tables.

It takes longer than expected to publish a project to a server that is running Project Server 2010 when there are many projects on the server.

October 2014

No rollup this month Individual - http://support.microsoft.com/kb/2899485/ and http://support.microsoft.com/kb/2880539/ Database Version - 14.0.7134.5000

Assume that you log on to your Project Server 2010, open a timesheet, and then select the Add Yourself to a Task option from the Insert Row button. The Add Tasks page is refreshed every 10 seconds, and this behavior makes it very difficult to enter information on the page.
Assume that there are tens of thousands of projects on your Project Server 2010 server. It may take a long time for you to open or save a project on the server.

September 2014

Rollup - http://support.microsoft.com/kb/2883006 Individual - http://support.microsoft.com/kb/2880531 Database Version - 14.0.7132.5000

Assume that you log on to Project Web App by using Windows Internet Explorer 10 or a later version. When you try to export the resource availability information by using the Export to Excel function on the Resource Availability page, the function does not work.
Assume that you edit a project on the Project Details page. When you change a property such as the name, the value of the Cost field of material resources may be changed to $0.00.

August 2014

No Project Server 2010 Cumulative Update released

July 2014 -

No Project Server 2010 Cumulative Update released

June 2014

Rollup - http://support.microsoft.com/kb/2880974 Individual - No individual package released. Database Version - 14.0.7121.5000 (Not updated - same as for April 2014)

Timephased values shown in Project don't appear correctly in the PWA availability page

April 2014

Rollup - No rollup package released Individual - http://support.microsoft.com/kb/2878259 and http://support.microsoft.com/kb/2878266 14.0.7121.5000

The decimal value in the Standard Rate field does not always round correctly after you edit any resources in Project Web App (PWA). For example, assume that you enter a resource’s standard rate as $733/d. On an hourly basis this is equal to $91.625 and is stored in the Project Server database as $91.625 though it appears in the interface in Project Professional and PWA as $91.63. However, if you edit the resource in PWA, the value that is stored internally changes to $91.63. Therefore, costs dependent on rate may change because of the rounding problem.
The Assignment Baseline Finish field and the Task Baseline Finish field are missing from the Published Field list when you create an approval rule in the Approval Center.
Assume that you have a timesheet and that since its creation one or more custom fields that were available when the timesheet was created are deleted (from the Enterprise Custom Fields and Lookup Tables page). When you open the Timesheetview, you receive the error message that resembles the following:

The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.
Assume that you create a project by using a project template where, for example, the Hours per day option is set to 9 hours. In this situation, the project may schedule incorrectly in Project Web App. Additionally, you receive the error message that resembles the following:

An error occurred scheduling the project. Try to schedule the project again in a moment.
When in a project detail page in Project Web App you save a project that contains cost resource assignments. In this case, the costs on the assignments may change unexpectedly. For example, a cost of $1.16 changes to $1.00.
When resources in a project have many assignments in other projects in Project Server 2010, it takes longer than expected to publish the project. Note The time that is required to publish the project may increase if many projects that use the same resource are published at the same time as can occur if you enable the Automatically publish the updates option.
Because of SQL Server deadlock errors, data is not always transferred to the Reporting database when you save a timesheet.

February 2014

Rollup - http://support.microsoft.com/kb/2863917 Individual - http://support.microsoft.com/kb/2863927 and http://support.microsoft.com/kb/2863934 Database Version 14.0.7115.5000

When users are marked as inactive, the User can be assigned as a resource option on the Server Settings Edit Users page can still be changed. Deselecting this option can lead to project publishing errors and the loss of resources on projects.
If dependencies between tasks in the project have unusually large lead times or lag times, saving a project in Project Web App may fail. Additionally, you receive the following error message:

An error has occurred when saving your project to the server. Please contact your administrator for assistance.
Automatic approval rules may not get executed as expected. Additionally, you can find a job in the queue with a state of Failed But Not Blocking Correlation. When you click View Error Details, you may see details about the error that resembles the following:

A GeneralQueueJobFailed (26000) error occurs

When Project Server is using Claims Based Authentication, the Enterprise Resource Pool and Security Group Active Directory synchronization jobs may fail and in the ULS logs you may see errors similar to:

A resource could not be updated during Project Server Active Directory Synchronization because a duplicate windows account name conflict occurred that could not be resolved

December 2013

Rollup - http://support.microsoft.com/kb/2849972 Individual - http://support.microsoft.com/kb/2849978 and http://support.microsoft.com/kb/2849988 Database Version - 14.0.7113.5000

Consider the following scenario:When you add yourself to a task in Project Web App, the Timesheet page buttons in the Submit and Tasks sections are greyed out. Therefore, you cannot save or send the timesheet.
- A resource is assigned to a 2 day fixed duration task.
- The resource only works the first day of the task, and then you set the task’s % Complete option to 100%.
- You open, calculate, and save the project in Project Web App.
- You open the project in Project Professional 2010 again.
In this scenario, the task’s % Complete option is set to 50%.
After you approve some status updates in the Approval Center, the updates are not applied to schedules. Additionally, when you click the Error link on the Manage Queuepage, you see an error message that resembles the following:

General Status approval internal error: StatusingInternalError (3116). Details: id='3116' name='StatusingInternalError' uid='5cb8a27d-71db-491a-9c0a-782950a2d6ce'. Queue: GeneralQueueJobFailed (26000) - StatusApproval.StatusApprovalMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='16a0be21-3b4d-44a2-98e0-d6452342bf7a' JobUID='43b6dac0-53c9-4fbe-ad3c-1731608c4cbc' ComputerName='ComputerName' GroupType='StatusApproval' MessageType='StatusApprovalMessage' MessageId='3' Stage=''. For more details, check the ULS logs on machine ComputerName for entries with JobUID 43b6dac0-53c9-4fbe-ad3c-1731608c4cbc.

When you publish a project on a Project Server 2010 server, there is a publish failure message in the queue, and deadlock errors are logged in the ULS logs.

October 2013

Rollup - http://support.microsoft.com/kb/2825793

Individual - http://support.microsoft.com/kb/2825803

Database Version - 14.0.7110.5001

Assume that you accept some updates for a project on the Approval Center page in Project Web App. When you open the Status updates history page, you receive the following error message:

There was an internal error applying the update.

Additionally, when you open the project in Project 2010, the update is not applied.
After you accept updates for a project in Project Web App, the work and duration information for some tasks and assignments is set to zero.

August 2013

Rollup - http://support.microsoft.com/kb/2817573

Individual - http://support.microsoft.com/kb/2817587

Database Version 14.0.7104.5000

Assume that you belong to many security groups that have many security categories applied, and the security categories have many of the dynamic RBS permissions applied. When you move from one Project Detail Page (PDP) to another, it may take longer than expected.

June 2013 (Actually re-released in July)

Rollup - http://support.microsoft.com/kb/2817530 Individual - http://support.microsoft.com/kb/2817538 Database Version 14.0.7102.5000

When you edit a project that contains cross-project links and enterprise custom fields in Project Web App, task durations are changed unexpectedly.
When you edit a custom field from the Assignment Details page in Project Web App, you cannot input more than 50 characters.
Consider the following scenario:
- You enable the Protected Actuals feature and then create a task.
- A team member reports an actual work, and the actual work is approved.
- You edit a work or remaining work of the task in a Project view in Project Web App.
In this situation, you receive the following error message:

Your last edit changes actual work on the project. Currently Project Web App is set up to protect actuals on tasks.
Consider the following scenario:When you use Project Server Interface (PSI) to update a project that contains multiple cost rate table entries in Project Server 2010, resource costs are calculated incorrectly.
- You create a task that has predecessor relationship, multiple assignments and at least one assignment that has actual work applied.
- You report and approve actual work for one of the other assignments.
- The work is reported earlier than scheduled and earlier than when the actual work that is already reported on the other assignments.
In this situation, the actual work on the assignment is scheduled incorrectly. Therefore, the start date and duration of the task is calculated incorrectly.
Unnecessary user account synchronization occurs and you experience performance issues in Project Web App. For example, you cannot log on the server.
When you use a template that contains a null task to create a project in Project Web App, the project cannot be displayed in Project views. Note A null task is a blank row between rows.
Totals for grouping rows on the Approvals page in Project Web App are not rolled up.

Service Pack 2 (SP2)

Download - http://www.microsoft.com/downloads/details.aspx?FamilyId=387a7889-8266-429a-bfd3-b6bb2f9cbe63 List of fixes - http://download.microsoft.com/download/9/5/9/959F3A24-80B3-4930-8FF8-D3C631BB878F/Microsoft%20Office%20and%20SharePoint%202010%20Service%20Pack%202%20Changes.xlsx Database Version - 14.0.7015.1000

April 2013

Rollup - http://support.microsoft.com/kb/2775426 Individual - http://support.microsoft.com/kb/2791064 Database Version 14.0.6136.5000

Consider the following scenario:
- You create a proposal on the Project Center page in Project Server 2010.
- You do not enter data into all the required fields.
- You submit the proposal, and it is displayed unexpectedly as "checked in".
- You edit the proposal. However, you do not enter data into all the required fields.
- You submit the proposal again.
In this situation, the proposal is displayed unexpectedly as "checked out".
Assume that you set some values for the date range, filter, and group fields on the Approval Center page in Project Server 2010. When you move away from the Approval Center page and then move back to the Approval Center page, you experience the following issues:When resources in a project have many assignments in other projects in Project Server 2010, it takes longer than expected to publish the project.
- The value is not retained in the date range field.
- The filter and group fields are set. However, the filter and group settings are not applied to the data.
Note The time that is required to publish the project increases if many projects that use the same resource are published at the same time. This can occur after you enable the Automatically publish the updates option.

February 2013

Rollup - http://support.microsoft.com/kb/2767794 Individual - http://support.microsoft.com/kb/2760772 Database Version - 14.0.6131.5000 (Not updated - same as December 2012)

Consider the following scenario:Assume that you try to create a new project that is based on a template in Project Web Application. However, the Queue service job never finishes, and the Queue service restarts continuously. Additionally, Project Server 2010 crashes.
- You create a new task in Project Web Application.
- You associate the new task with an existing summary task in the project.
- You open the project in Project Professional 2010.
- You search for the new task.
In this scenario, the new task is not associated with the correct summary task.
Assume that you add users to custom SharePoint groups in a Project Web Application site collection. However, when the server performs a user synchronization Queue Service job, these users lose their permissions to access resources.
After you update the "% Work Complete" value in a sub-task when you edit a project in a Project Web App schedule view, the "% Work Complete" value in the parent task is incorrect.

December 2012

Rollup - http://support.microsoft.com/kb/2596956 Individual - http://support.microsoft.com/kb/2553504 and http://support.microsoft.com/kb/2553268 Database Version 14.0.6131.5000

Assume that you install update 2730388 on a computer that has Microsoft Project Server 2010 installed. In this situation, the updated actual work value is not displayed in the project plan after you accept updates that include actual work in Project Professional 2010.
In the Project Web App (PWA) approval center, the actual work values that are submitted for approval on a timesheet will be displayed in hours when the submitted values are in days.
Consider the following scenario:
- You enable single entry mode in Project Server 2010.
- You insert a personal task on a timesheet.
- You edit the start date or another non-timephased field for the task, and then try to save the timesheet.
In this situation, you receive an error message, and the timesheet cannot be saved.
Consider the following scenario:Assume that you set up a multiple forest environment. When you perform an Active Directory resource pool or an Active Directory security group synchronization over an external trust to another forest, the process fails.
- User A and user B are status managers in Project Server 2010.
- User A creates a task and assigns it to a Work Resource in Project Web App (PWA).
- User A saves the project plan.
- User B opens the project and removes the Work Resource on the task.
- User B saves the project plan.
In this scenario, the status manager for the task automatically switches from user A to user B. Note If the resource is a Work Resource or a Generic Resource, the status manager does not change in the Project Professional 2010. Additionally, if the resource is the Generic Resource, the status manager does not change in the PWA for the user who removes the Work Resource.
Assume that you publish a project with actual costs outside the task span in Project Server 2010. In this situation, the timephased and baseline actual cost do not appear correctly in the reporting database. This occurs when there is no timephased or baseline work span associated with the actual cost.
Assume that you set up a delegation in Project Server 2010. Then you assign yourself as a delegate and create new timesheets. In this situation, the newly created timesheets are missing administrative lines. Additionally, you receive the following error message:

The timesheet creation failed, because of problems with the project server or with data validations, such as resources not being valid work resources or users. Check your environment, and then try again.
When you submit timesheets in Project Server 2010, a deadlock situation occurs, and the timesheet page is not updated correctly. Additionally, you receive the following error message:

The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.

October 2012

Rollup - http://support.microsoft.com/kb/2687565 Individual - http://support.microsoft.com/kb/2687615 Database Version - 14.0.6129.5002

Assume that you configure Project Server 2010 in two or more zones that are accessed by using different URLs. Additionally, assume that you create Project sites that contain a Project web part. In this situation, when you try to connect to the Project site from a zone that differs from the zone in which the Project site is created, you receive the following error message from the web part:

Cannot communicate with the server. Verify your connection and try again.
Consider the following scenario:Assume that a resource has the Max Units field set to a value that is not 100 percent. Additionally, assume that the default task type for a project is "Fixed Duration." The resource creates a new task in Project Web App and adds the task to the project. In this situation, the task is displayed in the project with a high amount of work. Additionally, the task does not appear in the Approval Center and causes an error on the approval page.
- You have an enterprise resource that is assigned to a task in a plan.
- The resource enters actual work in a timesheet and saves (but does not submit) the timesheet in Project Web App.
- You set the Publish field in the task to No," and then you publish the plan.
- You set the Publish field in the task to Yes," and then you publish the plan.
- The resource submits the timesheet update for approval.
In this scenario, the actual work is not submitted in Approval Center.
Assume that a delegate user makes corrections to a timesheet that was previously rejected in Project Web App and then sends the timesheet for approval. In this situation, time that is added to the lines that already contain approved status updates cannot be resubmitted and approved.
Assume that you try to edit an existing project in Project Web App while you are using Internet Explorer 10. However, occasionally you cannot edit the project.
When you create and load a timesheet in Project Web App, the process takes longer than expected.
When you create a project plan from a template in Project Web App, the value of the Publish field is not copied from the template.
Assume that you create an enterprise project template in Microsoft Office Project Professional 2010 in which you configure the default start time and the default finish time at the project level. Then, you create a new project plan that is based on the template. In this situation, the default start time and the default finish time are those from the enterprise global template instead of the template from which thenew project was created.
Assume that you set the WADMIN_USER_SYNC_SETTING setting to a value greater than one in the published database of Project Server 2010. When you try to add a user to a project by using the project permissions feature, the user is not added to the project site.
Assume that you enter the actual work for a task by using Project Web App. However, when you click Status Updates to view task update history, the actual work column is blank.
When all task updates are submitted to Project Server 2010, the OnStatusSubmitted event returns a NULL value instead of an array of GUIDs that match the submitted updates.

August 2012 (Actually released in September)

Rollup - http://support.microsoft.com/kb/2687354 Individual - http://support.microsoft.com/kb/2687390 and http://support.microsoft.com/kb/2687385 Database Version - 14.0.6126.5001

When enterprise flag fields are defined in a project, and you publish the project, the MSP_TASK_CUSTOM_FIELD_VALUES_SHADOW table in the published database contains two times as many records as the original table.Note To resolve this issue, apply update 2687386 on the Project client application. For more information about the update, click the following article number:
2687386
(http://support.microsoft.com/kb/2687386/ )
Description of the Project 2010 hotfix package (Project-x-none.msp): August 28, 2012
Assume that you set a baseline cost value for a task that contains negative cost values. When you publish the task while it is synchronizing with the Reporting database, the negative cost values are converted to 0 in the MSP_EpmAssignmentByDay and MSP_EpmAssignmentBaselineByDay tables.
On the History page for certain projects in Project Server 2010, error messages are displayed in the status updates field. These error messages are displayed even though you already applied the updates to resolve the issues that caused the error messages.
Assume that you assign a resource to a task, and the resource's calendar contains nonworking time. Additionally, assume that you enter actual work for the task. When you open the task, the actual work is displayed in the wrong time period.
Assume that you submit actual work for a resource that has a nonzero cost rate on the My Tasks page. When you publish the project that contains the resource, the actual costs that are calculated through the actual work are not updated in the reporting database.
When you configure a Project Server 2010 server to run in single entry mode, and then you open a project, tasks that are manually scheduled in the project are not displayedin the Add an Existing Task dialog box. Therefore, you cannot enter time for these tasks.
When you start a delegation session as a delegate in Project Server 2010, auto-approval rules for task updates do not work as expected.
Assume that you assign some material resources to some summary tasks in a project. When you edit and publish the project through Project Web App, the number of material resources in the published project is much greater than the number of material resources in the original project.
Assume that you set the replacement character for Active Directory synchronization to a null value on a Project 2010 server. After you synchronize the server, resource names are displayed with two additional spaces on the server. For example, "LastName, FirstName" is displayed as "LastName FirstName."
Assume that many projects contain local custom fields in Project Server 2010, and the local custom fields contain custom field formulas. When you open a project in the publishing database, the project contains formulas that are from other projects.

Project 2013 Cumulative Updates 2016 to Date

Brian Smith — Tue, 21 May 2019 21:03:14 GMT

This page lists all of the released Cumulative Updates (CU) and Service Packs (SP) for Microsoft Project 2013, both Standard and Professional from 2016 to date From February 2015 onwards all fixes are shipped in Public Updates (PU). From March 2015 client updates available via Windows Update and Download Center, server updates only via Download Center. From April 2016 the Office client updates are shipped 1st Tuesday. The October 2016 client updates were released on the 2nd Tuesday. From April 2015 onwards all fixes require SP1 as a prerequisite. They are listed in reverse date order - newest at the top. Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack). I have also recorded the version you will see in the File, Account, About Microsoft Project link Project 2013. If you are running a click to run installation - such as Project for Office 365 see http://support2.microsoft.com/gp/office-2013-365-update for details of the update schedules - but the version numbers and fixes should be roughly in line with the CU releases below.

May 2019 - no updates for Project 2013

April 2019 - no updates for Project 2013

March 2019 - no updates for Project 2013

February 2019 - no updates for Project 2013

January 2019

15.0.5101.1000 https://support.microsoft.com/en-us/help/4461560/january-2-2019-update-for-project-2013-kb4461560 Improvements and fixes

This update adds support for Japanese era changes in Project 2013.

December 2018

No client update in December

November 2018

15.0.5085.1000 https://support.microsoft.com/en-us/help/4461489/description-of-the-security-update-for-project-2013-november-13-2018 Improvements and fixes

This security update contains improvements and fixes for the following nonsecurity issue:
Consider the following scenario:
- You have a SharePoint document library.
- The document library list experience is set to the new "modern" experience.
- The document library versioning settings require checkout.
- You have a Project file that is stored in the library.
- You open the file from the library by using Project 2013.
In this situation, you find that the expected "checkout required" prompt isn't displayed, and therefore you can't respond to it. This means that if you make changes to the project and save, Project tells you that the changes can't be saved because checkout is required.

October 2018

15.0.5075.1000 https://support.microsoft.com/en-us/help/4022227/october-2-2018-update-for-project-2013-kb4022227 Improvements and fixes

This update makes sure that the Japanese era name in Project 2016 is displayed correctly when a new era begins.

September 2018

No client update in September

August 2018

No client update in August

July 2018

No client update in July

June 2018

15.0.5037.1000 https://support.microsoft.com/en-us/help/4022171/june-5-2018-update-for-project-2013-kb4022171 Improvements and fixes

When you delete a Gantt chart type view that has a drawing in Project 2013, Project 2013 may crash. Related to this, when you delete a drawing in a Gantt view, you may see the drawing is deleted from another view.
When you try to open an enterprise calendar while it is connected to a Project Web App instance by using Google Chrome, you receive the following error message:

Sorry, we were unable to open your project. Please try again. Is this happens again, contact your administrator.

May 2018

15.0.5031.1000 https://support.microsoft.com/en-us/help/4018379/may-1-2018-update-for-project-2013-kb4018379 Improvements and fixes

Consider the following scenario:
- You create a local project with some tasks and save it as a file.
- You create a second project, you have the first project share resources from it and you save it as a local file.
- You assign the resource to the tasks.
- You save the projects.
- You upload the project file and shared resource file to a SharePoint Online document library.
- You open the project file from the document library, and you receive the message:
  This file shares resources from a resource pool
- After you select OK, the shared resource file is also opened.
- You add a new task to the project file and assign it to a resource.
- You save the project file and close both files.
In this scenario, when you reopen the project file, the link to the shared resource file is lost.
Consider the following scenario:
- As a team member, you open your timesheet and enter work for two adjacent days.
- On the first day, you set the actual work value back to zero.
- On the first day, you set 8 hours of non-working time on an administrator task (for example, vacation).
- You send a status update for approval.
- You open the previous week timesheet.
- You enter actual work values.
- You send the timesheet for approval and the status manager approves it.
In this case, the actual work that's entered on the second day of the two days moves to the first day. The actual work should not move when the status update is applied to the project.
Consider the following scenario:
- You create a fixed duration task that is 100% complete.
- You create a custom calendar and add a one-day exception in the range of task duration.
- You change the task calendar to the custom calendar, and then you see that the duration reduces by one day.
- You save and then close the project.
- You reopen and recalculate the project, and then check the finish date.
In this scenario, the actual finish date is shifted to one day later.

April 2018

15.0.5023.1000 https://support.microsoft.com/en-us/help/4018335/april-3-2018-update-for-project-2013-kb4018335 Improvements and fixes

The Change Working Time dialog box enables you to select a date and to see the working shifts for that day listed in the Working times section. For example, a date shows working shifts of 8:00 AM to 12:00 PM and 1:00 PM to 5:00 PM. In some cases, you may be unable to see all the defined shifts for the given date because it's hidden behind the text that tells you the date's base calendar.
You open a project from the Project Center while using the Google Chrome browser. Then you see the following error message:
Sorry, we were unable to open your project. Please try again. If this happens again, contact your administrator.
Consider the following scenario:
- You have a project plan that has many tasks with long durations.
- You may have some baselines established.
- You save the project plan to an XML file.
- You open the XML file.
In this situation, if you use the 32-bit version of Project, it may crash. If you use the 64-bit version of Project, you notice that it takes a long time to open the file and Project uses many gigabytes of memory. When you look at the size of the XML file, you'll also notice that it is hundreds of megabytes in size. Note To fix this issue, you also have to set the value of registry key XmlDisableTimephasedSplitByDay to 1. See the Registry information for more information.
This update also contains the following improvement:
- When you save a project to the XML format, the following pieces of new information are exported:
  - The build number of Project that created the XML file.
  - Project, task, resource and assignment GUIDs.
  - Names of views.
  - Names of tables.
  - Names of filters.
  - Names of groups.
  - Names of data import and export maps.
  - Names of reports.
  - Names of drawings.
  Project exports these pieces of information but does not read them when you open or merge an XML file. Therefore, you can't, for example, add or change view names within an XML file, and have Project read and understood the information. Note If you do not want your XML files to have this new information, you can set the following registry key:
  - Location: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\15.0\MS Project\Options\Save\
  - Type: DWORD
  - Name: SimpleXmlexport
  - Value: 1

March 2018

15.0.5015.1000 https://support.microsoft.com/en-us/help/4018292/march-6-2018-update-for-project-2013-kb4018292 Improvements and fixes

If your project has manually scheduled tasks, and server notifications and reminders are turned on, you may receive unnecessary modified task notifications.
After actual work from a status update is applied to a project task, the work values may not appear in the project as expected. For example, you report 4 hours on a day, but when you open the project, you don't see the time-phased actual work value. This issue may occur when you assign a new resource to a task that is completed.
Assume that you create an .mpp file in a SharePoint document library, and then synchronize the library to the local computer by using OneDrive. When the file path is longer than 128 characters, the .mpp file can't be opened in Project 2013.
When you open an XML file that has time-phased baseline data in Project 2013, the time-phased data on assignments may be displayed incorrectly. For example, the time-phased work hours that you entered are 2, 2, 2, 2. However, they are displayed as 2, 0, 0.58, 1.42, 0. The totals stay the same.
When the Status field is referenced in a task custom field formula, other calculations may go slowly. For example, when you enter time-phased work data, it takes several seconds before you gain back control.

February 2018

15.0.5007.1000 https://support.microsoft.com/en-us/help/4011679/february-6-2018-update-for-project-2013-kb4011679 Improvements and fixes

Consider the following scenario:
- You save a baseline in your project and then you save the project.
- You save another baseline and you save the project, close it, and check it in.
- You query the database and view the MOD_DATE property for the given baselines.
- Another user opens the project and saves a different baseline.
- You query the database and check the MOD_DATE property for the three baselines.
In this situation, you find that the values of the MOD_DATE property for the baselines are the same. They should be different and reflect the date and time when you saved the baselines.
Consider the following scenario:
- You have a task that has a resource assigned.
- The task has a split in it. For example, there is a week of work, a week where no work exists and then a final week that has work.
- In the timesheet for this task, you enter hours on the task so that the work is completed up to the date where the split begins.
- The timesheet is submitted and then the status update is approved.
- After that, the project is opened in Project Web App and the task finish date is adjusted to a date that's after where the actual work is completed. For example, the actual finish date is set to the middle of the week where there is no work.
In this situation, the actual work is spread over the whole duration.
Consider the following scenario:
- You have a Project Web App site and Project Professional 2013 in your organization.
- You create some custom project fields and add them to your project detail pages (PDPs).
- In Project Web App, you create a new project and add values for these custom fields.
- You open the project in Project Professional 2013, make a change and then save the project.
- You open the project in Project Web App and view the custom field values on the PDPs.
In this situation, the values for these custom fields may be lost.

January 2018

15.0.4997.1000 https://support.microsoft.com/en-us/help/4011640/january-2-2018-update-for-project-2013-kb4011640 Improvements and fixes

When you operate on a project in Project 2013, you receive the following error message:
This operation cannot be completed because the source file contains invalid project data or the total number of rows would exceed the limit of 1,048,000 rows in a project. Validate the data in the source file, insert fewer rows, delete some rows, or consider dividing your project into subprojects to provide more space for tasks and resources.
This issue occurs if the assignment maximum unique ID of 1048576 is exceeded.
Consider the following scenario:
- You are using the German version of Project 2013.
- In Project 2013, you set the date format to use Weeks. For example, “3/W05".
- You create an automatically scheduled task.
- Then you modify either the Start or Finish field to change the date and save.
In this scenario, you receive the following error message:
The date you entered isn't supported for this field. Dates must be between January 1, 1984, through December 31, 2149. Enter the date in the correct format, eg., 15/06/00 or 15 June 2000

December 2017

15.0.4989.1000 https://support.microsoft.com/en-us/help/4011285/december-5-2017-update-for-project-2013-kb4011285 Improvements and fixes

Actual work that's been reported by team members in a project inadvertently gets spread differently from what was reported. For example, the actual work hours of 2, 2, 2, 2 are changed to 1.78, 1.78, 1.78, 2.45, and the totals stay the same but appear differently across the days. This issue occurs in certain situations when the project is edited in Project Web App even though the task setting and display server option Only allow task updates via Tasks and Timesheets is enabled.
When visual reports are generated from the context of a master project, the results are inconsistent and may fail completely in certain cases. For example, if you select the Earned Value Over Time Report chart, you may find that not all the costs from the sub projects are included in the pivot chart, and you may receive the following error message when you create a visual report:An unknown error has occurred. An error occurred and the requested action could not be completed at this time.
Consider the following scenario:
- You open a project from Project Server.
- You save the project by using the Save for Sharing functionality.
- You delete data from the project. For example, you delete an assignment on a task.
- You save the project back to the server.
In this situation, you may find that there is still data for the deleted element in reporting database. For instance, you still see actual work in the project.

November 2017

15.0.4981.1000 https://support.microsoft.com/en-us/help/4011235/november-7-2017-update-for-project-2013-kb4011235 Improvements and fixes

Consider the following scenario:
- You save a baseline in your project.
- You query the database and view the MOD_DATE property for the given baseline.
- You open the project and save a different baseline.
- You query the database and check the MOD_DATE property for the two baselines.
In this situation, you find that the values of the MOD_DATE property for the two baselines are the same. They should be different and reflect the dates when you save the baselines.

October 2017

15.0.4971.1000 https://support.microsoft.com/en-us/help/4011156/september-5-2017-update-for-project-2013-kb4011156 Improvements and fixes

Assume that you edit a project that's connected to Project Server 2013 in Project Professional 2013. When you try to save the project, you may receive the following error message:

Change would modify work entered by a team member We can't make that change because Project Web App is set to only allow actual work to be entered by team members through Timesheets or My Work.
This issue occurs after you install the July 11, 2017, update for Project 2013 (KB3213538).

September 2017

15.0.4963.1000 https://support.microsoft.com/en-us/help/4011109/september-5-2017-update-for-project-2013-kb4011109 Improvements and fixes

Consider the following scenario:
- You are using Project Professional 2013 or Project Standard 2013.
- You are working in a sheet-type view, such as the Gantt Chart view.
- You have created and applied a grouping in the Gantt Chart view.
In this scenario, when you print or preview a project, the horizontal bands appear. However, the vertical parts of the band that tie together the top and bottom of the band don't appear.

August 2017

15.0.4953.1000 https://support.microsoft.com/en-us/help/4011084/august-1-2017-update-for-project-2013-kb4011084 Improvements and fixes

Improves some translations for the Danish version of Project 2013.
This update also fixes the following issues:
- After you copy and paste a task within a project, the cost precision may be lost. For example, the cost of $76.85 on the source task becomes $76.65 on the pasted task.
- The Status value may be calculated incorrectly at the summary task level. For example, a summary task's status is displayed as Late even though all of its subtasks are calculated as Complete, Future Task, or On Schedule.

July 2017

15.0.4945.1000 https://support.microsoft.com/en-us/help/3213538/july-11-2017-update-for-project-2013-kb3213538 Improvements and fixes

After you import task, resource, and assignment information from an Excel worksheet in Project 2013, the work value is ignored.
If the task finish date is changed in the schedule web part, the actual work is spread unexpectedly.
Consider the following scenario:
- Your system region setting uses a comma as the decimal separator.
- In your project, you have a custom cost or number field defined.
- You save your data to the XML format.
- You give the XML file to an individual who opens it in the system where the decimal separator is a period.
In this scenario, the decimal portion of a number is lost. For example, 45.32 turns into 45.
After you replace a local resource with an enterprise resource, the actual work is transferred to the enterprise resource even though it's a protected work.

June 2017

15.0.4937.1000 https://support.microsoft.com/en-us/help/3191941/june-6-2017-update-for-project-2013-kb3191941 Improvements and fixes

Translates some terms in multiple languages to make sure that the meaning is accurate.
Pasting into the Resource Names field within the Task Usage view allows you to paste the same resource name more than once. This creates a duplicate and causes problems when you apply status updates from Project Server.
This update fixes the following issues:
- When you open an XML file that has timephased baseline data in Project 2013, the timephased data appears incorrectly. For example, on Saturday, the timephased baseline work should appear as 0.9h, but it instead appears as 0.88h.
- When you open a project from Project Server, you incorrectly see the following error message:

This project cannot be opened in read-write mode because a previous project checkin for this project is not complete.

When you open a .mpp file from a network location that has high latency, it takes a long time to open the file.
Consider the following:
- A project manager publishes a task to a team member.
- The team member in either a timesheet or in tasks within Project Web App reports work that's earlier than what was scheduled. For example, 8h of work was scheduled on Wednesday but 8h of actual work was reported and submitted for Monday.
- The status manager approves the update.
- The team member zeros out the actual work and moves it to a later date.
- The status manager approves the update.
- The project is opened in Project Server.

In this situation, the task's actual start date still reflects the set with the earlier update instead of the new update where the actual start date is later.

May 2017

15.0.4927.1000 https://support.microsoft.com/en-us/help/3191878/may-2-2017-update-for-project-2013-kb3191878 This update includes the following improvements and fixes:

When you print review project data, you may find that text that's wrapping in a cell appears differently than it does in the view. For example, the text may be missing, or the location where the text breaks from one line to the next is different.
When you open a project from a SharePoint list, Project 2013 may crash during the synchronization process.
If a cost and work resource are assigned to the same task, you may be unable to change the task's status manager.
It takes a long time to run VBA code that calls the CustomFieldValueListAdd method.

April 2017

15.0.4919.1000 https://support.microsoft.com/help/3178713 This update includes the following improvements and fixes:

Consider the following scenario:

You install either of the following updates that target Internet Explorer. October 2016 security monthly quality rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1 October 2016 Security Only Quality Update for Windows 7 SP1 and Windows Server 2008 R2 SP1 After this, you use one of the following features in Project:

Task Inspector.
Import Project Wizard.
Import Resources Wizard.
Deliverables.

In this situation, the given feature pane isn't displayed as expected.

In some circumstances, leveling on a week-by-week basis pushes tasks to the end of time (12/31/2149). Meanwhile, the leveling operation takes a long time to complete, and Project 2013 is unresponsive during that time.
When you open a project file from a SharePoint site through the Recent menu in Project 2013, the file is opened with read/write access, and you are not prompted to check out the project even though the Require documents to be checked out before they can be edited? SharePoint option is enabled.
When you assign a task to a resource with a max units 0, the assignment units is unexpectedly assigned as 100%.
Removing the start date from a resource assignment may cause the start date of the task to reschedule to "as soon as possible", and this may cause huge leading splits on the assignment.
When you edit an assignment finish date from a Task From type view, Project 2013 may crash.
When you open the Build Team dialog box in Project 2013 and enable the Online status next to name display option, Project may crash.

March 2017

15.0.4911.1000

https://support.microsoft.com/help/3178650 This update fixes the following issues:

The Visual Basic Applications ScreenUpdating property does not work as expected in Project 2013. Instead of freezing the screen content when the code runs, the screen continues to update. This produces screen flicker and causes the code to run slower.
In some cases, enterprise custom field data may be lost from a project after a status update has been applied, and the project is then opened in Project Professional 2013.
Assume that you open a project plan, and transfer local resource custom field lookup table values to an enterprise resource enterprise field. Then you save the project plan to a Project server. In this situation, some custom enterprise resource lookup table values may be lost.

February 2017

15.0.4903.1000 https://support.microsoft.com/en-us/help/3141499/february-7-2017-update-for-project-2013-kb3141499 This update fixes the following issues:

- When you print a project view such as the Gantt chartone one by one page in Project 2013, you may find that the row heights are taller than expected, that column widths are narrower than expected, and that font sizes are smaller than expected.
- When you open a project that has a milestone task, an actual start date may be added unexpectedly even though it did not have a date the last time it was saved.
- A task's % Complete value is also updated unexpectedly after you update the % Work Complete value.
- When you open a project and save it, the project ownership may unexpectedly change to you.
- The Cost Performance Index (CPI) value on a summary task may incorrectly display a value that's similar to -99999999999999.
- Consider the following scenario:
  - You are a user who edits projects in Project Professional or Project Web app.
  - You have been denied the Save Protected Baseline permission.
  - You open a project from Project Server.
  - You copy and paste a task to another location in the project.

January 2017

15.0.4893.1000 https://support.microsoft.com/en-us/kb/3141470 Fixes the following issues:

Assume that you save a project that has timephased baseline data to the XML format. When you open the XML file, the timephased baseline data is incorrect.
In Project Professional, you can now add the Locked field to a task view to facilitate closing tasks to update.In Microsoft Project Server, team members have project tasks assigned to them and they report their status (the work that they have performed) on these tasks. In some cases, a project manager may want to close these tasks to update so that team members are prevented from submitting status but still have visibility to the tasks.To achieve this, previously the project manager had to edit the project in Project Web App and set the Locked field on the given tasks in the project. Now, in order to lock or close tasks to update, the project manager can open their project in Project Professional and insert the Locked field into a task view where they can set the value to Yes or No as appropriate.
When you apply status updates in PWA, actual work is added to some assignments unexpectedly. For example, suppose that you have an assignment that has 35 hours total work and the status update is to apply 9 hours. When you view the results in Project Professional, you find that the assignment is unexpectedly completed. Meanwhile, the total work and the actual work have increased to 400 hours.
When you open a project from a SharePoint document library through a direct URL, the project is opened as checked-out even though the Require documents to be checked out before they can be edited? setting is enabled.
The Last Modified date in the Project Professional Open dialog box does not reflect the current time zone. For example, your time zone is Pacific Time (UTC-08:00) and the Last Modified date shows 09:15 instead of the expected 01:15.
When you save a baseline for a selected task, the task or assignment baseline values may be incorrectly rolled-up to and displayed on the related resources.

December 2016

15.0.4885.1000 https://support.microsoft.com/en-us/kb/3127978 Fixes the following issues:

Update the translation of the confirm message on a dialog box that appears when you change and close a project in Project 2013.
Fixes the following issues:
- Ribbon buttons such as the Edit Item button may be disabled on a SharePoint tasks list if there are multiple pages of tasks.
- After you save a baseline, timephased work and cost values aren't displayed as expected. For example, you may see work and cost during periods where no work or cost exists.
- When you save a Project 2003 project to Project Server, resource custom field values may be lost.
- When you open an XML file, you may find that work on existing assignments is lost, assignment delay is reset to zero, and assignment finish dates are incorrect.
- You may find that the modified date for a project as seen within the Clean Up Cache dialog box incorrectly shows the date and time as Coordinated Universal Time (UTC) instead of being adjusted to your time zone.
- In a master project, when you view the finish date of an inserted project summary task (this is the task that represents a subproject), you may find that it doesn't reflect the latest finish date of the tasks in the subproject.

November 2016

15.0.4875.1000 https://support.microsoft.com/en-us/kb/3127959 Fixes the following issues:

When you open certain XML files, you may receive the following invalid error message:

The actual finish date is before some of the previously entered timephased actual work values. If you continue with this operation, Project will truncate some of the previously entered timephased actual work values. To continue, click OK. To remove the actual finish date, click Cancel.

Additionally, when you open some XML files, the Gantt bars for fixed or an elapsed duration task show an unexpected trailing split.
If you have a task that has a duration of four elapsed months or longer, Project 2013 freezes when you save the project as an XML file.
Assume that you start Project Professional and connect it to a server, and then you select the load summary resource assignments check box. When you go to a resource usage view, a given resource may be displayed to be underallocated during a certain period (for example, daily) even though it should be displayed as overallocated.
When you level a project on a week-by-week basis, Project may freeze. Additionally, when the leveling finally finishes, tasks are scheduled out to the end of time which is December 31, 2149.
If an inserted subproject has a task that's 100% complete and has an ALAP constraint, the summary tasks within the subprojectmay have an incorrectly calculated start, finish, and duration.
Assume that you start Project Professional and connect it to a server, and then you select the load summary resource assignments (SRA) check box. When you go to a resource usage view, a given resource may displayed to be overallocated during a certain period (for example, daily) even though it should not displayed as overallocated. This can occur if the actual work value from the SRA for the given period isn’t handled correctly.
When you open a project from a SharePoint site and then click the Edit Project button from the banner, you may see an error message that resembles the following:

You have made changes to '<project name>'.

Another user has also made changes. What would you like to do?

Click Discard to discard your changes and edit the latest version.

Click Save as to save your changes to a different file and open the latest version.

This problem can occur with projects that were stored in Project Server.

If you want to fix the following issue in Project 2013, please install November 1, 2016, update for Office 2016 (KB3118340).

When you use the Send as Attachment email function to share a project, Project 2013 may crash if you have Outlook 2016 installed.

October 2016

https://support.microsoft.com/en-us/kb/3118351 15.0.4867.1003 Fixes the following issues:

Consider the following scenario:
- You have an enterprise calendar.
- You set the enterprise calendar as the base calendar for some projects in the project server.
- In preparation to delete the enterprise calendar, you go to the projects that are using the calendar and select a different calendar for them.
- In Project Web App settings, you go to the Enterprise Calendars page and try to delete the calendar.
In this situation, you can't delete the calendar because you're told that it's in use. After you install this update, you can now go to the projects in which the calendar is used, and use the organizer to delete it. After the calendar is deleted from the individual project that uses it, you will then be able to go to PWA and delete the calendar.
When you publish a project from Project 2013 to PWA, resource enterprise custom field values may be lost.
When you open an XML file, the duration of a fixed duration task may be changed unexpectedly. For example, you have a 9-day fixed duration task that begins on Monday and also an assignment that has 80h of work. 10h of work is completed across the first five days. Therefore, the work contour resembles the following:
2h, 2h, 2h, 2h, 2h, 0h, 0h, 17.5h, 17.5h, 17.5h, 17.5h
When you open the project, the duration is changed to 13.75 days and the contour resembles the following:
2h, 2h, 2h, 2h, 2h, 0h, 0h, 8h, 8h, 8h, 8h, 8h, 0h, 0h, 8h, 8h, 8h, 6h
If a task is updated to be 100% complete and the cost resource for the task is more than $83.33, the duration is reset unexpectedly.
Consider the following scenario:
- You have a master project in which you have at least one sub project.
- The master and sub projects have been saved to Project Server.
- You unlink the sub project from the master project.
- You save the sub project back to Project Server.
In this situation, the assignments in the sub project are lost.
When you publish a project to Project Server, formulas associated with a custom field that use the Current Date function will display the correct values. However, the published data for the same field may display a different value. For example, you have a custom task field with a formula that displays the current date. Then, you publish a project and you see the expected values on tasks in the custom field in PWA. Two days later, you open the same project in Project 2013, you see the correct values and publish the project. However, when you see the published values within the custom field in PWA, you see the same value in two days earlier.
Consider the following scenario:
- You have a master project.
- You have several sub projects in the master project.
- The sub projects are set to read-only.
- You open the master project.
- You select the Edit Project button from the banner.
In this situation, the sub projects are opened by using the read/write access even though they are set to read-only.
Consider the following scenario:
- You have a task in a project that has a resource assigned.
- The resource assignment has 80h of work.
- The resource assignment has split work wherein it works the first week, and it has a zero work split for the second week and finally has work on the last week.
- The assignment is 50% complete and the first week is completed.
On the Task Usage view, the actual work details of the assignment resemble the following:
8h, 8h, 8h, 8h, 8h, 0h, 0h, 0h, 0h, 0h
You view the stop date and also notice that it's the same as the resume date. After you install the update, the trailing zero actual work values no longer appear and the stop date corresponds to where the last timephased actual work value that's more than zero is ended, and it's not the resume date which starts at the beginning of the third week.

September 2016

https://support.microsoft.com/en-us/kb/3115493 15.0.4859.1000

Enables DialogAPI 1.1 requirement set in Office 2013 applications and Mailbox 1.4 requirement set in Outlook 2013.
Fixes the following issues:
- When you merge or append a tab-delimited text document into an existing project, the changes that are made can't be saved in Project 2013.
- Assume that you create a project from a template in Project Web App. When you try to enter the timephased cost or actual cost for a cost resource in Project 2013, the values that you enter can't be applied, and Project 2013 may crash.
- When status updates are applied, trailing timephased actual work values are created. This causes finish dates are later than expected.

August 2016

https://support.microsoft.com/en-us/kb/3115434 15.0.4849.1000 This update fixes the following issues:

Translates some terms in multiple languages to make sure that the meaning is accurate.
When you try to reduce remaining work on a task or assignment, you may receive the following error message unexpectedly:

Change would modify work entered by a team member.

July 2016

https://support.microsoft.com/en-us/kb/3115264 15.0.4841.1000 This update fixes the following issues:

Assume that you have a Project .mpp file that's stored in a SharePoint document library. When you click the file name, the project opens but you don't see a banner that offers you the ability to edit or check out the project. Instead, the project may keep in a read-only state and you can't save or check in changes.Note To fix this issue, you also need to install July 5, 2016, update for Office 2013 (KB3115255).
Assume that you start Project 2013 and connect it to a server, and then you select to load summary resource assignments. In this situation, when you go to a Resource Usage view and scroll through the resources, Project 2013 may crash. This issue occurs after you install March 8, 2016, update for Project 2013 (KB3114843).
Assume that you set the primary or default Project Web App language to simplified Chinese and set the alternative language to English. When you try to synchronize projects with a SharePoint task list, the process fails.

June 2016

https://support.microsoft.com/en-us/kb/3115164 15.0.4833.1000

Updates the translation of the project check in dialog box for French to make sure that the meaning is accurate.
Fixes the following issues:
- When you save a project for sharing, and then you save it back to the server, the baseline data is deleted from the project if you don't have the Save Protected Baseline permission.
- When you use Project 2013 with Project Web App online, some users can't edit enterprise calendars. Meanwhile, the following error message is displayed:
  
  You need to have Microsoft Project Professional 2016 Preview installed and configured to connect to a profile for this Project Web App site. You can do so by opening Project Professional, and adding the URL of a site in your PWA site collection to the Manage Accounts dialog in the Info tab of the File menu. Then, close Project Professional, and open it connected to this profile before trying this operation again. If Project Professional is already loaded, ensure that it is connected to the profile for this Project Web App site and that there are no dialog boxes open.
- When you add a resource or do a Save As operation to the MPP format on a project that's connected to Project Web App, Project 2013 may crash.
- After you set a resource to have max units that's greater than 100%, you can't assign the resource to a task at 100% units.
- When you open projects, Project 2013 may crash. This issue occurs for some projects in which certain calendars in those projects were duplicated.
- Consider the following scenario:
  - You have a task in your project.
  - You have two resources that are assigned to the task.
  - On one of the assignments, delay is added.
  - You publish the project to a server where protected actual work is enabled.
  - The resource who owns the assignment where delay doesn't exist reports work and the status update is applied to the task. The other assignment still has no actual work.
  - As the project manager, you set the work value to zero on the assignment that has no actual work.
  In this situation, the actual start and actual finish dates are set on the assignment even though these dates weren't reported by the team member. Later, when the project manager adds work back to the assignment and tries to reschedule it, he fails. Because Project tells him that the change would change work entered by a team member.
- Consider this scenario:
  - A task has one 8-hour assignment and it is published to a team member.
  - The team member opens their timesheet and enters multiple time-phased actual work values. For example, 8h on the first day and 3h on the second day.
  - The team member changes his mind and zeros out the last time-phased value. In this case, the 3h turns to 0h.
  - The team member submits their timesheet and the status manager approves the update which is then applied to the project.
  When the task and assignment are viewed in Project Professional, the task ends on the second day and the assignment ends on the first day. The expectation is that the task ends at the same time as the assignment.
- Assume that you change the name of the project summary task and save the project in Project 2013 on a computer that has Windows 8.1 or Windows 10 installed. When you open the project again, the name is reverted to the previous one.
- When you try to reset the work breakdown structure (WBS) for a selection of tasks, the whole project is updated instead.
- Assume that you open a master project that has many subprojects in Project 2013. When you press ESC to cancel the loading, Project 2013 may crash.
- When you open a project that has many cross project links in Project 2013, it may freeze and eventually crash if the computer runs out of memory.
- When you use the Project Import Wizard, you receive an incorrect merge result if the merge key is set to a custom field.
- Consider the following scenario:
  - You open a project in Project Server.
  - You close the project but don't check it in.
  - The project on the server is forced checked-in.
  - You try to open the project.
  In this situation, you don't receive a dialog message that indicates to load the latest version from the server.
- When you scale a printout to fit to one page in Project 2013, the printed output is unreadable.
- Assume that you change the name of an enterprise calendar. When you open projects that use that calendar, Project 2013 may crash.
- When you save a project, some baseline information may be lost if you don't have permission to save a baseline.
- When you set the % Work Complete value for summary tasks in Project 2013, Project 2013 may stop responding. This issue may occur if Project is connected to a Project server where the Only allow task updates via Tasks and Timesheets setting is enabled.
- If you set % Work Complete progress on a summary task in Project 2013, work and actual work may incorrectly be added to subtasks that don't have a resource assigned.
- When you connect to Project Server, the last modified and last published timestamps aren't displayed as your current timezone in Project 2013.

May 2016

https://support.microsoft.com/en-us/kb/3115040 15.0.4823.1000

A better translation of the following messages is now available for the Japanese language. These messages appear when a user tries to edit the name of an enterprise resource within a project:
- Changes to enterprise resources will be lost.
- You can modify an enterprise resource in a project for modeling purposes and publishing the project will include any changes. Your changes will be overwritten when the project is next opened.
A user with security permission can modify the attributes of this resource by checking out the resource with the Open Enterprise Resource Pool command.
Fixes the following issues:
- Consider the following scenario:
  - A team member is assigned to a task that begins on Monday.
  - The task is published to the team member.
  - The team member opens their timesheet and enters actual work on Wednesday.
  - The team member submits their timesheet.
  - The project manager approves the status update from the team member.
  In this situation, the task still shows that it begins on Monday instead of Wednesday.
- After you import data from an Excel workbook, the project plan isn't updated accordingly. For example, in the Excel workbook, you update the work on an assignment. Then, you import the data to Project. In this situation, the update is ignored.
- When you try to print a specified amount of pages and select to have the timescale fit to the end of the page, the timescale doesn't fill the horizontal page.
- Consider the following scenario:
  - A task has a resource assigned to it.
  - An actual start date is entered on the assignment, and the date is earlier than the task’s start date.
  In this scenario, the assignment's work remains on the same dates, and the task's finish date remains the same. And there are leading zero actual work values that go from the assignment actual start date up to the point where the assignment work begins. The expected scenario is the assignment work moves back to the new actual start date as appropriate, and the task's finish date should reflect the new finish date of the assignment.
- Assume that you change a date by using the date picker, and the date is not in the current year. In this situation, the day and month are changed but the year isn't changed. This issue occurs when the date format is set to 4/W04.
- When a summary task is viewed in the task inspector, the subtasks aren't listed.
- When you save subprojects in the context of a master project, Project 2013 may crash. This issue may occur if the subprojects have Visual Basic Applications code in them.
- When you delete a resource from a split task, the split task is deleted unexpectedly.
- When you set a finish date for a fixed duration task in which assignments on the task have actual work entered on non-working times, the finish date is changed to a different date from what you entered, and the assignment finish date is changed to the task finish date even though the assignment doesn't share the task's finish date.
- Setting actual cost for cost assignments on tasks doesn't always calculate the correct progress as expected. This issue occurs when the assignment is the only resource on the task.
- When you import a project from an XML file, time-phased baseline work isn't imported correctly. For example, on an assignment, the baseline cost values over a 10-day period are as follows:
  2h, 3h, 4h, 5h, 6h, 8h, 8h, 8h, 8h, 8h.
  When it's imported, the values change to 2h, 6h, 6h, 6h, 6h, 6h, 6h, 6h, 6h.
- If you use the Assign Resources dialog box to replace one resource with another resource, the total work value displayed in the Resource Usage view isn't always updated correctly.

April 2016

https://support.microsoft.com/en-us/kb/3114954 15.0.4815.1000

Assume that you open a project that shares resources from a common resource pool, and when you are prompted, you click to open the resource pool. When you change the assignments in the sharing project, the changes are not reflected in the resource pool project.
When a resource is overallocated by a combination of actual work and remaining work, the work doesn't appear in red (overallocated) in that period when it's leveled on a day-by-day basis.
You can't create a project from a SharePoint task list if the list has data validation rules set.
Microsoft Project doesn't always calculate the finish dates of some tasks. This causes them to finish later than expected. This can occur in a scheduled from finish project where implied dependencies from a summary task to the sub tasks aren't always respected.
Consider the following scenario:
- You have an enterprise resource that's assigned to a project.
- You change the booking type for the resource.
- You save and then open the project again.
In this situation, the booking type property isn't saved.
Consider this scenario:
- You have an enterprise resource custom field.
- The field has a lookup table applied to it, and multiple values can be selected.
- You have a resource that has a value in the field that's longer than 255 characters.
- You open a project in Project Professional that uses this resource.
In this situation, you receive the following error message:

The value you entered does not exist in the lookup table of this code. All values must be predefined in the code lookup table. Contact your server administrator to get new values added.

You also find that the list of values in the field is truncated or has disappeared completely.This issue occurs after you install December 8, 2015, update for Project 2013 (KB3114366).
When you select multiple tasks and try to replace a resource, the replace action doesn't work if the initial resource that you are replacing isn't assigned to all the selected tasks.
The Visual Basic Application (VBA) OpenXML method fails with the following error message:

Run-time error '1101'

Application-defined or object-defined error.

This issue occurs after you install September 8, 2015, update for Project 2013 (KB3085510).
When you open a master project that has cross project links, Project 2013 may crash.

March 2016

https://support.microsoft.com/en-us/kb/3114843 15.0.4805.1000

When you open a Project file from a SharePoint document library, the file is sometimes opened as read-only when it should be read and write. In other cases, the project is sometimes opened as read and write but you can't save changes.Note To fix this issue, you also need to install March 8, 2016, update for Office 2013 (KB3114816).
You can't publish a project in Project Web App and receive an error message that looks something like the following:

Cannot insert duplicate key in object 'pub.MSP_PROJECT_RESOURCES'
After you level a project, some resources may remain overallocated.
You set the Default Assignment Owner field for an enterprise resource. Then, you create a project that uses the resource. In this situation, the Default Assignment Owner field is blank.
When a plan is opened for edit in Project 2013 or in Project Web App, in some cases, additional actual work may appear on an assignment.
It takes a long time to close and check-in a master project if Summary Resource Assignments (SRA) are loaded.
It takes a long time to open multiple projects from Project Server in Project 2013.
If you enable the Only allow task updates via Tasks and Timesheets option, you can't set tasks to 100% complete if the task has an assignment with zero work.
If you have a project saved to Project Server, you can't access project level properties.
Macros that exist in the local global template don't work if they are invoked from the ribbon. This issue occurs when Project 2013 is connected to Project Server.
After you edit projects in Project Web App, paste-linked data no longer works properly. Normally, when you open a project that has paste-linked information, you see the following message:

"<project name>" contains lined information. Do you want to re-establish the links? * If you want to update this information by accessing the linked project or the linked program and file, click Yes. * If you do not want this information and you want to use the existing information instead, click No.

In this case, if you select Yes, you receive the following error message:

Project cannot connect to link. Do you want to delete the link?
If you save an incremental baseline that rolls up baseline values from a task to summary tasks, the timephased baseline values of the summary tasks are deleted from the dbo.MSP_EpmTaskBaselineByDay table in the reporting database.
If you delete data by using the delete or backspace key in Project 2013, the BeforeTaskChange, BeforeResourceChange, and BeforeAssignmentChange events will not be triggered.
When you level resources for projects in Project 2013, Project 2013 may crash.
If you have the option to clear leveling values before leveling or you click the Clear Leveling button within the Resource Leveling dialog box, it doesn't always work correctly. Instead, tasks may be leveled to unexpected dates or values may still be found in the Leveling Delay field.

February 2016

https://support.microsoft.com/en-us/kb/3114739 15.0.4797.1000

When you enable the Level only within available slack option to level a resource, this option should allow assignments to be scheduled later as long as the overall project isn't finished. However, you receive a message stating that leveling can't resolve over allocated resources. When you select the Skip All button, leveling pushes tasks past the project finish date.
When you open a project from a server, it may take a long time if the project doesn't exist in the user's local active cache.
When you apply a grouping to a task type view, baseline finish type fields may not show the expected value on the grouping summary row tasks. Instead of showing the latest finish date as expected, the field shows Not Available if at least one of the grouped tasks doesn't have a baseline finish date.
Consider the following scenario:
- A user enters time phased actual work on an assignment and submits the work for approval.
- The status manager approves the update.
- The user changes the assignment start date and then submits the change.
- The status manager approves the update.
In this scenario, the time phased actual work may move to another date.
Assume that you have a series of related tasks (they have dependencies between them) and you now make one of the tasks inactive. In this situation, the successor tasks to the inactive task may be scheduled later than expected.
Consider the following scenario:
- You have a 1d task that has an assigned resource and the assignment has 8h of work on a single day.
- You set the assignment contour to front-loaded. At this point, you now have two daily work segments of 6.67h and 1.33h.
- You save the project as an XML file and reopen it.
In this situation, the work contour is lost and the opened assignment has a single work segment of 8h. In a related scenario, if you open an XML file, Project 2013 may crash and becomes unresponsive. This issue occurs after you install December 8, 2015, update for Project 2013 (KB3114366).

January 2016

https://support.microsoft.com/en-us/kb/3114510 15.0.4787.1000

When you save a password protected file by using the Save As function in Project 2013, the file may become corrupted and then can't be opened.
When you try to save a project to the Project 2007 format in Project 2013, Project 2013 crashes. This issue occurs if the project has a table defined, and the Lock first column option is enabled in the table and the locked column has a title associated with it.
When you use Project 2013 with certain Windows region date and time formats (for example, Spanish (Mexico)), baseline bars aren't displayed in the Gantt chart.
When you scroll horizontally across the timescale in a Gantt type view, the nonworking time shading might not be displayed correctly. This issue occurs if you have chosen to display the shading in front of the bars.
When you try to import an XML file in Project 2013, nothing is imported and no error message is displayed. This issue occurs if the namespace tag is different from the following default one:
<Project xmlns="http://schemas.microsoft.com/project">
This issue occurs after you install September 8, 2015, update for Project 2013 (KB3085510).
When you import data from an Excel workbook in Project 2013, text data that is mapped into text type fields is truncated to 128 characters. For example, a task name is truncated.

Project 2013 Cumulative Update (RTM to the end of 2015)

Brian Smith — Mon, 25 Mar 2019 21:14:52 GMT

This page lists all of the released Cumulative Updates (CU) and Service Packs (SP) for Microsoft Project 2013, both Standard and Professional, from RTM to the end of 2015. From February 2015 onwards all fixes are shipped in Public Updates (PU). From March 2015 client updates available via Windows Update and Download Center, server updates only via Download Center. From April 2016 the Office client updates are shipped 1st Tuesday. The October 2016 client updates were released on the 2nd Tuesday. From April 2015 onwards all fixes require SP1 as a prerequisite. They are listed in reverse date order - newest at the top. Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack). I have also recorded the version you will see in the File, Account, About Microsoft Project link Project 2013. If you are running a click to run installation - such as Project for Office 365 see http://support2.microsoft.com/gp/office-2013-365-update for details of the update schedules - but the version numbers and fixes should be roughly in line with the CU releases below.

December 2015

https://support.microsoft.com/en-us/kb/3114366 15.0.4779.1000

Assume that you have an MPP file that is created by using the Project server Save for Sharing feature, and you are now saving it back to the server. In this case, the status manager property on each task and the project owner may change unexpectedly to be the person who is saving the file to the server.
In some cases, when you save a project to Project Server, you receive a 9000 error code.
When you import timephased data by using XML files in Project 2013, the <WorkContour> tags are ignored. This issue occurs when the timephased actual work values exist but the remaining work timephased values are not complete in the XML file.
When you try to unlink a subproject from a master project that has a custom field with a lookup table defined, Project 2013 crashes. This issue occurs if the subproject doesn't have the same lookup table definition as in the master project but the custom field has values.
When you open an XML file in Project 2013, only the last row of the resource availability lines is displayed.
When you try to open a large project in Project 2013, you receive the following error message:

This operation cannot be completed because the source file contains invalid project data or the total number of rows would exceed the limit of 1,048,000 rows in a project. Validate the data in the source file, insert fewer rows, delete some rows, or consider dividing your project into subprojects to provide more space for tasks and resources.

This issue occurs if the assignment maximum unique ID of 1048576 is exceeded.
When you use the UpdateResources Project Server Interface (PSI) method to change a resource, security groups that are assigned to the resource and the claims account information about the resource may be lost.
It takes a long time to open an XML file and create a new project in Project 2013.
When you view the physical "% complete" field on an inserted project summary task in a master project, the value doesn't always reflect the same value on the project summary task in the sub project. In addition, if you open the master project and the sub project isn't in memory, the physical "% value" is displayed as "0%."

November 2015

https://support.microsoft.com/en-us/kb/3101506 15.0.4771.1000

After you apply status updates to project schedules, the actual work contours on some assignments unexpectedly display zero actual work values in various time periods.
Assume that you display the Hyperlink field in Project Professional. On a task, you enter an address in the Hyperlink field to a document that's stored on a SharePoint site, and then you click the link. Sometimes in this situation, the document doesn't open, and you're redirected to the root site where the document is stored.
Assume that you have a summary task that contains one or more subtasks. Then, you make the summary task become a non-summary task (either by outdenting all subtasks or by deleting all subtasks). In this scenario,the internal property on the task that specifies the duration format (minutes, hours, days, weeks, and months) may not get set correctly. Therefore, when you publish the project, the reporting data is inaccurate, and the duration of the given task isn't correct.
When you use an auto filter on a text type field (such as the task name) and the values in the field are many and varied, Project 2013 may crash.
In some cases, a task's % Complete displays 99% even though the % Work Complete on all the assignments on the task shows 100%.
Saving to a SharePoint task list from Project Professional 2013 may fail when there's both an enterprise resource and a user account on the Project server that share the same name.
When you save a project back to a server, you receive the following error message:
Project Web App was unable to find the specified resource.
After you import and merge data from an external source (for example, from an Excel workbook), only the first assignment on the task is updated.

Additionally, this security update also includes the fixes for the issues that are described in this following Microsoft Knowledge Base article:

3101502 November 10, 2015, update for Project Server 2013

October 2015

https://support.microsoft.com/en-us/kb/3085590 15.0.4763.1000

After status updates are accepted and applied to tasks in a project, the total actual work on the assignments may become larger, and the new actual work appears in time periods where the user didn't report it. For example, you report 8h on Monday and 3h on Tuesday. When you view the assignment in the project after the update is applied, besides the 8h on Monday and 3h on Tuesday, you may also see 8h on Thursday and Friday.
After you level resources by using the week-by-week or month-by-month basis in Project 2013, the resources remain overallocated.
When you force check in a project on a Project 2013 server, the project is still displayed as checked out in Project Professional. If you try to open and edit it in Project Professional, you receive an error message that states that the file in the local cache is damaged.
When you open and then save a project file to a Project server, the task finish date and duration are changed. This issue occurs if the assignment finish date doesn't match the task finish date. This can be the case with fixed duration tasks.
When you use Microsoft Visual Basic for Applications (VBA) macros to edit project data within the Project.BeforeSave event handler, the edits to the project may not be saved if the project is saved to Project Server.
When you start a task before the project start date, certain time scale labels in a Gantt view such as those that work from a project's start (for example, the "W1, W2, W3, W4… (From Start)" label) show the week starting at the beginning of the task instead of at the beginning of the project.
In some cases, the font control shown on the Tasks tab in the ribbon within the Font group is empty and the font size is 0. When you try to select a font or size, Project 2013 may crash.
After you use the Replace button on the Assign Resource dialog to switch one resource for another, the new assignment keeps all the custom properties of the old assignment. For example, if the old assignment contains values in custom fields or baselines and other such properties, the new assignment will have these same values.
When you try to import and merge to an existing project in Project 2013, Project 2013 may crash and the task outline in the project may be damaged. This issue occurs after you have September 8, 2015, update for Project 2013 (KB3085510) installed.
When you try to import certain XML files in Project 2013, Project 2013 may crash.

September 2015

https://support.microsoft.com/en-us/kb/3085510 15.0.4753.1000

Enables single sign-on (SSO) for ADAL on cloud domain-joined computers. On cloud domain-joined computer that has Modern Authentication enabled, domain accounts seem to be logged in but can't open files.
When Project 2013 is running in the background, the Auto Save feature that has the Prompt before saving option enabled causes the processor to be fully allocated.
When you open an .xml file to create a project in Project 2013, it takes longer than merging the data into an existing or blank project.
When you try to import an Excel workbook into a project in Project 2013, some assignment information is lost.
When you reduce the work of a fixed work task while editing in Project in the schedule web part, the duration of the task may be reduced unexpectedly.
When you open an Excel workbook in Project 2013, not all actual works are imported for resources for tasks.
When you apply actual work to a project in Project 2013, the actual work may be applied to an incorrect resource. This issue may occur when one resource is exchanged for another while you're using the Assign Resources dialog box and a status update is pending.
When you open a SharePoint task list in Project 2013 and close it without saving, the %Complete fields of tasks are updated to incorrect values.
When you assign a resource on the Resources tab of the Task Information dialog box to a task in Project 2013, the Units value of the resource is always set to 100% even if another value is entered.
You can't remove remaining work from a manually scheduled task in Project 2013 when the task is published to Project Server, and when the Only allow task updates via Tasks and Timesheets task settings and display options are enabled.
After you change a custom field on a project detail page, the milestone flag on a task is reset to Yes unexpectedly.
When you use a task template that has cost resources assigned to create a project in Project Web App and then you open the project in Project 2013, Project 2013 crashes.
When you try to update budget costs on resources in Project 2013, Project 2013 may crash.
When you try to save a project to Project Server or you try to view the project properties of the project, Project 2013 may crash if some project level custom fields type is number.
When Project Professional 2013 attempts to save a project to a Project server right after the first failure, Project 2013 may crash.
When you try to save a project from an earlier version of Project Server, you receive the following error message:

Error 9000 Save job cancelled in the queue: Root element is missing.

August 2015

https://support.microsoft.com/en-us/kb/3055022 15.0.4745.1000

When you create a visual report that is based on task usage data in Project 2013 and set the level of usage data option to weeks, you may receive the following error message:

Unknown error has occurred. An error occurred and the requested action could not be completed at this time.

You may also receive the previous error message when you try to save cube data. Then, if you click OK, you receive the following error message:

This is not a valid file name. File names must be less than 255 characters and they cannot contain any of the following characters: \ " / ; ? < > |
If a subproject in a master project has a baseline date that is earlier than its start date while the master project does not have a baseline set for the task that represents the subproject, you may be unable to create a visual report for the master project in Project 2013. Instead, you receive the following error message:

An unknown error has occurred. An error occurred and the requested action could not be completed at this time.
When you use Project 2013 to open a project that is saved in Project Web App, the start date and the end date of a task is reset to the constraint date instead of the dates that are scheduled according to the associated summary task. This issue occurs if you set the Calculate project after each edit option to Off.
When you try to synchronize tasks with a SharePoint task list in Project 2013, Project 2013 crashes.
Consider the following scenario:If you save a project as an .xml file, custom calendar information may not be saved. Therefore, when you open the .xml file, the calendar information is not found.
- You use Project 2013 to open a project file (.mpp) from a SharePoint document library.
- You Save the file to a nondefault file format such as .txt, csv, or xlsx.
- You keep the MPP file open.
- You make some changes to the project, and then save it.
In this scenario, the changes that you made to the MPP file are not saved properly.
When you open an XML project file in Project 2013, a milestone task that is marked as completed may incorrectly be set to 99%.
When you set a baseline for a project in Project 2013, if a cost resource is assigned to a milestone task, the sum of the timephased cost for that assignment is displayed incorrectly as the assignment remaining cost.

July 2015

https://support.microsoft.com/en-us/kb/3054956 15.0.4737.1001

Assume that a project has a fixed work task, and a resource assignment on the task has a delay. In this situation, an unexpected trailing zero actual work contour may be created on a resource assignment on the task.
When you roll up baseline values from selected tasks into all summary tasks, the time-phased baseline work and cost values may be incorrect. For example, suppose that over a series of days, the time-phased baseline work values on the summary task are 4h, 2h, 8h, 0h, and 2.5h. After you save the baseline, the values may change to something like 4h, 4.13h, 4.13h, 4.13h, and 4.13h.
When you scroll through a project in the Gantt Chart view in Project 2013, the Gantt chart might not be displayed correctly until you press F9 to recalculate the schedule.
When you scroll to different resources in the Assign Resource dialog box in order to select those that you want to assign to a task, an incorrect resource may be assigned as soon as you click the Assign button. Also, dragging and dropping resources from the Assign Resources dialog box to tasks in the project does not work.
After you change a task's schedule mode from automatic to manual or vice versa, the actual work of the task is changed unexpectedly. For example, you may have actual work that resembles the following:
5, 2, 2, 1, 0, -, 9, 9, 3, 9
After you change the task mode, the actual work is changed to the following:
4.45, 2.33, 2, 1.12, 0.12, -, 8, 9, 3.67, 8.33, 1
When you apply view grouping on tasks by using a field that has lookup table values, incorrect labels are displayed for the grouping summary rows.
When you recalculate a Project 2007 based project in Project 2013, milestone tasks may have unexpected schedule and progress changes. For example, the progress is reduced from 100% to 99%.
When you try to create a visual report on a master project that contains a project summary task, you receive the following error message if the project summary task does not have a matching baseline:

An error occurred and the requested action could not be completed at this time.
When you edit a custom flag field for an enterprise resource in Project 2013 Professional, the changes are not saved as expected.
After you set the Site creation settings value to Do not create a site on the Project Site Provisioning Settings page, the Publish Project dialog box is still displayed when you publish a project.
Consider the following scenario:.
- You add a local resource to a project.
- You save the project to a Project server.
- You add an enterprise resource to the server that has exactly the same name as the local resource in the project.
- You open the project, make some changes and then save the project.
In this situation, the save process fails and the project is not saved.
When you assign a resource to a task in the Task Information dialog box in Project 2013, the resource assignment unit may be incorrect if the Resource Availability for that resource is changed
When you synchronize a project to a SharePoint task list and map a custom field, the save operation is slow.

June 2015

https://support.microsoft.com/en-us/kb/3054830 15.0.4727.1000

When you use the Update Project function, it may incorrectly apply progress to inactive tasks. As soon as this occurs, the inactive tasks are no longer activated.
When Project Professional 2013 opens a Project Server-based project from the local cache, Project Professional 2013 crashes.
You cannot assign a resource in Project Professional 2013 if the resource name contains a semicolon and if the semicolon is set as the list separator on the client computer.
When you print a project that contains tasks, resources or assignments that have multiline notes, Project 2013 crashes. This issue occurs if the Print notes option in the Page Setup dialog box is selected.
When tasks have resource assignments, and the assignments on the task do not share the same start date as the task, resource leveling does not level resources as expected.
After you set the Week starts on field to a value other than Sunday, calendar nonworking time exceptions are highlighted incorrectly in usage type views.
When you import resource data from an Excel, TXT, or CSV format file in Project 2013, the resource is not imported successfully. Instead, you see an error that resembles the following:

The file "<file name>." cannot be opened. * Check that the file name and path are correct. * Check that the file format is recognized by Project.

Additionally, when you edit a data map, you may see a message that resembles the following if you try to add a field on the Map Optionspage of the Import Wizard:

The field "<characters listed here>" does not exist.

In the part of this message that states "characters listed here," garbage characters are displayed instead of a field name.
When you save a project in Project Professional or Project Web App, custom field values are lost.Note This issue occurs after you apply the March 10, 2015 update for Project Server 2013 (KB2956178).
When you open a project in Project Professional, you find that local custom fields are copied from the enterprise global template into your project. The enterprise global should not have local custom fields in it, and these fields should not be copied to individual projects. This fix prevents these fields from being incorrectly copied into your project and overwriting local custom fields that you may have already defined.

May 2015

https://support.microsoft.com/en-us/kb/2986246/ 15.0.4719.1000

When you apply actual work to a project in Project 2013, the actual work may be applied to an incorrect resource. This issue may occur when one resource is exchanged for another while a status update is pending.
When you edit a cell through the entry bar for a project in Project 2013, the cell is displayed as solid black and you cannot see the cell value.
When you export an XML file and then import it to a new project in Project 2013, the work and the actual work time-phased values may be incorrect.
When you publish a project to a project server that contains an updated status manager on a task, the status manager name is not updated in the reporting database on the server.
When you browse to the Project Center and then click to open a project in Project Professional, the wrong profile may be used and the URL information in the profile is overwritten with the wrong details. This issue occurs most frequently when you have multiple URLs that point to the same physical Project Web App (PWA) instance, and you have different profile in Project Professional for each URL.
When you try to save enterprise resources where there is an enterprise custom field originally created in Project 2003, the changes are not saved.
When you open a series of projects that have cross-project dependencies in Project 2013, Project may crash.

April 2015

https://support.microsoft.com/en-us/kb/2965279/ 15.0.4709.1000 This article describes update KB2965279 for Microsoft Project 2013 that was released on April 14, 2015. This update has a prerequisite. Please be aware that the update in Download Center applies to Microsoft Installer (.msi)-based edition of Office 2013. It does not apply to the Office 2013 Click-to-Run editions such as Microsoft Office 365 Home. (How to determine?).

Improvements and Fixes

Fixes the following issues:

When you open a project document from a SharePoint Server 2013 document library, the document is opened in read-only mode, and you cannot change the option to edit the document.
Some fields such as the % Comp. and the Date fields are not displayed in the Links Between Projects dialog box in Project 2013.
When you use the week-by-week basis to level resources for a project in Project 2013, Project 2013 may stop responding.
When you make some changes to a project in a form view such as the Task Form view in Project 2013, the unsaved changes may be lost. This issue occurs if Project 2013 is integrated with Microsoft Lync and your status is changed in Lync.Note To disable the Lync integration, follow the steps in the "Registry Information" section after you apply the update.
When you merge the data of an .xml file into a project in Project 2013, levelling delays of all tasks are reset unexpectedly. Additionally, the total task work may be increased in some cases.
You cannot complete a task that has milestone assignments (assignments that contain zero work) and in which the Only allow task updates via Tasks and Timesheets option is enabled in the Task Settings and Display dialog box in Project Web App.
When you use Project 2013 to publish a project and the Do not create a site option is enabled, Project 2013 continuously requests data from the server about the nonexistent site.

March 2015

http://support.microsoft.com/kb/2956187 15.0.4701.1000

When you set a baseline for a sub-project in Project 2013, the baseline data may be incorrect.
When you try to resource level a project in Project 2013, Project may stop responding.
Consider the following scenario:
- You set the Decimal symbol to be a comma in Windows Region Settings.
- You set Show assignments units as a to be a Decimal in Project 2013.
- You set a non-integer value in the Units column of the Assign Resources dialog box.
- You check the Units value in the Task Information dialog box.
In this scenario, the Units value is incorrect. For example, you enter 9,5 but the value changes to 95.

February 2015 (Now Public Updates)

http://support.microsoft.com/KB/2956091 15.0.4693.1000

Assume that you open and edit a project from Project Server in Project Professional 2013, and the Protected Actuals feature is enabled. When you select a task in the project, and then click Move -> Incomplete Part to Status Date, the task schedule does not change as expected.
Consider the following scenario:When you update a project by using a Project Server Interface (PSI) application, the values in the Leveling Delay fields may be lost.
- You create an Enterprise project in Project Professional 2013, and then you add a formula to a local custom field.
- You save and publish the project to Project Server. Then, you open and save the project in Project Web App.
In this scenario, the formula on the local custom field is removed and replaced by its value.
Assume that you save a baseline for a project, and then you save the project as a XML Format (*.xml) file. When you open the file and select the As a new project option, then view the timephased baseline work, the values are lost.
Project 2013 may crash in the following scenarios when Lync 2013 or 2010 is running:Assume that you open a project in Project Professional 2013 on a computer where one of the installed Office 2013 editing languages is Hebrew or Arabic. In this situation, some fields such as resource names, predecessors, and successors may only display part of what it should be. For example, the Resource Names field should display "Resource1" but instead shows "Resour".
- When you perform actions such as opening projects.
- When you move the mouse pointer over fields such as resource names.
Project may crash after you install the October 2014 cumulative update for Project 2013.
Consider the following scenario:When you apply the Task Path feature to a project that contains many predecessors or successors in Project 2013, Project may stop responding and even crash.
- You have a project that contains more than two enterprise resources.
- You open the project in Project Professional 2013.
- You change the list separator so that the client's and the server's characters are different.
- You open the Assign Resources dialog box by clicking the Assign Resources button in the Resource tab.
- You select more than one enterprise resource.
In this scenario, the Assign button in the Assign Resources dialog box becomes unavailable.
When you assign more than two resources that all contain long names to a task, the names of the resources are displayed incorrectly.
Assume that you select more than 40 items from a multiple value lookup table on an enterprise custom field. Then, you save the project. When you open the project in Project Professional 2013, the items that you selected are missing.

December 2014

http://support.microsoft.com/KB/2910920 15.0.4675.1000

When you move assignments around in the Team Planner in Project 2013, Project may stop responding or crash.
Assume that the Youdao Dictionary application is running. When you copy information or perform actions like resizing columns, task GUIDs are renumbered with the result that task dependencies no longer connect properly.
Consider the following scenario:
- On a Project Server, you have at least two user accounts defined by using the following properties:
  - Both have the same name.
  - One is defined that the User can be assigned as a resource check box is selected and the other is not.
- You start Project 2013 and connect to Project Server.
- You add an enterprise resource to a project and you save it.
- You make some changes in the project and try to save the changes.
In this scenario, the saving operation may fail.
Consider the following scenario:Assume that you open and edit a project from Project Server in Project Professional 2013, and the Protected Actuals feature is enabled. You try to change an assignment's time-phased work (remaining work) values. In this situation, you receive the "Your action may result in actuals in this project becoming out of sync with the actuals updated from timesheets" message.
- You create a task that contains a long name in a project in Project 2013.
- In another project, you create a task dependency to the task with the long name.
- You review the relationship information by clicking the Links Between Projects button in the Project tab.
In this scenario, the Task column is not scrollable so that you cannot see the whole task name in the Links Between Projects dialog box.
Assume that you have at least two Project Web App (PWA) sites, and you have different profiles in Project Professional for each sites. In this situation, when you browse to the Project Center and then click to open a project in Project Professional, the wrong profile may be used and information in the profile is overwritten with the wrong details.

November 2014

http://support.microsoft.com/kb/2899569 15.0.4667.1000

Assume that you have previously opened a given project from Project Web App (PWA) into Project Professional 2013. Then, you start Project Professional 2013, you click File, and you click Open. When you select the project in the Recent Projects list, Project 2013 may crash.
When you run a macro that executes the Calendar.Reset method in Project 2013, Project may crash.
When you open a .mpp file that is created from an earlier version of Project in Project 2013, Project 2013 may stop responding.
Assume that you open a .mpp file that is created from an earlier version of Project in Project 2013, and that the "Save files in this format" option is set to the same version as the .mpp file that you are opening. When you try to save the .mpp file, Microsoft Project 2013 asks whether you want to save the project to the Project 2013 MPP format, which is unnecessary.
When you run a custom report that uses parameter queries to filter results it may take a long time for the report to display. You may also notice that Project consumes a large amount of memory and the size of the file grows significantly.
Assume that you apply a custom date based interactive filter to a view in a project in Project 2013. Then, you switch to a different view. When you change back to the original view, the Date/Time Picker control associated with the interactive filter may not work.
Assume that you have a project that has a budget resource assigned to the project summary task. When you view the project in Project Center within Project Web App, the Gantt bar does not correctly display the progress status of the project.
If you start Project 2013 and try to connect to Project Server before you log on to Project Web App (PWA), Project may crash.
Assume that you create a text enterprise custom field that contains a lookup table in Project Web App. When you use the text enterprise custom field to apply a grouping to an enterprise view in the enterprise global template in Project 2013, Project 2013 crashes and then restarts.
When you print a note of a task, and the note spans a page break, the remaining part of the note after the break is missing in Project 2013.

October 2014

http://support.microsoft.com/kb/2889957/ 15.0.4659.1001

Project 2013 may crash in the following scenarios when Lync 2013 or 2010 is running:
- When you perform actions such as opening projects.
- When you move the mouse pointer over the fields such as resource names.
Consider the following scenarios:Consider the following scenario:
- You create a lookup table in Project Web App (PWA), and the lookup table contains multiple values. The total length of the values exceeds 255 characters.
- You create a custom field that uses the lookup table, and you set the option that requires information in this field.
- You create a project in PWA for the custom field, you select multiple lookup table values so that the total length exceeds 255 characters.
- You save, check in, and close the project.
- You open the project in Project Professional.
- You make a change in the project and then save it.
In this scenario, the project cannot be saved, and you may receive the following error message:

Project cannot save the project to Project Web App. You must first specify values for all required project fields. These fields are indicated with an asterisk in the Project Information dialog box, available from the Project tab.

In another scenario, you add resources to tasks from PWA.
- You have multiple resources defined in the server, and the combined length of the names exceeds 255 characters.
- You open the Project Center in PWA, open a project, select the Schedule project detail page, and then you click the Edit button.
- You open the Resource Names field for a task and select multiple resources. The total length of the names exceeds 255 characters.
- You save and then close the project.
- You open the project and then view the resources assigned to the task.
In this scenario, some of the resources that you added to the task are not saved. For the resource names that straddle the 255 character limit, only partial resource names are displayed. To resolve these issues, you must install both the fixes in this knowledge base article, and you must also install the fix in KB 2889957.
You add an outline code field to a project, and you enter a value in the field, and then you save the project as a XML Format (*.xml) file.
You open the file and select the As a new project option, and then you add the outline code field.

In this scenario, the value of the outline code field is lost.

September 2014

http://support.microsoft.com/kb/2889883 15.0.4649.1000

Consider the following scenario:Assume that you add a task, resource or assignment note that contains many lines of text. When you print the project, you select the Print notes check box on the View tab of Page Setup. In this situation, the last line of the note may not be printed.
- You create a project plan, and assign a Work value to a task.
- You do not assign any resources to the task.
- You publish the project plan to a Project Server 2013 server where the Only allow task updates via Tasks and Timesheets option is enabled on the Task Settings and Display page in Project Web App.
In this scenario, when you assign an enterprise resource to the task, the value for total work in the Work field may be changed to zero.
Consider the following scenario:Views, tables, filters and groups that are added to Enterprise Global do not save the Show in Menu option correctly. Therefore, this option is always enabled.
- You install the April 2014 cumulative update for Project Server 2013.
- You do not set the Open Project Template global permission on the Add or Edit Group page in Project Web App.
In this scenario, Project may crash when you try to connect to the Project server.

August 2014

http://support.microsoft.com/kb/2883080 15.0.4641.1000

When you use VBA UserForms and controls in Project 2013, you may experience one of the following issues:When you input double-byte characters (for example, Japanese or Chinese characters) in a text box in a report page in Project 2013, the characters are duplicated.
- You may receive the following error message:
  
  System error &H80070057 (-2147024809). The parameter is incorrect.
- Project 2013 may crash.
Assume that you insert a task after an empty row in an enterprise project. When you publish the project to a Project server, the time-phased work may be incorrect.
You cannot change the values in the Physical % Complete column when the Protected Actuals feature is enabled.
Consider the following scenario:Assume that you start Project 2013 to open a project that has an expanded subproject. When you update time-phased data in the Work field in Resource Usage view, the operation may fail, or Project 2013 may crash.
- You create an Enterprise custom field that refers to a lookup table.
- You insert the Enterprise custom field to a project.
- You create a new project and you insert the first project as a subproject.
- You unlink the subproject from its source project.
In this scenario, the value of the Enterprise custom field is lost.
Assume that you create a Group by and the Group assignments, not tasks option is enabled. The time-phased baseline cost values for cost and material resources may not rollup to the grouping row in Task Usage and Resources Usage views.
Assume that you enable the Move end of completed parts after status date back to status date advanced scheduling feature in Project 2013. When you try to update the value in the % Work Complete field or in the Actual Work field, Project may crash.
Assume that you use Save As to save a project file with a new name in Project 2013, and then you close the file. When you reopen the new file, the value of time-phased actual work has been changed unexpectedly.
Assume that you open a project from Project Server in Project Professional 2013, and the project contains an enterprise project type custom duration field. Values that you enter into the field may be saved incorrectly. For example, you enter the value "5d", and then you click to save and close the project. When you reopen the project, you find that the value is "0d".
Assume that you open and edit a project from Project Server in Project Professional 2013, and the Protected Actuals feature is enabled. You try to change an assignment's start, finish and remaining work values. In this situation, you receive the "Your action may result in actuals in this project becoming out of sync with the actuals updated from timesheets" message.

July 2014

http://support.microsoft.com/kb/2882986 15.0.4629.1000

Assume that you use somelocal custom fields that contain some lookup tables in a project in Project 2013. Then, you save the project to Project Server. Later, you delete the project from the cache. When you open the project and save the project again, the lookup tables may be corrupted and you receivean error message that resembles the following:

The following job failed to complete Jog Type: Save Error ID: 9000(0x2328) Error

Additionally, you may see part of an error message that resembles the following in the Unified Logging Service (ULS) log:

Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.WinProjException: LookupTableItemInvalidLookupTable for lookup table value.
When you use Project 2013 to open a Microsoft SharePoint task list, you receive email message notifications unexpectedly.
When you open a project that contains multiple baselines, the time-phased baseline cost for tasks or assignments is displayed incorrectly. For example, when you check the time-phased Baseline1 cost values, they display the values for the time-phased Baseline cost instead.
When the ProjectBeforeAssignmentChange event is raised, the Assg.Index property returns -1 instead of the correct value. For example, this issue occurs when you add a new resourceto a task.

June 2014

http://support.microsoft.com/kb/2880493 15.0.4623.1000

You cannot resize or scroll the list on the Manage Deliverables window in Project 2013. Therefore, when you have many deliverables in the list, not all are visible.
Assume that you check the Only allow task updates via Tasks and Timesheetsoption in the Project Web App. When you open a project in Project 2013, you may be unable to indent the tasks. Additionally, you may receive an error message that resembles the following:

Change would modify work entered by a team member. We can't make that change because Project Web App is set to only allow actual work to be entered by team members through Timesheets or My Work.
When you try to open a project that contains Summary Resource Assignments (SRA) in Project 2013, you may experience slow performance. This issue occurs when the SRA has work where the resources do not have working time.
Assume that you open a project in Project 2013 from a Project server. Then you click File > Share > Email > Send as Attachment or File > Save As to save it as another file. In this situation, when you try to save the project to the server, the save operation may fail silently. As a result, the Resource Assignments are deleted.
You may be able to change actual work values by using Project Professional 2013, even though the administrator turns on the Only allow task updates via task and timesheets option.

April 2014

http://support.microsoft.com/kb/2878276 15.0.4605.1000

Enterprise project templates are not sorted alphabetically in Project Professional 2013 making it difficult to find a specific template if you have a large amount.
When you try to print a file that has grouping applied with the Maintain hierarchy option enabled, Project 2013 crashes.
If you use a split view with the usage view on the bottom in a project, Project 2013 may crash.
When you use Project 2013 on a high DPI device, dropdowns in dialog boxes may not be drawn correctly.
When you create a security category, category rule is ignored that results in incorrect effective permissions.
When you try to level resources in some projects that contain combinations of task constraints, Project may crash.
When you run a macro that uses the DeliverableUpdate method, the time component of the deliverable start date and finish date is not updated correctly. For example, if the deliverable start date and time is March 31, 2014 10:00 AM, the deliverable start date is updated instead to March 31, 2014 12:00 AM.
You cannot reference assignments with a unique ID as returned by the object model. Additionally, you receive the following error message:

Run-time error '1101'. The argument value is not valid
When you log on to a Project Server that uses Project Professional, it may take longer than expected if the server has many lookup tables and defined values.
Assume that you add some users to a project and the project is published. After the user synchronization process is complete, not all the users are added to the project’s SharePoint site in the given SharePoint security group as expected.
When you group assignments in usage views in Project 2013, grouping row labels do not always appear and assignments may appear in an incorrect grouping.
When you link tasks between projects and use a combination of auto-scheduled tasks and manually scheduled tasks, the start date of the auto-scheduled tasks can be calculated incorrectly.

February 2014 - Microsoft Project 2013 Service Pack 1 (SP1)

No cumulative Update in February as the Service Pack was released. The Server service pack was re-released in April, this did not affect the client SP1. http://support.microsoft.com/kb/2817433 15.0.4569.1000

32 bit - http://www.microsoft.com/en-us/download/details.aspx?id=42013

64 bit - http://www.microsoft.com/en-us/download/details.aspx?id=42020

List of SP1 fixes - http://download.microsoft.com/download/0/A/8/0A870358-D451-488E-BF54-9616292E19EC/Microsoft%20Office%20and%20SharePoint%202013%20Service%20Pack%201%20Changes.xlsx

December 2013

http://support.microsoft.com/kb/2837665 15.0.4551.1507 (KB references 15.0.4551.1508)

After you configure the Fit to: option on the Page tab in the Page Setup dialog box in Project 2013, bars and text may be clipped vertically.

October 2013

http://support.microsoft.com/kb/2825651 15.0.4551.1001

Assume that a project contains a local resource whose name is the same as an enterprise resource. Additionally, the local resource is assigned to a task that is incomplete and a task this is 100 percent complete. When you save the project on a server, the local resource is assigned to the completed task, and the enterprise resource is assigned to the incomplete task.
Consider the following scenario:
- You connect to a Project 2013 server in Project 2013.
- You checkout the enterprise global template.
- You open theVisual Basic Editor, and then you make some changes to some visual basic code that is stored in the global template.
- You save the project, and then you restart Project 2013.
In this scenario, the changes to the visual basic code are not saved.
Consider the following scenario:Assume that you open a project that contains an interim baseline plan in Project 2013. When you insert interim baseline fields, such as Start1 and Finish1, the properties of the fields are empty.
- The system locale is set to a setting other than English (United States) on a computer.
- A Microsoft Excel workbook on the computer contains columns whose names are Outline Level and Start Date.
- You try to import the workbook into Project 2013.
In this scenario, Project 2013 freezes. This issue may also occur when you open sub projects in a master project.

August 2013

http://support.microsoft.com/kb/2817502 15.0.4535.1000

Assume that you use the Gantt Chart view to view a specific number of pages in Project 2013. When you print the pages, the "Fit to" settings in the Page Setup dialog box are not applied correctly. For example, Gantt bars and text may not be printed.
When you change the font for the "All assignments row" in the Bar Styles dialog box in Task or Resource Usage view in Project 2013, the changes are not applied correctly.
When you clear the "Show bar splits" check box in the Layout dialog box on the FORMATtab in Project 2013, you receive the following error message:

An unexpected error occurred.

June 2013

http://support.microsoft.com/kb/2817338

15.0.4517.1001

Consider the following scenario: You try to paste some data in the timescale pane on the right side of a usage view in Project 2013. For example, you try to paste work values into the resource usage view. However, the data is not pasted.
- You create a task that contains a long task name in a project in Project 2013.
- The task name is wrapped in a new row.
- You print or print preview the project.
In this scenario, the long task name is truncated unexpectedly. Note The expected action is that the task name is wrapped.
It takes longer than expected to open a project that is located on a network share in Project 2013.
You set a Gantt chart bar to have a hollow middle pattern. When you print or print preview the project, the Gantt bar of the task does not appear.

April 2013

http://support.microsoft.com/kb/2768336 15.0.4505.1000

Assume that you print a view or a report in Project 2013. Additionally, assume that you specify that the pages be stapled together. Then, you print multiple copies of the view or report. In this situation, each copy is not stapled separately.
Assume that you set the Week starts on calendar option to any day except Sunday in Project 2013. Additionally, assume that you set the bottom timescale of a usage view to months or years. In this situation, data in the calendar is displayed in the incorrect month.
When you print or print preview a task or resource usage view in Project 2013, only the first one or two pages in a multiple page printout are printed or displayed correctly. Additionally, the remaining data on the pages may be misplaced or blank where data is expected.
Assume that you display the Resource Graph view in Project 2013. Additionally, assume that the view in the top pane is a task or resource view. In this situation, the data in the Resource Graph view is displayed in an incorrect period.

February 2013

http://support.microsoft.com/kb/2738031 15.0.4481.1000

Assume that you create two tasks that you must manually schedule in Project 2013, and then you assign the same resource to both tasks. When you assign a duration of time that includes nonworking days to the tasks, the resource leveling feature does not work correctly.

RTM - Version at initial release - 15.0.4420.1017

Project Server 2013 Cumulative Updates from 2016 to Date

Brian Smith — Tue, 21 May 2019 21:06:44 GMT

This page lists all of the released Cumulative Updates (CU), Service Packs (SP) and one important Public Update (PU) for Project Server 2013 from January 2016 to date. From February 2015 onwards all fixes are shipped in Public Updates. From March 2015 client updates available via Windows Update and Download Center, server updates only via Download Center. From April 2015 onwards fixes have a pre-requisite of SP1 - please ensure all components are patched to SP1, including any language packs you may have installed. They are listed in reverse date order - newest at the top. The PU/CUs are normally available in a 'rollup' package that also includes the SharePoint Server and SharePoint Foundation CUs as well as one (sometimes two) 'Individual' packages which just contain the Project Server fixes. Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack). In some months a rollup package did not get released. I have also recorded the version you will see in the dbo.Versions table in the Project Server database after applying each update and running the configuration wizard. In some months this does not get incremented if there were no database changes.

May 2019

This is a roll-up - no specific fixes for Project Server 2013

https://support.microsoft.com/en-us/help/4464562/may-14-2019-cumulative-update-for-project-server-2013-kb4464562

April 2019

This is a roll-up - no specific fixes for Project Server 2013

https://support.microsoft.com/en-us/help/4464513/april-9-2019-cumulative-update-for-project-server-2013-kb4464513

March 2019

https://support.microsoft.com/en-us/help/4462218/march-12-2019-cumulative-update-for-project-server-2013-kb4462218

This is a roll-up - no specific fixes for Project Server 2013

February 2019

https://support.microsoft.com/en-us/help/4462151/february-12-2019-cumulative-update-for-project-server-2013-kb4462151

This is a roll-up - no specific fixes for Project Server 2013

January 2019

Rollup - https://support.microsoft.com/en-us/help/4461604/january-8-2019-cumulative-update-for-project-server-2013-kb4461604 Individual - https://support.microsoft.com/en-us/help/4461606/january-8-2019-update-for-project-server-2013-kb4461606 Database schema: 15.0.5101.1000 Improvements and fixes

This update fixes the following issue: Assume that you have selected PEN, AED or other values in the Currency Settings section on the Additional Server Settings page. When you create a project from Project Web App (PWA), you receive a ProjectOptCurrencySymbolInvalid error and the project is not successfully created.

December 2018

Rollup - https://support.microsoft.com/en-us/help/4461553/december112018cumulativeupdateforprojectserver2013kb4461553 Individual - https://support.microsoft.com/en-us/help/4461461/december112018updateforprojectserver2013kb4461461 Database schema: 15.0.5093.1000 Improvements and fixes

This update fixes the following issues when you work in Project Detail Pages (PDPs):

You can't type multiple digits in a cost type field. Therefore, the Cost value is not displayed as expected.
If you can select lookup table values from fields that have lookup tables associated with them, when you save the project and then come back to it, the values that you selected earlier were not saved.

November 2018

Rollup - https://support.microsoft.com/en-us/help/4461509/november-13-2018-cumulative-update-for-project-server-2013-kb4461509 This month, the cumulative package does not contain patches for Project Server 2013 but only for SharePoint 2013. If you also use SharePoint in your environment, we recommend to install this update. Database schema: 15.0.5085.1000

October 2018

Rollup - https://support.microsoft.com/en-us/help/4461456/october-9-2018-cumulative-update-for-project-server-2013 This month, the cumulative package does not contain patches for Project Server 2013 but only for SharePoint 2013. If you also use SharePoint in your environment, we recommend to install this update. Database schema: 15.0.5075.1000

September 2018

Rollup - https://support.microsoft.com/en-us/help/4092475/september-11-2018-cumulative-update-for-project-server-2013-kb4092475 Individual - https://support.microsoft.com/en-us/help/4092480/september-11-2018-update-for-project-server-2013-kb4092480 Database schema: 15.0.5067.1000 Improvements and fixes

Assume that you open a Project Web App by using the latest Microsoft Edge browser. You experience the following issues:

After you create and apparently save a project in the Project Center, the project is not actually saved and no longer exists.
If you change a custom field value in an existing project, the change is not saved.

August 2018

Rollup - https://support.microsoft.com/en-us/help/4032245/august-14-2018-cumulative-update-for-project-server-2013-kb4032245 Individual - https://support.microsoft.com/en-us/help/4032253/august-14-2018-update-for-project-server-2013-kb4032253 Database schema: 15.0.5059.1000 Improvements and fixes

Assume that you open a Project Server 2013 Project Web App site through Chrome and the name of a project on the site contains spaces. If you use Project 2013 to open the project from the site, you experience an error. After you install this update, you can open the project successfully.

July 2018

Rollup - https://support.microsoft.com/en-us/help/4022240/july-10-2018-cumulative-update-for-project-server-2013-kb4022240 Individual - https://support.microsoft.com/en-us/help/4022245/july-10-2018-update-for-project-server-2013-kb4022245 Database schema: 15.0.5049.1000 Improvements and fixes

Local custom date type fields that have a formula and have the Calculation for task and group summary rows option set to minimum or maximum are not rolled up correctly to summary tasks when you update a project in Project Web App.
The ReadStatusTimephasedData API is not available for users who have the Status Broker permission. Therefore, they cannot get the timesheet time-phased related data.
When you assign a resource to an unassigned task and publish the task in Project 2013, the newly created assignment does not properly update the AssignmentResourceType, AssignmentType, ResourceUID, and ResourceOwnerUID fields in the MSP_EpmAssignment table in the reporting database. Additionally, the expected time-phased data for the assignment in the MSP_EpmAssignmentByDay table is not found. This issue occurs after you install March 6, 2018, update for Project 2013 (KB4018292).
A custom event receiver that's associated with timesheets generates an error in Project Server in Windows Server 2012 R2. When you create a timesheet, you receive the following error message:

Timesheet

This Web Part was unable to load.

Information that may be useful in solving this problem was written to the Unified Logging Service (ULS) log on the Project Web App with the following ID: IDNumber

For more information, contact your Project Web App ADMINISTRATOR.

June 2018

Rollup - https://support.microsoft.com/en-us/help/4022185/june-12-2018-cumulative-update-for-project-server-2013-kb4022185 Individual - https://support.microsoft.com/en-us/help/4022192/june-12-2018-update-for-project-server-2013-kb4022192 Database schema: 15.0.5011.1000 Improvements and fixes

Even if a user never touches or owns an assignment, the Status Update History page shows the assignment is updated by the user. For example, the status history in the approval center shows that a status manager approved an assignment even if the status manager did not approve.

May 2018

Rollup - https://support.microsoft.com/en-us/help/4018395/may-8-2018-cumulative-update-for-project-server-2013-kb4018395 Individual - https://support.microsoft.com/en-us/help/4022130/description-of-the-security-update-for-project-server-2013-may-8-2018 Database schema: 15.0.5011.1000 Improvements and fixes

After you publish a project plan, you look at the Manage Queue Jobs page and find that the ManagedModeTaskSynchronization job has failed, and you see error details similar to the following:

GeneralQueueJobFailed (26000) - ManagedModeTaskSynchronization.SynchronizeTaskListInManagedModeMessage.

The title on a Project Detail Page shows the "&" (ampersand) character displayed as "&amp".
When you try to open a project from the Project Center while using Internet Explorer 11 in Windows 7, you receive the following error message:

Action Not available. Project Professional needs to be installed to open the project. Install project and try again.

Status managers see the following error message in the status updates history page:

_error loading

Consider the following scenario:

As a team member, you open your timesheet and enter work for two adjacent days.
On the first day, you set the actual work value back to zero.
On the first day, you set 8 hours of non-working time on an administrator task (for example, vacation)
You send a status update for approval.
You open the previous week timesheet.
You enter actual work values.
You send the timesheet for approval, and the status manager approves it.

In this case, the actual work entered on the second of the two days moves to the first day. The actual work should not move when the status update is applied to the project.

This update fixes the CRTL+S keyboard shortcut save functionality on Project Detail Pages for the Arabic, Finish, and Portuguese versions.

April 2018

Rollup - https://support.microsoft.com/en-us/help/4018346/april-10-2018-cumulative-update-for-project-server-2013-kb4018346 Individual - https://support.microsoft.com/en-us/help/4018352/april-10-2018-update-for-project-server-2013-kb4018352 Database schema: 15.0.5011.1000 Improvements and fixes

When an assignment actual work is missing in a published database, the timesheets page does not load in single entry mode. In addition, you receive the following error message:

The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.

March 2018

Rollup - https://support.microsoft.com/en-us/help/4018301/march-13-2018-cumulative-update-for-project-server-2013-kb4018301 Individual - https://support.microsoft.com/en-us/help/4018305/descriptionofthesecurityupdateforprojectserver2013march13-2018 Database schema: 15.0.5011.1000 Improvements and fixes

Consider the following scenario:

You have a Project Web App (PWA) site and Project Server 2013 in your organization.
You log in to the PWA instance, and then you create an enterprise custom field for the resource entity and another enterprise custom field for the project entity.
You start Project Professional 2013 and connect to Project Server 2013, add a resource, and set a value to its custom field.
You save the project and check it in.
In PWA, you locate the Project Center, drill into the project, and select a Project Details Page (PDP) if you have not already selected one.
You make a change to the project custom field and then save the project from the PDP.
In Project Professional 2013, you open the project and view the custom field value.

In this situation, the value of the resource custom field is missing.

The Manage Queue page may not to be loaded if there is a duplicate Reporting (Project Publish) job. In addition, you may receive the following error message:

Error System.ArgumentException: An item with the same key has already been added.

February 2018

Rollup - https://support.microsoft.com/en-us/help/4011694/february-13-2018-cumulative-update-for-project-server-2013-kb4011694 Individual - https://support.microsoft.com/en-us/help/4011701/descriptionofthesecurityupdateforprojectserver2013february13-2018 Database schema: 15.0.4991.1000 Improvements and fixes

Consider the following scenario:

You have a task that has a resource assigned.
The task has a split in it. For example, there is a week of work, a week that has no work, and then a final week that has work.
In the timesheet for this task, you enter hours on the task so that the work is completed up to the date where the split begins.
The timesheet is submitted, and then the status update is approved.
After that, the project is opened in Project Web App, and the task finish date is adjusted to a date that's after the actual work is completed. For example, the actual finish date is set to the middle of the week where there is no work.

In this situation, the actual work is spread over the whole duration.

Consider the following scenario:

You have a Project Web App site and Project Professional 2013 in your organization.
You create some custom project fields and add them to your project detail pages (PDPs).
In Project Web App, you create a new project and add values for these custom fields.
You open the project in Project Professional 2013, make a change, and then save the project.
You open the project in Project Web App and view the custom field values on the PDPs.

In this situation, the values for these custom fields may be lost.

January 2018

Rollup - https://support.microsoft.com/en-us/help/4011650/january-9-2018-cumulative-update-for-project-server-2013-kb4011650 Individual - https://support.microsoft.com/en-us/help/4011654/january-9-2018-update-for-project-server-2013-kb4011654 Database schema: 15.0.4991.1000 Improvements and fixes

Consider the following scenario:

You go to the Delete Enterprise Objects page and then select timesheets.
You select a date range.
You click the Delete button.

In this scenario, the process starts, but later you see an error message that resembles the following:

Sorry, something went wrong An unexpected error has occurred. Technical Details Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: 0xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx Date and Time:< Date> <Time>

Additionally, when you view the queue jobs, you find that they have not completed. This problem can occur if there are thousands of timesheets and hundreds of reporting periods.

December 2017

Rollup - https://support.microsoft.com/en-us/help/4011589/december-12-2017-cumulative-update-for-project-server-2013-kb4011589 Individual - https://support.microsoft.com/en-us/help/4011598/december-12-2017-update-for-project-server-2013-kb4011598 Database schema: 15.0.4989.1000 Improvements and fixes

Actual work that's been reported by team members in a project inadvertently gets spread differently from what was reported. For example, the actual work hours of 2, 2, 2, 2 are changed to 1.78, 1.78, 1.78, 2.45; the totals stay the same but appear differently across the days. This issue occurs in certain situations when the project is edited in Project Web App even though the Only allow task updates via Tasks and Timesheets task setting and display server option is enabled.
After an administrative time category name is changed, the new name isn't always used when you create new timesheets.
Time phased planned work values don't display on a timesheet when the Task Settings and Display Reporting Display option is set to "Resources should report their total hours worked for a week".
When you delete a value from a custom field that's configured to display a graphical indicator, the record in the database is not deleted, instead the value is set to NULL and the indicator value is preserved in reporting.
Consider the following scenario:

A project manager publishes a task to a team member.
The team member goes to her or his timesheet and enters actual work on the task.
The timesheet is submitted and then approved.
The project in which the task exists is deleted.
The team member goes back to their timesheet.

In this situation, the task on which the actual work was submitted is no longer there.

November 2017

Rollup - https://support.microsoft.com/en-us/help/4011249/november-14-2017-cumulative-update-for-project-server-2013-kb4011249 Individual - https://support.microsoft.com/en-us/help/4011257/description-of-the-security-update-for-project-server-2013-november-14 Database schema: 15.0.4951.1000 Improvements and fixes

Assume that you have Office Web Apps Server 2013 installed. In the on-premises version of Microsoft Word Online and Microsoft PowerPoint Online, decimal values are truncated in a chart axis or data label.
After you change the SharePoint farm authentication realm, Project Server workflows stop progressing and go into suspended mode.
If you don't have permission to approve a timesheet, the browse button in the Confirm Approval dialog displays the following message:

<%<%$Resource:PWA.ADMIN_ADDMODIFYUSER_BROWSE%>>

If the previous publish failed, the publish of the master project is blocked.

October 2017

Rollup - https://support.microsoft.com/en-us/help/4011175/october-10-2017-cumulative-update-for-project-server-2013-kb4011175 Individual - https://support.microsoft.com/en-us/help/4011182/october-10-2017-update-for-project-server-2013-kb4011182 Database schema: 15.0.4951.1000 Improvements and fixes

This update improves the translation of the Task Mode setting name for the Spanish version of Project Server 2013.

September 2017

Rollup - https://support.microsoft.com/en-us/help/4011115/september-12-2017-cumulative-update-for-project-server-2013-kb4011115 Individual - https://support.microsoft.com/en-us/help/4011118/september-12-2017-update-for-project-server-2013-kb4011118 Database schema: 15.0.4951.1000 Improvements and fixes

After you submit a timesheet, the resource utilization calculation option of a resource plan is changed.

August 2017

Rollup - https://support.microsoft.com/en-us/help/4011074/august-8-2017-cumulative-update-for-project-server-2013-kb4011074 Individual - https://support.microsoft.com/en-us/help/4011082/august-8-2017-update-for-project-server-2013-kb4011082 Database schema updated to 15.0.4951.1000 Improvements and fixes

If you apply a filter that uses the Does not Contain filter test to a project that you are editing in Project Web App, tasks that have the filtered characters are still displayed.
Consider the following scenario:

You have a project-level custom field that's defined.
A lookup table is associated with the custom field.
The lookup table allows multiple values to be selected.
You publish a project where multiple values are selected from the lookup table for the given custom field.

In this situation, the report may show multiple copies of the same lookup table value.

Consider the following scenario:

You have a local custom date field that's defined by using a formula.
The formula rollup behavior is set to display either the minimum or maximum date value.
You edit a project in Project Web App and supply data into the fields that drive the formula in the local date field.

In this situation, the date value does not roll up to related summary tasks.

When you try to rename a project that has a required project level custom field from Project Professional 2013, you may receive the following error message:

Renaming project failed with error code hr = 0x80020009

When you try to rename a project to a name that contains the ampersand (&) character, you receive the following error message:

Renaming project failed with error code hr = 0x80020009

July 2017

Rollup - https://support.microsoft.com/en-us/help/3213566/july-11-2017-cumulative-update-for-project-server-2013-kb3213566 Individual - https://support.microsoft.com/en-us/help/3213577/july-11-2017-update-for-project-server-2013-kb3213577 Database schema updated to 15.0.4945.1000 Improvements and fixes

Sporadically, master or sub projects become usual projects.
A user cannot edit summary tasks lock field in the Project Center while using Project Web App.

June 2017

Rollup - https://support.microsoft.com/en-us/help/3203429/june-13-2017-cumulative-update-for-project-server-2013-kb3203429 Individual - https://support.microsoft.com/en-us/help/3203399/descriptionofthesecurityupdateforprojectserver2013june13,2017 Database schema updated to 15.0.4937.1000 Improvements and fixes This security update contains improvements and fixes for the following nonsecurity issues:

Suppose you go to the Project Center page in the Project Web app and select many projects. When you click the Open In Microsoft Project option, nothing seems to happen, and the expected master project isn't created in Project Professional. Now, when you've selected more projects than can be used to create a master project via this method, you'll see a message similar to this:

Added auditing capability to determine when and who changes the "Only allow tasks updates via Tasks and Timesheets" and tracking method Task Settings and Display server settings. When changes are made on the Task Settings and Display page, details are written to the ULS logs under the Project Server Administration category and look similar to these:

PWA:http://server/PWA, ServiceApp:Project Service Application, User:i:0#.w|domain\user, PSI: WS_ADMIN setting WADMIN_PROTECT_ACTUALS changed. New Value: 0. Old Value: 1. Resource Id: xxx PWA:http://server/PWA, ServiceApp:Project Service Application, User:i:0#.w|domain\user, PSI: WS_ADMIN setting WADMIN_DEFAULT_TRACKING_METHOD changed. New Value: 1. Old Value: 2. Resource Id: xxx

This update also fixes the following issues:

Consider the following scenario:

You have a series of tasks that are linked.
Because of the way that the tasks are scheduled, the successor tasks don't necessarily start and finish at the day boundaries. For example, start at 8:00 AM and finish at 5:00 PM.
A resource is assigned to the tasks, and they are published.
The resource completes the work on the tasks entering all actual work on a given date and sends the status update to the project manager for approval.
The project manager approves the updates.

In this case, the start date of the given tasks may be different than what's expected. For example, show an actual start time of 9:10 AM whereas in another case it may show 8:00 AM. This issue occurs because the order in which the status updates were applied was not consistent.

Consider the following scenario:

A project manager publishes a task to a team member.
The team member in either a timesheet or in tasks within the Project Web app reports work that's earlier than what was scheduled. For example, 8h of work was scheduled on Wednesday but 8h of actual work was reported and submitted for Monday.
The status manager approves the update.
The team member zeros out the actual work and moves it to a later date.
The status manager approves the update.
The project is opened in Project Server.

In this situation, the task's actual start date still reflects the earlier update instead of the new update where the actual start date is later.

When a Project server is processing a huge number of timesheets, the Reporting (Timesheet Save) jobs may fail. In the ULS logs, you may see an error similar to this: ReportingTimesheetSaveMessageFailed (24014) - A network-related or instance-specific error occurred while establishing a connection to SQL Server.
After you close a project resource plan, the resource plan isn't check in.
The performance of the Approval Center PWA page is poor. This issue occurs after you install the January 12, 2016, update for Project Server 2013 (KB3114507).
User generated (ad hoc) custom filters that are applied to PWA views don't display data values. For example, you open a custom filter dialog box in Project Center to add a filter on a date column. After you save, close, and then reopen the dialog box, the date you set isn't displayed.
When you submit a status update, task-level baseline data disappears from the Tasks view for the given task assignments.
Server-side defined timesheet view grouping doesn't work with custom fields.

To fix the following issue, install June 13, 2017, update for SharePoint Foundation 2013 (KB3203398). When you add new tasks to a project while editing a project in PWA, formulas that use the Now() or CurrentDate() function don't calculate the correct result.

May 2017

Rollup - https://support.microsoft.com/en-us/help/3191912/may-9-2017-cumulative-update-for-project-server-2013-kb3191912 Individual - https://support.microsoft.com/en-us/help/3191890/description-of-the-security-update-for-project-server-2013-may-9-2017 No database schema update this month - so will be set or stay at 15.0.4911.1000 This security update fixes the following nonsecurity issues:

Some summary resource assignment work or actual work values may have large negative numbers. This issue may cause the project publish process to fail.
When you create a project web app instance at the root, and then you create project sites under a different site collection, you can't use the project details link in the project sites to return to the project. Instead, you may see an error message that resembles the following:This page can't be displayedMake sure the web address http://projectdrilldown.aspx is correct.Look for the page with your search engine. Refresh the page in a few minutes.
Consider the following scenario:

In project professional, you publish a project that contains a collapsed summary task.
You open the project in Project Web App, and then you edit the project.
You apply a filter to the project that sets criteria that should display tasks that are underneath the collapsed summary task.

In this scenario, tasks that should appear do not appear.

April 2017

Rollup - https://support.microsoft.com/help/3178728/ Individual - https://support.microsoft.com/help/3191824 Correction - database schema NOT upgraded this month - will still be 15.0.4911.1000 This update contains the following improvements and fixes:

You have a required custom field with a lookup table and with a default value defined. When you create a project through a project detail page, the custom field isn't pre-filled with the default value. Instead, you have to select a value from the dropdown manually.
Screen readers don't identify that the Delegate Name and the User Name fields on the Add Delegation page are required.
On the Manage Queue Jobs page, the dates in the From and To in the Job History section don't work as expected. For example, you may not be able to set a date in order to see jobs from previous days.

March 2017

Rollup - https://support.microsoft.com/help/3172462

Individual - https://support.microsoft.com/help/3178625

Database schema updated to 15.0.4911.1000

This update fixes the following issues:

Updates the translations to make sure that the meaning of the word "Drivers" is correct in Project Server.
This update fixes the following issues:
- You can't create resources by using the client-side object model (CSOM) if a resource custom field is required.
- When you use the Add Yourself to a Task function, all projects that you have access to are displayed even if there are no tasks in the project to select. This can cause a performance issue. Now, the project manager can lock the project summary task, and publish the project so that the given project isn't displayed as a candidate project to the team member.
- When you browse PWA pages that have HTML grids in standard mode in Internet Explorer 8 or in enterprise mode in Internet Explorer, you can't scroll pages because the scroll bars don't appear.
- If a project-level lookup table value that's assigned to a project is later deleted from the lookup table definition, you can't use the CSOM code to load the project and its custom fields included.
- Assume that you have a server event driven code that responds to status approvals. If a status update is accepted while the project is checked out, the CancelReason returns the default error instead of the error specific to the problem.

February 2017

Just an individual package this month - https://support.microsoft.com/help/3141525 Database schema updated to 15.0.4903.1000 This update fixes the following issues:

After you edit a project in PWA, formulas that rely on the Now() function and the [Current Date] property aren't calculated.

When multiple user and group synchronization jobs run in parallel, SQL deadlocks may occur. This issue may cause orphaned records in the MSP_WEB_SECURITY_PSMODE_PERMISSION_SYNC_STATES table that may also cause poor synchronization performance and large amounts of disk space consumed by the orphaned rows.
Assume that a task is locked while a status update is pending, and then the project is checked in. In this situation, the status updates history page shows the update is both applied and published. However, the published job has not occurred.
When you edit a project in PWA, you receive the following error message if the project summary task has a budget resource assigned:

The view failed to load.

When you update a task on a timesheet, the Process Status field on other untouched tasks may be incorrectly changed to Not Submitted.

January 2017

Rollup - https://support.microsoft.com/en-us/kb/3141480 Individual - https://support.microsoft.com/en-us/kb/3141484 DB Version - No update this month, so still 15.0.4883.1000 from December.

On a Brazilian Portuguese Project Web App home page, the timesheet reminder uses the term Unsubmitted instead of Não enviados.
Fixes the following bugs:

Status updates aren't applied and the Project Calculation Service (PCS) returns an internal error even though the queue job shows no error.
Consider the following scenario:

The server is set to use single entry mode.
You enter time on a task and save the timesheet without submitting it.
A project manager deletes a task that has the saved time.
You go to submit the timesheet or send a status update for the timesheet.

In this scenario, you receive the following error message:

An error occurred while communicating with the server.

When you apply status updates in PWA, actual work is added to some assignments unexpectedly. For example, suppose that you have an assignment that has 35 hours total work and the status update is to apply 9 hours. When you view the results in Project Professional, you find that the assignment is unexpectedly completed. Meanwhile, the total work and the actual work have increased to 400 hours.
Assume that you apply a change to a timesheet line in which the Process Status value appears as Awaiting Approval. In some cases, the status of the timesheet line is incorrectly changed to Approved and reporting also incorrectly shows the line as Approved.
Consider the following two scenarios:

From the Project Center, you drill into a project and choose to edit it. The process fails and you have to try the process again.
A project is updated programmatically through some custom code and the Project Update from a PSI queue job fails at 50%.

In both scenarios, you receive the following error message in the ULS logs:

FilterSEH: The server encountered a very serious error but will continue to function. Exception code was: 0xc0000005 (EXCEPTION_ACCESS_VIOLATION).

You may also find that the error message is generated when a status update is applied to a project even though the status update is successfully applied during the retry operation.

December 2016

Rollup - https://support.microsoft.com/en-us/kb/3128003 This cumulative update package fixes the issues that are described in the following Microsoft Knowledge Base (KB) articles:

Individual - https://support.microsoft.com/en-us/kb/3128009 Fixes the following bugs:

Updates the translation of the check in confirm dialog box in Ukrainian when you close a changed project in PWA.
Fixes the following bugs:

If you have work in a resource plan and save or submit a timesheet which contains nonworking time and overlaps the dates of the resource plan, your work values in the resource plan may change.
Consider the following scenario:

You enter time on a task in your timesheet and then submit the timesheet.
You enter time on the same task in a following timesheet and then save the timesheet.
You go back and recall the earlier timesheet.
You change time on the task and then resubmit the timesheet.
You go to the following timesheet and then add more time to the task.
You submit the timesheet.

In this scenario, the updated task isn't submitted for approval.

When you publish a project, the SharePoint Visitors security group on the project site is truncated (users are deleted). This issue occurs even though the Enable Project Site Sync Project Permission sync setting is disabled.
When a team member views a task's status history, the accepted date of an update is incorrectly displayed as the submitted date. Similarly, when the status manager views the Status Update History page, the approval date is incorrectly displayed as the submitted date.
Changes to enterprise custom files within timesheets aren't submitted as a part of a status update. This issue occurs after you install September 13, 2016, update for Project Server 2013 (KB3118285).

November 2016

Rollup - https://support.microsoft.com/en-us/kb/3127931 This cumulative update package fixes the issues that are described in the following Microsoft Knowledge Base (KB) articles:

Individual - https://support.microsoft.com/en-us/kb/3127937 Fixes the following bugs:

Tasks, resources, or assignments, which are created, for example, with client-side object model (CSOM), and use the same UID as the Project UID, cannot be edited in Project Web App (PWA).
Making changes to timesheet lines may change the TASK_PUBLISHED_UID field of other timesheet lines.
List properties such as MSPWAPROJUID were not set as expected. Therefore, accessing these properties returns NULL.

October 2016

Rollup - https://support.microsoft.com/en-us/kb/3118365 Contains fixes from:

Individual - https://support.microsoft.com/en-us/kb/3118370 DB Version - 15.0.4867.1003

Translates a new string in multiple languages to enable third-party screen readers to recognize it on localized sites of Project Server.
Fixes the following issues:

When you use a screen reader, it doesn't tell you whether some fields are required on a project details page. Additionally, if a custom field is associated with a lookup table, the screen reader displays no context for that, and it doesn't tell you that there are lookup table values.
Windows SharePoint Services user synchronization fails.
When you edit a OneNote notebook, the queue job performance is affected. This update optimizes the Project Sync Jobs trigger.

September 2016

Rollup - https://support.microsoft.com/en-us/kb/3118274 Contains fixes from:

Individual - https://support.microsoft.com/en-us/kb/3118285 DB Version - 15.0.4855.1000

If the farm administrator upgrades a Project Server 2010 database and has non US-en settings, the process may fail with an error message that resembles the following:

ConvertTo-SPProjectDatabase : Action 15.0.10.0 of Microsoft.Office.Project.Server.Upgrade.ReportingDatabaseSequence failed. At line:1 char:1

Workflow fails (internal status turns to canceled) if the status information text contains an ampersand "&".
When you create a project from a SharePoint task list, queue jobs related to workflows that are associated with the list may fail. For example, the "Reporting (Enterprise Project Type and Workflow Information Sync)" jobs may display failed.
After you delete a value from a custom field on the My Tasks page, the change isn't saved and the value comes back when you go to the My Tasks page again.
When you update a task on a timesheet, the Process Status field on other untouched tasks may be incorrectly changed to "Not Submitted".
Document properties update in Project site document libraries could lead to a flood of Reporting (Project Sync) jobs in the Project Server queue if there's also a workflow that's applied to the document library.

August 2016

Rollup - https://support.microsoft.com/en-us/kb/3115448 DB version - 15.0.4849.1000

Contains fixes from:

KB3115456 – Project Server stand alone

KB3115454 - SharePoint Foundation

KB3115458 - SharePoint Foundation

KB3115445 - SharePoint Foundation

Individual - https://support.microsoft.com/en-us/kb/3115456

After you copy and paste a task from the schedule project detail page, the duration of the pasted task appears incorrect. For example, the duration of a task is 1 emon (one elapsed month). After you copy and paste the task, the duration is displayed as 1.01 emon.
After earned values are calculated in Project Web App (PWA) from the schedule project detail page, the values may not be saved, which means the published views of the earned value may not be accurate.
A server-side correlation cancelation on a save job causes deferred jobs to be canceled. For example, a team member submits time against a task and the status manager approves the update. Then, the project is checked out and the Status Update job state is listed as Skipped for Optimization. If a future save on the given project is canceled for whatever reason, the Skipped for Optimization status update job is also canceled.
Assume that you have created a Text type project level enterprise custom field, and it's defined to allow multiple lines. Then, you navigate to a project detail page where the Start field and the previously mentioned field are present. When you then make a change to the Start date and save the changes, the start date isn't saved. Likewise, changes to the custom field are also not saved.
When you add a task to a timesheet, the Select from Existing Assignments dialog box can't be displayed so you can't add the task. Instead, you receive the following error message:

Sorry, something went wrong

An unexpected error has occurred.

July 2016

Rollup - https://support.microsoft.com/en-us/kb/3115291 Individual - https://support.microsoft.com/en-us/kb/3115295

Translates some terms in multiple languages to make sure that the meaning is accurate.
Fixes the following issue:

If you have an enterprise custom field that has a formula that references a custom field with a lookup table, the value may not be set correctly.

June 2016

Rollup - https://support.microsoft.com/en-us/kb/3115172 Individual - https://support.microsoft.com/en-us/kb/3115179 DB Version - 15.0.4833.1000

Improves performance of Project Server Enterprise Resources CSOM API if there's a large number of resources.
Updates the translation of the project check in dialog box to make sure that the meaning is accurate.
On the Manage Timesheets page, a screen reader can't determine which cell is selected and therefore it can't read out the information in the cell to the user.
When you create a project in Project Web App and then you save, close and check in the project, it takes a long time before the page goes back to the Project Center. You may also see an informational dialog which states that it's taking a long time and suggests that you check the queue. This problem may occur when the "Prepare Project Web App Permission Synchronization For Projects" queue job takes a long time. This is possible if there're many user accounts in the server.
When you edit and publish a project through the Project Server Interface (PSI), the outline numbers of tasks aren't updated to the reporting schema.
Assume that you make a migration from Project Server 2010 to Project Server 2013. When you edit a resource, you receive the following error message:

The resource could not be saved due to the following reasons: A resource availability contour cannot go outside the range of the resource's earliest and latest availability dates.

If project sites are created on a different site collection than Project Web App, the Web Admins group is created but never synchronized.
If the submitted actual work hasn't yet been applied to a project, the related enterprise resources can be deleted.
Timesheet page fails to load, and you receive the following error message:

The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.

Note This issue occurs after you install February 9, 2016, update for Project Server 2013 (KB3114737).

Assume that you view a project on which there's at least one task that doesn't have a resource assigned. When you edit the project and switch from a task view to an assignment view that also has a task ID field, the view gets stuck in a loading state.
The Project.CreateProjectFromTemplate PSI method creates inaccessible projects because the project owner doesn't get properly set.
The approval date is incorrectly displayed as the submitted date in Status Update history.
The Edit page function doesn't work as expected in Project Web App. For example, the ribbon appears dimmed and the Web Part menu can't be edited. This issue occurs after you install February 10, 2015 update for Project Server 2013 (KB2880996).
Assume that your Project Web App UI language is French, and exporting the Resource Assignment view to an Excel workbook fails. In this situation, if you try to open the .xlsx file, you receive the following error message:

We found a problem with some content in 'xxx.xlsx'. Do you want us to try to recover as much as we can? If you trust the source of this workbook, click Yes.

If you click Yes, then it opens in Excel, but you see other errors pointing you to the problem.

May 2016

Rollup - https://support.microsoft.com/en-us/kb/3115024 Individual - https://support.microsoft.com/en-us/kb/3115036 DB Version - 15.0.4819.1000

When you try to edit the name of an enterprise resource in your project, a better translation is available for the Japanese language for the following message that appears:

Changes to enterprise resources will be lost.You can modify an enterprise resource in a project for modeling purposes and publishing the project will include any changes. Your changes will be overwritten when the project is next opened.

Fixes the following issues:

On your timesheet, you enter an actual work value that's after the task start date or you enter an actual start date that's after the task's start date. When the status update is applied to the project, the task's actual start date isn't updated accordingly to the assignment actual start date.
Assume that you press the Tab key to move the focus on a column header on the Manage Timesheets page. Then, you press the Enter key in order to sort by this field. In this situation, the focus is lost from the column header, and you have to press the Tab key many times in order to return to the column header.
Self-assigned timesheet lines may display an incorrect TASKUID in the OData feed.
The project start date on a project detail page, such as Project Details, is different from the date in the Project Information dialog box in Project Professional 2013.
When you try to query OData from a workflow in Project Server 2013, an access denied error message is displayed.
Consider the following scenario:

You have an enterprise project level flag field defined.
You have this field displayed on a Project Detail Page (PDP).
A user goes to the PDP page and by-default sees the value of No.
The user saves and moves to a different PDP page.
The user then goes to a different or the previous same PDP page.

In this case, the value is empty or NULL versus the expected No value.

April 2016

Rollup - https://support.microsoft.com/en-us/kb/3114936 Individual - https://support.microsoft.com/en-us/kb/3114950 DB Version - 15.0.4815.1000

If dependencies between tasks in a project have unusually large lead times or lag times, saving the project in Project Web App may fail, and you receive the following error message:

An error has occurred when saving your project to the server. Please contact your administrator for assistance.

After you change the start date of an assignment on the My Tasks page or the Timesheet page in Single Entry mode, actual work on the assignment is changed unexpectedly.
After you change project-level custom fields in a project through the Client-Server Object Model (CSOM), the project schedule may be changed unexpectedly.
Even though you have already installed Project 2013, you may still receive the following error message from PWA:

Action Not Available. Project Professional needs to be installed to open the project. Install Project and try again.

Project Server doesn't always test the checked-in status of a project correctly. Therefore, if a project is checked-out, there may not be a proper notification and a workflow running on the project may fail.
After you change the booking type of a resource in a project, the booking type of the resource's assignments aren't updated to reflect the new booking type.
Pending status updates may not be applied to a project upon check-in. Instead, they are applied until later check-in.
The User Synchronization process may incorrectly remove users from their associated SharePoint security groups. Therefore, the users may no longer have access to Project Server.

March 2016

Rollup - https://support.microsoft.com/en-us/kb/3114823 Individual - https://support.microsoft.com/en-us/kb/3114836 DB Version - 15.0.4805.1002

When the data is grouped, the rows under the grouping rows on the Approvals page are always collapsed. This makes it difficult to quickly and easily view the detailed records that need to be responded to. Now, the Outline Level functionality control has been added to the ribbon on the Approval page.
The Process Status field may show blank for a timesheet line when the status approval is pending.
When you switch to a different filter type on the Manage Queue Jobs page, you may receive the following error message if many jobs are present:

Sorry, something went wrong.

Consider the following scenario:

You have a project-level enterprise field that's linked to a lookup table.
The custom field is exposed on a project detail page (PDP).
You edit a project from the PDP.
You change the value of the custom field as well as another field such as the project description.
You save the project.

In this situation, you receive the following error message:

An error has occurred while saving your project to the server. Please contact your administrator for assistance.

In addition, the queue job error details state GeneralItemDoesNotExist. This issue occurs after you install August 11, 2015, update for Project Server 2013 (KB3055018).

The indicator for issues and risks is still displayed for a project in the Project Center even after the issues or risks are deleted from the project.
When you create an enterprise project from a SharePoint task list, the project owner mapping is ignored and you become the project owner.
When you edit a project in a project detail page, you can remove the project name and successfully save the project without instead receiving an expected error message stating that a project must have a name.
On the Approvals page, when you select the units button and then select one of the work values (Minutes, Hours, Days Weeks), the grid can't be loaded. Sometimes, when you try to expand a grouped row, the expansion fails.

February 2016

Rollup - https://support.microsoft.com/en-us/kb/3114723 Individual - https://support.microsoft.com/en-us/kb/3114737 DB Version - 15.0.4797.1000

Consider the following scenario:

You create a project in Project Professional 2013.
In the new project, you disable the Actual cost are always calculated by Project calculation option under Project Options in the Schedule section.
You create a task that has a duration value of 20d, and then you assign the task to an Enterprise resource.
You insert the Cost and Actual Cost columns into the view, and then you update the values for the two columns.
You save and publish the project to Project Server 2013.
You create a report that is based on an OLAP cube that is generated from the server reporting data.

In this scenario, the task costs for this project are incorrect in the report because an additional cost for unassigned resources is added.

When you apply a filter on an enterprise field that has a lookup-table within the schedule web part, no tasks are displayed for the project.
When you save new resources to Project Server by using Project Professional, nothing happens. This issue occurs if the resources have a logon account defined. If the WindowsAccountEditable registry key is enabled, the resources can be saved successfully.
You receive the following error message when you view the timesheet:

The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.

The Approvals page doesn't roll up totals on grouping rows for the timephased data.
Consider the following scenario:

A team member adds actual work in their timesheet.
The team member submits their timesheet.
The timesheet approver accepts the update. At this point, the team member sees the Process Status field showing the expected Awaiting Approval message for the status update.
The project manager opens the project but doesn't accept the updates.
The project manager saves and publishes the project.
The team member recreates the timesheet.

In this case, the Process Status field is empty instead of showing the expected Awaiting Approval message.

When you add an existing assignment to the timesheet from a project, you receive the following error message:

error loading.

This issue occurs if the name of the project has the "&" character.

Consider the following scenario:

A user enters time phased actual work on an assignment and submits the work for approval.
The status manager approves the update.
The user changes the assignment start date and then submits the change.
The status manager approves the update.

In this scenario, the time phased actual work may move to another date.

A summary task may not correctly compute the rollup value of a custom field if the field is configured with the following properties:

A date type
A minimum rollup
A formula where the value may be null (N/A)

If you only change the project description on the Project Details page, the description isn't saved. This issue occurs after you install August 11, 2015, update for Project Server 2013 (KB3055018).
On the Resource Availability page, you try to deselect some resources, but the resources stay selected if certain characters (for example, "<", ">", or "&") are contained in the resource names.

January 2016

Rollup https://support.microsoft.com/en-us/kb/3114493 Individual https://support.microsoft.com/en-us/kb/3114507 DB Version - 15.0.4787.1000

After you synchronize users to a project site in Project Web App (PWA), the users who should have access to the PWA instance do not have access to it, although these same users may still have access to the specific project site. When you view the PWA root site, these users are unexpectedly missing from the Readers (Project Web App Synchronized) group. This issue occurs after you install June 9, 2015, cumulative update for Project Server 2013 (KB3054865).
If a self-assigned task has actual work applied and the "New assignment request" is rejected by the approver, the "Task update" record incorrectly appears in the approval center. This causes the status manager to approve work incorrectly for a task that was rejected previously. This situation may occur if the project is checked out when the "New assignment request" is rejected.
Assume that you edit a project in Project Web App. After you change the work on a fixed work task that has no resource assigned, the duration of the task is changed. By default, the duration should not change for a fixed work task.
Assume that you add the Project Details web part to a project site. When you select the resource plan button from the Project tab, you receive an error message that looks like the following:

Application error when access /_layouts/15/PWA/RM/ResPlans.aspx

Consider the following scenario:

A project server has thousands of users defined.
A project manager creates a project in the project center.
The project manager saves, publishes, and then closes the project.

In this scenario, the users may have to wait several minutes until the "Prepare Project Web App Permission Synchronization For Projects" queue job is completed.

In certain situation, status updates aren't applied to a project through the approval process. This fix adds an auto retry mechanism to try the status approval again.
When you try to add or delete a user from a project server security group, you experience an error if the project site is a root web and the host header configuration is enabled.
It takes a long time to go to the Add or Edit Group page of a security group even though the security group doesn't have many users.
After you edit a project through a project detail page, a project level custom field may become blank. This issue may occur if the project level field contains a formula that points to a task level field that also contains a formula.
Some Project Web App pages don't properly set the cache-control property to no-store.

Project Server 2013 Cumulative Updates (RTM to Dec 2015)

Brian Smith — Mon, 25 Mar 2019 21:01:35 GMT

This page lists all of the released Cumulative Updates (CU), Service Packs (SP) and one important Public Update (PU) for Project Server 2013 from the release until the end of 2015. From February 2015 onwards all fixes are shipped in Public Updates. From March 2015 client updates available via Windows Update and Download Center, server updates only via Download Center. From April 2015 onwards fixes have a pre-requisite of SP1 - please ensure all components are patched to SP1, including any language packs you may have installed. They are listed in reverse date order - newest at the top. The PU/CUs are normally available in a 'rollup' package that also includes the SharePoint Server and SharePoint Foundation CUs as well as one (sometimes two) 'Individual' packages which just contain the Project Server fixes. Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack). In some months a rollup package did not get released. I have also recorded the version you will see in the dbo.Versions table in the Project Server database after applying each update and running the configuration wizard. In some months this does not get incremented if there were no database changes.

December 2015

Rollup KB3114341 https://www.microsoft.com/en-us/download/details.aspx?id=50175 Individual https://support.microsoft.com/en-us/kb/3114360 DB Version - 15.0.4779.1000

Some timesheet lines are displayed as not approved even though all status updates are accepted.
When you use the Project Server Interface (PSI) to change a master project, the project is no longer displayed as a master project in Project Web App (PWA), and the hierarchical relationship between the master project and its sub projects is lost.
After you apply status updates to a fixed duration task, the remaining schedule of the task changes unexpectedly.
When you use the UpdateResources Project Server Interface (PSI) method to change a resource, security groups that are assigned to the resource and the claims account information about the resource may be lost.
On the Timesheet page, if you select a task to see the assignment details, you receive a web part error message that looks like the following:

This Web Part was unable to load.

This error occurs when the assignment no longer exists in the project, or the assignment was un-published, or the resource commitment on the project was changed to proposed. With this update, users will no longer drill into assignments that are in these states.

You can't submit a timesheet that contains locked tasks where no actual work exists.
In some cases, tasks on a timeline are different in Project 2013 and Project Web App.

November 2015

Rollup https://support.microsoft.com/en-us/kb/3101369 Individual - https://support.microsoft.com/en-us/kb/3101502 DB Version - no change from September - 15.0.4753.1000

Assume that a project manager publishes a project and grants you access through the Project Permissions feature. You're only given sufficient permissions to edit project level fields. When you edit and save the project from a Project Detail page, you receive the following error message:

You need to have permissions to create a new project. Please ask the Project Web App administrator for permissions.

When you publish a project, the publish process fails at 66%. and you receive a queue failure message that looks something like:

GeneralQueueJobFailed (26000) - ProjectPublish.UpdateSRAMessage

Consider the following scenario:Assume that you change the Project Owner field from a project detail page and then save it. When you move away from the page and then go back to the page, the project owner isn't changed.

As a team member, you go to your timesheet.
You enter actual work hours on a task.
You submit your timesheet.
You recall your timesheet.
You delete the actual work hours that you entered previously.
You resubmit your timesheet

In this scenario, the Reporting publish job fails and the ULS log contains details similar to the following:

System.InvalidOperationException: Reporting publish failed. The entity 'ID' is too large.

In some instances, when you drill into a task from the Task page, you receive a message that states the web part can't be loaded. In the ULS logs, you see an error message that resembles the following:

Exception occured in method 'Statusing.ReadStatusForStatusingViews' System.Data.ConstraintException: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.

After a submitted timesheet is rejected and recalled, you can't save changes to the timesheet any longer even if you have the Adjust Timesheet permission.
Consider the following scenario:Consider the following scenario:

You add some Visual Basic Applications (VBA) code to a project in Project Professional 2013.
You save and publish the project to Project Server, and then you check in the project.
You edit the project on the schedule project detail page in Project Server.
You change and save the project.
You open the project again in Project Professional 2013.

In this situation, the VBA code is missing.

You define an enterprise project level date field.
The date field resides on a project detail page (PDP).
You edit a project and change the custom date field by using the date picker control on the PDP.
You select the Save button.

In this situation, the date that you set in the field isn't saved as expected.

October 2015

Rollup - https://support.microsoft.com/en-us/kb/3085489 Individual - https://support.microsoft.com/en-us/kb/3085586 DB Version - no change from September - 15.0.4753.1000

After status updates are accepted and applied to tasks in a project, the total actual work on the assignments may become larger, and the new actual work appears in time periods where the user didn't report it. For example, you report 8h on Monday and 3h on Tuesday. When you view the assignment in the project after the update is applied, besides the 8h on Monday and 3h on Tuesday, you may also see 8h on Thursday and Friday.
You can use the keyboard shortcut (Ctrl + Delete) to delete tasks from a timesheet even though the actual work is submitted or saved.
When you select the Publish button while editing a project in Project Web App, the project stays in a "saving" state. This issue occurs if there're no changes to save within the project.
You can change your own timesheet data after you submit it if you have the Adjust Timesheet permission.
The queue service may consume all server memory over time and eventually crashes. This issue occurs if you have Project Server notifications and reminders enabled.
Assume that you create a task and then submit it for approval. However, the submission is rejected. In this situation, the task remains on the timesheet, and you can't submit the timesheet because the rejected task is still on it.

September 2015

No rollup this month Rollup - https://support.microsoft.com/en-us/kb/2986195 Individual - https://support.microsoft.com/en-us/kb/3085505 DB Version 15.0.4753.1000

Consider the following scenario: After a timesheet is submitted and approved, you can edit a task from the timesheet on the Assignment Detail page but you can't submit the changes for approval as status updates.

A task is published to your timesheet.
You add actual work to the task and submit a status update.
Your status manager approves the actual work that you submitted.
Your status manager locks the task that you submitted work to.
You delete and re-create your timesheet.
You submit your timesheet.

In this scenario, upon recreating the timesheet, the locked task does not reappear on the timesheet. Therefore, as soon as the timesheet is submitted, the actual work that's previously been approved and is seen in the project isn't on the timesheet. This means the actual work in the project and the timesheet are no longer synchronized.

After a timesheet is submitted and approved, you can edit a task from the timesheet on the Assignment Detail page but you can't submit the changes for approval as status updates.
It may take a long time to load a resource plan if there are many resources and custom fields on the resource plans.
When you approve multiple status updates at one time, all remaining updates fail if a single update fails.
If the calendar on which a task is calculated does not have the default 8am and 5pm start times and finish times, when you edit the task's start or finish dates on the Task Details page, the newly calculated duration is wrong.

August 2015

Rollup - https://support.microsoft.com/en-us/kb/3055005 Individual - https://support.microsoft.com/en-us/kb/3055018 DB Version 15.0.4743.1000

New API to bulk update project custom fields to improve performance of demand management workflows.
Fixes the following issues:
- A team member adds himself or herself to an existing task.
- The team member adds actual work to the task.
- The team member submits the task and actual work for approval.
- The status manager rejects both the new task request and the actual work on the task.

You cannot update a local custom field by using the Project Server Interface (PSI) if the field is associated with a lookup table. Additionally, you may receive a "GeneralUnhandledException" exception.
Consider the following scenario:After you unlink a project site from a project server, you cannot create a new project site by using a new name, and no project site update job is triggered.

In this scenario, the rejected task still appears in the timesheet. If you try to submit the timesheet before deleting the task, you receive the following error message:

The submitted timesheet contains lines that have been rejected. Update these lines on your timesheet and then resubmit it.

You cannot use the QueueUpdateProject2 method in a PSI application to update values of custom fields.
Approved status updates are delayed from being applied to a project schedule of a project on a Project server until they are checked out and checked in again. Usually, status updates are applied to a project as soon as they are checked in. However, in this case, it takes an additional check-out or check-in cycle before updates are applied.
In the Project Web App Project Center, you cannot select to open or edit a project in Project Professional when you use Chrome or Firefox.
When you use a PSI application to update a project-level custom field of a project, values of calculated custom fields are blank on tasks when you view them in Project Web App.

July 2015

Rollup - https://support.microsoft.com/en-us/kb/3054933 Individual - https://support.microsoft.com/en-us/kb/3054952 DB Version 15.0.4735.1000

Consider the following scenario: When you associate a project from one site collection to another site collection, the "Prepare Project Web App Permission Synchronization For Projects" queue fails, and the user permissions of the project are not updated.

As a team member from your timesheet, you assign yourself an existing task in a project.
You add actual work to this task.
You send the new task to your status manager for approval.
Your status manager approves the new task, but rejects the actual work that is submitted.

When you refresh your timesheet, the Process Status field does not show that the actual work was rejected. Therefore, you assume that it is approved.

The assignment timephased work may be incorrect in the reporting schema EpmAssignmentByDay table.
When you drill into a task from the My Taskspage and the My Tasks Web Part is on a SharePoint page, you receive the following error message:

The webpage cannot be found.

When you change the view for a Project Center or Project Schedule view and apply a different filter or grouping, the filter option and the grouping option do not change as expected, and the view may still be filtered or grouped based on the previous view.
If a task custom field has a formula and the formula references a project custom field that has a lookup table, the task custom field is not always updated as expected when changes are made to the project in Microsoft Project Web App.
When you try to run the Deficit and Surplus report on the Analyze Resources page in Project Web App, you experience a time-out issue.
When you create deliverables directly in a SharePoint site that has the Project Web App Connectivity feature enabled, you cannot see the deliverables in Microsoft Project Professional 2013.
After you delete a security group for a user in Project Server 2013, the user still has the permission of the security group.
You cannot create a project that has a task custom field with a formula that has a reference to the Status field.

June 2015

Rollup - https://support.microsoft.com/en-us/kb/3054865 Individual - https://support.microsoft.com/en-us/kb/3054869 DB Version - 15.0.4723.1000

You add a nonstandard line for a task in your timesheet, add actual work to it, and then save the timesheet. In this situation, the actual work for the same day is replicated onto the standard line. Therefore, the total actual work is doubled.
In Project Web App, when you create a project from a template in which a budget resource is assigned to the project summary task, the project cannot be published. Additionally, you receive an error message that resembles the following:

Your new <project_name> has been created successfully, but failed to publish and will not be listed in the Project Center.

Tasks and approvals are not displayed on the home page in Project Web App when the Polish language pack is applied.
After you use the Turn in Final Timesheet function to send a timesheet in Project Web App, the timesheet can still be edited and saved.
From a project detail page in Project Web App, you save a project that contains cost resource assignments. In this situation, the costs on the assignments may change unexpectedly. For example, a cost of $1.16 changes to $1.00.
In Project Professional, assume that a summary task is edited in such a way that its subtasks are hidden, and the plan is later published to Project Server. However, when you edit the project in the Schedule Web Part in Project Web App, the previously hidden subtasks cannot be displayed and edited.
When you import external data from an OData data feed to a workbook in Microsoft Excel 2013, you receive the following error message:

The content of the data fee is not valid for an Atom feed.

This issue occurs if the data feed has a custom field that has a lookup table and a graphical indicator.

When you apply a grouping to a view, and the view contains an enterprise custom field that has a formula, the values from the custom field do not roll up into the grouping row.
When you create a project that's based on a template in Project Web App, you do not become the owner of the project. This means that you cannot see it in the project center. Additionally, the user who created the template is set as the owner of the project.
After you rename a custom field that's used in a timesheet, the changed field name is not displayed correctly in the dbo.MSP_TimesheetLine_UserViewCF table, and it may be associated with another field.
When you set a SharePoint list indicator on a timeline Web Part on a SharePoint Server 2013 site, a duplicate timeline Web Part is displayed when you refresh.
In single entry mode, after you submit a timesheet, the timesheet manager can adjust the time that you submitted. However, these changes are not reflected in the tasks in the project. This means that the work that was recognized in the timesheet in out of sync with the project.
When you save a project in Project Professional or Project Web App, custom field values are lost.Note This issue occurs after you apply March 10, 2015 update for Project Server 2013 (KB2956178).
In Project Web App, when you create a project that's based on a template, the tasks do not have the TaskOutlineNumber field value that's set in the template. This is reflected when you view the data in locations such as the dbo.MSP_EpmTask database table.
When you update a plan by submitting updates through a timesheet or tasks in Project Web App, auto approval rules may not apply the update. Instead, the approval appears on the status manager's approvals page.
The Configure Columns settings (for example, column width, or order) on a timesheet are reset unexpectedly to the default every time that the timesheet is refreshed.
When you publish a project that has a task marked as a milestone in Project 2013 to a Project server, the task is not displayed as a milestone in the timeline view in Project Web App.
To fix the following issue for Project Server 2013, install June 9, 2015, update for SharePoint Foundation 2013 (KB3054867):

You cannot scroll to see all the resources on the right-side grid of the build team page if hundreds of resources are added to the project team.

May 2015

Rollup - https://support.microsoft.com/en-us/kb/3039753/ Individual - https://support.microsoft.com/en-us/kb/3054804/ DB Version - 15.0.4699.1000 (No change since March)

When you view a Gantt view of a task list in SharePoint, you cannot filter items if grouping is applied to the list.
You receive the following error message in Status Updates history:

There was an internal error applying the update.

This issue occurs if the decimal separator is a comma in Windows Regional settings, and an enterprise custom field that is displayed as a graphical indicator contains a decimal value.

If a Project Web App team member inputs actual work that is earlier than the task and project start date, when the updates are applied to the project, time-phased actual work may display an incorrect value.
When you go to a project detail page and then go back to another project detail page in Project Web App, the values in project-level custom fields may disappear. This issue occurs after you edit and save projects through different project detail pages.
When you use your keyboard and then press ENTER on the SHOW MORE link during editing or adding a task in SharePoint Server 2013, the focus is reset to the first field of the form instead of the first field of the added list of fields.
When you apply status updates to a project, you may receive the following message in the status field in the status updates history:

There was an internal error applying the update.

This issue occurs because the Project Calculation Service failed. When you view the Unified Logging Service (ULS) logs, you see an error message that resembles the following:

Microsoft.Office.Project.Server (0x06A4) 0x3598 Project Server Project Calculation Service (M) adf34 Unexpected Failed to create a new desktop

When you publish a project to a project server that has the Project Site Sync permissions synchronization options enabled, the publish job takes a long time.
When you publish a project that contains thousands of tasks, it may take longer than expected. In addition, the Project Publish queue job stays at 78% for an extended time. This issue may occur when the corresponding SharePoint tasks list exists and it is synchronized.
Assume that you change a view of a Project Server 2013-based task list to display the item count for a column. When you filter the items in the column, the item count does not update correctly.
When you clear the User can be assigned as a resource check box on the Edit User page in Project Server 2013, publish errors or a loss of resource in projects may occur.

April 2015

Rollup - https://support.microsoft.com/en-us/kb/2965263/ Individual - https://support.microsoft.com/en-us/kb/2965278/ DB Version - 15.0.4699.1000 (No change) This update resolves vulnerabilities that could allow elevation of privilege if an attacker sends a specially crafted request to an affected Microsoft Project Server 2013. The attacker who successfully exploited these vulnerabilities could then perform cross-site scripting attacks on affected systems and run script in the security context of the current user. An attacker who successfully exploited the vulnerabilities could read content that the attacker is not authorized to read, use the victim's identity to take actions on behalf of the victim, such as change permissions, delete content, and insert malicious content in the victim’s browser.

Improvements and fixes

This update also contains fixes for the following nonsecurity issues and improvements:

Translates some Russian language UI elements for Project Server 2013 to guarantee accuracy of meaning. This improvement also provides consistency with the Project Professional 2013 client. For example, these elements translate "Рабочий" to "Трудозатраты".
Disabled property and account of a user is not inactive in Project Web App. Additionally, the presence of particular accounts in Active Directory Domain Services cause partial sync errors in Project Server 2013.
Formula values may not be calculated for a project field on the project details page in Project Web App until you publish the project.
Improves security for cross-site scripting (XSS) on project detail pages.
Assume that you try to create a new site from the Connected SharePoint Sites page for an existing project plan. If a web application that you use has a managed path, the site is not created, and the Prepare Project Web App Permission Synchronization For Projects job is displayed as Failed But Not Blocking Correlation on the Manage Queue Jobs page.
When you open the Connected SharePoint Sites page in a site collection that has lots of projects, the page takes a long time to load or may time out.
When you try to access a view for which you have permissions, you receive an access denied error if you do not have permissions to view the default My Assignments view.

March 2015

Rollup - http://support.microsoft.com/KB/2956162 Individual - http://support.microsoft.com/kb/2956178 DB Version - 15.0.4699.1000

When you create a report that uses a Project OData feed, in the query string you cannot filter on nullable Boolean fields. Instead, the query fails.
Assume that you edit a project from the Schedule page (Schedule.aspx) in Project Web App. You set the value of the Locked field for a task or series of tasks to Yes, and then you save the project. When you return to the project later, you find that the value you set is lost and is now No. Therefore, the task is not locked and team members can still report actual work to the tasks.
Assume that you modify a view of a Project Server 2013 task list to display the item count for a column. When you filter the items in the column, the item count does not update correctly.
When you publish a project to a Project Server 2013 server, the start dates of the tasks in the published project may be calculated incorrectly.
When you create a security group in the Manage Groups page, the Deny permission on the View Project Site permission does not work. Therefore, users may still be able to gain access to sites.
Assume that you save an Enterprise project as a template where tasks on the project are associated with an Enterprise calendar. When you create a new Enterprise project by using the template in Project Web App, the Enterprise calendar is missing. Additionally, the tasks that use the missing calendar may contain incorrect values such as start dates and finish dates.
When you submit a status update that contains notes, the existing task note as viewed in Project Professional may be partly overwritten.
When you edit a project in the Schedule page (Schedule.aspx), some fields such as Task Summary Name may not be displayed.
Consider the following scenario:

You have an enterprise custom field that has a lookup table associated with it, and the field lets multiple values to be selected.
The regional settings locale that you select in SharePoint does not use a comma as the list separator.
You edit a task in Project Web App from the Tasks page, and you have more than one value selected in the custom field.

In this scenario, when you save the task, the values may be lost. Additionally, you do not receive a warning message.

February 2015 (Now Public Updates)

Rollup - http://support.microsoft.com/KB/2920796 Individual - http://support.microsoft.com/KB/2880996 DB Version - 15.0.4693.1000

When you create a new task directly on the Timesheet page, regardless of the Finish Date entered for the task, the task will always be created on the correct Start Date but with a duration of one day.
When you add nonstandard line classification tasks to a timesheet or manipulate tasks on an un-submitted timesheet where nonstandard lines exist, you may receive the "_error loading" error message.
The permissions for all users who should have access to a project site may be synchronized incorrectly when you publish a project.
Assume that you add the SQL Server Reporting web part to a Project Server 2013 page that contains other Project Server web parts. When you click the Refresh button in the SQL Server Reporting web part, the given Project Server web parts will be duplicated.
Assume that you add the Project Server task list as a web part to a SharePoint page, and then you set a filter for the task list web part. When you browse to the page, the filter does not work correctly.
Assume that you create a Project Web App (PWA) view for the schedule web part, and the view contains a filter that has more than 12 clauses. When you apply the view to the Schedule page while you edit a project, the view loads incorrectly. Additionally, you may receive the following error message:

Project Web App hit an error processing your request and your unsaved changes were lost. Press OK to reload the session. Press CANCEL to close the session. If this happens again, contact your administrator.

Assume that you create a site template in Project Server 2010. Then, you migrate Project Server 2010 to Project Server 2013. When you edit an Enterprise Project Type, you cannot select the given site template from the Project Site Template drop-down menu.
If you cancel the selection of the Enable Project Site Sync option in the Project Permission Sync Settings page, you cannot sync the users by clicking Synchronize in the Connected SharePoint Sites page.
When you click Close on the Build Team page, you may receive one of the following messages:

Working on Checking In

The project cannot be written to the server

Consider the following scenario:

You open a project plan in Project 2013 from a Project Server 2013-based server.
You delete the value of a custom field that uses a lookup table on the server.
You publish and check in the project plan. Then, you open the project plan in Project Web App.

In this scenario, when you click Edit on the Project Detailspage, you may receive an error message that resembles the following:

This Web Part was unable to load. Information that may be useful in solving this problem was written to the Unified Logging Service (ULS) log on the Project Web App with the following ID: <ID> For more information, contact your Project Web App administrator.

Consider the following scenario:

You connect to a Project Web App (PWA) site by using Project Professional.
You create a project, and then add some resources to it.
You save and publish the project; in the Publish Project dialog box, you decide to provision the site as a subsite of another project.

In this scenario, the permissions on the newly created site may be incorrect. Additionally, in the Project Server Queue Job Error Details it shows information similar to the following:

GeneralQueueJobFailed (26000) - PreparePSProjectPermissionSynchronization.PreparePSProjectPermissionSynchronizationMessage. Details: id='26000' name='GeneralQueueJobFailed' GroupType='PreparePSProjectPermissionSynchronization' MessageType='PreparePSProjectPermissionSynchronizationMessage'

December 2014

Rollup - http://support.microsoft.com/KB/2910911 Individual - http://support.microsoft.com/KB/2910944 DB Version - 15.0.4673.1000

Assume that you add actual work to a task in a timesheet and then save it. Later, the project manager publishes another task, and the new task appears on the same timesheet. You add actual work to the new task and you submit the timesheet for approval. In this situation, the timesheet line for approval of the new task is not displayed in the Approval center.
Assume that you change the working time of the enterprise calendar associated with your project to a nondefault working timesuch as 9:00-17:00. Then you publish a task. You go to the Tasks page in Project Web App (PWA), then you change the finish date and the duration of the task and save the change. In this situation, both the finish hour and the task duration are incorrect.
Assume that you create a risk or an issue for a project in PWA, then you save it. When you visit a Project Centerview that includes Active Risks and Active Issues fields, the values are always zero.
Assume that you have a custom field that is defined to include a lookup table and the table contains many values. In this situation, you may be unable to select lookup table values from the custom field on a Project Detail Pages page that shows this field.
Assume that you apply a filter in the Approval Center in PWA. When you refresh the page, or when you go back to the Approval Center after you visit other pages, the filter is not applied though it is already set in the ribbon.
When you use a template to create a project in PWA, and the template contains a null task, the project cannot be displayed in Project views, and you may receive the following error message:

View Failure The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.

Additionally, the CPU usage may reach 100 percent. Note A null task is a blank row between rows.

Assume that you set a baseline for a project, and then you publish and check in the project in PWA. When you open the Schedule project details page, the baseline value is incorrect. For example, the baseline value should be $1.00. However, it is displayed as $100.00.
Consider the following scenario:Consider the following scenario:

You visit the Project Center and you drill into a project.
You select the Schedule project detail page.
You click the Tasks tab in the ribbon.
You view the list of views that you have access to.

In this scenario, some views which you have access to are missing from the drop-down list because of the way security categories are assigned to you.

You browse to a PWA site.
You click the Gear icon on the top-right-corner, then click Site contents, and then click Project Detail Pages.
You select an item in the library, then click the Files tab, and then click the Edit Properties button.

In this scenario, when you click Open Web Part Page in maintenance view on the page, you may receive the following error message:

Sorry, something went wrong An unexpected error has occurred.

When you try to check in an item in the library, you may receive the similar error message.

November 2014

Rollup - http://support.microsoft.com/kb/2889949 Individual - http://support.microsoft.com/kb/2899547 DB Version - 15.0.4667.1000 Consider the following scenario:

You select the check box of the Single Entry Mode option on the Timesheet Settings and Defaults page on a Project server.
You start Project 2013 and connect to the server.
You create many tasks that have long names.
You link the tasks together in a finish-to-start relationship.
You assign the tasks to a user.
You save and publish the project.
The user logs on to Project Web App (PWA) and opens the Timesheet. The user clicks Add Row, and then clicks the Select from Existing Assignments option.

In this scenario, you see an error message similar to the following:

Sorry, something went wrong An unexpected error has occurred.

If an instance of PWA for Project Server 2013 has multiple event handlers defined for the same event, the server processes that listen to the given event may fail completely. For example, you may be unable to create new projects or submit timesheets.
Assume that you open Manage Timesheets on the PWA Settings page. When you try to open a timesheet, the timesheet may not be loaded. Additionally, you receive the following error message:

The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.

Assume that a team member creates a sub task under a summary task of a project in PWA. Then, the team member sends it for approval. When the project manager opens the project in Project Professional 2013, the newly created sub task is located in the wrong place, and it becomes a summary task.
Consider the following scenario:Assume that you create a new enterprise custom text field in PWA, and you add a long description for this field. When you add the custom field into a web part of a project detail page, the word wrapping works incorrectly in the field description.

You create a security group in PWA and add a user to the group.
You set the same Resource Breakdown Structure (RBS) value for the user and a project manager.
You create a new category and select the The Project Owner has the same RBS value as the User check box.
You add the newly created security group to this category and select the View Project Site check box.
The project manager creates a new Enterprise project and publishes the project.

In this scenario, the user is added into the Team Member SharePoint security group in the SharePoint site of this project, which is unexpected. This gives the user contributor rights to the content in the project site instead of reader rights.

Consider the following scenario:Assume that you start Project 2013 and connect to Project server, then you open a project. When you try to add new dependencies for the project by clicking the Add new dependency… link in the deliverable pane, it takes longer time than expected to load and returns the following error message:

You create a new enterprise custom text field, and you select the Behavior controlled by workflow check box.
You add the custom field to the Project Information project detail page.
You create a new enterprise project type, and you select Project Information for the New Project Page field, and then you select Project Information for the Available Project Detail Pages field.
You create a new project by using the newly created enterprise project type, and you change the value of the date fields in the Project Information page, and then you save the project.

In this scenario, when you refresh the page, the value of the date fields, such as the project start date, are not saved as expected.

An unspecified error has occurred. Error Code:0 Error Message: The argument value is not valid.

Additionally, Project's connection state changes to Work Offline.

Assume that you can access a given Team Builder view by clicking Build Team button in the Projects tab in PWA. Then, your access permission to this Team Builder view is removed. However, you still have access permission to other Team Builder views. When you try to visit other Team Builder views by clicking Build Team, you receive the following error message:

Access Denied.

Consider the following scenario:

You create an Active Directory group and add a user to the group, and the user name contains semicolon.
You sync the Active Directory group to a security group in PWA.
You click Regional Settings in the Site Settings page, and then you change the Locale, for example, to Swedish.
You start Project Professional 2013 to create a project that contains a task, you assign the user to the task, and then you save and publish the project to Project server.
You create a new task for this project in PWA, and then you try to copy the user name from the original task and paste it to the Resource Name column for the newly created task.

In this scenario, a red bullet that indicates an error appears on the left of the task.

Consider the following scenario:Assume that you delete the default out-of-the-box Tasks Summary project view in a Project Server 2010 server, and then you upgrade from Project Server 2010 to Project Server 2013. When you log on to PWA and try to access the Project Center, you receive the following error message:

You start Project 2013 to create a project that has a budget cost resource assigned to a project summary task.
You set a value for Budget Cost in the Task Usage view or in the Resource Usage view.
You insert the Baseline Budget Cost column in the Gantt Chart.
You save a baseline for the project, and the Baseline Budget cost becomes the same value as you set for the Budget Cost.
You save and publish the project.
You query the reporting database and find the Baseline Budget Cost as expected.
You perform a reporting database refresh operation.

In this scenario, when you query the Reporting Database (RDB), the Baseline Budget cost is missing.

You do not have sufficient permissions to view the specified page. Please contact your administrator for permissions to view this page.
Consider the following scenario:

You create a project and assign a resource to a task.
You set a baseline for a project in Project 2013, and you save it.
You change the units of the resource assignment, and you set a new baseline (Baseline 1) for this project.
You save and publish the project to the Project server.

In this scenario, the cumulative baseline by day data is incorrect in the reporting database because it was aggregated across all baselines.

October 2014

Individual - http://support.microsoft.com/kb/2889959/ DB Version - 15.0.4659.1001

After you install the June 2014 cumulative update for Project Server 2013, the Project Professional Versions setting does not work correctly. Therefore, you may be unable to edit a project, preview updates, or apply status updates in Project Web App.
Assume that you enable the Only allow task updates via Tasks and Timesheets option. When you edit a project in Project Web App, and try to delete a protected task, you receive no error message. Additionally, the task disappear from the list until you refresh the page.
Assume that you set a value for the Maximum Hours per Day setting. The setting is ignored when a user makes use of the Send a progress for... feature from the Timesheets page.
Project Queue service might process jobs slowly when there are many pending jobs.
You may be unable to edit a project, preview updates, or apply status updates through Project Web App. Additionally, if you apply status updates, you may see an error similar to the following in the ULS logs:

StatusingInternalError. Details: Status approval internal error Attributes: System.TimeoutException: This request operation sent to net.pipe://localhost/pscalc_ef84be5e83f242fa81604afdf9348d52 did not receive a reply within the configured timeout (00:05:00). The time allotted to this operation may have been a portion of a longer timeout.

Assume that you have a project that contains a resource whose display name contains a colon (:). If the project has an associated SharePoint site, you may be unable to publish the project to a Project Server 2013 server.
When you change the view of the Project Center page and apply a different filter or grouping, the filter option and the grouping option do not change as expected. Instead, the view may still be filtered or grouped based on the previous view.
Consider the following scenario:

You add a task to a project in Project 2013, and then you add to the task a note that contains a special character such as a vertical tab.
You publish the project to a Project Server 2013 server.
You log on to the project site through Project Web App, and then you browse to the Task page.

In this scenario, the Task page is not loaded.

Consider the following scenario:

You create a custom field that uses a lookup table, and you allow multiple values to be selected.
You insert several tasks into a project, and then you select values from the custom field for the tasks.
You save and publish the project.
You change the value of the custom field for one of the tasks, and then you save the project.
You change the value of the custom field on the other tasks, and then you save the project.
You publish the project.

In this scenario, the value of the custom field for the tasks may be incorrect when you query the value from the reporting database tables.

Consider the following scenarios:

You create a lookup table in Project Web App (PWA), and the lookup table contains multiple values. The total length of the values exceeds 255 characters.
You create a custom field that uses the lookup table, and you set the option that requires information in this field.
You create a project in PWA for the custom field, you select multiple lookup table values, and the total length exceeds 255 characters.
You save, check in, and then close the project.
You open the project in Project Professional.
You make a change in the project and then save it.

In this scenario, the project cannot be saved, and you may receive the following error message:

Project cannot save the project to Project Web App. You must first specify values for all required project fields. These fields are indicated with an asterisk in the Project Information dialog box, available from the Project tab.

In another scenario, you add resources to tasks from PWA.

You have multiple resources defined in your server, and the combined length of the names exceeds 255 characters.
You go to the Project Center in PWA, drill into a project, select the Schedule project detail page, and then you click the Edit button.
You go to the Resource Names field for a task and select multiple resources. The total length of the names exceeds 255 characters.
You save and then close the project.
You open the project.

In this scenario, some of the resources that you added to the task are not saved. For the resource names that straddle the 255 character limit, only partial resource names are displayed. To resolve these issues, you must install both the fixes in this knowledge base article, and you must also install the fix in KB 2889957.

Consider the following scenario:Consider the following scenario:

You create a custom list, and you add a lookup column to the list, and then you create an item in the list.
You log on to the Project Web App site as Project Manager.
You browse to the list, and you select the item, and then you click the Create Projects button.

In this scenario, you may receive the following error message:

Sorry, this site hasn't been shared with you.

You create a custom field, and you check the check box of the Behavior controlled by workflow option.
You add the custom field to the Project Details page.
You open and edit a project in the Project Details page.
You change the value of the custom field, and you change another value for the other field such as the Start Date of the project, and then you save the project.

In this scenario, when you refresh the page, the value in the custom field is not saved, and the Start Date is reverted to the previous date.

September 2014

Rollup - http://support.microsoft.com/kb/2883072 Individual - http://support.microsoft.com/kb/2889856 DB Version - 15.0.4649.1001

Assume that you edit the resource plan of a project in Project Web App by using Windows Internet Explorer 10 or Windows Internet Explorer 11. When you save and close the resource plan, it is still in a checked-out state.
Assume that you enable multiple authentication providers for a Project Server 2013 server. Then, you create a user account in Project Web App. When you try to edit the user from the Edit User or Edit Resourcepage, you may receive the following error message:

Multiple entries matched, please click to resolve.

In addition, there is a red squiggly line in the people picker field.

When you use a Project Server Interface (PSI) application to update a project level enterprise field that uses formulas, the values of the field may be lost.
Assume that you set the date format to "dd/mm/yyyy" for a Project Server 2013 server. The Custom Date Range filter on the Timesheet page may change unexpectedly when you click the Apply button.
The resource name that is written to the dbo.MSP_TimesheetResource reporting table becomes different after the approval of a timesheet or a status update. Therefore, it is difficult to do a report that is correlated by resource name.
Assume that you create a project level custom field that uses a formula, and the formula refers to other custom fields. Then, you change the values of the other custom fields and then click the Save button in the Project Details page in Project Web App. In this situation, the project level custom field does not always calculate as expected.
A project reporting publish job may fail. Additionally, the Reporting (Project Publish) queue job error resembles:

The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignmentBaselineByDay_ProjectUID_AssignmentUID". The conflict occurred in database "PWA", table "dbo.MSP_EpmAssignmentBaseline". The statement has been terminated.

Consider the following scenario:

You create an Active Directory group and add a user to the group.
You sync the Active Directory group to a group in Project Web App (PWA).
You delete the user from the Active Directory group.
You execute the sync operation again.

In this scenario, the user is still active in PWA.

Consider the following scenario:Consider the following scenario:

You select the Allow users to choose option in the Project Site Provisioning Settings page.
You create a rule that enables Automatically run this rule option, and the Automatically publish the updates option is selected in the Edit/Create Rule page.
You create a project, assign a task to an enterprise resource in Project 2013, and then you publish the assignment.
The user who owns the assignment enters progress against the task.

In this scenario, when the user sends an update for approval by clicking the Send Status button in the Tasks page, there is an error message in the queue resembles the following:

Queue:?GeneralQueueJobFailed (26000) - CreateWssSite.CreateWssSiteMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='c2cd523c-9ec1-e311-beee-00155d4a810b' JobUID='bfc3b935-9ec1-e311-beee-00155d4a810b' ComputerName='1c1a4290-cfc3-40a9-981b-bfe9e25c9982' GroupType='CreateWssSite' MessageType='CreateWssSiteMessage' MessageId='1' Stage='' CorrelationUID='ed3f869c-4723-1009-c998-2ee8b732a4c4'. For more details, check the ULS logs on machine 1c1a4290-cfc3-40a9-981b-bfe9e25c9982 for entries with JobUID bfc3b935-9ec1-e311-beee-00155d4a810b.

Additionally, the job owner is listed as the user who sent the update.

You enable single entry mode on a Project Web App (PWA) site on a Project Server 2013 server.
You delete the default My Work view for the Timesheet page.
You create a project and assign a task to a resource.

In this scenario, the resource cannot create a new timesheet.

August 2014

Individual - http://support.microsoft.com/kb/2883083 DB Version - 15.0.4639.1000

Assume that you sort the items in the Approvals page by the Remaining Work field in Project Web App. When you browse to the Approvals page again, you may receive an error message that resembles the following:

General Unhandled Exception in _Statusing.ReadStatusApprovalsForProjectForGridJson_

If an error occurs when you approve and apply status updates to a project, the status approval may still show that it is successfully applied.
You may be unable to open a timesheet that contains a specific field in a specific case. Additionally, you receive an error message that resembles the following:

The View failed to Load...

You may be unable to send status update by clicking the Send Progress for all Tasksbutton. Additionally, you may receive an error message that resembles the following:

An error occurred while communicating with the server. Check connectivity with your administrator to determine whether further action is necessary.

When you click OK, you receive an error message that resembles the following:

__Error loading

You may be unable to edit or apply status updates to a large project in Project Web App.
When you create a resource that contains more than one rate in Project Web App, duplicate rows are displayed for the resource in the hired resources report.
If you publish many projects to a Project server in a very short time span, the "Synchronize Project Web App Permissions to Project Site" user synchronization job may fail and you may no longer be able to access the given project site.
You may be unable to publish a project to a Project 2013 server. Additionally, the publish error resembles:

Assume that you approve a status update from Project Web App. When you open the project in Project Professional 2013, the actual work may not apply to the project.
Assume that you create a project in Project Web App from a template that contains an inactive task. When you open the project and activate the inactive task in Project Professional 2013, the schedule may not change correctly based on the duration information.

July 2014

Rollup - http://support.microsoft.com/kb/2882990 Individual - http://support.microsoft.com/kb/2882995 DB Version - 15.0.4629.1000

When you save and publish a project that has baseline data with negative cost values, the cost values in the Reporting database may be incorrect. For example, a fixed cost of negative $5 distributed over 5 days should be -$1/day. Instead, it is displayed as $0/day.
If you publish many projects to a Project server in a very short time span, the "Synchronize Project Web App Permissions to Project Web App" user synchronization job may fail and you may no longer be able to access the given project site.

June 2014

Rollup - http://support.microsoft.com/kb/2881062 Individual - http://support.microsoft.com/kb/2880489 and http://support.microsoft.com/kb/2837680 DB Version - 15.0.4615.1000

When you open the Server Settings > Quick Launchpage, you may find that the ribbon is disabled. Additionally, you receive an error message that resembles the following:

It seems like the order of the items in the Quick Launch has changed unexpectedly. This could have been caused during the upgrade or as a result of modifying the Quick Launch table in the Project Database. You can use this page to update and fix the order of these items. Make sure to save your changes at the end.

Assume that you have a loop in a workflow, and the two stages in the loop are in the same phase. The Workflow Status Web Part cannot load when you open the Workflow Stage Status page after one roundtrip in the loop.
When you try to edit or apply status updates to a project in Project Web App that contains many complex custom formula fields, the operation fails. Additionally, you receive an error message that resembles the following:

Sorry, something went wrong. An unexpected error has occurred.

When you approve a status update in Project Web App, the status of the associated timesheet as seen in the reporting database changes unexpectedly.

Assume that you have a local custom field that is defined to include a lookup table, and yet the table is missing. When you save the project to the Project server, the save operation fails. Additionally, you receive an error message that resembles the following:

The following job failed to complete. Job Type: Save Error ID: 9000(0x2328) Error Description: The project could not be saved to the server. Please retry saving the project. If the problem persists, save the project as a MPP file and contact your system administrator.

May 2014 - (April re-release)

Individual - http://support.microsoft.com/kb/2880484 DB Version 15.0.4605.1000

When you create deliverables directly in a SharePoint site that has the Project Web App Connectivity feature enabled, you cannot see the deliverables in Project Professional 2013.
When you try to update project-level fields such as "owner" or "description" in Project Web App on a project that contains multiple formulas, the update times out, and you receive the following error message:

An error has occurred when saving your project to the server. Please contact your administrator for assistance.

Assume that you have an accepted or rejected timesheet that includes a line for a task that is reassigned, deleted, or unpublished. When you open the timesheet, it cannot be displayed. Additionally, you receive the following error message:

The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.

When you send status updates to a task that belongs to a master project upon approving the status updates, the changes are not seen, and they are lost.
If you do not have the Save Unprotected Baseline permission, you can still save baselines in a Project View in Project Web App Schedule Web Part unexpectedly. Additionally, when you try to save baselines in a Project view in Project Web App Schedule Web Part, you receive the following error message if you correctly have the Save Unprotected Baseline permission:

Cannot clear or Save Baseline. You do not have the adequate permission to clear or save baselines to baselines <number>.

When you create a project site that contains multiple issues lists in a project, you cannot publish the project. You also see an error in the queue that resembles the following:

General•Reporting Wss list sync failed:?ReportingWssSyncListFailed (24018) - 1100. Details: id='24018' name='ReportingWssSyncListFailed' uid='9ad16b75-059f-e311-8481-00155dec4705' SPListType='b20c6cbb-f59e-e311-b49a-402cf488d340' Error='1100'.

April 2014

Individual - http://support.microsoft.com/kb/2863881 DB Version - 15.0.4605.1000

When you assign a resource to a task through Schedule Web Part, the resource assignment does not propagate to the reporting tables correctly in the database. For example, a resource assigned to a task is associated incorrectly with the unassigned resource.
When you try to open a project from a project server and the project does not already exist within the Project Professional active cache, it may take longer than expected.
You run a macro that sets the duration of a custom duration field for a task in a project in Project 2013. When you save and then reopen the project, you receive the following error message:

Invalid Duration

This is not a valid duration, or is outside the range for this field.

Type a duration in the correct format: for example, 4 hours (or 4h), 12 days (or 12d), or 2ed for elapsed days.

If there is budget resource assignment on a project summary task, you are unable to load any assignments through the client-side object model (CSOM) for the project.
When you create a security category, category rule is ignored that results in incorrect effective permissions.
You are unable to use a rule in the approval center to compare the Assignment Finish field with the Assignment Baseline Finish field.
When you try to level resources in some projects that contains combinations of task constraints, Project may crash.
After you upgrade from Project 2010 to Project 2013 and the default out of the box view is deleted, default views are unable to load for Project Center, Project Details and Resource Center. Additionally, you receive the following error message:

The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view.

If you click OK, you receive the following error message:

You don't have permissions to view any projects.

When you click the New Project button in Project Center, you are unable to see the enterprise project types in the order that you have specified in their definition.
Assume that you add some users to a project and the project is published. After the user synchronization process is complete, not all users are added to the project’s SharePoint site in the given SharePoint security group as expected.
Assume that you have a project level enterprise custom field (ECF) that is defined as controlled by workflow. Then, you set the field to a value in Project Web App. When you view the custom field in Project Professional 2013, the ECF is displayed as zero.
When you try to save a project without filling in values for workflow controlled required fields for the stage that the project is currently in or for globally required fields, you receive the following error message:

Specify values for all required custom fields.

When you view a resource plan, then enter work daily and finally set the plan to display the work on an hourly basis, the incorrect value is seen. For example, the calendar and default hours per day setting specifies 7.5 hours yet the value in the resource shows 8 hours.

April 2014 - Service Pack 1 (Re-release)

Description of Project Server 2013 SP1 - http://support.microsoft.com/kb/2880553 List of fixes - http://download.microsoft.com/download/0/A/8/0A870358-D451-488E-BF54-9616292E19EC/Microsoft%20Office%20and%20SharePoint%202013%20Service%20Pack%201%20Changes.xlsx Download - http://www.microsoft.com/downloads/details.aspx?FamilyId=cbc2a006-638b-482b-9604-43bddda66ac0 DB Version - 15.0.4569.1000 February 2014 - skipped as Service Pack 1 was coming out.

December 2013

Individual - http://support.microsoft.com/kb/2837668 DB Version - 15.0.4525.1000 (not actually updated in Dec 2013 - same as August 2013)

Assume that you change values for fields such as Project Owner and Name on a Project Detail Page (PDP) in Project Web App. When you save and refresh the page, the values are reverted to what they were before the change.
You cannot enter complex link types in Schedule Web Part for a task in Project Web App. For example, you cannot enter relationship type and lag and lead time.

October 2013

Individual - http://support.microsoft.com/kb/2825659 DB Version - 15.0.4525.1000 (not actually updated in Dec 2013 - same as August 2013)

Consider the following scenario:

You have a project in Project Server 2013.
You set a baseline for a milestone task.
You try to save and publish the project.

In this scenario, you cannot publish the project successfully. Additionally, the Project Server Queue Job Error Detailscontains information that resembles the following:

ReportingProjectChangeMessageFailed (24006) - Object reference not set to an instance of an object.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='2d2c33cf-6024-e311-ab17-00155dec2002' QueueMessageBody='Project UID='18cbcfc1-6024-e311-80b1-402cf488d340'. PublishType='ProjectPublish'' Error='Object reference not set to an instance of an object.'.

Although you can set up Active Directory group synchronization in Project Server 2013, the timer process never starts, and the security groups are never synchronized.

August 2013

Rollup - http://support.microsoft.com/kb/2817615 Individual - http://support.microsoft.com/kb/2817508 DB Version - 15.0.4525.1000

When you change the color of a Gantt chart bar in Project Web App, the wrong color is displayed.
When you change the pattern of a Gantt bar in Project Web App, the wrong pattern is displayed.
You cannot change the start or end date of a fiscal period on the Fiscal Periodspage in Project Web App. Additionally, when you try to change a start or end date, you receive the following error message:

Project Web App fiscal periods are not allowed to have duplicate names, gaps or overlaps between adjoining period start and end dates, or overlaps between adjoining fiscal years.

June 2013

Rollup - http://support.microsoft.com/kb/2817415

Individual - http://support.microsoft.com/kb/2817341

DB Version - 15.0.4510.1000

When you build an OLAP cube on a Project Web App site, you are not added to the ProjectServerViewOlapDataRole role. This issue occurs even if you have the View OLAP Cube data permissions.
When you try to add a task list from a root Microsoft SharePoint Server 2013 site collection to a SharePoint Server 2013 site in Project Web App, you receive the following error message:

Failed But Not Blocking Correlation

It takes longer than expected to open a project that is located on a network share in Project 2013.
After you create a timesheet for a period of time in Project Web App, you cannot close the timesheet.

April 2013

Rollup - http://support.microsoft.com/kb/2737990 Individual - http://support.microsoft.com/kb/2760261 (Sorry, I don't have a record of the DB version for this update)

Assume that you use cost resources in a project. After you set baselines in the project, the sum of individual time phased portions does not equal the baseline cost value at the task summary level.
Consider the following scenario:

You use Project Server Interface (PSI) or Project Web App to create a project plan.
You add some tasks whose Published fields are set to NO in the project plan.
You create a new project that is based on the project plan.

In this scenario, the Published fields are set to YES in the new project.

When you submit a timesheet in Project Server 2013, timesheet view is not displayed. Additionally, you receive the following error message:

The view failed to load

When you create a timesheet, all projects except the projects that occur during the timesheet period are added to the timesheet.
Actual Work values that users submit to the Approval Center are displayed only in units of hours. This issue occurs in Project Web App.
When you view the cost or resource analysis page in certain resolutions (such as 1600x900 or 1280x960), the pane that is typically displayed on the right side of the page is displayed at the bottom of the page.
After you upgrade from Project Server 2013 Release to Manufacturing (RTM) to Project Server 2013, you cannot use "O data Assignment Custom Field" views.
After you configure an Alternate Access Mapping for Project Web App, you cannot create a project site.
When you use the PSConfig or Upgrade-SPFarm command to upgrade Project Server 2013 RTM, the upgrade is unsuccessful. Additionally, all services are stopped.

March 2013

March Public Update - http://support.microsoft.com/kb/2768001

See the KB for all issues fixed as the package is SharePoint as well - these are the Project fixes:

Assume that a pinned task is split into two parts in Microsoft Project 2013. When you change the duration of the pinned task in Task Usage view, the duration of the task is calculated incorrectly.
Assume that you create two tasks that you must manually schedule in Project 2013 and then assign the same resource to both tasks. When you assign a duration of time that includes nonworking days to the tasks, the resource-leveling feature does not work correctly.
After you upgrade Microsoft Project Server 2010 to Project Server 2013, you cannot access document libraries and issues or risks lists in Project Server 2013.

February 2013 - No server release - included in the March PU

RTM DB Version - 15.0.4420.1017

Project 2010 Cumulative Updates

Brian Smith — Mon, 25 Mar 2019 17:00:56 GMT

This page lists all of the released Cumulative Updates (CU) and Service Packs (SP) for Microsoft Project 2010, both Standard and Professional.

From February 2015 onwards all fixes are shipped in Public Updates. From March 2015 client updates available via Windows Update and Download Center, server updates only via Download Center.

They are listed in reverse date order - newest at the top. Each of these packages is cumulative, including all the previous fixes back to the last baseline (either the initial release or a Service Pack). I have also recorded the version you will see in the File, Help, About Microsoft Project - then the Additional Version and Copyright Information (the version shown just above this link is the Office shared components version)

December 2016

No client update for Project 2010 in December 2016.

November 2016

https://support.microsoft.com/en-us/kb/3118393

The update from November 2016 contains one new fix.

If you have a task that has a duration of four elapsed months or longer, Project 2010 freezes when you save the project as an XML file.

October 2016

No client update for Project 2010 in October 2016.

September 2016

https://support.microsoft.com/en-us/kb/3115249

14.0.7173.5000

When you try to save a project as an XML file in Project 2010, Project 2010 may freeze if there's a task with an elapsed duration.

August 2016

No client update for Project 2010 in August 2016.

July 2016

No client update for Project 2010 in July 2016.

June 2016

No client update for Project 2010 in June 2016.

May 2016

https://support.microsoft.com/en-us/kb/3115001

14.0.7169.5000

Consider the following scenario:
A team member submits a status update.
A status manager approves the update.
A project manager opens the project and verifies that the status update has been applied correctly to the project.
The project manager then saves the project.
In this situation, depending on the state of the project manager's local active cache, the updated version of the project may be overwritten by an older version of the project in the project manager's active cache. Therefore, the status updates that have been applied are lost.

This update also fixes the following issues:

After you remove all progress from a task, a leading split is added incorrectly to the task.
When a task is observed from the Gantt view, you may see an unexplained split, for example, at the end, and when you try to remove the split, it grows larger, and the task finish is now later than before.

April 2016

No client update for Project 2010 in April 2016.

March 2016

https://support.microsoft.com/en-us/kb/3114891

14.0.7167.5000

If you save an incremental baseline that rolls up baseline values from a task to summary tasks, the timephased baseline values of the summary tasks are deleted from the MSP_EpmTaskBaselineByDay table in the reporting database.

February 2016

https://support.microsoft.com/en-us/kb/3114568

14.0.7166.5000

Consider the following scenario:
You have a 1d task that has an assigned resource and the assignment has 8h of work on a single day.
You set the assignment contour to front-loaded. At this point, you now have two daily work segments of 6.67h and 1.33h.
You save the project as an XML file and reopen it.
In this situation, the work contour is lost and the opened assignment has a single work segment of 8h. In a related scenario, if you open an XML file, Project 2010 may crash and become unresponsive. This issue occurs after you install December 8, 2015, update for Project 2010 (KB3114419).

January 2016

No client update for Project 2010 in January 2016.

December 2015

https://support.microsoft.com/en-us/kb/3114419

14.0.7164.5000

It takes a long time to open an XML file and to create a new project in Project 2010.

November 2015

https://support.microsoft.com/en-us/kb/3085614

14.0.7162.5000

When you view the physical "% complete" field on an inserted project summary task in a master project, the value doesn't always reflect the same value on the project summary task in the sub project. In addition, if you open the master project and the sub project isn't in memory, the physical "% value" is displayed as "0%."
This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user opens a specially crafted Office file. To learn more about these vulnerabilities, see Microsoft Security Bulletin MS15-116.

October 2015

https://support.microsoft.com/en-us/kb/3054882

14.0.7160.5000

When you import timephased data by using XML files in Project 2010, the< WorkContour> tags are ignored if timephased actual work exists and not all remaining work values exist.
When you resource level, assignments that are updated from Project Web App may be ignored by leveling, and the Remaining Availability value for certain time periods is incorrect.
When you try to unlink a subproject from a master project that has a custom field with a lookup table defined, Project 2010 crashes if the subproject doesn't have the same lookup table definition as in the master project yet the custom field has values.

September 2015

https://support.microsoft.com/en-us/kb/3085531

14.0.7157.5000

When you assign a resource on the Resources tab of the Task Information dialog box to a task in Project 2010, the Units value of the resource is always set to 100% even if another value is entered.

August 2015

https://support.microsoft.com/en-us/kb/3055050

14.0.7154.5000

Consider the following:
When you open a project in Project Professional, you may find that local custom fields are copied from the enterprise global template into your project. The enterprise global should not have local custom fields in it, and these fields should not be copied to individual projects. This fix prevents these fields from getting into the Global template and then getting incorrectly copied into your project and overwriting local custom fields that you may have already defined.
You use Project 2010 to open a project file (.mpp) from a SharePoint document library.
You save the file to a nondefault file format such as .txt, csv, or xlsx.
You keep the MPP file open.
You make some changes to the project, and then save it.
You save the In this scenario, the changes that you made to the MPP file are not saved properly
When you open an XML project file in Project 2010, a milestone task that is marked as completed may incorrectly be set to 99%.

July 2015

https://support.microsoft.com/en-us/kb/3054985

14.0.7153.5000

If a subproject in a master project has a baseline date that is earlier than its start date while the master project does not have a baseline set for the task that represents the subproject, you may be unable to create a visual report for the master project in Project 2010. Instead, you receive the following error message:
An unknown error has occurred.
An error occurred and the requested action could not be completed at this time.
When you try to create a visual report on a master project that contains a project summary task, you receive the following error message if the project summary task does not have a matching baseline:
An error occurred and the requested action could not be completed at this time.
When you assign a resource to a task in the Task Information dialog box in Project 2010, the resource assignment unit may be incorrect if Resource Availability for that resource is changed.

June 2015

https://support.microsoft.com/en-us/kb/3017816

14.0.7151.5000

After you open an .xml file in a new project in Project 2010, the work and the actual work of some assignments are incorrect.
Consider the following scenario:
As a team member in Project Web App, you set an actual start date on a task that is assigned to you.
You submit the update.
Your status manager approves and applies the update to the project.
You open the project in Project Professional.
In this situation, the actual start date on the assignment is not found.

May 2015

https://support.microsoft.com/en-us/kb/2553251/

14.0.7149.5000

When you roll up baseline values from selected tasks into all summary tasks, the time-phased baseline work and cost values may be incorrect. For example, suppose that over a series of days, the time-phased baseline work values on the summary task are 4h, 2h, 8h, 0h, and 2.5h. After you save the baseline, the values may change to something like 4h, 4.13h, 4.13h, 4.13h, and 4.13h.

April 2015

https://support.microsoft.com/en-us/kb/2965204/

14.0.7147.5000

When you merge the data of an .xml file into a project in Project 2010, levelling delays of all tasks are reset unexpectedly. Additionally, the total task work may be increased in some cases.
When you group on a field for some tasks in Project 2010, the Duration field value on the group summary row is incorrect. The duration should reflect the working time between the earliest and the latest dates on the tasks that are grouped. Instead, it is the task in the grouping that has the maximum duration.
When you change the Status Manager value for a task and publish the project in Project 2010, the changed value is not updated as expected within the reporting database.

March 2015 - No updates for Project 2010 this month.

February 2015

http://support.microsoft.com/KB/2589387

14.0.7141.5000

When you update the same project by using Project 2010 or a Project Server Interface (PSI) application, the task’s critical path may differ. For example, a task that is marked as critical by Project 2010 may not be marked as critical when updated by using a PSI application.

December 2014

http://support.microsoft.com/KB/2910893

14.0.7140.5000

It takes longer time to use Project 2010 to open an .mpp file from a remote file server.
Assume that your project has a baseline set. When you set a baseline on specific tasks in Project 2010, and roll the baseline data up to the summary tasks, the rollup on the summary tasks may be incorrect.
Assume that you open a project that shares resources from a common resource pool, and when you are prompted, you click to open the resource pool. When you change the assignments in the sharing project, the changes are not reflected in the resource pool project.

November 2014

http://support.microsoft.com/kb/2899539

14.0.7136.5000

Assume that you apply a custom date-based interactive filter to a view in a project in Project 2010,and then you switch to a different view. When you revert to the original view, the Date/Time Picker control that is associated with the interactive filter may not work.
Assume that you configure Project 2010 to load the complete subproject when you expand a subproject by using the CloseSubProjHandleAfterOpen registry key. Then, you save and close a master project after you do a recalculation. When you open the subproject again, the tasks in the subprojectmay be damaged. For example, tasks may be in the wrong location in the project, tasks that previously were non-summary tasks may now be summary tasks, or you may see a message that resembles the following:
No calculations can be performed now. There is a circular relationship in task <task name> of <project name>. The successors of this task refer back to this task or its predecessors, causing a circular reference.

October 2014

http://support.microsoft.com/kb/2899488/

14.0.7134.5000

When you set a baseline for a project in Project 2010, if a cost resource is assigned to a milestone task, the values of the timephased remaining cost for that cost resource are assigned to the timephased baseline cost incorrectly.
When you create a visual report that is based on task usage data in Project 2010, and the level of usage data is set to weeks, you may receive the following error message:
Unknown error has occurred. An error occurred and the requested action could not be completed at this time.
In addition, if you try to save the cube data, the previous error is also generated. If you click OK, you receive the following error message:
This is not a valid file name. File names must be less than 255 characters and they cannot contain any of the following characters: \ " / ; ? < > |

September 2014

http://support.microsoft.com/kb/2889911

14.0.7131.5000

When you create a grouping by clicking the New Group By button, the values in the % Complete and % Work Complete fields may not be rolled up to the grouping row in the Task Usage or Resources Usage view.

August 2014

http://support.microsoft.com/kb/2883021

14.0.7130.5000

Assume that you open and edit a project from Project Server in Project Professional 2010, and the Protected Actuals feature is enabled. When you sync the actual work, the timephased actual work may change. The Sync to Protected Actuals function may also run automatically when you save a project after you see the "Your action may result in actuals in this project becoming out of sync with the actuals updated from timesheets" message.
Consider the following scenario:
You have a project file that contains more than two enterprise resources.
You open the project file in Project Professional 2010.
You change the list separator so that the client's and the server's characters are different.
In this scenario, you cannot save or import this project to a Project Server.

June 2014

http://support.microsoft.com/kb/2880537

14.0.7125.5000

When you open a project in Project Web App, the timephased value appears incorrectly.

April 2014

http://support.microsoft.com/kb/2878263

14.0.7121.5000

When you save a sub project in a master project, the save process may fail. Additionally, you may find an error message that resembles the following in the Universal Logging Service (ULS) logs:
Canceling correlation 088954b8-eec2-4e6a-9b23-1fb1654e411f as save is an overwrite or resubmit.
When you open a project in Project 2010 from a Project Server, you may receive a message that resembles the following:
Your action may result in actuals in this project becoming out of synch with the actuals updated from timesheets.
You can: sync actuals with the Synch actuals command on the Tracking menu, or synch actuals when you save the project.
After you install the December 2013 or February 2014 cumulative update, every time that you open a project in Project 2010, all built-in filters and filters in the global template are copied to and duplicated in the If you connect to a Project Server, then every time that you save the enterprise global template, these filters will be copied to it. Additionally, you may receive a message that resembles the following:
The enterprise global already contains a filter named "Critical".
Do you want to replace the filter with the one from the enterprise global, replace all items with duplicate names, rename the filter in the project, or cancel opening the project?

February 2014

http://support.microsoft.com/kb/2863931

14.0.7117.5002

Assume that you have a project that has a budget resource assigned to the project summary task. When you view the project in Project Center within Project Web App, the Gantt bar does not correctly display the progress status of the project.
Views, tables, filters and groups added to the Enterprise Global do not properly save the Show in Menu option and therefore the property is always enabled.
When Project is running in the background, the Auto Save feature causes the processor to be fully allocated.
When you open a read-only project from Project Server 2010 in Project Professional 2010, removing a deliverable from a task deletes and saves it from the deliverables SharePoint list, which is unexpected.
When you try to print a project that contains grouping in Project 2010, Project may crash.
Assume that you have an MPP file that is created by using the Project server Save for Sharing feature and you are now saving it back to the server. In this case, the status manager property on each task and the project owner may change unexpectedly to be the person who is saving the Save for Sharing MPP file to the server.

December 2013

http://support.microsoft.com/kb/2849987

14.0.7113.5000

When you calculate an earned value field such as "Budgeted cost of work performed" (BCWP) based on a baseline other than Baseline0 for a project in Microsoft Project 2010, the earned value field is calculated incorrectly.

October 2013

http://support.microsoft.com/kb/2825812

14.0.7109.5000

Assume that a lookup table contains many entries. When you run the CustomFieldValueListAdd Microsoft Visual Basic for Applications (VBA) method to add the entries to a project in Project 2010, it takes longer than expected.
Assume that you use the Gantt Chart view to view some pages in Project 2010. When you print the pages, the "Fit to" settings in the Page Setup dialog box are not applied correctly. For example, Gantt bars and text are not printed.
Assume that you create a task that contains three or more assignments in Project 2010. Then, you sequentially enter some actual work for the assignments in the Task Usage view. In this situation, the actual work for other assignments that the task contains may be displayed for the wrong day.
After you group some assignments in the Task Usage view or Resource Usage view in Project 2010, some tasks or resources may be displayed in the wrong group.
When you assign a budget cost resource to the Project Summary task in Project 2010, the "% Work Complete" value for the Project Summary task is calculated incorrectly.

August 2013

http://support.microsoft.com/kb/2817584

14.0.7106.5000

Assume that you create a text enterprise custom field that contains a lookup table in Project Web App. When you use the text enterprise custom field to apply a grouping to an enterprise view in the enterprise global template in Project 2010, Project 2010 crashes and then restarts.

June 2013

http://support.microsoft.com/kb/2817385

14.0.7102.5000

Project 2010 may crash when you open a project that contains a macro.
You run a macro that sets the duration of a custom duration field for a task in a project in Project 2010. When you save and then reopen the project, you receive the following error message:
Invalid Duration
This is not a valid duration, or is outside the range for this field.
Type a duration in the correct format: for example, 4 hours (or 4h), 12 days (or 12d), or 2ed for elapsed days.
When you use VBA Userforms and controls in Project 2010, you experience one of the following issues:
You receive the following error message:
System error &H80070057 (-2147024809). The parameter is incorrect.
Project 2010 crashes.
You copy a group of tasks that have predecessor and successor relationships. When you paste the groups of tasks into a different part of the project, the relationships to the tasks outside the copied relationships are not preserved. For example, consider the following scenario:
You have three tasks in which the second task is linked to the first task in a finish to start (FS) relationship.
The third task is linked to the second in a FS relationship.
You paste the second task and third task into a different part of the project.
In this scenario, the relationship between the original first task and the new instance of the second task is lost. However, the relationship between the new instance of the second task and the third task is maintained.
You create a drawing object in a Gantt chart view for a project in Project 2010. When you undo a formatting change, the created draw object is deleted and cannot be recovered.
The CustomFieldValueListAdd method for Visual Basic for Applications (VBA) cannot write a value that is longer than 127 characters in Project 2010.
When you export a project as an Excel workbook in Project 2010, dates that appear as NA in Project 2010 appear as 1/0/1900 or 12:00 AM in the workbook. Then, when you import the workbook into Project 2010, the task progress information is incorrect, and constraints are ignored.

Service Pack 2

http://support.microsoft.com/kb/2687457

Downloads:

32-bit - Download the Microsoft Project 2010 Service Pack 2 32-bit package now.
http://www.microsoft.com/downloads/details.aspx?FamilyId=e8e59ec1-9d75-4f35-b8cf-0be6b2f0be08
64-bit - Download the Microsoft Project 2010 Service Pack 2 64-bit package now.
http://www.microsoft.com/downloads/details.aspx?FamilyId=98465a0c-fcfa-44bf-a3f2-66010b1a9db7
List of fixes - Download the Microsoft Office and SharePoint 2010 Service Pack 2 Changes.xlsx package now.
http://download.microsoft.com/download/9/5/9/959F3A24-80B3-4930-8FF8-D3C631BB878F/Microsoft Office and SharePoint 2010 Service Pack 2 Changes.xlsx

April 2013

http://support.microsoft.com/kb/2794664

14.0.6137.5000

When the custom field values of a sub-project are rolled up to a master project, you may see an #ERROR. However, you can see the correct values when you expand the sub-project within the master project and then calculate the master project.
When you try to create a site for a project and set up the site as a sub-site of another project in Project 2010, you find that the projects are not listed alphabetically in the Select a project drop-down list.
When you open a project that has cross-project links in Project 2010, the scheduling engine may incorrectly detect a circular reference in the project. You may also see more than one external task in another project that is linked to the same task.
When you print or print preview a project in Project 2010, the inside text of the project in the Gantt bar is not truncated on the right-side of the bar as expected. Instead, the text extends beyond and overwrites the text on the right-side of the Gantt bar.
Assume that you set the Schedule from value to Project Finish Date in the Project Information dialog box for a project in Project 2010. You click the Update Project button to set a Reschedule uncompleted work to start after date for the project. In this scenario, some scheduled work is unexpectedly deleted.
Assume that you create a project in the English version of Project 2010 and you open the project in the French version of Project 2010. In some cases, the schedule of the project unexpectedly changes.
Assume that you use the Save for Sharing feature in Project Server 2010 and you have the saved for sharing project open. When you change the value of an enterprise custom field and save the project, the change is not saved and the custom field reverts to the original value.
When you view the allocation of resource in resource usage view, for example, the view may display the resource as overallocated even though no overallocation exists. To resolve the problem, you have to update the summary resources assignment (SRA) data.

February 2013

http://support.microsoft.com/kb/2760778

14.0.6134.5000

Assume that you apply hotfix 2687386 in Project Professional 2010, and then you apply a group definition to create a custom group. Then, you open a project that contains summary resource assignments (SRAs). When you expand the "Other projects and commitments" node in Resource Usage view, the SRAs are not displayed with the corresponding resource.
Assume that you apply hotfix 2687386 in Project Professional 2010. After you expand subtasks that correspond to project SRAs in Resource Usage view, you cannot collapse resource nodes.
When you open a project plan in Project Professional 2010, actual work is applied to an assignment in the plan. However, the owner of the assignment did not submit any actual work to the assignment.
Assume that you apply resource leveling to multiple projects, and the projects contain the same resource but have different booking types. In this situation, the "Level resources with the proposed booking type" option does not work as expected across multiple project plans.
Assume that you print a view or report, and you specify that the pages be stabled together. When you print multiple copies of the view or report, all the copies are stapled together as one unit.
Assume that a project contains a local resource whose name is the same as an enterprise resource. Additionally, the local resource is assigned to a task that is incomplete and a task this is 100 percent complete. When you save the project to a server, the local resource is assigned to the completed task, and the enterprise resource is assigned to the incomplete task.

December 2012

http://support.microsoft.com/kb/2553188

14.0.6131.5000

When you try to sync a list of tasks from a SharePoint server in Project 2010, Project 2010 crashes. This issue occurs if the length of the URL in the Site URL box exceeds URL length limitations.

October 2012

http://support.microsoft.com/kb/2687612

14.0.6129.5000

Assume that you open an existing project plan in Project Professional 2010 from Project Server 2010. When you select any kind of Resource Usage report in Visual Reports, you receive an error message that resembles the following:
An unknown error has occurred.
An error occurred and the requested action could not be completed at this time.
Consider the following scenario:
You save a project that shares resources from a resource pool project in Project 2010.
You are prompted to also save changes to the resource pool project.
You save changes.
In this scenario, Project 2010 may crash.
Assume that you have a task that has more than one resource assigned and at least one of the assigned resources has no Actual Work associated with it. Then you use the Update Projectoption to reschedule work for a time before the task's start date. In this scenario, all existing Actual Work for the assignments on the task is deleted.
Assume that you enable the legacy formats in Project 2010. When you import text data to the project, you may receive an error message that resembles the following:
An import error occurred.
Check row n column n
The number you entered is invalid or is outside the range for a Number field. Make sure you are typing only numbers and no letters or other characters in this field, or type a smaller number.
Assume that you start Project Professional and it is connected to a server. In this situation, when you select to load summary resource assignment (SRA) information, you may see unexpected work overallocations problems.
Consider the following scenario:
You open a project from Project Server that contains enterprise lookup fields and values and then use the Save for Sharing feature.
When you are disconnected from the server profile, you change the file in certain ways (for example, you edit the title, start, finish or duration).
You reconnect to the project server and then save the file to the server.
You open the plan.
In this scenario, the values in the enterprise lookup field are lost.
When you open a project file from a Project server, Project Note This occurs because the contour data on the project summary task has gone bad.

August 2012

http://support.microsoft.com/kb/2687386

14.0.6126.5000

Assume that you add a resource to the plan of a project in Project Professional 2010 and then save the plan. After you publish the project to a Project server, you cannot open the plan from the server. This issue occurs because there are duplicate RES_OPTINDX values in the MSP_PROJECT_RESOURCES table.
Duplicate project names are displayed for summary resource assignments under the Other Projects and Commitments section in Resource Usage view.
After you apply the hotfix package that is described in Microsoft Knowledge Base (KB) article 2536590 to the French version of Project Professional 2010, tasks in an .mpp file are scheduled incorrectly. This issue occurs because Project Professional 2010 uses a wrong Note For more information about KB article 2536590, click the following article number to view it:
2536590 (http://support.microsoft.com/kb/2536590/ )
Description of the Project 2010 hotfix package (project-x-none.msp): June 28, 2011
Assume that you view a plan in Resource Usage view and apply a grouping on the view. When you select the Maintain Hierarchy in Current Group option, Project 2010 crashes.
When you view the baseline work field for an unassigned resource by using Resource Usage view, incorrect values are displayed in the baseline work field.
When you publish a project that contains defined enterprise flag fields, the number of records in the MSP_TASK_CUSTOM_FIELD_VALUES_SHADOW table doubles in the published Note To resolve this issue, you should apply the update that is described in this article and then apply the update that is described in KB article 2687390 on the Project server. For more information about the update, click the following article number:
2687390 (http://support.microsoft.com/kb/2687390/ )
Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none): August 28, 2012
When you set the list separator in Regional Settings to a character other than a comma (,), the following issues occur:
You cannot use Form view to create task dependencies.
You cannot assign resources to a task. For example, you cannot assign resources to a task by using the Assign Resources dialog box.
A resource in a summary field that shows summary resource assignments is displayed as overallocated unexpectedly.
Consider the following scenario:
You schedule a project from the project finish date.
You create a task in the project and assign two resources to the task.
You start one of the assignments.
You click the Reschedule uncompleted work to start after: button to update the project.
In this scenario, the scheduled work for an assignment that is not started is reduced.
Assume that you enable the Keep local with base calendar optionon resources when you use the import wizard to import a project from Project Professional 2010 to a Project server. When the import wizard finishes and you view the Resource Center through Project Web App, resources that are supposed to be local to the imported project are displayed unexpectedlyas enterprise resources.
When an assignment has a protected actual work field that contains a zero value in Project Professional 2010, the assignment cannot be completed.
When you enter timephased actual work for a period of time on an assignment in a manually scheduled task, the actual work value is divided and displayed in two periods of time.

June 2012

http://support.microsoft.com/kb/2598351

14.0.6123.5000

Assume that the Protected Actuals feature is enabled in a project, and you use a date auto filter in Project 2010. Additionally, assume that you set actual work in the project. When you save the project and then sync the actual work, the actual work is not cleared.
Assume that you perform earned value calculations in a task that has cost resource assignments. When you manually change costs in the task, the estimate at completion (EAC) values are calculated incorrectly.
Assume that you open a project in Project Server 2010. When you save the project in a different file format, the project on the server contains orphan baseline records.
Assume that you create some enterprise custom fields that contain rollups in a project. When you change the project in Project 2010, the values that should be rolled up are not immediately visible. Additionally, the values that should be rolled up are not saved.
Assume that you create an enterprise custom field that is based on a hierarchical lookup table. When you group the items in the field, the items are not grouped hierarchically.
If a task has a duration of less than a month, and if you enter the actual cost for the month in the time-phased view, the actual cost is divided between the days in the month.
When you disable the "Save protected baseline" option in Project 2010, you can change the Baseline Start, Baseline Finish, and Baseline Duration fields unexpectedly.
Assume that you disable the "Actual costs are always calculated by project" option, and then you assign a cost resource to a task. When the assignment is finished, all time-phased costs and actual costs are cleared unexpectedly.

April 2012

http://support.microsoft.com/kb/2598274

14.0.6120.5000

Assume that a certain unit is incompatible with the upper unit in the Timescale dialog box in Project 2010. When you try to change the Label drop-down list or the Aligndrop-down list, you receive the following warning message:
Tier size mismatch: An upper tier has less time per tick than one of the tiers below it.
Trying the following:
Change the value in the tier’s Units box.
Change the number of units you want displayed in the tier’s Count box.
Additionally, every time that you click the OK button or the Close button in the warning message, you receive the warning message again.
When Microsoft Visual Basic for Applications (VBA) code is executed from a ribbon button in Project 2010, the End statement does not work. Additionally, you receive the following error message:
Automation error
Assume that you have a milestone task that is in the Manually Scheduled task mode in a project plan in Project Professional 2010. If you set the duration of the milestone task to 0 days, and then you define an actual start date and actual finish date, the milestone task is 100 percent complete. However, when you reopen the project plan, the manually scheduled milestone task is 99 percent complete. Additionally, when you open the project in Project Web App, the manually scheduled milestone task is also 99 percent complete.
When you try to scroll up and down in the Resource Usage view in Project 2010, the grid jumps to the active cell.
Assume that the Protected Actuals feature is enabled and that a resource contains an assignment that is 100 percent completed in Project 2010. In this situation, you cannot transfer the Remaining Work part of other assignments in the resource to a different resource by using the Replace functionality in the Build Team dialog box.
When you try to open a project that contains some invalid lookup table values, Project 2010 crashes.
Assume that you include some milestone tasks in a summary task in Project Professional 2010. Then, you assign some cost resources to the milestone tasks. Finally, you select the From subtasks into selected summary task(s) check box in the Set Baseline dialog box. In this situation, the value of the Baseline Cost field does not roll up to the summary task.
When you try to clear the Generate WBS code for new task check box in the WBS Code Definition in ProjectName dialog box, the check box remains selected.
Assume that you save a project that contains more than 255 resources as an .xml file in Project 2010. Then, you open the .xml file as a new project. In this situation, the resource notes contain corrupted data.
Assume that you open a project that has at least one baseline saved and that is in the Project 2007 format from a Project server. Additionally, you do not have permission to save protected baselines. Then, you save the project in the Project 2010 format. In this situation, all data in the protected baselines in the project is lost.
Assume that you change a calendar on a project server. Then, you open a project that relies on the calendar. In this situation, Project 2010 crashes.

February 2012

http://support.microsoft.com/kb/2597942

14.0.6117.5000

Assume that you open a project that contains Microsoft Visual Basic for Applications (VBA) code in Project 2010. When you use the Save As command to replace the existing file many times, the save process eventually fails. Additionally, the project is corrupted and cannot be opened.
You create an .mpp file that was saved from a Project server by using the Save for Sharingcommand. When you try to resave the .mpp file back to the Project server in Project 2010, the save process fails, and you receive the following error message:
Project Server was unable to find the specified resource. If the problem continues, contact your server administrator.
This issue occurs when the list separator character that is contained in resource names within the .mpp file on the client differs from the list separator character on the server.
When you open a project that contains a milestone task that has actual work but does not have an actual work contour, Project Professional 2010 crashes.
Consider the following scenario:
You have a subtask whose progress is set to incomplete.
The summary task of the sub task has a predecessor task.
You schedule the predecessor task to finish at a later date.
In this scenario, the remaining duration of the sub task is not split, and the remaining duration of the sub task is not pushed to begin after the predecessor task finishes.
When you open and edit a project that contains some cost resource assignments that have actual cost values in Project 2010, some resource assignments are not marked as completed. And if you set the assignments to complete and then save the project, the next time that you open the project, the assignments are incomplete. Additionally, the finish dates of the assignments are extended.
After you open and work on a project in Project 2010 for a while, the user interface does not draw correctly, and you may be unable to save the project.
Assume that a task that has resource assignments and actual work values is changed into a summary task in a Project 2010 project. In this situation, the actual work values in the summary task may differ from the actual work values that were in the original task. Or, the actual work values may be lost.
Consider the following scenario in Project 2010:
You change the Hours per day setting to a real number value (for example, you change the setting to 7.6). You also change the Work is entered in setting to Days on the Schedule tab under Options.
You assign a material resource to a task.
You type a value in the work field or in the actual work field (for example, you type 1 in the work field or in the actual work field) in Task Usage view.
In this scenario, the value in the work field or in the actual work field is incorrect (in the example, the value is displayed incorrectly as 1.09).
Project 2010 crashes when you save a project. This issue may occur when summary resource assignments are loaded.

December 2011

http://support.microsoft.com/kb/2597006

14.0.6114.5000

When you use VBA code to create a custom solution for a custom field in Project 2010, and then you change the value of the custom field in the Project Information dialog box, the ProjectBeforeTaskChange event is not raised as expected.
When you try to save a project in Project 2010, the save operation fails and you receive the following error message:
The following job failed to complete.
Job Type: Save
Error ID: 9000(0x2328)
Error Description:
The project could not be saved to the server. Please retry saving the project. If the problem persists, save the project as a MPP file and contact your system administrator.
Note To resolve this issue, apply this hotfix package on the Project client computer and the Project server.
Consider the following scenario. You select the Actual costs are always calculated by project option in a project and you manually enter the actual costs of a cost resource into the project. You save and close the project. Then, you open the project in Project 2010. In this situation, Project 2010 crashes.
Assume that the status updates for a project are accepted. When you open, save, and then publish the project plan for the project in Project 2010, not all the accepted actual overtime work values are displayed in the project plan.
When you change a custom field in a project and then publish the project in Project 2010, the graphical indicator for the custom field is not displayed in the Project Center.

October 2011

http://support.microsoft.com/kb/2596495

14.0.6112.5000

When you change certain values in a project that contains many tasks in Project 2010, Project 2010 takes a long time to recalculate the project.
Consider the following scenarios:
You change the timephased work in a Project 2010 project.
You change the remaining work for a task or assignment in a Project 2010 project.
You enter a time value for the timephased work, and the time scale granularity is more than one day.
In these scenarios, the actual work is rescheduled unexpectedly. Additionally, you do not receive a message that notifies you that the project is out of sync with the Project server.
When you try to print an .mpp file directly from Windows Explorer, you receive the following error message:
An unexpected error occurred.
Project 2010 stops responding when you try to open a project that contains incorrect, manually scheduled task date values.
When you open a Network Diagram view in Project 2010, and you print or print preview a project, the fill color of the task boxes is the same as the border color of the task boxes. Therefore, the text inside the task boxes appears fuzzy or unreadable. This issue specifically occurs when you use a black-and-white printer to print preview a project or to print a project.
When the custom duration fields are defined in an Office Project 2007 project, you may be unable to open the project file in Project 2010.
When you try to update deliverables or dependencies in a project that contains more than 159 deliverables, the update process may fail.

August 2011

http://support.microsoft.com/kb/2584056

14.0.6109.500

When you restore projects from backups in Project 2010, the deliverables and dependencies are restored incorrectly.
Assume that you have a milestone that has a task link in its own project and a cross-project link from a different project. In this case, the cross-project link incorrectly schedules if the date format does not display the time.
When you create a visual report in a master project, Project 2010 crashes.
Assume that you clear the local cache after you change the task data. In this case, the custom flag field values are lost.
Assume that you click a resource after the Links Between Projects dialog box appears. In this case, Project 2010 crashes when you switch to the Resource Sheet view on a customer file.
Consider the following scenario:
You create a deliverable that has a finish date for a task in Project 2010.
You create another task.
You add a dependency for the two tasks. In this scenario, the dependency finish date that is shown in the Gantt chart differs from the finish date that is shown in the Dependency pane.
When you click the Reschedule uncompleted work to start after button, remaining work is not rescheduled if only a material resource is assigned to a task in Project 2010.
Project 2010 crashes when projects in a master project calculate contour information.
Task names and other demand-loaded properties are lost after you perform undo actions in Project 2010.

June 2011

http://support.microsoft.com/kb/2536590

14.0.6106.5000

A Microsoft Project 2010 report enables you to select and print a specific data range. For example, you can print all tasks, resources, assignments or all time scaled dates. When you try to print a specific data range in a report in Project 2010, the whole data range is printed.
Project Professional 2010 may crash or suddenly disappear without any crash error message when you save a project plan to a Project server.
You cannot receive correct values for the % Complete field, and the Cumulative % Complete field by using the VBA code in Project 2010.
Project 2010 may stop responding (hang) when you use the Team Planner view.
Assume that you use Project Web Application to apply status updates to a task. When you open the task in Project 2010, the updates for the actual work are lost.
After you import a project plan in Project 2010 from a format such as TXT, CSV or Excel, all new baselines (baseline 1 to baseline 10) are duplicated as the default baseline for all tasks.
When you clear the baseline in a view, such as the Task Usage view, certain assignment baseline cost values are not cleared.
When you open a Project 2003 plan in Project 2010, the task outline collapsed or expanded state displays incorrectly. Additionally, the percentage complete status of the summary tasks also displays incorrectly.
Consider the following scenario:
You create a project plan that contains a task in Project 2010.
You configure a baseline for the project plan.
You click the Project Information command to change the project status date.
You change the date in the Reschedule uncompleted work to start after: list in the Update Project window.
You click the File tab, and then you select the Options option to change to a date format that does not include elements such as the year or the time.
In this scenario, the Gantt bar for the task's baseline draws in an incorrect place.
Assume that you view a task in a new Window, and then you edit the task name on task name field in Project 2010. When you reproduce these two steps for many times, the data in the task disappears. Additionally, Project 2010 may stop responding.
You add actual cost values to a resource assignment in a project. Then, you open the project in Project 2010. In this situation, Project 2010 crashes.
Consider the following scenario:
You add a new task into a project in Project 2010.
You receive a prompt to save and check in the project when you close the project.
You click OK on the prompt dialog box to save and check in the project.
You immediately close the prompt dialog box before the project is checked in.
You click Yes when another prompt dialog box pops out to prompt to check in the project.
In this scenario, the project is saved. However, it is not checked in.
You clear the Link to Project check box in the Insert Project dialog box when you try to insert tasks into a project in Project Professional 2010. Then, you open the project. In this situation, Project Professional 2010 crashes.
Assume that a SOAP error occurs in Project Professional 2010. When you view more information about the error in the error dialog box for a while, and then you click OK on the error dialog box, Project Professional 2010 crashes.
Assume that you type a Korean character as a task name in a project. When you want to change the task name to another Korean character that has the same initial consonant and middle consonant as the former Korean character, Project 2010 generates the final consonant as the former Korean character automatically. Additionally, you cannot change the final Note A Korean character consists of three components, initial consonant, middle consonant and final consonant in Korean language.
The ProjectBeforeTaskChange event does not trigger in Project 2010 when you click the Mark On Track button in the ribbon.
Certain actual work and orphaned pending updates are missing in Project Professional 2010 when you select the Save for Sharing option for a project file from a Project Note This issue occurs because the project file is saved locally with different GUIDs when you select the Save for Sharing option for the project file.

Service Pack 1 (SPI)

http://support.microsoft.com/kb/2460052

14.0.6027.1000

Downloads:

32-bit - Download the Microsoft Project 2010 32-bit Service Pack 1 package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=C72141FE-D264-4F6E-AE09-D0FBD32DE5D5)
64-bit - Download the Microsoft Project 2010 64-bit Service Pack 1 package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=CE1FD136-A1F4-4FF5-909B-50808D6F39CB)
List of fixes - Download the Microsoft Office 2010 Service Pack 1 Changes.xlsx package now.
(http://download.microsoft.com/download/5/1/2/512CC712-4070-4CFF-BC4A-B3AFF0E21A1E/Microsoft Office 2010 Service Pack 1 Changes.xlsx)

April 2011

http://support.microsoft.com/kb/2516479

14.0.5137.5000

When you try to save a project in Microsoft Project 2010, the Start1 to Start10 fields, and the Finish1 to Finish10 fields that are related to a task’s interim baseline may be lost. This issue occurs when the fields are not visible in an active table when you save the project.
Project 2010 crashes when you copy a task in a master project that contains a local custom field. This issue specially occurs when the local custom field in the master project has a lookup table defined. However, the local custom field in a subproject does not have a lookup table defined.
Project Professional 2010 may crash when you try to save a project in Project Professional 2010.
Consider the following scenario:
You create a deliverable that has a finish date for a task in Project 2010.
You create another task.
You add a dependency for the two tasks.
In this scenario, the dependency finish date that is shown in the Gantt chart differs from the finish date that is shown in the Dependency pane.

February 2011

http://support.microsoft.com/kb/2496946

14.0.5136.5000

When you save a project plan in Microsoft Project 2010, and then you reopen this project plan, you experience one of the following symptoms:
Assignments are moved to other tasks.
Data is missing.
Data is moved around.
Consider the following scenario:
You configure a Project Server 2010 server to operate in Backwards Compatibility mode.
You have a project plan that contains cross-project dependencies.
You connect to the Project server by using Project Professional 2010, and then you open the project plan.
You try to save the project.
In this scenario, Project 2010 crashes. Additionally, you receive an error message that resembles the following:
Problem Event Name: APPCRASH
Application Name: WINPROJ.EXE
Application Version: 14.0.4751.1000
Application Timestamp: 4b8e2679
Fault Module Name: WINPROJ.EXE
Fault Module Version: 14.0.4751.1000
Fault Module Timestamp: 4b8e2679
Exception Code: c0000005
Exception Offset: 00000000001282c0
OS Version: 6.1.7600.2.0.0.274.10
Locale ID: 1033
Project 2010 crashes when you update cross-project links through the Links Between Projects dialog box.
When you select to display a baseline in the Gantt Chart view, bars that represent milestones or summary tasks do not display.

December 2010

http://support.microsoft.com/kb/2466263

14.0.5130.5000

In Microsoft Project 2010, when you changean assignment value by using code, the ProjectBeforeAssignmentChange event is not triggered as expected.
Project 2010 is not designed to enable users to create a project deliverable against Project Summary Task. However, you can create a project deliverable against Project Summary Task in Project 2010. Therefore, when you try to manage the project deliverable, you receive the following error message:
An error has occurred in the script on this page.
Line: line number
Char: character number
Error:error
Code: code number
URL: URL
Consider the following scenario:
You insert two custom text fields into a Project 2010 plan.
You type text in a column of the first text field.
You copy the whole column from the first text field and then paste it into the second text field.
In this scenario, the second text field contains additional spaces within the values that are pasted.
Project 2010 may crash when resources are disconnected from a pool of shared resources. Specifically, this issue occurs when a project is closed.

October 2010

http://support.microsoft.com/kb/2413663

14.0.5126.5000

Assume that you open an .mpp file from a document library in the Explorer View. When you open a second .mpp file, Microsoft Project 2010 crashes. Additionally, you receive the following error message:
Microsoft Project has stopped working
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

August 2010 - No client release in August 2010

June 2010

http://support.microsoft.com/kb/2075992

14.0.5112.5000

When you use the Visual Reports feature in Project 2010, you receive an error message that states that you do not have access to the .mdb
Some Visual Basic for Applications (VBA) methods such as FileOpen, FileOpenEx, and OutlineIndent, do not raise error messages when they should.
You copy formatted cells from an Excel workbook and then paste them into the Task Name column in Project 2010. When you click to select the Match Destination Formatting option from the Paste Options list, Project 2010 may Note If you use the option button directly, this issue does not occur.
You insert many tasks into a project that is connected to a server. When you save, close, and then reopen the project, all null (empty) tasks in the file are moved.
When you print or preview a project that has a dependency to a task and that task ends up as the last task on the page, the link line goes off the left side of the pageWhen you print or preview a project that has a dependency to a task and that task ends up as the last task on the page, the link line goes off the left side of the page toward infinity.
When you click Replace All, Project 2010 crashes. For example, Project 2010 crashes when you click Replace All to replace TaskName to TaskName2.
If a subproject task on the timeline is deleted from the subproject, the timeline data becomes corrupted, and tasks cannot be added to the Timeline view.
When you save a project as an XML file, the values that are in that XML file do not have a period as the XML decimal symbol. Instead, the values have a decimal symbol that is determined by the regional settings. For example, the values are the cost values.

RTM Initial Release

14.0.4751.1000

Projects with spaces in their names? A recent Windows Security update could cause issues!

Brian Smith — Wed, 01 May 2019 15:58:00 GMT

A further update - as far as we can tell this ONLY affects Project Server 2019, assuming you are patched up to date on Project Server 2013 and 2016. We fixed this condition for Chrome a while back - and the recent Windows fix exposed this for other browsers. See https://support.microsoft.com/en-us/help/4022228/description-of-the-security-update-for-sharepoint-s... for Project Server 2016 and for 2013 - https://support.microsoft.com/en-us/help/4032245/august-14-2018-cumulative-update-for-project-server... A more recent update would include these too. Not sure when we will get the fix for Project Server 2019, but will have probably missed the May deadline.

If you have recently loaded the Window Security update https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0784 and are not able to open certain projects from the Project Center then check if the project name contains a space. We are investigating and hopefully will soon get a fix for this, but depending which part we need to fix (client, server or service) it could take a while before it is available in an update or your distribution channel. There are workarounds - you can still open just fine by opening the client Project application and then File, Open to select the project, or you could just rename the plan and remove the space(s). Personally I try and avoid using spaces and other special characters in project names, and of course spaces are supported and should work, but occasionally they can trip something up unexpectedly - like this recent change.

Welcome to the new home of the Project Support Blog!

Brian Smith — Thu, 21 Mar 2019 19:58:43 GMT

What used to be over on TechNet on blogs.technet.microsoft.com/projectsupport is now to be found here on the TechCommunity. It may seem odd that all the posts show 3/6/2019 as the post date, when some refer to th 2007 or 2010 release, but this is the date they were migrated - and were made public today. The top of each does show the original posting date. I've tried to keep the most valuable, and lose some of the ones that no longer apply - let me know if any of your favourites didn't make the cut. If they still have value I'm happy to go find them or re-write as necessary. The long articles showing all the updates for 2010, 2013 and 2019 should be posted here soon too! Enjoy!Screenshot of the new Project Support blog

Roadmap - Now 'On' by default - go try it!

Brian Smith — Wed, 20 Mar 2019 15:18:00 GMT

I wrote a little over a month ago about the new default behavior of Roadmap - https://techcommunity.microsoft.com/t5/Project-Blog/Roadmap-New-default-setting-coming-soon/ba-p/335347 and you will now find that it is ''On by default. So if you have a Project Online Professional or Premium license then head over to https://project.microsoft.com to see what it is all about. Take a look at the collection of videos from our User Assistance team at https://support.office.com/en-us/article/video-welcome-to-roadmap-57764149-51b8-468f-a50d-9ea6a4fd835a

Screenshot of the Roadmap video landing page

Project, Project Online and Planner Accessibility

Brian Smith (CSS) — Wed, 06 Mar 2019 22:58:00 GMT

First published on MSDN on Jul 16, 2018
The Project and Planner engineering teams have been hard at work improving the accessibility of our products. A set of documents is now live that walks through some of the screen reading functionality that has been added to help users relying on Narrator or Jaws to navigate Project and Planner – as well as other accessibility features . The landing pages for Project Web App in Project Online, the desktop client and Microsoft Planner can be found at:

Accessibility support for Project web app

Accessibility support for Project desktop

Accessibility support for Microsoft Planner

The screen reader can tell you where you are on the screen – and for example if you are in the schedule web part it tells you which column and row you are on – and if the field is editable or read only. Similarly if you are in the desktop client it identifies row and column and the edit options – such as knowing that the duration columns has a spinner control.

Keyboard shortcuts are listed both for the web and desktop client – and worth remembering Alt-q which takes you directly to the Tell Me dialog where you can search for commands and execute them right from the dialog – as an example here I am getting Tell Me to give me the Scroll to Task option rather than hunting it down:

For Planner the various screen elements are described which will help the Narrator user to understand the layout – and details of the keyboard controls are given too.

All the articles also include links to both the Microsoft Disability Answer Desk and for our government, commercial and enterprise customers the enterprise Disability Answer Desk – where links to all Microsoft’s accessibility resources can be found

Project Online: Reporting and Portfolio Analysis

Brian Smith (CSS) — Wed, 06 Mar 2019 22:57:45 GMT

First published on MSDN on Feb 14, 2018
The new reporting options that are rolling out to Project Online customers allow you to choose how you want your time phased data and give you control of the time buckets you use – and you can choose not to have any at all. My favourite is to use Fiscal Periods as that also limits the timescale of data that gets published – so reducing the data footprint and publish and reporting times by making sure you have just the data you need. For example I could choose just to have fiscal periods defined for 2018 and 2019 and wouldn’t need to worry about my 15 year long mega-project – as the data after 2019 wouldn’t be clogging up my system. But the blog title mentions Portfolio Analysis? Where does that fit in? I’ll explain…

When you are creating a new Analysis you can define the time period and granularity – but the granularity is limited to Calendar Months or Calendar Quarters:

And as I have checked the option to analyze project resource requirements against capacity the next page in the setup of the analysis will check if I have resource requirements – and give me a red banner if it finds none.

Often that message will just mean you haven’t published the projects yet – but I know mine are all up to date. What happened? Let’s take a look at my Reporting options in Server Settings:

Yes, that will do it! Having Never set for my reporting options means I am feeding no time phased data through to reporting – and the Portfolio Analysis actually uses that data for its resource requirements. Which option should I choose? Any of the others will ‘work’ in that they will show you have requirements – but some will give you the results you want – others less so. I’ll start with a bad choice so that you can understand how this all fits together. I’ll go for Fiscal Periods – and I have defined my Fiscal Periods as 4,4,5 (Each quarter split into 4,4, and then 5 weeks). I was going to make a case for 2,3,5 being a better formation – but I’m guessing not too many of my US readers would get the reference.

Now I need to publish all of my projects that are going into the Analysis and build my Portfolio Analysis again. I’ve already built an analysis on the same data set in my Project Server 2013 system and I’d expect my requirement details to look exactly like this – as I have exactly the same data. Here is my Project Server 2013 analysis and I have enough resources to do 3 of my 5 plans. If you are not familiar with the tool my availability for the different roles is shown in the top grid – then my requirments are listed in the bottom grid – along with the priority of the plans based on my pair-wise comparison to other projects and weighted by the driver priority.

How does this compare to my Project Online Analysis – where I have my reporting using my 4,4,5 Fiscal Periods? A quick aside – in Project Online we have a bug where we show you the Enterprise Global (EGlobal) as one of the projects you can select for the analysis – please don’t as it will break your analysis. I have all the same projects and drivers – same resources and used Calendar Months from March 2018 to March 2019 – so it should be the same as the analysis above shouldn't it? Well if it was I wouldn’t be blogging…

A very different picture…

My analysis say I can only resource a single project – and it looks like I have no requirements at all for resources in March, June and September – but April and July look crazy! January to March are also showing no requirements and I’ll deal with that first. My Fiscal Periods were only defined for 2018 – so I publish no timephased data for 2019 – so that makes sense.

But March, June and September? If I look at the first rows from my time phased data from the OData feed for AssignmentTimephasedDataset this gives me a clue – I see data for 2/26, 4/2, 4/30… and these are the start dates of my Fiscal Periods.

Looking at my Fiscal Period Definitions again I can confirm that none of the start dates are in March, June or September. That explains why I see no requirements. But April July and October (and January) each have two of the start dates – so in effect the choosing of the 4,4,5 pattern has doubled up my requirements in some months and isn’t registering at all in others. This is the extreme example – but you will get a similar but not so pronounced effect if you chose weekly because some calendar months will contain more ‘week start dates’ than others. The new reporting options will always show the sum time phased data for the period against the start date of that period. The effect this has on Portfolio Analysis is one thing you need to take into account when making your choice. So what would work? Daily certainly would – but you wouldn’t gain any benefit in terms of faster publishing and reporting. Monthly would also work just fine – as the start date of the period is the start date of the month – and this give good publish improvements over daily. For my money the Fiscal Period option is the best – but with Standard calendar year as the model.

With this new Fiscal Period defined and reporting configured to use Fiscal Periods I’ll re-publish my plans and build my analysis again.

Perfect! Matches up to my 2013 one – except for the 2019 data which I excluded on purpose by not setting the 2019 fiscal period yet. I hope you like the new reporting options and if you are also using Portfolio Analysis I hope this helps you make the right choice!

Project Online: Getting Started with Roadmap

Brian Smith (CSS) — Wed, 06 Mar 2019 22:56:02 GMT

First published on MSDN on Dec 07, 2018
*** Update 2019-01-31 Another point of confusion - Roadmap is only available for customers with the Project Online Premium or Project Online Professional sku. It IS NOT available (and will not be made available) if you do not have a t least one of these. Customers with the older Project Online with/without Project Pro for Office 365, or Dynamics customers who have Project Online through the PSA sku will not be able to activate Roadmap. ***

*** Update 2019-01-07 - as we continue rolling out some customers may be blocked due to not having the latest CDS for Apps version - so please see this documentation that will help overcome that problem - https://docs.microsoft.com/en-us/common-data-service/upgradecds/introduction-upgrade-cds ***

As we start deploying the various pieces of infrastructure needed to support Roadmap you may see some different things in your Office 365 Tenant – so here is a quick explanation of the different parts and what they mean – and the most asked question – how to turn it on!.

TL;DR – Just go to Office 365 Admin, Settings, Services & add-ins and look for Project Online – then see if Roadmap is available for you to turn on yet. If you don’t see Project Online listed then go to https://project.microsoft.com and hitting that page should trigger the back-fill that will make Project Online appear in the Services & add-ins page (although that doesn’t mean Roadmap is ready for you yet). More info at https://docs.microsoft.com/en-us/projectonline/turn-roadmap-on-or-off

One thing that people have noticed is the new service plans that show up under Project Online Professional and Premium.

The top 3 are new, and are used behind the scenes for the various parts of Roadmap – Common Data Service for Apps (CDS), Flow for Project – and P3 which you can think of as the Project Online equivalent to E3. These would have appeared around the end of November – but do not mean that Roadmap is deployed – just some of the pieces we needed in place first. Along with the CDS comes a new App link to Dynamics 365 – even if you didn’t previously have any Dynamics subscriptions.

Starting today, December 7th 2018, we turned on Roadmap, but just for a small percentage of tenants initially. The tenant administrator can check if it is available yet for your tenant by going to Office 365 Admin Center - https://admin.microsoft.com/AdminPortal/Home#/homepage and then the Settings option and the Service & add-ins option under that.

If Project Online isn’t shown it could be that no one has visited https://project.microsoft.com (the new Home experience) recently – as that page is used to trigger the back-fill of other Roadmap requirements – so go to that page – then look again at the admin center.

*** Update 12/10 - we also have a current issue that the preview Admin Center isn't showing Project Online - so switch to the classic version - we should have this fixed shortly ***

If Project Online is shown then you can click that option and another pane opens with a switch to turn Roadmap on. If Roadmap isn’t ready for you then you will see the following:

If Roadmap is ready then you will see the same – without the red note – and you can slide the switch and Save to turn Roadmap on – after reading the mentioned article of course!.

One you have switched on then you can navigate back to https://project.microsoft.com – or hit the Project icon in the App Launcher – and you will land on the Home page – but it will have a new super power – creating Roadmaps!

For further help on Roadmaps you can see our new videos on the Welcome to Roadmap landing page - https://support.office.com/en-us/article/video-welcome-to-roadmap-57764149-51b8-468f-a50d-9ea6a4fd835a . There will be even more videos arriving from December 10th 2018 onwards.

If Roadmap isn’t ready it could be that we are still not fully rolled out – or that your tenant needs to be updated to CDS 2.0 and we should have more information on that soon.

Enjoy!

Office 365: New Reader role for the Message Center

Brian Smith (CSS) — Wed, 06 Mar 2019 22:55:04 GMT

First published on MSDN on Jun 08, 2018
Regular readers will know that the message center is somewhere that I feel we make it too hard for our customers reach – and the people who could get there (admins) may not fully understand the impact of some of the issues and do not pass on to the people who need to know. This was behind my example of using Azure Functions to read from the message center and write out to Planner tasks (covered recently too at the Project Virtual Conference ) so I was particularly happy to see (ironically on the message center) that a new role is rolling out (pun intended) that will allow Office 365 users to be made Message Center Readers. Very cool!

This is rolling out and the expectation is that it should be complete later this month (June 2018). Please speak with your Office 365 admin and make sure someone in your PMO is made a reader and can see the messages pertinent for Project, Planner, SharePoint or any other workloads you are interested in.

Project and Project Server January 2019 Updates Released

Project-Support — Wed, 06 Mar 2019 22:50:11 GMT

First published on TECHNET on Jan 24, 2019
Last week the Public Update (PU) for Project Server 2013 and 2016 were released for January 2019 . This month, client and server updates were released on January 8th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month that contains fix for security vulnerability. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for January 2019 can be found here -

https://support.microsoft.com/en-us/help/4484800/january-2019-updates-for-microsoft-office - January 2019 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: January 8, 2019- Includes Project fixes, like the roll-up patch in Project Server 2016.

https://support.microsoft.com/en-us/help/4461541/descriptionofthesecurityupdateforsharepointenterpriseserver2016decembe

There is a database schema update this month - it changes to 16.0.4795.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4795.1000 can be used to control the connecting client to the January 2019 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
January 2nd, 2018, update for Project 2016 (KB4461587)

https://support.microsoft.com/en-us/help/4461587/january-2-2019-update-for-project-2016-kb4461587

The version of Project Professional 2016 will be updated to 16.0.4795.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.

Project and Project Server 2013

An overview of all the Office 2013 releases for January 2019 can be found here - https://support.microsoft.com/en-us/help/4484800/january-2019-updates-for-microsoft-office - January 2019, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server December PUs from the following articles:
Project Server 2013 Server Rollup Package
January 8, 2019, cumulative update for Project Server 2013 (KB4461604)

https://support.microsoft.com/en-us/help/4461604/january-8-2019-cumulative-update-for-project-server-2013-kb4461604
Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):
January 8, 2019, update for Project Server 2013 (KB4461461)

https://support.microsoft.com/en-us/help/4461606/january-8-2019-update-for-project-server-2013-kb4461606

The dbo.Versions table should show 15.0.5101.1000 after applying the January 2019 PU. The version number 15.0.5101.1000 can be used to control the connecting client to the January 2019 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
January 2, 2019, update for Project 2013 (KB4461560)

https://support.microsoft.com/en-us/help/4461560/january-2-2019-update-for-project-2013-kb4461560

Project and Project Server December 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:50:05 GMT

First published on TECHNET on Dec 17, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for December 2018 . This month, client and server updates were released on December 11th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month that contains fix for security vulnerability. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for December 2018 can be found here -

https://support.microsoft.com/en-us/help/4477615/december2018updatesformicrosoftoffice - December 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: December 11, 2018- Includes Project fixes, like the roll-up patch in Project Server 2016.

https://support.microsoft.com/en-us/help/4461541/descriptionofthesecurityupdateforsharepointenterpriseserver2016decembe

There is a database schema update this month - it changes to 16.0.4783.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4783.1000 can be used to control the connecting client to the December 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
December 4th, 2018, update for Project 2016 (KB4461540)

https://support.microsoft.com/en-us/help/4461540/december42018updateforproject2016kb4461540

The version of Project Professional 2016 will be updated to 16.0.4783.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.
Project and Project Server 2013
An overview of all the Office 2013 releases for December 2018 can be found here - https://support.microsoft.com/en-us/help/4477615/december2018updatesformicrosoftoffice - December 2018, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server December PUs from the following articles:
Project Server 2013 Server Rollup Package
December 11, 2018, cumulative update for Project Server 2013 (KB4461553)

https://support.microsoft.com/en-us/help/4461553/december112018cumulativeupdateforprojectserver2013kb4461553

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

December 11, 2018, update for Project Server 2013 (KB4461461)

https://support.microsoft.com/en-us/help/4461461/december112018updateforprojectserver2013kb4461461

The dbo.Versions table should show 15.0.5093.1000 after applying the December 2018 PU. The version number 15.0.5093.1000 can be used to control the connecting client to the December 2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
No Project client update this month.

Project and Project Server November 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:49:59 GMT

First published on TECHNET on Nov 16, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for November 2018 . This month, client and server updates were released on November 13th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month that contains fix for security vulnerability. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for November 2018 can be found here -

https://support.microsoft.com/en-us/help/4469617/november-2018-updates-for-microsoft-office - November 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: November 13, 2018- Includes Project fixes, like the roll-up patch in Project Server 2016.

https://support.microsoft.com/en-us/help/4461501/description-of-the-security-update-for-sharepoint-enterprise-server

There is a database schema update this month - it changes to 16.0.4771.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4717.1000 can be used to control the connecting client to the November 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
November 13th, 2018, update for Project 2016 (KB4461478)

https://support.microsoft.com/en-us/help/4461478/description-of-the-security-update-for-project-2016-november-13-2018

The version of Project Professional 2016 will be updated to 16.0.4771.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.
Project and Project Server 2013
An overview of all the Office 2013 releases for November 2018 can be found here - https://support.microsoft.com/en-us/help/4469617/november-2018-updates-for-microsoft-office - November 2018, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server November PUs from the following articles:
Project Server 2013 Server Rollup Package
November 13, 2018, cumulative update for Project Server 2013 (KB4461509)

https://support.microsoft.com/en-us/help/4461509/november-13-2018-cumulative-update-for-project-server-2013-kb4461509

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

There is no individual package for Project Server 2013 this month.

The dbo.Versions table should show 15.0.5085.1000 after applying the November 2018 PU. The version number 15.0.5085.1000 can be used to control the connecting client to the November 2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
November 13, 2018, cumulative update for Project 2013 (KB4461489)

https://support.microsoft.com/en-us/help/4461489/description-of-the-security-update-for-project-2013-november-13-2018

Project and Project Server October 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:49:53 GMT

First published on TECHNET on Oct 16, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for October 2018 . Client updates were released on Oct 2nd; server updates on Oct 7th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle. An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751. We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/- you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now - but leaving this comment here just in case...

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for September 2018 can be found here -

https://support.microsoft.com/en-us/help/4464656/october-2018-updates-for-microsoft-office - October 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: October 9, 2018- Includes Project fixes, like the roll-up patch in Project Server 2016.

https://support.microsoft.com/en-us/help/4461447/description-of-the-security-update-for-sharepoint-enterprise-server

There is a database schema update this month - it changes to 16.0.4756.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4756.1000 can be used to control the connecting client to the October 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client package:
October 2, 2018, cumulative update for Project Server 2016 (KB4461443)

https://support.microsoft.com/en-us/help/4461443/october-2-2018-update-for-project-2016-kb4461443

Project and Project Server 2013

An overview of all the Office 2013 releases for October 2018 can be found here - https://support.microsoft.com/en-us/help/4464656/october-2018-updates-for-microsoft-office - October 2018 updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server July PUs from the following articles:
Project Server 2013 Server Rollup Package
October 9, 2018, cumulative update for Project Server 2013 (KB4461456)

https://support.microsoft.com/en-us/help/4461456/october-9-2018-cumulative-update-for-project-server-2013

This month, the cumulative package does not contain patches for Project Server 2013 but only for SharePoint 2013. If you also use SharePoint in your environment, we recommend to install this update.
Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):
None
Project 2013 Client Package:
October 2, 2018, cumulative update for Project Server 2013 (KB4022227)

https://support.microsoft.com/en-us/help/4022227/october-2-2018-update-for-project-2013-kb4022227

Project and Project Server September 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:49:48 GMT

First published on TECHNET on Sep 17, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for September 2018 . Client updates were released on Sept 4th; server updates on Sept 11h. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle. An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751. We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/- you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now - but leaving this comment here just in case...

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for September 2018 can be found here -

https://support.microsoft.com/en-us/help/4459402/september-2018-updates-for-microsoft-office - September 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: September 11, 2018- Includes Project fixes, like the roll-up patch in Project Server 2016.

https://support.microsoft.com/en-us/help/4092459/description-of-the-security-update-for-sharepoint-enterprise-server

There is a database schema update this month - it changes to 16.0.4744.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4744.1000 can be used to control the connecting client to the September 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client package:
None

Project and Project Server 2013

An overview of all the Office 2013 releases for September 2018 can be found here - https://support.microsoft.com/en-us/help/4459402/september-2018-updates-for-microsoft-office - September 2018 updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server July PUs from the following articles:
Project Server 2013 Server Rollup Package
September 11, 2018, cumulative update for Project Server 2013 (KB4092475)

https://support.microsoft.com/en-us/help/4092475/september-11-2018-cumulative-update-for-project-server-2013-kb4092475
Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):
Description of the security update for Project Server 2013: September 11, 2018 (KB4092480)

https://support.microsoft.com/en-us/help/4092480/september-11-2018-update-for-project-server-2013-kb4092480

The version number 15.0.5067.1000 can be used to control the connecting client to the September 2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
None

Project and Project Server August 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:49:43 GMT

First published on TECHNET on Aug 24, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for August 2018 . Client updates were released on August 7th; server updates on August 14h. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now - but leaving this comment here just in case...

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for August 2018 can be found here -

https://support.microsoft.com/en-us/help/4346823/august-2018-updates-for-microsoft-office - August 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: August 14, 2018- Includes Project fixes, like the roll-up patch in Project Server 2016.

https://support.microsoft.com/en-us/help/4032256/description-of-the-security-update-for-sharepoint-enterprise-server

There is a database schema update this month - it changes to 16.0.4732.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4732.1000 can be used to control the connecting client to the August 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
August 7th, 2018, update for Project 2016 (KB4032238)

https://support.microsoft.com/en-us/help/4032238/august-7-2018-update-for-project-2016-kb4032238

The version of Project Professional 2016 will be updated to 16.0.4732.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.
Project and Project Server 2013
An overview of all the Office 2013 releases for July 2018 can be found here - https://support.microsoft.com/en-us/help/4346823/august-2018-updates-for-microsoft-office - August 2018 updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server July PUs from the following articles:
Project Server 2013 Server Rollup Package
August 14, 2018, cumulative update for Project Server 2013 (KB4032245)

https://support.microsoft.com/en-us/help/4032245/august-14-2018-cumulative-update-for-project-server-2013-kb4032245

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: August 14, 2018 (KB4032253)

https://support.microsoft.com/en-us/help/4032253/august-14-2018-update-for-project-server-2013-kb4032253

There is no database schema update this month - and the dbo.Versions table should show 15.0.5059.1000 after applying the August 2018 PU. The version number 15.0.5059.1000 can be used to control the connecting client to the August 2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
None

Project Online: Project Publishing Improvements

Brian Smith (CSS) — Wed, 06 Mar 2019 22:49:37 GMT

First published on TECHNET on Aug 23, 2018
Just a short post today to talk about some changes you may see in Project Online over the next few days. The product group have been working on improving the publish process and tackling the problem from a few angles – a couple of these result in things you will see – rather than just performance imrpvements that are not so immediately visible.

The first one is that when you publish from the schedule web part in PWA you will no longer be left looking at a ‘Publishing’ notification when you’d rather be doing something else – we now let you get on with your life – and give a shortcut to go to the queue jobs if you really do need to keep watching the publish.

The second one relates to summary resource assignments (SRAs) and how that data now gets through the queue. Rather than spend a few seconds (or minutes) doing this within the publish job for the project this is now handled as a separate publish process, as it does not really need to be handled at the same time. This should mean the publish can finish quicker and the reporting publish can start sooner.

Enjoy all the time this saves you!

Project Online: The new ‘Home’ experience

Brian Smith (CSS) — Wed, 06 Mar 2019 22:49:15 GMT

First published on TECHNET on Aug 15, 2018
*** Update 8/16 I did get some feedback that I was using Chrome in my screenshots - and why not Edge? I actually have Edge as my default browser, but I do use in private Chrome as the usual way to connect to my Office 365 demo tenant - just to avoid conflicts with login (as I also have other tenants/sites I use in Edge, in private Edge and even in-private IE). I am editing this in Edge. We do obviously support other modern browsers too - so I need to use them from a support perspective. ***

I’m following up on the recent blog post about the new home experience and giving a quick walk through – and answering some of the question that have been raised by the announcement.

It should be rolling out over the next few weeks, and it isn’t something that you can choose to have or not have – you will get it. If you have been using the current landing page (the default PWA site) then you can still easily get there by clicking on the Go to Project Web App link at the foot of the page, but hopefully you will find this page useful after reading more about the capabilities. It will gain extra features too – so give it a try and let us know which features you want to see added/changed over on UserVoice .

The first time you visit the new home page (from the Project icon in the app launcher aka waffle, or the similar link on www.office.com or even navigating directly to project.microsoft.com) you will get the ‘first run’ experience. This displays three screens to introduce the basic features.

The links on this page allow you to go to the default Project Web App (/sites/PWA – this cannot be changed) so that you can continue to use any customized page that you had configured, or you can click Create New, which currently just has one option – Project.

Clicking Create New will take you to the first page of the create project wizard in the default PWA site (/sites/PWA) and assuming you have permissions to any Enterprise Project Types (EPT) it will show the EPTs that can be used to create a new plan.

In my case I have quite a few – and further down the page there is a Next button – to go ahead and create the new project. I clicked next and created a new project called New Project for Recent List – just to show how this would then appear in my recent projects.

So back to my Home page – and here I see my recent project above – and I also opened a few other projects so that I would see more. This will only show projects opened since the feature was turned on so it will grow the list over time. The cool feature here is that it will be populated with projects opened in ALL of the PWA sites that you access across your tenant – and will include those opened in Project Professional as well as those opened through the schedule web part in PWA.

These are my recent projects – so what can I do from here? Clicking the project will open it in the correct PWA instance with the default PDP active. There isn’t currently a way to open in the desktop client (Project Professional). I can also choose to remove it from the list if I no longer need to have it as a recent plan (the project does not get deleted) – or I can make it a favourite.

Once I add as a favourite then a tile will be displayed above the list. Here are my 3 favourites.

And just to prove that these can be from any of my PWA sites (these recent ones were opened from 4 different sites) I’ll click on FirstWelsh – which will take me to my /sites/Welsh PWA site – which was provisioned in Welsh, but as Welsh isn’t a supported language for Project Online it actually shows a mix of languages – with the SharePoint content in Welsh and the PJO content in the fallback language – which is English.

Expect further enhancements to come later which will add even more value to the experience and please give us feedback via UserVoice .

Today the target user is the project manager who opens projects either through PWA of Project Professional and gives them a quick way to get to their favourites. Not so useful to team members right now – but you can continue on to the default PWA to get to all the features team members need – or carry on using direct links to the PWA that you need to work in.

Project and Project Server July 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:47:34 GMT

First published on TECHNET on Jul 26, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for July 2018 . Client updates were released on July 3rd; server updates on July 10th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for July 2018 can be found here -

https://support.microsoft.com/en-us/help/4340798/july-2018-updates-for-microsoft-office - July 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: July 10, 2018- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4022228/description-of-the-security-update-for-sharepoint-server-2016

There is a database schema update this month - it changes to 16.0.4717.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4717.1000 can be used to control the connecting client to the July 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
July 3rd, 2018, update for Project 2016 (KB4022217)

https://support.microsoft.com/en-us/help/4022217/july-3-2018-update-for-project-2016-kb4022217

The version of Project Professional 2016 will be updated to 16.0.4717.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.
Project and Project Server 2013
An overview of all the Office 2013 releases for July 2018 can be found here - https://support.microsoft.com/en-us/help/4340798/july-2018-updates-for-microsoft-office - July 2018, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server July PUs from the following articles:
Project Server 2013 Server Rollup Package
July 10, 2018, cumulative update for Project Server 2013 (KB4022240)

https://support.microsoft.com/en-us/help/4022240/july-10-2018-cumulative-update-for-project-server-2013-kb4022240

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: July 10, 2018 (KB4022245)

https://support.microsoft.com/en-us/help/4022245/july-10-2018-update-for-project-server-2013-kb4022245

There is no database schema update this month - and the dbo.Versions table should show 15.0.5049.1000 after applying the July 2018 PU. The version number 15.0.5049.1000 can be used to control the connecting client to the July 2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
None

Project Online: New home page for users

Brian Smith (CSS) — Wed, 06 Mar 2019 22:47:26 GMT

First published on TECHNET on Jul 19, 2018
The Project Online users new home page called Project Home lets you Open, Favorite a Project and Create New Projects, helping you get organized and find Projects of your interest from one place thus making it fastest and easiest. You can also see your recently accessed Project files to resume editing your Project. In this blog post, we will discuss how to access the Project Home and its features.

Note Currently to access Project Home from www.office.com users need to have a subscription of Project Online Essential, Project Online Professional and Project Online Premium. For more information, see Compare Project versions .

Using www.office.com

The www.office.com portal is the fastest and easiest way to get started with the Project Home experience. The Office.com app gallery provides a Project tile. Clicking that tile launches the Project Home of Project Online. With the new www.office.com experience, if you can’t find the Project tile in the gallery, click Explore all your apps to get access to Project Home.

Using the Office 365 app launcher (also called the “waffle”)

You can switch to Project Home from Office.com (or other Office 365 web apps and services for which you have a license) after clicking the app launcher (or “waffle”) icon in the top menu. If the Project tile is not shown, click All apps to get to the Project Home page.

Creating a new Project

From your Project home you can create new Project with the Create New menu. With one click on Project , a blank Project is created in your default PWA (Project Web Access) site.

Opening an existing Project for editing

From your Project Home, you can open a Project listed in the Recent section, which shows your recently access Projects from various PWA sites. By clicking on the list entry the Project opens in the new tab to start editing.

Favoriting an existing Project

You can Favorite a Project shown in the in the Recent section, by clicking on overflow menu icon on the Recent list entry and selecting the Add to favorites option. This moves the Project entry from the Recent section to Favorites section of Project Home and Project entry appears as cards in Favorites section.

Users can also select the Remove from list, to remove the Project entry from Recent section, this does not delete your Project, but just removes the entry.

Thanks for reading. Please asks any question or provide comments

Project and Project Server June 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:46:19 GMT

First published on TECHNET on Jun 14, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for June 2018 . Client updates were released on June 5th; server updates on June 12th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for June 2018 can be found here -

https://support.microsoft.com/en-us/help/4299875/june-2018-updates-for-microsoft-office - June 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: June 12, 2018- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4022173/description-of-the-security-update-for-sharepoint-enterprise-server-20

June 12, 2018, update for SharePoint Server 2016 (KB4022178)- Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/4022178/june-12-2018-update-for-sharepoint-enterprise-server-2016-kb4022178

There is a database schema update this month - it changes to 16.0.4705.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4705.1000 can be used to control the connecting client to the June 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
June 5th, 2018, update for Project 2016 (KB4022164)

https://support.microsoft.com/en-us/help/4022164/june-5-2018-update-for-project-2016-kb4022164

The version of Project Professional 2016 will be updated to 16.0.4705.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.
Project and Project Server 2013
An overview of all the Office 2013 releases for June 2018 can be found here - https://support.microsoft.com/en-us/help/4299875/june-2018-updates-for-microsoft-office - June 2018, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server June PUs from the following articles:
Project Server 2013 Server Rollup Package
June 12, 2018, cumulative update for Project Server 2013 (KB4022185)

https://support.microsoft.com/en-us/help/4022185/june-12-2018-cumulative-update-for-project-server-2013-kb4022185

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: June 12, 2018 (KB4022192)

https://support.microsoft.com/en-us/help/4022192/june-12-2018-update-for-project-server-2013-kb4022192

There is no database schema update this month - and the dbo.Versions table should show 15.0.5011.1000 after applying the June 2018 PU. The version number 15.0.5011.1000 can be used to control the connecting client to the June 2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
June 5, 2018, update for Project 2013 (KB4022171)

https://support.microsoft.com/en-us/help/4022171/june-5-2018-update-for-project-2013-kb4022171

The client version number will be 15.0.5037.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.5037.1000 value to control connection of the June 2018 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project Online: Setting a Status Manager with CSOM

Brian Smith (CSS) — Wed, 06 Mar 2019 22:46:02 GMT

First published on MSDN on May 25, 2018
Just a quick post today to share something that might help scenarios where you need to change a status manager for a task. As you may well know, it isn't possible to just select anyone to be a status manager for a task – and even in the client application you don’t see people in the Status Manager drop down unless they are already a status manager in the plan – and they only get there by having opened the plan and making assignments (and hence being the status manager for the new task/assignment). Hopefully there will be a broader change coming – but a recent change in Project Online does bring this a step closer.

You still (as of 5/25) can’t set just anyone programmatically as a status manager using CSOM – they have to be ‘on the list’ – so will need to have opened the plan as mentioned above – but you can set anyone to be an owner (permissions allowing of course). And guess what? That gets them on the list! So if you set the person who you want to be a status manager to be the owner of the plan – you can then set them as a status manager! You’d probably then want to set the original owner back again.

In code here is a snippet that shows how you might approach this (I don’t set the owner back here – so if you wanted to do that you’d need to persist the actual owner). This sample could be added as a class in the Github sample at https://github.com/OfficeDev/Project-Samples/tree/master/Create-Update-Project-Samples . For brevity I’ve stripped out some error checking.

public static void ReadAndUpdateStatusManager()
{
// Load csom context
context = GetContext(pwaInstanceUrl);

// Retrieve publish project named "New Project"
// if you know the Guid of project, you can just call context.Projects.GetByGuid()
csom.PublishedProject project = GetProjectByName(projectName, context);
csom.DraftProject draft = project.CheckOut();

draft.Context.Load(draft.Owner);
draft.Context.ExecuteQuery();
draft.Context.Load(draft.Tasks);
draft.Context.ExecuteQuery();

foreach (var task in draft.Tasks)
{
draft.Context.Load(task.StatusManager);
}

draft.Context.ExecuteQuery();

// We get the user we want to be our status manager

User StatusManager = context.Web.SiteUsers.GetByLoginName("i:0#.f|membership|<username goes here>@<and tenant here>.onmicrosoft.com");
context.Load(StatusManager);
context.ExecuteQuery();

// And set our user as the Owner

draft.Owner = StatusManager;

foreach (var task in draft.Tasks)
{
try
{
if (!task.IsSummary)
{

// Then we can set our new Owner as a Status Manager
task.StatusManager = draft.Owner;
}
}
catch (Exception ex)
{
Console.Write(string.Format("Error setting Status Manager:", ex.Message));
}
}

// Publish and check in the project
csom.JobState jobState = context.WaitForQueue(draft.Publish(true), DEFAULTTIMEOUTSECONDS);
JobStateLog(jobState, "Updating project");
}

Project and Project Server May 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:45:56 GMT

First published on TECHNET on May 10, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for May 2018 . Client updates were released on May 1st; server updates on May 8th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for May 2018 can be found here -

https://support.microsoft.com/en-us/help/4133083/may-2018-updates-for-microsoft-office - May 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: May 8, 2018- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4018381/description-of-the-security-update-for-sharepoint-enterprise-server-20

May 8, 2018, update for SharePoint Server 2016 (KB4018386)- Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/4018386/may-8-2018-update-for-sharepoint-enterprise-server-2016-kb4018386

There is a database schema update this month - it changes to 16.0.4690.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4690.1000 can be used to control the connecting client to the May 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
May 1st, 2018, update for Project 2016 (KB4018373)

https://support.microsoft.com/en-us/help/4018373/may-1-2018-update-for-project-2016-kb4018373

The version of Project Professional 2016 will be updated to 16.0.4690.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.
Project and Project Server 2013
An overview of all the Office 2013 releases for May 2018 can be found here - https://support.microsoft.com/en-us/help/4133083/may-2018-updates-for-microsoft-office - May 2018, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server May PUs from the following articles:
Project Server 2013 Server Rollup Package
May 8, 2018, cumulative update for Project Server 2013 (KB4018395)

https://support.microsoft.com/en-us/help/4018395/may-8-2018-cumulative-update-for-project-server-2013-kb4018395

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: May 8, 2018 (KB4022130)

https://support.microsoft.com/en-us/help/4022130/description-of-the-security-update-for-project-server-2013-may-8-2018

There is no database schema update this month - and the dbo.Versions table should show 15.0.5011.1000 after applying the May 2018 PU. The version number 15.0.5011.1000 can be used to control the connecting client to the May 2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
May 1, 2018, update for Project 2013 (KB4018379)

https://support.microsoft.com/en-us/help/4018379/may-1-2018-update-for-project-2013-kb4018379

The client version number will be 15.0.5031.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.5031.1000 value to control connection of the May 2018 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project and Project Server April 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:45:48 GMT

First published on TECHNET on Apr 12, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for April 2018 . Client updates were released on April 3rd; server updates on April 10th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for April 2018 can be found here -

https://support.microsoft.com/en-us/help/4098622/april-2018-updates-for-microsoft-office - April 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: April 10, 2018- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4018336/description-of-the-security-update-for-sps-2016

April 10, 2018, update for SharePoint Server 2016 (KB4018340)- Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/4018340/april-10-2018-update-for-sharepoint-enterprise-server-2016-kb4018340

There is a database schema update this month - it changes to 16.0.4678.1001. Remember, Project Server 2016 data is in the content database. The version number 16.0.4678.1001 can be used to control the connecting client to the April 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
April 3rd, 2018, update for Project 2016 (KB4018320)

https://support.microsoft.com/en-us/help/4018320/april-3-2018-update-for-project-2016-kb4018320

The version of Project Professional 2016 will be updated to 16.0.4678.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.
Project and Project Server 2013
An overview of all the Office 2013 releases for April 2018 can be found here - https://support.microsoft.com/en-us/help/4098622/april-2018-updates-for-microsoft-office - April 2018, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server April PUs from the following articles:
Project Server 2013 Server Rollup Package
April 10, 2018, cumulative update for Project Server 2013 (KB4018346)

https://support.microsoft.com/en-us/help/4018346/april-10-2018-cumulative-update-for-project-server-2013-kb4018346

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: April 10, 2018 (KB4018352)

https://support.microsoft.com/en-us/help/4018352/april-10-2018-update-for-project-server-2013-kb4018352

There is no database schema update this month - and the dbo.Versions table should show 15.0.5011.1000 after applying the April 2018 PU. The version number 15.0.5011.1000 can be used to control the connecting client to the April 2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
April 3, 2018, update for Project 2013 (KB4018335)

https://support.microsoft.com/en-us/help/4018335/april-3-2018-update-for-project-2013-kb4018335

The client version number will be 15.0.5023.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.5023.1000 value to control connection of the April 2018 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project and Project Server March 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:45:41 GMT

First published on TECHNET on Mar 16, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for March 2018 . Client updates were released on March 6th; server updates on March 13th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - you will have needed a '2016' level client to connect starting since the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for March 2018 can be found here -

https://support.microsoft.com/en-us/help/4090988/march-2018-updates-for-microsoft-office - March 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: March 13, 2018- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4018293/description-of-the-security-update-for-sharepoint-enterprise-server-20

March 13, 2018, update for SharePoint Server 2016 (KB4011687)- Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/4011687/march-13-2018-update-for-sharepoint-enterprise-server-2016-kb4011687

There is a database schema update this month - it changes to 16.0.4666.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4666.1000 can be used to control the connecting client to the March 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
March 6th, 2018, update for Project 2016 (KB4011734)

https://support.microsoft.com/en-us/help/4011734/march-6-2018-update-for-project-2016-kb4011734

The version of Project Professional 2016 will be updated to 16.0.4666.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.
Project and Project Server 2013
An overview of all the Office 2013 releases for March 2018 can be found here - https://support.microsoft.com/en-us/help/4090988/march-2018-updates-for-microsoft-office - March 2018, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server March PUs from the following articles:
Project Server 2013 Server Rollup Package
March 13, 2018, cumulative update for Project Server 2013 (KB4018301)

https://support.microsoft.com/en-us/help/4018301/march-13-2018-cumulative-update-for-project-server-2013-kb4018301

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: March 13, 2018 (KB4018305)

https://support.microsoft.com/en-us/help/4018305/descriptionofthesecurityupdateforprojectserver2013march13-2018

There is a database schema update this month - and the dbo.Versions table should show 15.0.5011.1000 after applying the March 2018 PU. The version number 15.0.5011.1000 can be used to control the connecting client to the March2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
March 6, 2018, update for Project 2013 (KB4018292)

https://support.microsoft.com/en-us/help/4018292/march-6-2018-update-for-project-2013-kb4018292

The client version number will be 15.0.5015.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.5015.1000 value to control connection of the March 2018 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project Server 2013: Important dates and patches

Brian Smith (CSS) — Wed, 06 Mar 2019 22:45:34 GMT

First published on TECHNET on Mar 06, 2018
As I write we are approaching an important date in the life of Project and Project Server 2013 – 10th April 2018 (thanks for the correction Andre!) will be the end of mainline support. This includes SharePoint Server 2013 too. This means that beyond this date we will only be taking fixes for the product that are security related (maybe recent regressions too). Hopefully you are already considering moving to Project Online, Project Server 2016 or possibly have an eye out for Project Server 2019. You need to be aware of other servicing policy details and this link is the place to go. https://technet.microsoft.com/en-us/library/mt493253.aspx

In brief – the most important paragraph is:

Starting with extended support on 4/11/2018, Microsoft will update the minimum supported build of SharePoint Server 2013 and SharePoint Foundation 2013. Customers must be running that build or higher to remain supported. If a customer contacts Microsoft support and their farm is not running the minimum supported build or higher, they will be asked to upgrade to that build before support can be offered.

The dates to be aware of:

SharePoint Server 2013 and SharePoint Foundation 2013 Releases              Support End Date

Service Pack 1                                                                                                            4/10/2018

April 2017 Public Update – March 2018 Public Update                                            4/10/2019

April 2018 Public Update – all future Public Updates                                               4/11/2023

So by 4/11/2018 you should be running at least the April 2017 Public update , and hopefully something even more recent. For all updates for Project Server 2013 please see https://blogs.technet.microsoft.com/projectsupport/p/ps13cu/ .

Project Online: Why might my site go read-only?

Brian Smith (CSS) — Wed, 06 Mar 2019 22:45:26 GMT

First published on MSDN on Mar 05, 2018

We are rolling out a change currently that could set some PWA sites to read-only – so I thought it worth mentioning 3 reasons why you might see a PWA site go into a read only mode – which would show as a yellow banner on the PWA pages. I’ll start with the most recent change.

We have seen a number of customers open cases where their Project Online PWA site appeared to just go away. Closer examination showed that the customer did not have either a Project Online Professional or Premium license – but just some Project Online Essentials licenses. I blogged about this combination a while ago . Normally when a license expires then the site will go into a read only state 30 days later – then after a further 90 days the site will be de-provisioned. The challenge here was that there were still valid licenses (the Project Essentials ones) and the sites were not showing as read-only – but would still finally get de-provisioned. The tenant and billing administrators would receive e-mails warning of the pending de-provision but it appears these where ignored in some cases. The change means that any sites where the only valid license is Project Essentials will now go to read-only after 30 days (or immediately if the Project Online Professional or Premium licenses expired more than 30 days ago). Many of the customers who have had this issue appear to be from the Education sector – and it seems to coincide with the change in offering where earlier the EDU customers had a free option for Project Online – but now have a reduced price offering – and some renewed with the cheapest license available and did not choose any Professional or Premium licenses. I should remind everyone that not only do you require at least one Project Online Professional or Premium license to keep your PWA alive – but you also need these licenses to perform administrative and other regular tasks that many of you users might need to do – so please ensure you are correctly licensed. See https://products.office.com/en-us/project/compare-microsoft-project-management-software?tab=1 for details of the different licenses and their features.

The 2nd reason you might go into a read-only state is if you are over your assigned quota. I’ll be following up with another blog that goes into more details here and offers some ways to ensure you are not using more data than you need to – and to avoid the risk of hitting your quota – and I’ll add a link here when that posting is live.

The 3rd is usually a very temporary condition that can occur during maintenance. Most maintenance is not even noticed by our customers and you will not often see this – but if for example we are failing over a SQL Server or migrating a tenant for load balancing our server farms there can be times when short periods of read-only are experienced.

And the 4th? Just in case you came here from my click-bait headline? If the planet runs out of 0’s and 1’s then I guess PWA would go read-only. I said you wouldn't believe it!

Project and Project Server February 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:45:18 GMT

First published on TECHNET on Feb 15, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for February 2018 . Client updates were released on February 6th; server updates on February 13th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - as you will need a '2016' level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for February 2018 can be found here -

https://support.microsoft.com/en-us/help/4077965/february-2018-updates-for-microsoft-office - February 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (usually this single patch comes in two parts... a wssloc and sts2016 part - however this month we only have the sts2016 part) - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: February 13, 2018- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4011680/descriptionofthesecurityupdateforsharepointentserver2016february13-201

There is a database schema update this month - it changes to 16.0.4651.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4651.1000 can be used to control the connecting client to the February 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
February 6th, 2018, update for Project 2016 (KB4011672)

https://support.microsoft.com/en-us/help/4011672/february-6-2018-update-for-project-2016-kb4011672

The version of Project Professional 2016 will be updated to 16.0.4654.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.
Project and Project Server 2013
An overview of all the Office 2013 releases for February 2018 can be found here - https://support.microsoft.com/en-us/help/4077965/february-2018-updates-for-microsoft-office - February 2018, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server February PUs from the following articles:
Project Server 2013 Server Rollup Package
February 13, 2018, cumulative update for Project Server 2013 (KB4011694)

https://support.microsoft.com/en-us/help/4011694/february-13-2018-cumulative-update-for-project-server-2013-kb4011694

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: February 13, 2018 (KB4011701)

https://support.microsoft.com/en-us/help/4011701/descriptionofthesecurityupdateforprojectserver2013february13-2018

There is a database schema update this month - and the dbo.Versions table should show 15.0.4991.1000 after applying the February 2018 PU. The version number 15.0.4991.1000 can be used to control the connecting client to the February 2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
February, 2018, update for Project 2013 (KB4011679)

https://support.microsoft.com/en-us/help/4011679/february-6-2018-update-for-project-2013-kb4011679

The client version number will be 15.0.5007.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.5007.1000 value to control connection of the February 2018 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project Server 2013: Building cubes when TLS 1.2 is enforced

Brian Smith (CSS) — Wed, 06 Mar 2019 22:45:10 GMT

First published on TECHNET on Jan 11, 2018
If anyone has been reading my blog for a while then they may have seen the various Project Server OLAP cube build failure postings over the years – but I hadn’t seen a really tricky one in a while, so thanks to Craig Sheppard from one of our aerospace customers for stumping me with this one – and Jason Eisenzimmer from our SQL team who came to the rescue. I also learned (or re-learned?) along the way a little more about the build process and which server is talking to which server at the various stages. This was 2013 – and in 2016 you wouldn’t have this same issue.

So lets start with the error:

Failed to build the OLAP cubes. Error: Error Adding DataSourceView 'Project Reporting data source' to database 'Test'. Error: Error Adding Table 'MSP_TimeByDay_OlapView' to database. Error: Client unable to establish connection
TCP Provider: An existing connection was forcibly closed by the remote host.

Looking at the Analysis Services server at that point it had created the database ‘Test’ and it had defined the Data Source – but not the Data Source Views.

And drilling in to the Project Reporting data source we can view the connection string and even test the connection.

My PWA database just happens to be called PWAOData as I’m doing some other tests on OData on that instance – but this is nothing to do with OData. In the customer’s environment the Test Connection fails – yet if they change the Provider to the Native Client 11.0 everything works fine. Not a workaround as the cube build will always reset to 10.0 and fail. The failure indicated, like the cube build error, that the existing connection was forcibly closed by the remote host. After trying a different version of the 10.0 native client and not getting anywhere I engaged with the SQL team and Jason – who quickly established that it was a TLS 1.2 problem (the forcibly closed was a clue apparently) and it was confirmed that TLS 1.2 was being enforced in this environment. Jason suggested this patch https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=3098860&kbln=en-us which support TLS 1.2 with SQL Native Client 10.0. And yes! The Test Connection worked! But the cube builds still failed… .

I’d originally thought that this part of the cube database construction was all happening from Analysis Services but when Jason suggested that Project Server was potentially the issue I did a profiler trace on both the database engine and Analysis Services while I built a cube in my environment. This showed me that Project Server is still driving things and making the call to AS to create the Data Source – and then making the call to create the view – but before it can create the view it needs some information from the database – such as the time dimensions – and this was the precise part that was failing. So in fact fixing the ‘Test Connection’ part above was still entirely necessary as later AS would need to read the reporting tables – but we hadn’t got that far in the cube build.

A quick e-mail to Craig and the Project Server was patched with the same patch as above so that it could talk to the server with Native Client 10.0 and cubes were building just fine. As mentioned you wouldn’t see this in 2016 as the default Native Client is 11.0 – which is fine with TLS 1.2.

Thanks again Craig for your patience and being a great customer to work with – and Jason for your super SQL insights.

Project and Project Server January 2018 Updates Released

Project-Support — Wed, 06 Mar 2019 22:44:23 GMT

First published on TECHNET on Jan 11, 2018
This week the Public Update (PU) for Project Server 2013 and 2016 were released for January 2018 . Client updates were released on January 2nd; server updates on January 9th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - as you will need a '2016' level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for January 2018 can be found here -

https://support.microsoft.com/en-us/help/4058103/january-2018-updates-for-microsoft-office - January 2018 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (but this month, as usual, the single patch comes in two parts... a wssloc and sts2016 part). - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: January 9, 2018- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4011642/descriptionofthesecurityupdateforsharepointenterpriseserver2016january

January 9, 2018, update for SharePoint Server 2016 (KB4011645)- Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/4011645/january-9-2018-update-for-sharepoint-enterprise-server-2016-kb4011645

There is a database schema update this month - it changes to 16.0.4639.1002. Remember, Project Server 2016 data is in the content database. The version number 16.0.4639.1002 can be used to control the connecting client to the January 2018 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
January 2, 2018, update for Project 2016 (KB4011633)

https://support.microsoft.com/en-us/help/4011633/january-2-2018-update-for-project-2016-kb4011633

The version of Project Professional 2016 will be updated to 16.0.4639.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.

Project and Project Server 2013
An overview of all the Office 2013 releases for January 2018 can be found here - https://support.microsoft.com/en-us/help/4058103/january-2018-updates-for-microsoft-office - January 2018, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server January PUs from the following articles:
Project Server 2013 Server Rollup Package
January 9, 2018, cumulative update for Project Server 2013 (KB4011650)

https://support.microsoft.com/en-us/help/4011650/january-9-2018-cumulative-update-for-project-server-2013-kb4011650

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: January 9, (KB4011654)

https://support.microsoft.com/en-us/help/4011654/january-9-2018-update-for-project-server-2013-kb4011654

There is a database schema update this month - and the dbo.Versions table should show 15.0.4991.1000 after applying the January 2018 PU. The version number 15.0.4991.1000 can be used to control the connecting client to the January 2018 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
January, 2018, update for Project 2013 (KB4011640)

https://support.microsoft.com/en-us/help/4011640/january-2-2018-update-for-project-2013-kb4011640

The client version number will be 15.0.4997.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4997.1000 value to control connection of the January 2018 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project Online: Assigning licenses to guest users with PowerShell

Brian Smith (CSS) — Wed, 06 Mar 2019 22:44:10 GMT

First published on TECHNET on Dec 29, 2017
*** 7/2/2018 - Update - just to address some confusion - the guest access to Project Online does not allow the guest to also have access to and download the Project Online Desktop Client application - that requires a full paid license. If you try to navigate to the application download you will get a message that no license is assigned ***

It looks like there is a current issue assigning licenses to guest users via the usual Admin Center route – and the Product Licenses section normally seen when editing users in Office 365 is not showing for guest users. And for PWA the guest user needs a license before they can see or do anything in Project Online. Hopefully this is temporary – but always good to know how to use PowerShell to do the license assignment too! And thanks Rolly Perreaux for bringing this to my attention.

A few useful resources first – then I’ll give a few short cuts for those already set up to use the PowerShell commands.

The support article for Project Online and guest users can be found here - https://support.office.com/en-us/article/Using-Project-Online-with-external-users-f305a365-3d81-48bc-a3d0-4260e7326899 and that also has the link to the more general SharePoint article - manage external sharing for your SharePoint Online environment . The article for assigning licenses is https://docs.microsoft.com/en-us/office365/enterprise/powershell/assign-licenses-to-user-accounts-with-office-365-powershell .

I’d already configured my tenant and site collection to allow Sharing (SharePoint Admin Center options) so I just needed to send the invite by using the ‘Share’ option top right in your PWA (or use the B2B options explained in the articles for adding in bulk)

The account needs to be a Microsoft (Hotmail, Live, MSN etc…) or Office 365 Work or Organizational account. The person then needs to respond to the request that arrives by e-mail – but at this point they will get a bad experience as they have no license.

But they will appear in your directory – and previously this was where licenses were assigned. The icon next to my name shows this is an external account.

As I couldn’t add licenses there I then reminded myself of the steps to do this with PowerShell from the articles above then opened my SharePoint Online Management shell (I already had all the right modules loaded) and executed the following:

PS C:\WINDOWS\system32> Connect-MsolService
PS C:\WINDOWS\system32> Get-MsolAccountSku

This first prompts you to log in – then the 2nd command lists your sku’s – useful for copy/pasting into the following commands.

PS C:\WINDOWS\system32> Get-MsolUser -all -UnlicensedUsersOnly

This will list the guest just added (and maybe others) - and they will need a usage location set before adding licenses. Mine is US - yours of course may be different. It is the ISO 3166-1 alpha-2 country code.

Then use the following, substituting your country code, upn and tenant as appropriate – and you can copy/paste the UPN form the output of the last command.

PS C:\WINDOWS\system32> Set-MsolUser -UserPrincipalName "<user principal name>" -UsageLocation US
PS C:\WINDOWS\system32> Set-MsolUserLicense -UserPrincipalName "<user principal name>" -AddLicenses “<yourtenant>:PROJECTONLINE_PLAN_2"
PS C:\WINDOWS\system32> Set-MsolUserLicense -UserPrincipalName "<user principal name>" -AddLicenses "<yourtenant>:ENTERPRISEPACK"

It can take a short while before the license is seen - logging out and back might help if you got the "do not have a license" message. My working external user! I’d edited the User Profile to make my display name unique.

Project Online: Provisioning a new PWA with PowerShell

Brian Smith (CSS) — Wed, 06 Mar 2019 22:43:27 GMT

First published on MSDN on Dec 22, 2017
This post comes from my “You learn something new every day” collection – and after responding to e-mail saying the only way to provision a PWA site in Project Online is through the UI I thought I’d better double check. I’d also seen a Twitter posting about a new update to the SharePoint Online Management Shell that came out yesterday – so what better time to install it (after uninstalling the previous one) and giving it a test drive.

Here is the download - https://www.microsoft.com/en-us/download/details.aspx?id=35588

There are no specific Project PowerShell commands there – I quickly established that hadn’t changed (gcm *PWA* and gcm *Project*) but what about New-SPOSite? Maybe if I use the PWA#0 template? But how would I enable the PWA features (I had my on-premises hat on…).

So this is what happened… First step – Connect-SPOService – and the Url is the admin page – not just the tenant page:

Then I used the New-SPOSite command – with the following parameters:

New-SPOSite -Url https://brismithpjo.sharepoint.com/sites/BlogDemoPS -Owner brismith@brismithpjo
.onmicrosoft.com -StorageQuota 20 -Title BlogPWAFromPowerShell -Template PWA#0

Then went over to my Admin Center to take a look:

And once the provisioning was complete – what would I find?

A working PWA site! I’m sure plenty reading this are saying “yes, of course” and already knew this – but it had somehow passed me by. There isn’t unfortunately a way to set permissions mode via PowerShell – as far as I could see anyway – but happy to proven wrong. It would make a great addition to Set-SPOSite.

I did notice that Set-SPOSite does already have an EnablePWA option – but having executed it against a SharePoint team site it didn’t seem to do what I expected (Add PWA) – so I’ll try and find out more,. as the example on the Set-SPOSite docs page is a little lacking.

Project Online: Now with Conditional Access

Brian Smith (CSS) — Wed, 06 Mar 2019 22:42:42 GMT

First published on TECHNET on Dec 21, 2017
Just a quick posting to confirm that Conditional Access for SharePoint Online and OneDrive also applies to Project Online – as it sits on top of SharePoint. You can’t just block Project Online though – you block it by blocking SharePoint. Bill Baer has a great blog post - https://blogs.technet.microsoft.com/wbaer/2017/02/17/conditional-access-policies-with-sharepoint-online-and-onedrive-for-business/ so I’ll just show that the same applies to Project.

To use Conditional Access some of the features require the Azure Active Directory Premium (See Bill’s blog and the Azure AD article https://docs.microsoft.com/en-us/azure/active-directory/active-directory-conditional-access-technical-reference and I’ll walk you through the simple scenario I configured.

I want to block Sara Davis from accessing Project Online so I go to the Office 365 Admin Portal and then to the Azure AD Admin center.

From there I take the Conditional access option (you can start a trial if you don’t have Premium) and add a New policy. You can see the various options here – and I’m going to select Sara Davis as my user, for the Cloud apps I will choose Office 365 SharePoint Online and OneDrive.

Under conditions I have various options – and as I just want to block I can choose the Client apps check Yes to configure and check both Browser and Mobile apps and desktop clients (I’ll leave you to review in the Azure AD document the other cool options for locations, device platform and sign-in risk – which give more granular control).

The final thing is to add the Access controls – and I just want to Block access. I select that, Enable Policy and Create – and I’m done.

Now when Sara tries to get to browse to PWA she will see this message – and I’ve expanded the details part:

Same if she tries to use the Project Online Desktop Client or Project Professional 2016

I hope you find this a useful addition to Project Online and Azure AD!

Project and Project Server December 2017 Updates Released

Project-Support — Wed, 06 Mar 2019 22:41:26 GMT

First published on TECHNET on Dec 13, 2017
This week the Public Update (PU) for Project Server 2013 and 2016 were released for December 2017 . Client updates were released on December 5th; server updates on December 12th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - as you will need a '2016' level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for December 2017 can be found here -

https://support.microsoft.com/en-us/help/4055454/december-2017-updates-for-microsoft-office - December 2017 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (but this month, as usual, the single patch comes in two parts... a wssloc and sts2016 part). - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: December 12, 2017- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4011576/descriptionofthesecurityupdateforsharepointserver2016december12-2017

December 12, 2017, update for SharePoint Server 2016 (KB4011578)- Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/4011578/december-12-2017-update-sharepoint-enterprise-server-2016-kb4011578

There is a database schema update this month - it changes to 16.0.4624.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4624.1000 can be used to control the connecting client to the December 2017 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
December 5, 2017, update for Project 2016 (KB4011573)

https://support.microsoft.com/en-us/help/4011573/december-5-2017-update-for-project-2016-kb4011573

The version of Project Professional 2016 will be updated to 16.0.4627.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.

Project and Project Server 2013
An overview of all the Office 2013 releases for December 2017 can be found here - https://support.microsoft.com/en-us/help/4055454/december-2017-updates-for-microsoft-office - December 2017, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server December PUs from the following articles:
Project Server 2013 Server Rollup Package
December 12, 2017, cumulative update for Project Server 2013 (KB4011589)

https://support.microsoft.com/en-us/help/4011589/december-12-2017-cumulative-update-for-project-server-2013-kb4011589

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: December 12, (KB4011598)

https://support.microsoft.com/en-us/help/4011598/december-12-2017-update-for-project-server-2013-kb4011598

There is a database schema update this month - and the dbo.Versions table should show 15.0.4989.1000 after applying the December 2017 PU. The version number 15.0.4989.1000 can be used to control the connecting client to the December 2017 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
December 5, 2017, update for Project 2013 (KB4011285)

https://support.microsoft.com/en-us/help/4011285/december-5-2017-update-for-project-2013-kb4011285

The client version number will be 15.0.4989.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4989.1000 value to control connection of the December 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project Online: Changes to OData–new Time phased data options

Brian Smith (CSS) — Tue, 22 Oct 2019 14:28:38 GMT

First published on TECHNET on Nov 29, 2017
I just posted an article over on the ‘BriSmith’ blog about the new options for time phased data that allow reporting at a weekly, monthly or fiscal period based granularity instead of the default daily. This can help speed up your OData reporting solutions as well as reducing the time your plans might take to publish. See https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-Online-Changes-to-Granularity-of-Time-phased-OData/ba-p/362088 for more details.

Project Online: Changes to Granularity of Time phased OData

Brian Smith (CSS) — Wed, 06 Mar 2019 22:40:49 GMT

First published on MSDN on Nov 29, 2017
This was announced a while back as you needed to be aware of the impact on reporting – and you should have seen the posting in the Office 365 Admin message center. This is rolling out now, and the message center post has just been updated to say that we should be completed by around the end of the year. (If you are not seeing the message center posts – then talk to your admin and share my blog post https://lwal.me/3n ). The official article on the time phased data roll-up feature can be found at https://support.office.com/en-us/article/Configure-rollup-of-timephased-reporting-data-in-Project-Online-da8487fe-899e-4510-a264-e2ebc948928c . I’ve also been beaten to the blogs by Paul Mather (and probably others) so I’ll try not to just repeat the great content that is already out there – but highlight a few of the nuances.

The change has a few different aims – and one is certainly to give you faster reporting against your Project Online data. This can be achieved if the new granularities of weekly or monthly work for you better than daily – with the added bonus that the publish will be a lot faster too! We don’t have to break the project data down to a daily level for publishing, then have you pull the daily data only to have you aggregate it back to weekly/monthly again. It will save space too – both in your tenant but also in any local data warehouse you are using.

The first thing to say is we aren’t changing anything automatically. We are changing the OData schema so you may need to change your reports to ensure the schema changes do not break anything – even if you stick with ‘Daily’ – see this article for more information on best practices.

If you create a new PWA however, we do now set the default granularity as ‘Never’ so that you will need to make a conscious choice on the granularity you want – or leave it as ‘Never’ if you do not need time phased data (your publish times will be faster!)

I’ll walk through some scenarios, and I’ve also changed my regional site settings to make it more interesting – with my week starting on a Saturday and the first week of the year being defined as the First full week.

I’ll use a dummy project that I’ve created with work, costs, baselines etc. – just so we can see what happens to the data in various scenarios. This is my plan – with 3 work resources, a material resources, a cost resource and a budget cost resource.

With my new default (as I only created this PWA site this morning) of ‘Never’ for my timephasded data I find that I have no records in any of my timephased data sets. This is expected! I’m showing this in Excel – but you’d see the same just browsing to the OData endpoints under …/PWA/_api/ProjectData. I see 2 projects as it records the Timesheet administrative dummy plan too too – which also accounts for the 7th Task – and the 6 baselines are for the 6 tasks in this project. The TimeSet just records the days from 1984 to 2149, and will always be 60,631.

I’ll switch to Daily in my reporting granularity settings and republish and see what I see… and now I have some time phased data – and 828 rows in each of the feeds. This is a record for each day that has values – and in this snippet I see some costs, actual work and budget cost for one of my tasks.

Next I’ll take a look and see what weekly looks like…. and this gives me 120 records for each time phased data set. One record for each task for each week there is something to report. The records aren’t in exactly the same order – but you can seer the weeks that are totaling 120 and 80 are those with 16 and 24 hours per day. The dates the time shows against – such as 9/30/2017 – are Saturdays as that was the day I had set in my regional site settings as the First day of the week. I’ll come back to ‘week of the year’ later.

*** Update 11/30 - there is a slight change that will likely arrive before you see the feature - any roll-up such as weekly/monthly/fiscal periods - will record data against the FINAL date of the period rather than the FIRST. Currently as of 11/30 you will still be seeing 'FIRST' as per my screenshots ***

*** Update 12/5/2017 - back to Plan A - all aggregations will list against the FIRST date in the period - as per my screenshots ***

Next I’ll go to the Monthly option – and that is Monthly set in the reporting time phased granularity page and not using a Fiscal Period of Monthly. Here I just have 32 records in my time phased data sets (and they are only matching as I just have 1 assignments per task and the same durations for task/assignment) – with each data item being recorded against the 1st of the month – and we get to see all the rows in one view – with the project summary task being at the top.

Now stepping on to Fiscal Periods. Hey – where did my data go!

As it mentions in the Reporting configuration page – “I mportant: Reporting data will only be generated for defined fiscal periods. Also, if you change an existing fiscal period, you will need to republish all projects.” and as I have no defined periods (see above – my FiscalPeriods feed is empty) so I will need to go and create some. I’ll define 2017 first on its own to stress the point – and I’ll use the 4,5,4 method.

Now at this point I discovered a bug of sorts – fiscal periods need to be complete years, and the default for the 4,5,4 pattern leave 12/31 out on a limb… My Reporting (Project Publish) jobs went down a hole trying to work out what their calendar was and after an hour or so they failed. We are looking in to it and the fix is easy (once you know what caused the problem – I had a few variables in my plan and hadn’t noticed my year finished too soon). Not sure if we will address this, but now we are making more use of fiscal periods it might make sense to not allow an incomplete year to be defined. So once you define the 4,5,4 make sure the final period goes to 12/31- unless you are creating 2018 now too in which case you could start that on 12/31 – whatever works for you. This same issue can be seen if you don’t have Fiscal Periods defined for the complete duration of your plan – so for example in my case as my plan starts in October 2017 and finishes in March 2018 and my Fiscal Periods start in January – I need to create both the 2017 and 2018 Fiscal Period. I’m getting some confirmations of this, as the reporting page appears to indicate that you will only get data if you have defined the Fiscal Period – which to me meant that I could ‘choose’ not to create my Fiscal Period for 2018 if I was only interested in 2017 at the moment – so my publish would be quicker and I would use less space and reporting would be quicker (though only for 2017). However, currently projects will fail (after about an hour in my tests) at the Reporting (Project Publish) unless all the Fiscal Periods you need are created. I hope to hear that this is a bug.

*** Update 11/30 Confirmed as a bug and we have a fix coming - we will not fail if any missing dates or periods exist. For example if you only defined Fiscal Periods for 2017 and 2019 then a plan from 2017 to 2020 would only publish the details for 2017 and 2019. Not sure why you ever would - but that is a good way to describe the behavior you will see) ***

Back to the main story – I have my Fiscal Periods for 2017 and 2018 configured – complete with 12/31 for each year so I publish my project:

Now I see 31 rows – 1 fewer than my monthly based report as the pattern of the fiscal periods doesn’t quite match up to the monthly boundaries. I can see too that I have records coming from my Fiscal Period feed – and also see the Fiscal Period UID in my TaskTimePhasedDataSet for each row (Previously I just saw the NULL GUID (0000000000…).

Time to take a look at some of the other fields new with these changes and lets dive into the ‘Projects’ feed. We can see for the project which time phased granularity we have from the new field ProjectTimePhased – so this confirms that when this project was last published the granularity was set to ‘By Fiscal Period’. We cannot tell what the fiscal period configuration is, but looking at the TimeSet feed we could deduce that from the dates and fiscal periods.

Towards the end of the field list in the Projects feed we have some more new fields – and these relate to workflow and you can read more about these in the support document at https://lwal.me/4f . In my feed these are unpopulated and I am planning another blog posting where I’ll take a deeper look at these, but you will see that we now expose the WorkflowCreatedDate, WorkflowError, WorkflowResponseCode, WorkflowInstanceId, WorkflowOwnerId and WorkflowOwnerName.

With this information we hopefully make it much easier to spot any issues with workflows, and you (The PMO or helpdesk) will be able to proactively see what is happening to workflow across all of your projects rather than waiting for a project manager to come across a suspended or failed workflow. As I said – more on that in a future post.

So in summary the new options for reporting allow you to considerable reduce the amount of data you might need to access – by 25 times in my example, that is assuming that monthly totals is ok for you – or around 1/6 of the data if weekly is your thing. And the added benefit not just when reporting on the data but each time you publish too! You can change these at any time, but you would then need to re-publish all of your projects (or at least the ones you wanted to report on) – so you might also want to look at some kind of automated publish option such as using PowerShell or Javascript. You can search online for various articles on this – one of my favourites would be Paul Mather’s javascript example .

I’d love to hear back on how you find this works for you and which granularity is best in your scenario. Or do you think you might change? Maybe run with Never or Monthly and maybe switch to Daily and republish when you need the deeper granularity?

Project and Project Server November 2017 Updates Released

Project-Support — Wed, 06 Mar 2019 22:38:31 GMT

First published on TECHNET on Nov 16, 2017
This week the Public Update (PU) for Project Server 2013 and 2016 were released for November 2017 . Client updates were released on November 7th; server updates on November 14th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - as you will need a '2016' level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for November 2017 can be found here - https://support.microsoft.com/en-us/help/4051890/november-2017-updates-for-microsoft-office - November 2017 updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (but this month, as usual, the single patch comes in two parts... a wssloc and sts2016 part). - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: November 14, 2017- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4011244/descriptionofthesecurityupdateforsharepointserver2016november14-2017

November 14, 2017, update for SharePoint Server 2016 (KB4011243)- Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/4011243/november-14-2017-update-sharepoint-enterprise-server-2016-kb4011243

There is a database schema update this month - it changes to 16.0.4615.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4615.1000 can be used to control the connecting client to the November 2017 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
November 7, 2017, update for Project 2016 (KB4011227)

https://support.microsoft.com/en-us/help/4011227/november-7-2017-update-for-project-2016-kb4011227

The version of Project Professional 2016 will be updated to 16.0.4615.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.

Project and Project Server 2013
An overview of all the Office 2013 releases for November 2017 can be found here - https://support.microsoft.com/en-us/help/4051890/november-2017-updates-for-microsoft-office - November 2017, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server November PUs from the following articles:
Project Server 2013 Server Rollup Package
November 14, 2017, cumulative update for Project Server 2013 (KB4011249)

https://support.microsoft.com/en-us/help/4011249/november-14-2017-cumulative-update-for-project-server-2013-kb4011249

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: November 14, (KB4011257)

https://support.microsoft.com/en-us/help/4011257/description-of-the-security-update-for-project-server-2013-november-14

There is a database schema update this month - and the dbo.Versions table should show 15.0.4981.1002 *** Update 11/28/2017 - 15.0.4951.1000 apologies for any confusion – the Content DB version had been reported initially *** after applying the November 2017 PU. The version number 15.0.4951.1000 can be used to control the connecting client to the November 2017 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
November 7, 2017, update for Project 2013 (KB4011235)

https://support.microsoft.com/en-us/help/4011235/november-7-2017-update-for-project-2013-kb4011235

The client version number will be 15.0.4981.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4981.1000 value to control connection of the November 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project Online: More chocolate teapots

Brian Smith (CSS) — Mon, 02 Nov 2020 15:10:58 GMT

First published on TECHNET on Nov 01, 2017
I posted a while ago with the provocative title Project Lite: Without Project Online it is as much use as a chocolate teapot – and time to remind everyone that Project Essentials is that same chocolate teapot – you need to have ~~Project Online Professional and/or Project Online Premium~~ Project Plan 3 and/or Project Plan 5 to give you the Project Online PWA site – otherwise there is nothing for your team members (the only allowable users of Project Essentials licenses) to be members of…

I raise this now as we have seen some customers confused by the new licenses that were introduce just over a year ago. The Message Center post read like this (since then the Professional/Premium skus have been renamed Project Plan 3 and Project Plan 5):

Message:

Project Online and Project for Office 365 subscriptions are changing

Details:

On August 15, 2016, we introduced new plans for Project Online and Project for Office 365 customers. The new plans are similar but not identical to your current plan. [How does this affect me?] Our records indicate you are on one of the following plans which are affected: Project Lite Project Online Project for Office 365 Project Online with Project for Office 365 [What do I need to do to prepare for this change?] Between now and December 31st, 2016, you don’t need to do anything. You can continue to add seats, get updates, and renew your existing plan until then. On your first renewal date following December 31st, 2016, you’ll need to select a different Project Online plan. To find out more about the new Project Online plans and how they’ll affect your organization, click Additional Information.

Completed Action By:

None

Received by:

10/21/2016

Expiration Date:

12/31/2017

The support article for this item is here https://support.office.com/en-us/article/Important-information-for-Project-Online-customers-about-plan-changes-496aafdd-9f62-4daf-8d2e-0e700925c6b2?ui=en-US&rs=en-US&ad=US and I also did a blog post to explain it https://techcommunity.microsoft.com/t5/project-support-blog/project-online-how-to-handle-the-sku-changes/ba-p/362013

It appears that some customers were confused and did not follow the right path in renewing their Project Online or Project Online with Project Pro for Office 365 and instead just renewed everything with the cheapest option – Project Essentials. This does not give you a Project Online capability on its own. You need to purchase at least one Project Online Premium or Professional license to keep your PWA alive – and realistically you may need more of each to cover the usage of the product planned for your users such as project managers, portfolio managers, resource managers and administrators.

We are reviewing the messaging to see if we could be any clearer – but please take care when switching to the new skus.

P.S. Since this posting we have a new product - Project for the web - which is included with Project Plan 3/5 and has a new sku - Project Plan 1. In the future (around the end of 2020) this new sku will also include Project Essentials - but Project Essentials on its own DOES NOT give you access to Project for the web - the new web based product.

Project goes agile!

Brian Smith (CSS) — Wed, 06 Mar 2019 22:38:13 GMT

First published on TECHNET on Oct 30, 2017
*** Update 8/3/2018 - There have been some UI changes in this feature set - all functionality remains but names and navigation changed to aid use of these features - see https://support.office.com/en-us/article/use-task-boards-in-microsoft-project-online-desktop-client-1b9b44d7-fd8e-4b3b-ab94-2b97deb9945b#bkmk_makeyourprojectagile for details. ***

Today sees the announcement from the Project team of the new agile capabilities in the Project Online Desktop client, which, along with the recently released Planner integration gives project managers a broad choice of working style when managing their projects – using an agile approach with Scrum and Kanban, or a hybrid approach with these mixed in with the more traditional waterfall approach. For full details please see the blog post at https://blogs.office.com/en-us/2017/10/30/introducing-new-ways-to-work-in-microsoft-project/ and the “ Use agile in Microsoft Project ” feature article.

For more information on the Planner integration see “ Streamline cross-team work with the newly integrated Project Online Desktop Client and Microsoft Planner .”

Some of you will already have seen the agile capabilities if you are in the Office Insiders channel – and the features will be coming to our monthly targeted channel (aka first release) over the coming days, and then for our customers in the deferred channels you will see these features next year. We are also renaming our release channels – and what we had called Deferred will be called Semi-Annual channel – and you will see the features next July 2018, and the First Release for Deferred will be called Semi-Annual Channel (Targeted) and you will see the new features a few months earlier in March 2018.

Technically the best way to think of these new features is as a new set of templates, views and columns available to allow more flexible options for managing your projects. For example going to the normal Gantt chart view you can add the column ‘Agile' which is a Yes/No field. When set to ‘Yes’ then these tagged tasks will show if you switched over to one of the new agile views – Scrum or Kanban. Same tasks – just displayed in a different view. In the Scrum views you can set a task to be delivered in a specific sprint – in Kanban you would choose to categorize the task as Backlog, Next up, in progress – or your own categories. You can also show the columns such as the sprint or spring start/finish dates in the other project views – but be careful when looking at dates. If you are planning in scrum then best to use manually scheduled tasks and not use (or at least don’t show in your working view) the project start/end dates. The specific sprint has its own configured date range which isn’t tied to any of the scheduling dates. If you entered scheduled dates then these would not affect the sprint – likewise changing the sprint will not change the scheduled dates – hence the suggestion to keep with just one of the other.

One other support tip is for adding sprints – as this has raised a few questions with the early users. You do this via the Adjust Sprints option – where you can generate new sprints through to a custom date, for example – and here I’ve also changed a couple of the lengths to 3 weeks over the local holiday period at the end of the year.

One final point – this feature is only released for the Project Online Desktop Client – basically the client that comes with the Project Online Professional or Premium subscriptions – so you will not be getting these features with Project Professional 2016 (sometimes referred to as the perpetual license, or msi install product) or indeed Project Professional 2013. You will also not be able to use these features when connected to Project Server 2016 even if you are using the subscription client. As the server does not know how to handle the additional information in the plan we block the functionality unless you are just working with mpp files or are connected to Project Online.

A new Project Online Content Pack for Power BI

Brian Smith (CSS) — Wed, 06 Mar 2019 22:37:33 GMT

First published on TECHNET on Oct 26, 2017
*** Update 11/3 - non-English installation? scroll down to Raphael's comment where you will find some tips on getting this working ***

We are pleased to announce the release of a new Project Online Content Pack for Power BI. Starting October 26 2017, Project Online users will be able to download the new content pack directly from AppSource:

https://app.powerbi.com/groups/me/getdata/services/project-online

Comprising of 13 visually rich report pages, the new content pack is designed to support the management needs of project managers, portfolio managers and resource managers, by retrieving planning and execution data from Project Online and arranging the data to support timely decision making.

The new content pack report includes reports in three key perspectives: Individual Projects, Portfolio of projects and the organization’s resources. Each perspective encompasses the following detailed report pages.

Individual Projects – This perspective includes 2 report pages presenting information of a single project at a time:

· Project Status – A summary of a selected project including work and cost, over time, upcoming milestones and overall status.

· Project Risks and Issues – Issues and risks for a selected project.

Portfolio of Projects – This perspective includes 6 report pages offering multiple analysis angles on portfolio of projects:

· Portfolio Dashboard – At a glance summary of all your projects, including completion status and performance KPIs.

· Portfolio Timeline – An interactive timeline of projects in the portfolio, their planned start and finish dates as well as completion data.

· Portfolio Costs – A detailed report of the portfolio costs, with details on cost status for specific projects.

· Portfolio Milestones – Key milestones in the portfolio and their statuses.

· Portfolio Risks – Aggregated risks across the portfolio and their impact on the portfolio.

· Portfolio Issues – Aggregated issues across the portfolio and the causes for those issues.

Resource – This perspective includes 5 report pages:

· Resource Availability - Availability and demand for resources over time, presented through interactive heatmap and charts.

· Resource Overview – A view of all the resources in the portfolio and their detailed information.

· Resource Assignments – Deeper view into how resources are invested across the different projects in the portfolio, with information on their progress in current assignments.

· Resource Details – A summary of a selected resource including availability, assignments and work over time.

· Resource Demand Forecast – Forecast of demand for resource in upcoming time periods, based on current plans and predictive analytics.

How to set up the Content Pack

Go to this Power BI site to learn how to set up the Content Pack.

FAQs

Where can I find the new Content Pack?

The new Content Pack is available for download, directly from Power BI through ‘Get Data’.

The Content Pack is also available on AppSource and a PBIT file is shared through GitHub .

Will the new content pack replace the previous Project Online Content Pack?

Yes, the new content pack replaces the previous Project Online Content Pack. The new Content Pack offers a larger number of reports and leverages latest Power BI capabilities, for a richer analysis experience.

Project and Project Server October 2017 Updates Released

Project-Support — Wed, 06 Mar 2019 22:36:27 GMT

First published on TECHNET on Oct 16, 2017
Last week the Public Update (PU) for Project Server 2013 and 2016 were released for October 2017 . Client updates were released on October 3rd; server updates on October 10th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - as you will need a '2016' level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for October 2017 can be found here - https://support.microsoft.com/en-us/help/4043461/october-2017-updates-for-microsoft-office - October 2017, updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (but this month, as usual, the single patch comes in two parts... a wssloc and sts2016 part). - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: October 10, 2017- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4011217/security-update-for-sharepoint-enterprise-server-2016

October 10, 2017, update for SharePoint Server 2016 (KB4011161)- Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/4011161/october-10-2017-update-for-sharepoint-server-2016-kb4011161

There is a database schema update this month - it changes to 16.0.4600.1001. Remember, Project Server 2016 data is in the content database. The version number 16.0.4600.1001 can be used to control the connecting client to the October 2017 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
October 3, 2017, update for Project 2016 (KB4011141)

https://support.microsoft.com/en-us/help/4011141/october-3-2017-update-for-project-2016-kb4011141

The version of Project Professional 2016 will be updated to 16.0.4600.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.

Project and Project Server 2013
An overview of all the Office 2013 releases for October 2017 can be found here - https://support.microsoft.com/en-us/help/4043461/october-2017-updates-for-microsoft-office - October 2017, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server October PUs from the following articles:
Project Server 2013 Server Rollup Package
October 10, 2017, cumulative update for Project Server 2013 (KB4011175)

https://support.microsoft.com/en-us/help/4011175/october-10-2017-cumulative-update-for-project-server-2013-kb4011175

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

October 10, 2017, update for Project Server 2013 (KB4011182)

https://support.microsoft.com/en-us/help/4011182/october-10-2017-update-for-project-server-2013-kb4011182

There is a database schema update this month - and the dbo.Versions table should show 15.0.4971.1001 *** Update 11/28/2017 - 15.0.4951.1000 apologies for any confusion – the Content DB version had been reported initially *** after applying the October 2017 PU. The version number 15.0.4951.1000 can be used to control the connecting client to the October 2017 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
October 3, 2017, update for Project 2013 (KB4011156)

https://support.microsoft.com/en-us/help/4011156/september-5-2017-update-for-project-2013-kb4011156

The client version number will be 15.0.4971.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4971.1000 value to control connection of the October 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Streamline cross-team work with the newly integrated Project Online Desktop Client and Microsoft Planner

Brian Smith (CSS) — Wed, 06 Mar 2019 22:36:13 GMT

First published on TECHNET on Oct 05, 2017
We have a Guest Post today for the Project Support Blog – over to Yuval Stern to introduce the Project/Planner integration!

We are pleased to announce the release of the integration between the Project Online Desktop Client and Microsoft Planner. Starting September 2017, Project users will be able to connect Project tasks to Planner plans. The feature will be available in the September update for Project Online Professional and Premium customers.

This feature release is in response to our customers, who have asked for a way to connect tasks in Project to plans in Planner. We have found that, as project management processes extend across all parts of an organization, there is an opportunity to link the work done by disparate teams and drive greater cross-team alignment. This integration allows teams that manage their work in Project Online to better streamline work with teams that use Planner.

With the integration, task owners can track granular task details in a lightweight tool. Project Managers retain control over the project's work breakdown structure and can easily view the detailed work being done against a task.

This capability may also be used to reduce complexity of project plans in Project keeping it simple for the project manager to control a smaller number of tasks while task owners can further breakdown the tasks in Planner.

How does it work?

Step 1: Create a Planner plan.

Step 2: Create a project plan in Project Online and publish the plan with the task that needs to be connected to the Planner plan.

Step 3: Open the project plan with Project Online Desktop Client and focus on the task that needs to be connected, then press the new ‘Link to Planner’ button.

Step 4: Find the Planner plan you would like to connect the task with and create the link, by following the instruction on the left pane. Note that in this case the chosen Group is a Microsoft Team and has two plans added as channels from which to choose.

Step 5: The task in Project Online and the Planner plan are now connected. Click the Planner icon in the ‘Indicators’ field in Project Online Desktop Client to open the Planner plan. Note that users assigned to the task prior to the linking are added to the Planner plan.

FAQ

Is this feature available in the on-premises versions of Project, namely Project Professional and Project Standard?

The new integration capability is built for project collaboration scenarios and therefore is a natural extension for Project Online our solution in the cloud for collaborative Project and Portfolio Management (PPM). Therefore, the new Planner integration is only available as part of our Project Online offerings and adds another great subscription value.

How would I get this new capability?

To use this new capability, you would need to subscribe to either Project Online Professional or Project Online Premium. In addition, you would need to subscribe to Office 365 Business Essentials, Business Premium, E1-E5, and Education plans, which Microsoft Planner is a part of.

Can I use this feature in standalone (.mpp files) use of Project Online Desktop Client?

No, to use this feature a project manager using the Project Online Desktop Client, must be connected to a Project Online service to be able to publish the project plan.

Project Online: Setting Permissions in sites beyond PWA

Brian Smith (CSS) — Wed, 06 Mar 2019 22:35:39 GMT

First published on MSDN on Oct 03, 2017
Thanks goes to Paul Mather for most of the technical content of this particular post – as I’m taking a couple of his ideas and bringing them together. I'm using PowerShell to set permissions in project sites and using Flow and Azure Functions to automate running that PowerShell. I’ve also included a video that walks through this. The original recording was for an internal presentation – so I’ve edited it down a bit.

First I’ll introduce the scenario. With the recent announcement that Project Online can now support 30,000 projects this was in part achieved by now allowing sites for your projects to be created in site collections outside of the ‘PWA’ site collection. So in my example I have /sites/pwa as my main Project Web App site collection – but I can create sites in /sites/pwasites. The recommended limit for subsites in a site collection is 2000, and going beyond this does impact the performance of Project Online – and if you also have the SharePoint publishing features activated it can seriously impact every single page load in PWA. Expect some guidance from the product group shortly that suggests having no subsites at all in your PWA site! Limitations when you move sites to another site collection are that you no longer can synchronize permissions to the site based on the project stakeholders; you also cannot sync tasks to these sites – and you also must be in Project Permissions mode. This article looks to address the first of those.

Here is the video – but I’ll also talk this through in words further down and have the sample code so you can try this for yourselves.

https://www.youtube.com/watch?v=DTboqj4YHwI&feature=youtu.be

I broad terms I’m triggering a Flow on publish from Project Online, then writing some data to a Planner plan (unnecessary step – but shows how you might also write status during the process) and then hitting the Azure Function Url and passing in the PROJ_UID for the published project.- so the flow looks like this:

So the first part is monitoring my pwa for publishes, then if the Project Type is 0 (a normal project) it writes ProjectName, ProjectType and ProjectId to my PublishedProjects plan in my To do bucket and then makes the HTTP call:

This is making a POST to my Azure Function and passing in the body some json that contains the ProjectId.

First the PowerShell code in my Function reads this ProjectId from the incoming request, references the module it needs (which are also loaded into the Azure Function environment) and sets up the environment – including forming the OData Url to pull the ProjectName and ProjectWorkspaceInternalUrl for the specific project.

# POST method: $req
$requestBody = Get-Content $req -Raw | ConvertFrom-Json
$projID = $requestBody.projID

# GET method: each querystring parameter is its own variable
if ($req_query_name)
{
$projID = $req_query_name
}

#add SharePoint Online DLL - update the location if required
Import-Module "D:\Home\site\wwwroot\HttpTriggerPowerShell1\Microsoft.SharePoint.Client.dll"
Import-Module "D:\Home\site\wwwroot\HttpTriggerPowerShell1\Microsoft.SharePoint.Client.Runtime.dll"

#set the environment details
$PWAInstanceURL = " https://brismithpjo.sharepoint.com/sites/pwa"

$username = "brismith@brismithpjo.onmicrosoft.com"
$password = "<password>"
$securePass = ConvertTo-SecureString $password -AsPlainText -Force

#set the Odata URL to get the Workspace Url
$url = $PWAInstanceURL + "/_api/ProjectData/Projects()?`$Filter=ProjectId eq GUID'$projID'&`$Select=ProjectName, ProjectWorkspaceInternalUrl"

Once we have this set then the next stage is to call the Odata Url and get that data. I’m using a ForEach even though this will only return a single row – which makes the code re-usable in other scenarios too where you might be pulling more data. I get my name and site Url as variables and also use these to construct my group name that I will be adding my users to – which will fit the default SahrePoint group of <Projectname> Members. This assume that the project name is the same as the site name – be careful here as that may not be a safe assumption depending on character set and any special characters used.

#get all of the data from the OData URL
while ($url){
[Microsoft.SharePoint.Client.SharePointOnlineCredentials]$spocreds = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($username, $securePass);
$webrequest = [System.Net.WebRequest]::Create($url)
$webrequest.Credentials = $spocreds
$webrequest.Accept = "application/json;odata=verbose"
$webrequest.Headers.Add("X-FORMS_BASED_AUTH_ACCEPTED", "f")
$response = $webrequest.GetResponse()
$reader = New-Object System.IO.StreamReader $response.GetResponseStream()
$data = $reader.ReadToEnd()
$results = ConvertFrom-Json -InputObject $data
$results1 += $results.d.results
if ($results.d.__next){
$url=$results.d.__next.ToString()
}
else {
$url=$null
}
}

#for each project, create the list item - update the newitem with the correct list columns and project data
foreach ($projectrow in $results1)
{
$projectSiteURL = $projectrow.ProjectWorkspaceInternalUrl
$groupName = $projectrow.ProjectName + " Members"
}

Next I’m checking the site Url to see if this is in my pwasites site collection – as these are the only ones I’m interested in. One thought I had was trying to make this differentiation in Flow and not even calling the function if I don’t need it – you can take that as homework. For those projects whose site is in pwasites I then make a REST call to the ProjectServer endpoint to get the Ids of the resources in the project. For each team member I then get their account and name from Odata – making sure I’m only getting ones that actually have a ResourceNTAccount – so taking my @team array and filtering down to a @teamusers array of ones that have accounts so I can add them to the SharePoint site. The final step is making a SharePoint CSOM call adding my users to the group.

#Filter only for projects that are external - if $projectSiteURL contains pwasites
if ($projectSiteURL -like '*pwasites*'){

#get all of the team members - will include resources that are not users too.
$team = @()

#set the REST URL project
$url = $PWAInstanceURL + "/_api/ProjectServer/Projects('$projID')/ProjectResources()?`$Select=Id"

#get all of the data from the REST URL for the Project Team
while ($url){
[Microsoft.SharePoint.Client.SharePointOnlineCredentials]$spocreds = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($username, $securePass);
$webrequest = [System.Net.WebRequest]::Create($url)
$webrequest.Credentials = $spocreds
$webrequest.Accept = "application/json;odata=verbose"
$webrequest.Headers.Add("X-FORMS_BASED_AUTH_ACCEPTED", "f")
$response = $webrequest.GetResponse()
$reader = New-Object System.IO.StreamReader $response.GetResponseStream()
$data = $reader.ReadToEnd()
$results = ConvertFrom-Json -InputObject $data
$team += $results.d.results
if ($results.d.__next){
$url=$results.d.__next.ToString()
}
else {
$url=$null
}
}

#get all of the team members login accounts and remove resources that are not users in PWA.
$teamusers = @()

Foreach ($teammember in $team)
{
#set the resource ID
$teammemberID = $teammember.Id

#set up the Odata URL
#$url = $PWAInstanceURL + "/_api/ProjectServer/EnterpriseResources('$teammemberID')/User?`$Select=LoginName,Id" #alternative to OData
$url = $PWAInstanceURL + "/_api/ProjectData/Resources()?`$Select=ResourceNTAccount,ResourceName&`$Filter=ResourceId eq guid'$teammemberID' and ResourceNTAccount ne null"

#get all of the data from the OData URL for the project team members that are users in PWA
[Microsoft.SharePoint.Client.SharePointOnlineCredentials]$spocreds = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($username, $securePass);
$webrequest = [System.Net.WebRequest]::Create($url)
$webrequest.Credentials = $spocreds
$webrequest.Accept = "application/json;odata=verbose"
$webrequest.Headers.Add("X-FORMS_BASED_AUTH_ACCEPTED", "f")
$response = $webrequest.GetResponse()
$reader = New-Object System.IO.StreamReader $response.GetResponseStream()
$data = $reader.ReadToEnd()
$results = ConvertFrom-Json -InputObject $data
$teamusers += $results.d.results
}

#add the user to the project site
Foreach ($teamuser in $teamusers)
{
$teamuserLogin = $teamuser.ResourceNTAccount
$teamusername = $teamuser.ResourceName

#get SP site client context
$ctx = New-Object Microsoft.SharePoint.Client.ClientContext($projectSiteURL)
$credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($username, $securePass)
$ctx.Credentials = $credentials

#get all the site groups on the Project Site
$projSiteGroups = $ctx.Web.SiteGroups
$ctx.Load.($projSiteGroups)

#get the correct group to add the user into
$projSiteGroup = $projSiteGroups.GetByName($groupName)
$ctx.Load($projSiteGroup)

#add the user to the group on the Project Site
$projSiteUser = $ctx.Web.EnsureUser($teamuserLogin)
$ctx.Load($projSiteUser)
$teamMemberToAdd = $projSiteGroup.Users.AddUser($projSiteUser)
$ctx.Load($teamMemberToAdd)
$ctx.ExecuteQuery()
}
}

To test your function you can manually give it the project GUID of a known project with a site in your 'pwasites' site - simply using the json format:

{
"projID": "77c4992f-562f-e711-80d3-00155de84000"
}

And once tested and working then use the Url for your function in the Flow HTTP step. Get function Url is a link at top right of your Azure function editing page.

You could probably use Azure Automation for this too as I’m using PowerShell – and run this on a timer rather than triggered by Flow. Really depends on your requirements. I’ve also simplistically added all users to members, but you could potentially do a more granular setting of permissions and add to other group. Subsequent publishes will add new users – but I don’t handle removing users who no longer have access.

Thanks again to Paul Mather – and these are his blog posts that inspired this post and video.

https://pwmather.wordpress.com/2017/07/07/projectonline-project-user-sync-to-project-sites-ppm-o365-powershell-sharepoint/

https://pwmather.wordpress.com/2017/07/28/running-projectonline-powershell-in-azure-using-azurefunctions-ppm-cloud-flow-logicapp-part1/

https://pwmather.wordpress.com/2017/08/01/running-projectonline-powershell-in-azure-using-azurefunctions-ppm-cloud-flow-logicapp-part2/

Project and Project Server September 2017 Updates Released

Project-Support — Wed, 06 Mar 2019 22:35:11 GMT

First published on TECHNET on Sep 14, 2017
This week the Public Update (PU) for Project Server 2013 and 2016 were released for September 2017 . Client updates were released on September 5th; server updates on September 12th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - as you will need a '2016' level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for September 2017 can be found here - https://support.microsoft.com/en-us/help/4040279/september-2017-updates-for-microsoft-office - September 2017, updates for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (but this month, as usual, the single patch comes in two parts... a wssloc and sts2016 part). - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: September 12, 2017- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4011127/descriptionofthesecurityupdateforsharepointserver2016september12-2017

September 12, 2017, update for SharePoint Server 2016 (KB4011112)- Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/4011112/september-12-2017-update-for-sharepoint-server-2016-kb4011112

There is a database schema update this month - it changes to 16.0.4588.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4588.1000 can be used to control the connecting client to the September 2017 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
September 5, 2017, update for Project 2016 (KB4011101)

https://support.microsoft.com/en-us/help/4011101/september-5-2017-update-for-project-2016-kb4011101

The version of Project Professional 2016 will be updated to 16.0.4588.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.

Project and Project Server 2013
An overview of all the Office 2013 releases for September 2017 can be found here - https://support.microsoft.com/en-us/help/4040279/september-2017-updates-for-microsoft-office - September 2017, updates for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server September PUs from the following articles:
Project Server 2013 Server Rollup Package
September 12, 2017, cumulative update for Project Server 2013 (KB4011115)

https://support.microsoft.com/en-us/help/4011115/september-12-2017-cumulative-update-for-project-server-2013-kb4011115

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

September 12, 2017, update for Project Server 2013 (KB4011118)

https://support.microsoft.com/en-us/help/4011118/september-12-2017-update-for-project-server-2013-kb4011118

There is a database schema update this month - and the dbo.Versions table should show 15.0.4963.1000 *** Update 11/28/2017 - 15.0.4951.1000 apologies for any confusion – the Content DB version had been reported initially ***after applying the September 2017 PU. The version number 15.0.4951.1000 can be used to control the connecting client to the September 2017 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
September 5, 2017, update for Project 2013 (KB4011109)

https://support.microsoft.com/en-us/help/4011109/september-5-2017-update-for-project-2013-kb4011109

The client version number will be 15.0.4963.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4963.1000 value to control connection of the September 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project Online: How to interpret common workflow errors

Brian Smith (CSS) — Wed, 06 Mar 2019 22:35:04 GMT

First published on TECHNET on Aug 25, 2017

Running workflows in Project Online involves plenty of moving parts and many configuration options that might affect how workflows flow – or maybe stop flowing. In this blog I aim to try and demystify some of the processes involved and help you understand why workflows may get suspended – and quite often it isn’t anything to do with any failure in our service. That’s not to say I am blaming customers – as we don’t make it at all easy to understand what happened – or why. We are working on that part – but for now…

If you are familiar with workflows and want to cut to the chase – scroll down a yard or so (just past the Excel screenshot) to get to where I start talking about the errors.

First lets cover where you can see status on workflows. From the main project workflow page itself, you can see the phase, stage and any workflow stage status that has been set through your workflow. In this case I’m not showing any specific stage status – but it is a good idea to put something here to let your users know what is going on – and maybe what it might be waiting for. Expanding the All Workflow Stages section as I have done here gives a broader view of where you are. Assuming you have the right permission level – you will see an option at the bottom right corner to see Additional Workflow Data:

Clicking the Additional Workflow Data option takes you to the next screen – and you will see any status information written to the workflow history list – and the internal status. If you are troubleshooting you might see the Internal Status show as suspended – and in my case this workflow would finally end up getting suspended after finishing the retries – as we can see the status under the information icon next to ‘Started’ in the subsequent screenshot.

You can also get to workflow status from Site Settings, Site Workflows and Show all workflows.

Unfortunately the page of workflows it shows are just displayed by workflow and have no direct project context – but you will be able to see which ones are suspended:

Another way you can get at workflow data is via odata – using _api/ProjectData/ProjectWorkflowStageDataSet added to your PWA Url. Here is a an Excel sheet I’ve created populated from that feed on my server, and I filtered the StageStatus down to just see errors and waiting – and some of the waiting ones would fail eventually – but I’m impatient…:

So that’s some background on where you can find status – so lets start with some common errors you might see – you may see these where a workflow goes into a suspended state – or you might see it in the interim when it is still going through a number of retries as above – but you see something like this if you view the workflow status. All of these would end up suspended after all the retires – unless the condition was rectified before the retry cycle completed:

The underlying cause of each of these errors was a permission problem with the account that was running the workflow. I can’t guarantee which error you might see in every scenario – as it is really a combination of the specific permission issue and the action the workflow is attempting. But which user account has the issue and is having their access denied?

When a project is created the workflow is kicked off using a token from the logged in user – and it continues to run in the context of that user until it completes – or for some reason fails. It still keeps this same user context even if the project owner changes! Things that can happen to induce a failure are lack of the right permissions to start with – and the last example fits this scenario – and it was the PDP that was triggering the ‘403’. This is fairly easy as it is usually obvious who is running the workflow if it fails right away. But what if the user who started the workflow leaves the company and becomes inactive? This can give rise to the Forbidden: Access Denied, and InternalServerError: GeneralSecurityAccessDenied messages. Restarting the workflows will resolve this issue. Another example I have seen is when the account that is running the workflow loses some permissions – maybe they changed from Project Manager to Team Member – or perhaps the category they were in was updated with more limited access (permissions or even projects!). The same two messages will appear, depending on the actions happening in the workflow.

How about this one?

Here we can see a little more information than the others. The workflow is reading some DateTime field and having a problem. We can see a propertyid referenced - '21af92c1-a389-e711-80c8-00155de44f0a' – and generally these will be referencing custom fields – usually at the project level. A quick way I tend to use for finding which custom field has that GUID is to use View Source on the Custom Field and Lookup Table page and search for the GUID. Here we can see I tracked it down to ProjDate:

In my workflow I was reading that date and setting a variable – but as the date hadn’t been set a NullReferenceException was thrown – which led to the InternalServerError that you see in the workflow. In this case ensuring that the date will have a value before reading it will avoid the problem.

The examples above are in most respects in the customers control – although if you weren’t aware that the user who started the workflow was still running it this probably wasn’t something you’d have considered. But we are looking to see if we can improve the experience here – so watch this space. We are also seeing if we can better deliver the true cause of the problem to ensure the errors are more actionable – and that you can tell if it is something you can resolve by just restarting or if you need to log a call as it is something broken on our end. An example of this you may have seen recently was this error:

RequestorId: 2d852b8a-41ad-5d86-0000-000000000000. Details: System.InvalidOperationException: Incomplete closure detected while loading subroutines for workflow 66149d57-9e52-4a69-970d-2324e6132ec1 in scope .

And explaining how the fix for this rolls out may help understand why you may sometimes continue to see things that we say we have fixed. The workflow team addressed this quite a while back – and they have some automated processes that also fix up the running (in most cases waiting or sleeping is a better description) workflow that may have the old copy of this code. To complicate this issue the automated process had some problems – so customers continued to see the problem way too long after it was fixed. We should be getting up to date with this fix – and again, a restart would have achieved the same result – getting the latest version of the code.

Hopefully this will help understand some of the mystery of suspended workflows and enable you to pick out which might need a case to resolve. I’ll be posting again when we have some news on better actionable errors and workflow handling.

For the search engines here is the text from the error screenshots above:

Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP InternalServerError to https://brismithpjo.sharepoint.com/sites/pwa/_api/ProjectServer/WorkflowActivities/ReadDateTimeProperty(projectId='ab3e700f-d789-e711-80d9-00155de43c08',propertyId='21af92c1-a389-e711-80c8-00155de44f0a') Correlation Id: a7da1060-9fbd-8fe0-82e6-678a0b0a2b6e Instance Id: 99d1d76b-daf2-45b2-9489-c9abdb7cce69

Retrying last request. Next attempt scheduled after 8/25/2017 4:11 PM. Details of last request: HTTP InternalServerError to https://brismithpjo.sharepoint.com/sites/pwa/_api/ProjectServer/WorkflowActivities/ReadyToLeaveProjectStage(projectId='4c4532af-b289-e711-80ce-00155de4880e') Correlation Id: a7da1060-9fbd-8fe0-a513-0efff7b5357b Instance Id: fc8f01bd-cb49-4cdc-9ed1-f53dff2d640f
ProjectServerError(s) LastError=GeneralSecurityAccessDenied Instructions: Pass this into PSClientError constructor to access all error information

Retrying last request. Next attempt scheduled after 8/25/2017 6:10 PM. Details of last request: HTTP Forbidden to https://brismithpjo.sharepoint.com/sites/pwa/_api/ProjectServer/WorkflowActivities/ReadyToLeaveProjectStage(projectId='1627a7c1-ad89-e711-80de-00155de42a0d') Correlation Id: a7da1060-9fbd-8fe0-8554-9c3f3931dc99 Instance Id: 7620f076-f706-4692-80d3-6d02a75f9fff
Access denied. You do not have permission to perform this action or access this resource.

RequestorId: 9e975a9a-2037-bbfa-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 403 {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"X-MSDAVEXT_Error":["917656; Access+denied.+Before+opening+files+in+this+location%2c+you+must+first+browse+to+the+web+site+and+select+the+option+to+login+automatically."],"X-SP-SERVERSTATE":["ReadOnly=0"],"DATASERVICEVERSION":["3.0"],"SPClientServiceRequestDuration":["74"],"SPRequestDuration":["142"],"SPRequestGuid":["9e975a9a-2037-bbfa-95aa-aa690c69f8a2"],"request-id":["9e975a9a-2037-bbfa-95aa-aa690c69f8a2"],"Strict-Transport-Security":["max-age=31536000"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["16.0.0.6809"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1; RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Fri, 18 Aug 2017 09:33:41 GMT"],"P3P":["CP=\"ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI\""],"Server":["Microsoft-IIS\/8.5"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]} at System.Activities.Statements.Throw.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation) Exception from activity Throw If Sequence Sequence TryCatch Sequence Microsoft.SharePoint.WorkflowServices.Activities.RetryForDurationPolicy HttpPost Sequence Microsoft.Office.Project.Server.WorkflowActivities.EnterProjectStage Sequence Flowchart Sequence BSTest.WorkflowXaml_f9e81a98_8151_4254_a524_eab9f8e99079

Project and Project Server August 2017 Updates Released

Project-Support — Wed, 06 Mar 2019 22:32:59 GMT

First published on TECHNET on Aug 09, 2017
Yesterday the Public Update (PU) for Project Server 2013 and 2016 were released for August 2017 . Client updates were released on August 1st; server updates on August 8th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - as you will need a '2016' level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for August 2017 can be found here - https://support.microsoft.com/en-us/help/4036121/august-8-2017-update-for-microsoft-office - August 8, 2017, update for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (but this month, as usual, the single patch comes in two parts... a wssloc and sts2016 part). - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

August 8, 2017, update for SharePoint Server 2016 (KB4011049)- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/4011049/august-8-2017-update-for-sharepoint-server-2016-kb4011049

August 8, 2017, update for SharePoint Server 2016 (KB4011053)- Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/4011053/august-8-2017-update-for-sharepoint-server-2016-kb4011053

There is a database schema update this month - it changes to 16.0.4573.1000. Remember, Project Server 2016 data is in the content database. The version number 16.0.4573.1000 can be used to control the connecting client to the August 2017 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
August 1, 2017, update for Project 2016 (KB4011034)

https://support.microsoft.com/en-us/help/4011034/august-1-2017-update-for-project-2016-kb4011034

The version of Project Professional 2016 will be updated to 16.0.4573.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.

Project and Project Server 2013
An overview of all the Office 2013 releases for August 2017 can be found here - https://support.microsoft.com/en-us/help/4036121/august-8-2017-update-for-microsoft-office - August 8, 2017, update for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server August PUs from the following articles:
Project Server 2013 Server Rollup Package
August 8, 2017, cumulative update for Project Server 2013 (KB4011074)

https://support.microsoft.com/en-us/help/4011074/august-8-2017-cumulative-update-for-project-server-2013-kb4011074

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

August 8, 2017, update for Project Server 2013 (KB4011082)

https://support.microsoft.com/en-us/help/4011082/august-8-2017-update-for-project-server-2013-kb4011082

There is a database schema update this month - and the dbo.Versions table should show 15.0.4953.1000 *** Update 11/28/2017 - 15.0.4951.1000 apologies for any confusion – the Content DB version had been reported initially ***after applying the August 2017 PU. The version number 15.0.4951.1000 can be used to control the connecting client to the August 2017 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
August 1, 2017, update for Project 2013 (KB4011084)

https://support.microsoft.com/en-us/help/4011084/august-1-2017-update-for-project-2013-kb4011084

The client version number will be 15.0.4953.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4953.1000 value to control connection of the August 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project and Project Server July 2017 Updates Released

Project-Support — Wed, 06 Mar 2019 22:32:53 GMT

First published on TECHNET on Jul 12, 2017
Yesterday the Public Update (PU) for Project Server 2013 and 2016 were released for July 2017 . Client updates were released on July 11th and 5th respectively; server updates on July 11th. Typically the client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates - just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 - see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported - see the Lifecycle site for more information - http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential - this month both SharePoint Server 2016 and 2013 fixes have security fixes - so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013).

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online - see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ - as you will need a '2016' level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to 'normal' install times now (I patched both my 2013 and 2016 systems in a couple of hours) - but leaving this comment here just in case... One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don't have the 'right' SP1. Slipstream would work with the original SP1 - but the updates require the re-released SP1. Since the May PU this shouldn't be an issue - but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed -this is fixed by applying the April 2013 or later- so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn't already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for July 2017 can be found here - https://support.microsoft.com/en-us/help/4033107/july-11-2017-update-for-microsoft-office - July 11, 2017, update for Microsoft Office
Project Server 2016
With the 2016 release, we just have a single patch (but this month, as usual, the single patch comes in two parts... a wssloc and sts2016 part). - as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: July 11, 2017- Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/3213544/descriptionofthesecurityupdateforsharepointserver2016july11,2017

July 11, 2017, update for SharePoint Server 2016 (KB3213543) - Can include Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/3213543/july-11-2017-update-for-sharepoint-server-2016-kb3213543

There is a database schema update this month - it changes to 16.0.4561.1000 - or will get updated to this if you hadn't patched in June. Remember, Project Server 2016 data is in the content database. The version number 16.0.4561.1000 can be used to control the connecting client to the July 2017 level. For reference - the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
July 5, 2017, update for Project 2016 (KB3203476 )

https://support.microsoft.com/en-us/help/3203476/july-5-2017-update-for-project-2016-kb3203476

The version of Project Professional 2016 will be updated to 16.0.4561.1000 in the properties for WinProj.exe. In 2016 we don't do a good job of displaying the version in File, Account, About Project - we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe - in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the '16' level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area - Current Branch for Business is now called Deferred Channel. We are aware that we don't appear to expose the full change details for Project and are looking into it - you should start seeing more here soon.

Project and Project Server 2013
An overview of all the Office 2013 releases for July 2017 can be found here - https://support.microsoft.com/en-us/help/4033107/july-11-2017-update-for-microsoft-office - July 11, 2017, update for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server July PUs from the following articles:
Project Server 2013 Server Rollup Package
J uly 11, 2017, cumulative update for Project Server 2013 (KB3213566)

https://support.microsoft.com/en-us/help/3213566/july-11-2017-cumulative-update-for-project-server-2013-kb3213566

Project Server 2013 Individual Project Package - (cumulative, but only the Project Server fixes):

July 11, 2017, update for Project Server 2013 (KB3213577)

https://support.microsoft.com/en-us/help/3213577/july-11-2017-update-for-project-server-2013-kb3213577

There is a database schema update this month - and the dbo.Versions table should show 15.0.4945.1000 after applying the July 2017 PU. The version number 15.0.4945.1000 can be used to control the connecting client to the July 2017 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here - https://support.microsoft.com/help/2880553
Project 2013 Client Package:
July 11, 2017, update for Project 2013 (KB3213538)

https://support.microsoft.com/en-us/help/3213538/july-11-2017-update-for-project-2013-kb3213538

The client version number will be 15.0.4945.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4945.1000 value to control connection of the July 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See https://blogs.technet.microsoft.com/projectsupport/2013/09/16/project-server-2013-controlling-the-version-of-connecting-clientsand-pwa-edits/ for more details. As mentioned above - the version number entered no longer controls the server side scheduling engine - so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here - https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project Online: Keeping your eye on the Message Center

Brian Smith (CSS) — Wed, 06 Mar 2019 22:32:47 GMT

First published on TECHNET on Jun 19, 2017

I posted last week about the client update requirements - Project Online- Two weeks to go–upgrade your Project client! and today there is another announcement that is important for Project Online (more further down this posting) but it got me thinking about how you can keep informed of these changes if you are not an Office 365 administrator. In the Message center there is an link to preferences:

Clicking takes you to this page where you can choose to get weekly e-mail digests of the messages (SharePoint – which includes the Project messages – is listed when you click MORE).

Knowing that these options are available you can go to your Office 365 administrator and ask if your e-mail address could be added. If they say no, then I’d suggest you ask that they create an Outlook rule so that whenever they receive the weekly digest and it contains the word ‘Project’ that it gets forwarded to you. Hopefully one or other of those options will be acceptable to them and will keep you and your PMO team up to date with changes coming down the pipeline.

From the top screenshot you can probably see MC106623 which is our early notice of an API change in oData due to a new feature – and this should be going live by September 18th. I’ll be doing a longer blog post giving more details later – but here is the Message Center posting and the Additional Information link will take you to the support article on this change. To be clear you get to choose just one rollup timescale – or none. You don’t get to keep the daily if you choose to switch to weekly for example.

Updated feature: Project Online Rollup of Task and Assignment Timephased Data

MC106623

Published On : June 19, 2017

Expires On : October 31, 2017

Action required by September 18, 2017

We have added the ability for a PWA admin to set how to rollup task and assignment timephased data. We now support weekly, monthly, by fiscal period timephased units, as well as the previously supported by day grouping.

How does this affect me?

If you choose to use this new option, you may benefit from simplified report building, reduced storage requirements, and improved report generation performance. However, existing reports that make use of the following entities could be impacted by this change: - AssignmentBaselineTimephasedDataSet - AssignmentTimephasedDataSet - TaskBaselineTimephasedDataSet - TaskTimephasedDataSet You can also choose not to generate the rollup task and assignment timephased data by selecting the "Never" option. We'll be gradually rolling this out in September, and the rollout will be completed by the end of October.

What do I need to do to prepare for this change?

Please review any reports that make use of the task and assignment by day information from the Project Online OData service once this feature is available to your organization. If your reports are rolling up timephased task and assignment data by one of the following new units: weekly, monthly, or by fiscal period, we recommend updating your reports to take advantage of the rollups for better performance. If you have an app that queries all the properties without specifying the property names, it may be impacted by this change. We recommend you set the apps query for specific properties. Please click Additional Information to learn more.

Additional information

Project Online: Two weeks to go–upgrade your Project client!

Brian Smith (CSS) — Wed, 06 Mar 2019 22:32:10 GMT

First published on TECHNET on Jun 15, 2017

30th June 2017 is just a couple of weeks away – so please be sure you have upgraded either to Project Professional 2016 or are running the subscription model and are actively updating to at least the deferred channel. Although RTM is acceptable for Project Professional 2016 you should consider patching to a more recent update. A list of the fixes we have made from the initial release to June 2017 can be found at https://blogs.technet.microsoft.com/projectsupport/project-2016-public-updates/ .

If you are still running Project 2013 then you will not be able to connect to Project Online once this deadline passes. As mentioned recently for the site creation changes – the Message Center is the place to learn about this and other changes. This or a previous version has been posted since 19th August 2016 – so you have had plenty of time – don’t leave it any longer!

This won’t affect you if you just use Project 2013 and don’t connect to Project Online – but the upgrade is worth considering anyway.

Project and Project Server June 2017 Updates Released

Brian Smith (CSS) — Wed, 06 Mar 2019 22:31:46 GMT

First published on TECHNET on Jun 14, 2017

Yesterday the Public Update (PU) for Project Server 2013 and 2016 were released for June 2017 . Client updates were released June 6th and server updates on June 13th. The client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

There was a Project Server 2010 Cumulative update package released this month but it did not contain any Project updates – just the SharePoint ones. Mainstream support for Project and Project Server 2010 ended October 13, 2015 – see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported – see the Lifecycle site for more information – http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential – this month both SharePoint Server 2016 and 2013 fixes have security fixes – so some may have come down via the update center). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013.

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We may have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online – see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ – as you will need a ‘2016’ level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to ‘normal’ install times now (I patched both my 2013 and 2016 systems in a couple of hours) – but leaving this comment here just in case… One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don’t have the ‘right’ SP1. Slipstream would work with the original SP1 – but the updates require the re-released SP1. Since the May PU this shouldn’t be an issue – but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed – this is fixed by applying the April 2013 or later– so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn’t already load the April 2013 through June 2014 CU).

Project and Project Server 2016

An overview of all the Office 2016 releases for June 2017 can be found here – https://support.microsoft.com/en-us/help/4023935/june-13-2017-update-for-microsoft-office – June 13, 2017, update for Microsoft Office

Project Server 2016

With the 2016 release, we just have a single patch (but this month, as usual, the single patch comes in two parts… a wssloc and sts2016 part). – as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the configuration wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: June 13, 2017 – Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/3203432/descriptionofthesecurityupdateforsharepointserver2016june13,2017

June 13, 2017, update for SharePoint Server 2016 (KB3203433) – Can includes Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/3203433/june-13-2017-update-for-sharepoint-server-2016-kb3203433

There is a database schema update this month – it changes to 16.0.4549.1001 – or will get updated to this if you hadn’t patched in May. Remember, Project Server 2016 data is in the content database. The version number 16.0.4549.1000 can be used to control the connecting client to the June 2017 level. For reference – the RTM build number seen for the DB schema would be 16.0.4327.1000.

Project 2016 Client Package:

June 6, 2017, update for Project 2016 (KB3191934 )

https://support.microsoft.com/en-us/help/3191934/june-6-2017-update-for-project-2016-kb3191934

The version of Project Professional 2016 will be updated to 16.0.4549.1000 in the properties for WinProj.exe. In 2016 we don’t do a good job of displaying the version in File, Account, About Project – we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe – in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the ‘16’ level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area – Current Branch for Business is now called Deferred Channel. We are aware that we don’t appear to expose the full change details for Project and are looking into it – you should start seeing more here soon.

Project and Project Server 2013

An overview of all the Office 2013 releases for June 2017 can be found here – https://support.microsoft.com/en-us/help/4023935/june-13-2017-update-for-microsoft-office – June 13, 2017, update for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server June PUs from the following articles:

Project Server 2013 Server Rollup Package

June 13, 2017, cumulative update for Project Server 2013 (KB3203429)

https://support.microsoft.com/en-us/help/3203429/june-13-2017-cumulative-update-for-project-server-2013-kb3203429

Project Server 2013 Individual Project Package – (cumulative, but only the Project Server fixes – and contains security fixes this month):

Description of the security update for Project Server 2013: June 13, 2017

https://support.microsoft.com/en-us/help/3203399/descriptionofthesecurityupdateforprojectserver2013june13,2017

There is a database schema update this month – and the dbo.Versions table should show 15.0.4937.1000 after applying the June 2017 PU. The version number 15.0.4937.1000 can be used to control the connecting client to the June 2017 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here – https://support.microsoft.com/help/2880553

Project 2013 Client Package:

June 6, 2017, update for Project 2013 (KB3191941)

https://support.microsoft.com/en-us/help/3191941/june-6-2017-update-for-project-2013-kb3191941

The client version number will be 15.0.4937.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4937.1000 value to control connection of the June 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See Project Server 2013- Controlling the version of connecting clients–and PWA edits- for more details. As mentioned above – the version number entered no longer controls the server side scheduling engine – so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here – https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.
Extract the patch package by running the .exe file that you downloaded.
Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project Online: What happened to my site creation settings?

Brian Smith (CSS) — Wed, 06 Mar 2019 22:31:34 GMT

First published on TECHNET on Jun 12, 2017

To use a Douglas Adams reference I sometimes feel like a Vogon telling customers that they should have known about stuff because it was posted to the Message Center. For many of our PMO folks who are not Office 365 Administrators they have more chance of getting to Alpha Centauri… But I digress, and even if you had seen the message center post it didn’t do a great job of explaining everything. What did happen to the site creation settings?

The first information behind this change was in a blog post that talked about the extension of the limits of the number of projects we support in a PWA instance in Project Online. One aspect of this was the support for sites outside of the PWA site collection – and the ability to use specific settings in an Enterprise Project Type (EPT) to set where a site should get created (and even if it should get created). The ‘where’ part is only available if you are using Project Permission Mode. What wasn’t explained was that the existing place where you had made the setting was going away. It was in the header for the Connected SharePoint Sites.

And when you clicked on it the settings options looked like this:

With the change to being able to set these values at the EPT level this was removed and instead you need to navigate to each EPT and make the setting there.

There is a new section within the EPT settings once you open up the EPT where the Site Creation options can be configured. If you don’t see the ‘Location’ part then you are probably in SharePoint Permissions mode and you don’t have the option to create in other site collections.

This is giving you the same options as before – but adds the flexibility to specify by EPT as well as choose other site collections to create your sites – thus spreading the project sites around and being able to reach the 30,000 project limit even if you need sites for each project. If you do choose a different site collection then you can’t sync user permissions or tasks lists either.

If that had all gone to plan you may not have noticed much (apart for the setting being gone from Connected SharePoint Sites) – but we did have an initial bug that was causing sites to not get created – which then raised the further questions of “what just happened”. The expiry of the original Message Center post has been extended and we will be updating the link to point to this blog post. Sorry for the confusion around this change – and we are learning for the next changes.

Two other useful links to give more context here – the support document for Enterprise Project Types - https://support.office.com/en-us/article/Enterprise-Project-Types-C576DE02-A25C-4EA1-9DE6-02BE44DBB0A6 and the support document for tuning Project Online performance https://support.office.com/en-us/article/Tune-Project-Online-performance-12ba0ebd-c616-42e5-b9b6-cad570e8409c .

Always a good idea to talk to your Office 365 administrator and let them know that you need to know about any notifications for Project Online changes. To see the Message center they need to go to the Admin tile in Office 365 and then under Health they will see Service health (where any known current issues should be posted) and Message center, where we post announcements. These can fall into different categories as the screenshot shows. You click on a row to get more details. The link in the Message center pane takes you here .

And while I’m here you might want to keep an eye out for another Message that will land soon concerning options to change the way time-phased data is presented – and allowing daily, weekly, monthly or fiscal period roll-ups instead of just daily. The initial posting is just a heads up on the change as it may require you to update your Odata reports – and I’ll be posting more details in a couple of months when that feature gets closer to being turned on.

I could finish as a Vogon too – and read you some poetry perhaps? Maybe not.

Project and Project Server May 2017 Updates Released

Brian Smith (CSS) — Wed, 06 Mar 2019 22:30:30 GMT

First published on TECHNET on Jun 06, 2017

Sorry for the delayed posting – vacation time! Public Update (PU) for Project Server 2013 and 2016 were released for May 2017 . Client updates were released May 2nd and server updates on May 9th. The client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

No Project Server 2010 Cumulative update package was released this month. Mainstream support for Project and Project Server 2010 ended October 13, 2015 – see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported – see the Lifecycle site for more information – http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

Project 2016

An overview of all the Office 2016 releases for May 2017 can be found here – https://support.microsoft.com/en-us/help/4020152/may-9-2017-update-for-microsoft-office – May 9, 2017, update for Microsoft Office

Project Server 2016

Description of the security update for SharePoint Server 2016: May 9, 2017 - Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/3191880/description-of-the-security-update-for-sharepoint-server-2016-may-9-20

May 9, 2017, update for SharePoint Server 2016 (KB3191884) - Can includes Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/en-us/help/3191884/may-9-2017-update-for-sharepoint-server-2016-kb3191884

There is a database schema update this month – it changes to 16.0.4534.1000 – or will get updated to this if you hadn’t patched in January. Remember, Project Server 2016 data is in the content database. The version number 16.0.4534.1000 can be used to control the connecting client to the May 2017 level. For reference – the RTM build number seen for the DB schema would be 16.0.4327.1000.

Project 2016 Client Package:

May 2, 2017, update for Project 2016 (KB3191870)

https://support.microsoft.com/en-us/help/3191870/may-2-2017-update-for-project-2016-kb3191870

The version of Project Professional 2016 will be updated to 16.0.4534.1000 in the properties for WinProj.exe. In 2016 we don’t do a good job of displaying the version in File, Account, About Project – we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe – in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

Project and Project Server 2013

An overview of all the Office 2013 releases for May 2017 can be found here – https://support.microsoft.com/en-us/help/4020152/may-9-2017-update-for-microsoft-office – May 9, 2017, update for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server February PUs from the following articles:

Project Server 2013 Server Rollup Package

May 9, 2017, cumulative update for Project Server 2013 (KB3191912)

https://support.microsoft.com/en-us/help/3191912/may-9-2017-cumulative-update-for-project-server-2013-kb3191912

Project Server 2013 Individual Project Package – (cumulative, but only the Project Server fixes – and contains security fixes this month):

Description of the security update for Project Server 2013: May 9, 2017

https://support.microsoft.com/en-us/help/3191890/description-of-the-security-update-for-project-server-2013-may-9-2017

There is a no database schema update this month – and the dbo.Versions table should show 15.0.4911.1000 after applying the May 2017 PU. (There was actually no DB update last month either – contrary to the original posting). The version number 15.0.4927.1000 can be used to control the connecting client to the May 2017 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here – https://support.microsoft.com/help/2880553

Project 2013 Client Package:

May 2, 2017, update for Project 2013 (KB3191878)

https://support.microsoft.com/en-us/help/3191878/may-2-2017-update-for-project-2013-kb3191878

The client version number will be 15.0.4927.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4927.1000 value to control connection of the May 2017 PU patched client.

SP1 for Project Professional 2013 can be found here – https://support.microsoft.com/help/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.
Extract the patch package by running the .exe file that you downloaded.
Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project and Project Server May 2017 Updates Released

Project-Support — Wed, 06 Mar 2019 22:30:27 GMT

First published on TECHNET on May 17, 2017
Public Update (PU) for Project Server 2013 and 2016 were released May 9, 2017 . Client updates were released April 4th and server updates on April 11th. The client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

The Project Server 2010 Cumulative update package released this month contains no new Project fixes, but does contain SharePoint Server security fixes. The update from May 2017 should be used only if you are upgrading your SharePoint Server hosting Project Server from a version earlier than November 2016. Update your SharePoint 2010 server with the SharePoint only updates if you have already applied the November 2016 or more recent update to Project Server 2010. Support for Project and Project Server 2010 ended October 13, 2015 – see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported – see the Lifecycle site for more information – http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential – this month one of the SharePoint Server 2016 fixes is a security fix). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013.

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We will have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online – see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ – as you will need a ‘2016’ level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to ‘normal’ install times now (I patched both my 2013 and 2016 systems in a couple of hours) – but leaving this comment here just in case… One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don’t have the ‘right’ SP1. Slipstream would work with the original SP1 – but the updates require the re-released SP1. Since the May PU this shouldn’t be an issue – but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed – this is fixed by applying the April 2013 or later– so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn’t already load the April 2013 through June 2014 CU).

An overview of all the Office releases for May 2017 can be found here – https://support.microsoft.com/help/4020152 – May 9, 2017, update for Microsoft Office.

Project 2016

Project Server 2016
With the 2016 release, we just have a single patch (but this month the single patch comes in two parts… a wssloc and sts2016 part). – as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the config wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

Description of the security update for SharePoint Server 2016: May 9, 2017 (KB3191880) - Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/help/3191880

May 9, 2017, update for SharePoint Server 2016 (KB3191884) - Includes Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/help/3191884

There is a database schema update this month – it changes to 16.0.4522.1000 – or will get updated to this if you hadn’t patched in January. Remember, Project Server 2016 data is in the content database. The version number 16.0.4522.1000 can be used to control the connecting client to the February 2017 level. For reference – the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
May 2, 2017, update for Project 2016 (KB3191870)

https://support.microsoft.com/help/3191870

The version of Project Professional 2016 will be updated to 16.0.4534.1000 in the properties for WinProj.exe. In 2016 we don’t do a good job of displaying the version in File, Account, About Project – we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe – in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the ‘16’ level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area – Current Branch for Business is now called Deferred Channel. We are aware that we don’t appear to expose the full change details for Project and are looking into it – you should start seeing more here soon.

Project and Project Server 2013

Project Server 2013 Server Rollup Package

May 9, 2017, cumulative update for Project Server 2013 (KB3191912)

https://support.microsoft.com/help/3191912

Project Server 2013 Individual Project Package – (cumulative, but only the Project Server fixes):

Description of the security update for Project Server 2013: May 9, 2017 (KB3191890)

https://support.microsoft.com/help/3191890

There is a database schema update this month – and the dbo.Versions table should show 15.0.XXXX.1000 after applying the May 2017 PU. The version number 15.0.4919.1000 can be used to control the connecting client to the April 2017 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here – https://support.microsoft.com/help/2880553
Project 2013 Client Package:
May 2, 2017, update for Project 2013 (KB3191878)

https://support.microsoft.com/help/3191878

The client version number will be 15.0.4927.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4927.1000 value to control connection of the May 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See Project Server 2013- Controlling the version of connecting clients–and PWA edits- for more details. As mentioned above – the version number entered no longer controls the server side scheduling engine – so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here – https://support.microsoft.com/help/2817433
Client Installation:
The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project Server: Remote event receivers and large payloads

Brian Smith (CSS) — Wed, 06 Mar 2019 22:30:20 GMT

First published on TECHNET on Apr 20, 2017
*** Update 4/27 - further testing and this does not affect Project Server 2016 - and therefore also unlikely to affect Project Online (although I haven't tested) ***

This blog post comes out of a recent support incident where a customer had configured a server side event handler on the Statusing Approvals Updating event – and had configured a remote event receiver. This type of event handler uses a web based endpoint – either on the same server as Project Server or another server – or even in the cloud – rather than the more commonly seen event handlers (at least for on-premises installations) that are based on locally installed assemblies. This issue can affect Project Server 2013, as well as Project Server 2016 – and at this time we are not fixing the issue in any upcoming patch but are sharing the information here (and will update other documentation too). It does not affect the local assembly based event handlers.

So enough of that – what’s the issue? In this case if a large number of approvals were listed in Approval Center (probably 40+ would be enough to trigger the problem) then when an item or items are approved the complete dataset passes across to the remote event receiver. The remote code does its job and then passes back the result (could be a cancel request or just a change of data – depending on the business logic). This is the point where the process was failing – and the error in this case was “An error occurred while processing one or more items”. It really depends on the event in question as the the precise error one might see when experiencing this problem – but the key aspect is having a large payload – so a lot of something going over the the remote event receiver and coming back.

The corresponding ULS errors are:

04/20/2017 11:00:58.00    Microsoft.Office.Project.Server (0x8148)    0x9AC4    Project Server    Server-Side Events    ac35f    Medium    SEP: Calling endpointUrl http://localhost:34282/StatusEvents.svc failed. Error 'Exception has been thrown by the target of an invocation.' StackTrace '   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)     at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)     at System.Delegate.DynamicInvokeImpl(Object[] args)     at Microsoft.Office.Project.Server.Events.ServerEventProxy.CallRemoteEventReceiver(DelegateInfo del, PSContextInfo contextInfo, String name, IPreEventArgs args)     at Microsoft.Office.Project.Server.Events.ServerEventProxy.FirePreDelegate(PSContextInfo contextInfo, String name, IPreEventArgs args)'

04/20/2017 11:00:58.00    Microsoft.Office.Project.Server (0x8148)    0x9AC4    Project Server    Server-Side Events    7941    Information    Operation canceled by event handler: assembly: http://localhost:34282/StatusEvents.svc class: Statusing event: StatusingApprovalsUpdating handler: Microsoft.Office.Project.Server.Events.StatusingApprovalsUpdatingHandler, method: OnApprovalsUpdating
04/20/2017 11:00:58.03    w3wp.exe (0x6358)    0x6F0C    Project Server    Server-Side Events    aisz6    Warning    Standard Information:PSI Entry Point:   Project User: i:0#.w|domain\user Correlation Id: b296e649-f325-e711-810d-001dd8b73698 PWA Site URL: http://<myserver>/Event SA Name: Project Server Service Application PSError: GeneralActionCanceledByEventHandler (22000) Action canceled by event handler. Reason: (null).    30ebe99d-aae4-e0fd-0000-09216c843577

The problem was found to be that the proxy waiting for the response from the remote event receiver was using the default http binding and the maxReceivedMessageSize in that default is 65536. Once you have 20+ approvals then this size of message can be exceeded. There probably aren’t too many events in Project that would have messages that exceed this – but I’m sure approvals updating isn’t the only one that could exceed this limit.

The fix is easy and can be implemented on the server by editing the config file for the Microsoft Project Server Events service. The file is called Microsoft.Office.Project.Server.Eventing.exe.config and can be found (in a default installation) at C:\Program Files\Microsoft Office Servers\15.0\Bin for Project Server 2013 – or C:\Program Files\Microsoft Office Servers\16.0\Bin for Project Server 2016. Make a copy before you edit – and then just add the following XML snippet one line from the end - between the </runtime> and </configuration> tags.

<system.serviceModel>
<bindings>
<basicHttpBinding>
<binding name="RemoteEventService" closeTimeout="00:05:00"
openTimeout="00:05:00" receiveTimeout="00:05:00" sendTimeout="00:05:00"
maxBufferPoolSize="524288" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647">
<readerQuotas maxDepth="32" maxStringContentLength="2147483647"
maxArrayLength="2147483646" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />
</binding>
</basicHttpBinding>
</bindings>
</system.serviceModel>

Once the file is edited (on all servers) then you will need to restart the Microsoft Project Server Events Service 2013 service (Or the 2016 version if you are hitting this issue on 2016) on all servers where it is running and execute an IISReset to be sure the new value is picked up.

With this correction in place I can now approve my hundreds of pending approvals and they flow through my remote event receiver and back again perfectly!

It is unlikely that we’d make any changes to this file in a patch (and we are not currently planning to make this update in a future PU) – but potentially if we did you’d need to re-do the correction. I’ll be seeing where it makes sense to also add these details – such as TechNet or any Remote Event receiver documents.

Project and Project Server April 2017 Updates Released

Project-Support — Wed, 06 Mar 2019 22:29:56 GMT

First published on TECHNET on Apr 11, 2017
Public Update (PU) for Project Server 2013 and 2016 were released April 11, 2017 . Client updates were released April 4th and server updates on April 11th. The client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

The Project Server 2010 Cumulative update package released this month contains no new Project fixes, but does contain SharePoint Server security fixes. The update from April 2017 should be used only if you are upgrading your SharePoint Server hosting Project Server from a version earlier than November 2016. Update your SharePoint 2010 server with the SharePoint only updates if you have already applied the November 2016 or more recent update to Project Server 2010. Support for Project and Project Server 2010 ended October 13, 2015 – see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported – see the Lifecycle site for more information – http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential – this month one of the SharePoint Server 2016 fixes is a security fix). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013.

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/office/mt465751 . We will have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online – see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ – as you will need a ‘2016’ level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to ‘normal’ install times now (I patched both my 2013 and 2016 systems in a couple of hours) – but leaving this comment here just in case… One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don’t have the ‘right’ SP1. Slipstream would work with the original SP1 – but the updates require the re-released SP1. Since the May PU this shouldn’t be an issue – but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed – this is fixed by applying the April 2013 or later– so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn’t already load the April 2013 through June 2014 CU).

Project 2016

An overview of all the Office 2016 releases for April 2017 can be found here – https://support.microsoft.com/Help/4016803 – April 11, 2017, update for Microsoft Office.
Project Server 2016
With the 2016 release, we just have a single patch (but this month the single patch comes in two parts… a wssloc and sts2016 part). – as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the config wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

April 11, 2017, update for SharePoint Server 2016 (KB3178721)– Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/help/3178721

April 11, 2017, update for SharePoint Server 2016 (KB3178718)– Can includes Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/help/3178718

There is a database schema update this month - it changes to 16.0.4522.1000 – or will get updated to this if you hadn’t patched in January. Remember, Project Server 2016 data is in the content database. The version number 16.0.4522.1000 can be used to control the connecting client to the February 2017 level. For reference – the RTM build number seen for the DB schema would be 16.0.4327.1000.
Project 2016 Client Package:
April 4, 2017, update for Project 2016 (KB3178708)

https://support.microsoft.com/help/3178708

The version of Project Professional 2016 will be updated to 16.0.4522.1000 in the properties for WinProj.exe. In 2016 we don’t do a good job of displaying the version in File, Account, About Project – we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe – in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the ‘16’ level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area – Current Branch for Business is now called Deferred Channel. We are aware that we don’t appear to expose the full change details for Project and are looking into it – you should start seeing more here soon.

Project and Project Server 2013

An overview of all the Office 2013 releases for April 2017 can be found here – https://support.microsoft.com/Help/4016803 – April 11, 2017, update for Microsoft Office. This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production. You can read about the fixes included in the Project and Project Server February PUs from the following articles:

Project Server 2013 Server Rollup Package

April 11, 2017, cumulative update for Project Server 2013 (KB3178728)

https://support.microsoft.com/help/3178728/

Project Server 2013 Individual Project Package – (cumulative, but only the Project Server fixes):

April 11, 2017, update for Project Server 2013 (KB3191824)

https://support.microsoft.com/help/3191824

*** 6/6/17 Correction - no DB update in April - schema should say 15.0.4911.1000 same as March ***

There is a database schema update this month – and the dbo.Versions table should show 15.0.4919.1000 after applying the April 2017 PU. The version number 15.0.4919.1000 can be used to control the connecting client to the April 2017 PU level. Project Professional Versions (Project Server 2013 settings)

SP1 for Project Server 2013 can be found here – https://support.microsoft.com/help/2880553
Project 2013 Client Package:
April 4, 2017, update for Project 2013 (KB3178713)

https://support.microsoft.com/help/3178713

The client version number will be 15.0.4919.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4919.1000 value to control connection of the April 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See Project Server 2013- Controlling the version of connecting clients–and PWA edits- for more details. As mentioned above – the version number entered no longer controls the server side scheduling engine – so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here – https://support.microsoft.com/help/2817433
Client Installation:
The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project and Project Server March 2017 Updates Released

Project-Support — Wed, 06 Mar 2019 22:29:47 GMT

First published on TECHNET on Mar 16, 2017
Earlier this week saw the delayed release of the March 2017 Public Update (PU) for Project Server 2013 and 2016. Client updates were released March 7th as planned and server updates on March 14th. The client updates release on the first Tuesday of the month and server on the second Tuesday release schedule.

The Project Server 2010 Cumulative update package released this month contains no new Project fixes, but does contain SharePoint Server security fixes. The update from March 2017 should be used only if you are upgrading your SharePoint Server hosting Project Server from a version earlier than November 2016. Update your SharePoint 2010 server with the SharePoint only updates if you have already applied the November 2016 or more recent update to Project Server 2010. Support for Project and Project Server 2010 ended October 13, 2015 – see https://support.microsoft.com/en-us/lifecycle . An SP1 patched 2010 system (with no SP2) is no longer supported – see the Lifecycle site for more information – http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential – this month one of the SharePoint Server 2016 fixes is a security fix). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013.

A note about Click-to-Run (sometimes abbreviated C2R) versions of Project for Office 365. The updates for this version are not included in this blog. For some information about Click-to-Run versions, please see the following site for version numbers and some fix information: https://technet.microsoft.com/en-us/office/mt465751 . We will have a future blog with additional information about Click-to-Run update channels and methods.

Also a note for users of the Project client connecting to Project Online – see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ – as you will need a ‘2016’ level client to connect starting at the end of June 2017.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to ‘normal’ install times now (I patched both my 2013 and 2016 systems in a couple of hours) – but leaving this comment here just in case… One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don’t have the ‘right’ SP1. Slipstream would work with the original SP1 – but the updates require the re-released SP1. Since the May PU this shouldn’t be an issue – but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed – this is fixed by applying the April 2013 or later– so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn’t already load the April 2013 through June 2014 CU).

Project 2016

An overview of all the Office 2016 releases for March 2017 can be found here – https://support.microsoft.com/help/4013886 – March 14, 2017, update for Microsoft Office

Project Server 2016

With the 2016 release, we just have a single patch (but this month the single patch comes in two parts… a wssloc and sts2016 part). – as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the config wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

March 14, 2017, update for SharePoint Server 2016 (KB3178675) – Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/help/3178675

March 14, 2017, update for SharePoint Server 2016 (KB3178672) – Can includes Project fixes, like the roll-up patch in Project Server 2013

https://support.microsoft.com/help/3178672

There is no database schema update this month so it remains at 16.0.4510.1000 – or will get updated to this if you hadn’t patched in January. Remember, Project Server 2016 data is in the content database. The version number 16.0.4507.1000 can be used to control the connecting client to the February 2017 level. For reference – the RTM build number seen for the DB schema would be 16.0.4327.1000.

Project 2016 Client Package:

March 7, 2017, update for Project 2016 (KB3178669)

https://support.microsoft.com/help/3178669

The version of Project Professional 2016 will be updated to 16.0.4507.1000 in the properties for WinProj.exe. In 2016 we don’t do a good job of displaying the version in File, Account, About Project – we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe – in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the ‘16’ level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area – Current Branch for Business is now called Deferred Channel. We are aware that we don’t appear to expose the full change details for Project and are looking into it – you should start seeing more here soon.

Project and Project Server 2013

An overview of all the Office 2013 releases for March 2017 can be found here – https://support.microsoft.com/help/4013886 – March 14, 2017, update for Microsoft Office

This include multiple fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production.

The article below provides information on how to deploy the Project Server Cumulative Update.

You can read about the fixes included in the Project and Project Server February PUs from the following articles:

Project Server 2013 Server Rollup Package

March 14, 2017, cumulative update for Project Server 2013 (KB3172462)

https://support.microsoft.com/help/3172462

Project Server 2013 Individual Project Package – (cumulative, but only the Project Server fixes):

March 14, 2017, update for Project Server 2013 (KB3178625)

https://support.microsoft.com/help/3178625

There is a database schema update this month – and the dbo.Versions table should show 15.0.4911.1001 after applying the March 2017 PU. The version number 15.0.4911.1001 can be used to control the connecting client to the March 2017 PU level.

SP1 for Project Server 2013 can be found here – http://support.microsoft.com/kb/2880553

Project 2013 Client Package:

March 7, 2017, update for Project 2013 (KB3178650)

https://support.microsoft.com/help/3178650

The client version number will be 15.0.4911.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4911.1000 value to control connection of the February 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See Project Server 2013- Controlling the version of connecting clients–and PWA edits- for more details. As mentioned above – the version number entered no longer controls the server side scheduling engine – so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here – http://support.microsoft.com/kb/2817433

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.

Project and Project Server February 2017 Updates Released

Brian Smith (CSS) — Wed, 06 Mar 2019 22:29:35 GMT

First published on TECHNET on Feb 24, 2017
Earlier this week saw the delayed release of the February 2017 Public Update (PU) for Project Server 2013 and 2016. Client updates were released February 7th as planned and server updates on February 21st The client updates release on the first Tuesday of the month and server on the second Tuesday release schedule – although this month the server was delayed a month – and the ‘roll-up’ package for Project Server 2013 was not released. Normal service and the full set of patches should continue in March (7th for client – 14th for server).

I’m dropping the 2010 updates as none are released this month – if we do have any going forward then I will mention those separately.

We are now delivering as Public Updates, although Server fixes are shipped just via the Download Center and not via Microsoft Update (Unless there is a security element or a fix deemed essential – this month one of the SharePoint Server 2016 fixes is a security fix). These are still all cumulative and include fixes released in all previous updates since the last baseline (Initial release for 2016 and SP1 for 2013.

Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed.

We should be back to ‘normal’ install times now (I patched both my 2013 and 2016 systems in a couple of hours) – but leaving this comment here just in case… One point to note is the installation of the Project Server 2016 package (SharePoint Server) for September 2016 and beyond can take longer to install than previous 2016 updates, on my slow server it took several hours, so you should ensure you test installation in a similar environment to production to ensure you allow enough downtime.

The 2013 PU releases also have a real prerequisite of the appropriate Service Pack 1 (SP1), and links for SP1 are given below. SP1 is enforced in this release, so you will find out (as I did) if you really do have SP1 for all your installed components and language packs! This also means RTM is no longer supported! See http://blogs.technet.com/b/stefan_gossner/archive/2015/04/15/common-issue-april-2015-fixes-for-sharepoint-2013-cannot-be-installed-on-sharepoint-2013-sp1-slipstream-builds.aspx too which describes an issue you might see if you don’t have the ‘right’ SP1. Slipstream would work with the original SP1 – but the updates require the re-released SP1. Since the May PU this shouldn’t be an issue – but including here just in case.

Another important point to add here is that there was in early 2013 running the SharePoint Configuration Wizard on a server with Project Server 2013 installed – this is fixed by applying the April 2013 or later– so a good practice would be to load SP1, then the current PU and then run the configuration wizard (if you didn’t already load the April 2013 through June 2014 CU).

Also worth noting that mainstream support for Project and Project Server 2010 ended October 13th 2015 – see https://support.microsoft.com/en-us/lifecycle

Also a reminder – an SP1 patched 2010 system (with no SP2) is no longer supported – see the Lifecycle site for more information – http://support.microsoft.com/lifecycle/search?sort=PN&alpha=project+2010&Filter=FilterNO

Project 2016

An overview of all the Office 2016 releases for February 2017 can be found here – https://support.microsoft.com/en-us/help/4010765/february-2017-update-for-microsoft-office – February, 2017, update for Microsoft Office

Project Server 2016

With the 2016 release we just have a single patch (but this month the single patch comes in two parts… a wssloc and sts2016 part). – as we have also the single msi for installation of SharePoint Server 2016 (Project Server still needs licensing separately though). Both parts need installing before the config wizard is executed. The sts2016 part of the patch also contains security fixes so is released via Microsoft Update, the Update catalog as well as the download center.

February 14, 2017, update for SharePoint Server 2016 (KB3141515) – Includes Project fixes, like the roll-up patch in Project Server 2013.

https://support.microsoft.com/en-us/help/3141515/february-14-2017-update-for-sharepoint-server-2016-kb3141515

February 21, 2017, update for SharePoint Server 2016 (KB3141517) – Can includes Project fixes, like the roll-up patch in Project Server 2013 – but doesn’t this month.

https://support.microsoft.com/en-us/help/3141517/february-21-2017-update-for-sharepoint-server-2016-kb3141517

There is no database schema update this month so it remains at 16.0.4483.1000 – or will get updated to this if you hadn’t patched in January. Remember, Project Server 2016 data is in the content database. The version number 16.0.4498.1002 can be used to control the connecting client to the February 2017 level. For reference – the RTM build number seen for the DB schema would be 16.0.4327.1000.

Project 2016 Client Package:

February 7, 2017, update for Project 2016 (KB3141514)

https://support.microsoft.com/en-us/help/3141514/february-7-2017-update-for-project-2016-kb3141514

The version of Project Professional 2016 will be updated to 16.0.4498.1002 in the properties for WinProj.exe. In 2016 we don’t do a good job of displaying the version in File, Account, About Project – we only display the MSO version and not the specific Project version (You can confirm this by looking at the version of winproj.exe – in (default for 32 bit) C:\Program Files (x86)\Microsoft Office\Office16)

If you have Click to Run and using Project Pro for Office 365 at the ‘16’ level, then your version will depend on which update frequency you have set. Take a look at https://blogs.office.com/2016/02/09/deferred-channel-build-now-available-for-the-office-365-client-apps/ for a few changes in this area – Current Branch for Business is now called Deferred Channel. We are aware that we don’t appear to expose the full change details for Project and are looking into it – you should start seeing more here soon.

Project and Project Server 2013

An overview of all the Office 2013 releases for February 2017 can be found here – https://support.microsoft.com/en-us/help/4010765/february-2017-update-for-microsoft-office – February, 2017, update for Microsoft Office

This include a number of fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production.

The article below provides information on how to deploy the Project Server Cumulative Update.

You can read about the fixes included in the Project and Project Server February PUs from the following articles:

Project Server 2013 Server Rollup Package

No rollup package this month – see https://support.microsoft.com/en-us/help/4010765/february-2017-update-for-microsoft-office for any other SharePoint Server 2013 patches you may wish to load along with the Project Server 2013 individual package

Project Server 2013 Individual Project Package – (cumulative, but only the Project Server fixes):

February 21, 2017, update for Project Server 2013 (KB3141525)

https://support.microsoft.com/en-us/help/3141525/february-21-2017-update-for-project-server-2013-kb3141525

There is a database schema update this month – and the dbo.Versions table should show 15.0.4903.1000 after applying the February 2017 PU. The version number 15.0.4903.1000 can be used to control the connecting client to the February 2017 PU level.

SP1 for Project Server 2013 can be found here – http://support.microsoft.com/kb/2880553

Project 2013 Client Package:

February 7, 2017, update for Project 2013 (KB3141499)

https://support.microsoft.com/en-us/help/3141499/february-7-2017-update-for-project-2013-kb3141499

The client version number will be 15.0.4903.1000. The server scheduling engine is no longer blocked by version control since the November 2014 CU on the server, so providing you have November 2014 CU or above on the server you can use the 15.0.4903.1000 value to control connection of the February 2017 PU patched client.

If you are running a server CU earlier than November 2014 CU, then follow the suggested version number for the server patch level you are running. See Project Server 2013- Controlling the version of connecting clients–and PWA edits- for more details. As mentioned above – the version number entered no longer controls the server side scheduling engine – so from the November 2014 CU release onward you can set a higher version to control clients without blocking the server side scheduling in the schedule web part.

SP1 for Project Professional 2013 can be found here – http://support.microsoft.com/kb/2817433

Also note that Click to Run installations will be automatically patched. Installations in Enterprise Environments that have been modified will be deployed based on the schedule determined by your Administrator. See http://support2.microsoft.com/gp/office-2013-click-to-run . You may also choose to update your click to run Project Pro for Office 365 to the new 2016 level – this can still connect to Project Server 2013 – see the 2016 section above for current version.

Also a note for users of the Project client connecting to Project Online – see https://blogs.technet.microsoft.com/projectsupport/2016/12/15/using-project-online-time-to-be-sure-you-upgrade-the-client-software/ – as you will need a ‘2016’ level client to connect starting in March 2017.

Client Installation:

The instructions for installing the client patch are below.

NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.

Download the hotfix from the link in the KB Article.

Extract the patch package by running the .exe file that you downloaded.

Run the extracted .exe file to apply the patch to your Project Professional/Standard client.

Or, from February 2015 onwards use Windows Update to download and install the patches.