Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Description of the Project Server 2013 hotfix package (Projectserverwfe-x-none.msp): April 8, 2014

View products that this article applies to.


This article describes the issues that are fixed in the Microsoft Project Server 2013 hotfix package that is dated April 8, 2014.

↑ Back to the top


Issues that this hotfix package fixes

  • 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.

↑ Back to the top

More Information

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


You must install the following public update before you apply this hotfix package:
2768001 Description of the SharePoint Server 2013 and Project Server 2013 update: March 12, 2013

Restart requirement

You do not have to restart the computer after you install this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

This hotfix package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to resolve the issue that listed in this article.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

x64 version

Download information
File nameFile versionFile sizeDateTime

Microsoft Windows Installer .msp file information
File nameFile versionFile sizeDateTime
Projectserverwfe-x-none.mspNot Applicable93,065,21614-Mar-201416:24

Projectserverwfe-x-none.msp file information
File nameFile versionFile sizeDateTime
Adsyncpsgroups.aspxNot Applicable1,63512-Mar-201412:10
Changeskipworkflow.aspxNot Applicable19,29712-Mar-201412:10
Comparedrivers.aspxNot Applicable18,90612-Mar-201412:10
Costconstraintanalysis.aspxNot Applicable80,84312-Mar-201412:10
Enterpriseprojecttypedetails.aspxNot Applicable36,66612-Mar-201412:10
Eventswsdl.aspxNot Applicable34,90912-Mar-201412:10
Fiscalperiod.aspxNot Applicable9,09312-Mar-201412:10
Locktask.aspxNot Applicable8,05612-Mar-201412:10
Lookuptablewsdl.aspxNot Applicable42,18712-Mar-201412:10,377,05612-Mar-201412:09,405,11212-Mar-201412:10,20012-Mar-201412:10,68012-Mar-201412:09,053,34412-Mar-201412:10,997,43212-Mar-201412:10,193,72012-Mar-201412:09,91212-Mar-201412:10,80012-Mar-201412:10,24012-Mar-201412:10,766,58412-Mar-201412:09,36012-Mar-201412:10,007,33612-Mar-201412:10,129,06412-Mar-201412:10,24012-Mar-201412:10,76012-Mar-201412:10,12012-Mar-201412:10,405,04812-Mar-201412:10,50412-Mar-201412:10,03212-Mar-201412:10,18412-Mar-201412:10,62412-Mar-201412:09,75212-Mar-201412:10,62412-Mar-201412:09,89612-Mar-201412:09,63212-Mar-201412:09
Mshy3hu.lexNot Applicable933,57912-Mar-201412:09
Notificationswsdl.aspxNot Applicable14,53812-Mar-201412:10
Pdplib.debug.jsNot Applicable79,31112-Mar-201412:10
Pdplib.debug.jsNot Applicable88,86112-Mar-201412:10
Pdplib.jsNot Applicable53,41312-Mar-201412:10
Pdplib.jsNot Applicable61,28612-Mar-201412:10
Portfolioanalyseswsdl.aspxNot Applicable92,99612-Mar-201412:10
Portfolioanalysis.debug.jsNot Applicable6,50312-Mar-201412:10
Portfolioanalysis.jsNot Applicable3,42112-Mar-201412:10
Projectdatabasecreate.sqlNot Applicable10,558,23412-Mar-201412:10
Projectdrilldownsatellite.debug.jsNot Applicable145,92812-Mar-201412:10
Projectdrilldownsatellite.jsNot Applicable95,38212-Mar-201412:10
Projectpostupgrade.sqlNot Applicable371,13412-Mar-201412:10
Projectpreupgrade.sqlNot Applicable6,73312-Mar-201412:10
Projectserverapishim.generated.debug.jsNot Applicable164,95412-Mar-201412:10
Projectserverapishim.generated.jsNot Applicable86,98412-Mar-201412:10
Projectserverscripts.debug.jsNot Applicable414,86112-Mar-201412:10
Projectserverscripts.jsNot Applicable308,95912-Mar-201412:10
Projectwsdl.aspxNot Applicable234,71512-Mar-201412:10
Ps.core.debug.jsNot Applicable354,70812-Mar-201412:10
Ps.core.jsNot Applicable218,23012-Mar-201412:10
Ps.debug.jsNot Applicable894,24112-Mar-201412:10
Ps.projectmanagers.debug.jsNot Applicable265,93512-Mar-201412:10
Ps.projectmanagers.jsNot Applicable167,74512-Mar-201412:10
Ps.teammembers.debug.jsNot Applicable341,84012-Mar-201412:10
Ps.teammembers.jsNot Applicable217,66512-Mar-201412:10
Ps.timeline.debug.jsNot Applicable77,10712-Mar-201412:10
Ps.timeline.jsNot Applicable77,10712-Mar-201412:10
Pstimelineapishim.generated.debug.jsNot Applicable2,25512-Mar-201412:10
Pstimelinesharedapi.generated.debug.jsNot Applicable3,28712-Mar-201412:10
Pwa.resxNot Applicable779,66412-Mar-201412:10
Pwaparts.ascxNot Applicable19,50412-Mar-201412:10
Pwastyle.cssNot Applicable10,25912-Mar-201412:10
Queuesystemwsdl.aspxNot Applicable66,39712-Mar-201412:10
Resourceconstraintanalysis.aspxNot Applicable67,14812-Mar-201412:10
Resourceconstraintreport.aspxNot Applicable30,44212-Mar-201412:10
Resourceplans.debug.jsNot Applicable29,63012-Mar-201412:10
Resourceplans.jsNot Applicable19,32012-Mar-201412:10
Resourcewsdl.aspxNot Applicable78,16012-Mar-201412:10
Rulesaddmod.aspxNot Applicable41,09712-Mar-201412:10
Securitywsdl.aspxNot Applicable94,07012-Mar-201412:10
Sharedapi.generated.debug.jsNot Applicable32,94412-Mar-201412:10
Shell.debug.jsNot Applicable86,15712-Mar-201412:10
Shell.jsNot Applicable42,15712-Mar-201412:10
Sp.userprofiles.debug.jsNot Applicable140,58112-Mar-201412:09
Sp.userprofiles.jsNot Applicable140,57512-Mar-201412:09
Srrequest.aspxNot Applicable31,93212-Mar-201412:10
Statusapprovalssatellite.jsNot Applicable19,68212-Mar-201412:10
Statusingwsdl.aspxNot Applicable205,00812-Mar-201412:10
Taskdetails.ascxNot Applicable24,78612-Mar-201412:10
Timesheetsatellite.jsNot Applicable56,37912-Mar-201412:10
Timesheetwsdl.aspxNot Applicable88,24812-Mar-201412:10
Viewwsdl.aspxNot Applicable40,23912-Mar-201412:10
Workflowwsdl.aspxNot Applicable84,41512-Mar-201412:10
Wssinteropwsdl.aspxNot Applicable36,51912-Mar-201412:10

↑ Back to the top


For more information about software update terminology, click the following article number to go to the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kbqfe, kbautohotfix, kbhotfixserver, kbexpertiseinter, kbsurveynew, kbcu, kbhotfixrollup, kb

↑ Back to the top

Article Info
Article ID : 2863881
Revision : 2
Created on : 3/30/2017
Published on : 3/30/2017
Exists online : False
Views : 343