Description of the Microsoft Office Project 2003 post-Service Pack 1 hotfix package: August 25, 2004 (841361)

SUMMARY

• Issues that the hotfix package fixes
• Prerequisites for installing the hotfix package
• Whether you must restart your computer after you install the hotfix package
• Whether the hotfix package is replaced by any other hotfix package
• Whether you must make any registry changes to use one or more of the hotfixes in the package
• The files that the hotfix package contains

SUMMARY

Issues that are fixed in the hotfix package

• 840376 Actual Work that is submitted by the local resources may be lost when you synchronize a project that uses Protected Actuals and local resources in Project 2003

• 843608 How to let Project Professional 2003 connect to your Project Server that is located in the intranet zone without being prompted to add the Project Server as a trusted site

• 883505 Actual Work Protected values for assignments that are in a Resource view may be blank or display a zero for their values in Project Professional 2003

• When you synchronize a project plan that uses Protected Actuals in Project 2003, the data that is in the Work field may increase for individual tasks and for Project Summary tasks every time that you synchronize your project plan.
  
• When you use the Define working times for resources option in the Project Guide, Project 2003 may stop responding if you change the working times after you check out a resource from the Enterprise Resource Pool.
  
• If you assign yourself to a task in Microsoft Project Web Access (PWA), a duplicate task may be created. Additionally, any one of the following symptoms may occur:
  • When the project manager accepts your submitted timesheet in PWA, the project manager receives one of the following error messages:
    Some approved task changes cannot be updated in Project files. Click view details for more information. If you rejected a task, the resource has been notified by e-mail. Please save your Project files with new updates. The updated tasks will remain in the table until you save the project files.
    
    The following projects were not updated correctly for the following reasons:
    
    1. ProjectFileName: Some of the tasks in this project failed to update. The specific errors will show up individually inside of Project.
    Some approved task changes cannot be updated in Project files. Click view details for more information. If you rejected a task, the resource has been notified by e-mail. Please save your Project files with new updates. The updated tasks will remain in the table until you save the project files.
    
    The following projects were not updated correctly for the following reasons:
    
    1. Duplicate Assignment: Unknown Error.
  • When the project manager accepts your submitted timesheet in Microsoft Office Project Professional 2003, the project manager receives the following error message:
    Microsoft Office Project
    
    The resource assignment cannot be updated because the resource "" is no longer assigned to task "taskname".
    
    Try one of the following:
    -You may be updating actuals on a new task created by the resource. In this case, update the new task to Project prior to updating its update information.
    -The resource may have been removed from the task before you received the updated information you are trying to incorporate.
    -The task you are trying to update may have been deleted from your project.
    -If you are updating a project that is inserted into another project, expand the project, and then try again.
  • When the project manager republishes the project plan in Project Professional 2003, the project manager receive one of the following spooler error messages:
    SYSTEM ERROR (0x80004005)
    DATABASE ERROR (0x80040E14)
• After you repeatedly save a baseline and your project plan in Project Professional 2003 as the project manager, the baseline data is incorrect when you reopen and view your project plan in the Resource Usage view.
  
• When you make changes to an enterprise custom field in your Master Project File in Project 2003, enterprise custom field values that are contained in a task may be blank.
  
• If you rename custom fields in Project Professional 2003 and then import a Microsoft Excel workbook as a new project, the renamed custom field names are missing in your new project.
  
• Every time that you synchronize your Protected Actuals in a project plan that contains a managed time period and a material resource that contains submitted actual hours worked, the values that are in the % Complete field, in the Actual Work field, and in the Actual Duration field change.
  
• Every time that you synchronize your Protected Actuals in a project plan, the value that is in the Actual Duration field increases. This issue may occur even after you install the hotfix that is described in the following article in the Microsoft Knowledge Base:
  
  

  839631 Microsoft Office Project 2003 hotfix package: April 1, 2004

• When you synchronize a project plan that uses Protected Actuals in Project Professional 2003, the values that are in the Work field, the Actual Work field, and the Remaining Work field may change. This issue may occur even after you install the hotfix that is described in the following article in the Microsoft Knowledge Base:
  
  

  839631 Microsoft Office Project 2003 hotfix package: April 1, 2004

• When you try to save your project plan in Project Professional 2003, you may receive the following error message:
  Microsoft Office Project has encountered a problem and needs to close. We are sorry for the inconvenience.
  
  To see what data this error report contains, click here.
  When you view the data in the error report, the report contains an error signature that is similar to the following error signature:

     Application name  Application version  Module name   Module version  Offset
     -----------------------------------------------------------------------------
     Winproj.exe       11.0.2003.816        Pj11od11.dll  11.0.2003.816   0000729c
  

• When you close your Master Project Plan in Project Professional 2003 and then click to save your sub projects, Project Professional 2003 may quit unexpectedly, and you receive the following error message:
  Microsoft Office Project has encountered a problem and needs to close. We are sorry for the inconvenience.
  
  To see what data this error report contains, click here.
  When you view the data in the error report, the report contains an error signature that is similar to the following error signature:

     Application name  Application version  Module name  Module version  Offset
     ----------------------------------------------------------------------------
     Winproj.exe       11.0.2004.401        Winproj.exe  11.0.2004.401   00180c18
  

• When Project 2003 calculates the BCWP of a task, of a resource, or of an assignment in the Task Usage view, an incorrect earned value is calculated.
  
• When you export data from Project 2003 by using the Analyze Timescaled Data Wizard, the value that is in the Baseline Cost field may appear incorrect on the Microsoft Excel worksheet.