Issues that are fixed in Project 2003 by Project 2003 Service Pack 2

Article translations Article translations
Article ID: 906428 - View products that this article applies to.
Expand all | Collapse all

On This Page

SUMMARY

Microsoft has released a service pack for Microsoft Office Project 2003. This service pack contains fixes for Project 2003.

INTRODUCTION

Microsoft Office Project 2003 Service Pack 2 (SP2) provides the latest updates to Microsoft Office Project 2003. Project 2003 SP2 contains security enhancements and stability and performance improvements. Some of the fixes that are included in Project 2003 SP2 have been previously released in Microsoft Office Project 2003 Service Pack 1 (SP1) or as separate updates. This service pack combines previously released fixes into one update.

For more information about Project 2003 SP2, click the following article number to view the article in the Microsoft Knowledge Base:
887620 Description of Project 2003 Service Pack 2

MORE INFORMATION

Downloadable list of issues that the service pack fixes

A Microsoft Excel workbook is available that contains a list of the Project 2003 post-Service Pack 1 issues that are fixed by Project 2003 SP2.

Note The workbook is in the English language. The workbook will not be translated into any other languages.

The following file is available for download from the Microsoft Download Center:
Collapse this imageExpand this image
Download
Download the Office2003System_SP2Changes.exe package now.

Release Date: September 27, 2005

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

List of issues that the service pack fixes

Issues that were previously documented in the Microsoft Knowledge

841361 Description of the Microsoft Office Project 2003 post-Service Pack 1 hotfix package: August 25, 2004
885833 Description of the Microsoft Office Project 2003 post-Service Pack 1 Hotfix Package: September 18, 2004
886661 Description of the Microsoft Office Project 2003 post-Service Pack 1 hotfix package: September 24, 2004
886963 Description of the Microsoft Office Project 2003 post-Service Pack 1 hotfix package: October 6, 2004
887801 Description of the Microsoft Office Project 2003 post-Service Pack 1 hotfix package: October 21, 2004
887803 Description of the Microsoft Office Project 2003 post-Service Pack 1 hotfix package: October 29, 2004
889089 Description of the Microsoft Office Project 2003 post-Service Pack 1 hotfix package: November 9, 2004
890073 Description of the Microsoft Office Project 2003 post-Service Pack 1 hotfix package: November 19, 2004
891203 Description of the Project 2003 post-Service Pack 1 hotfix package: January 13, 2005
891648 Description of the Project 2003 post-Service Pack 1 hotfix package: March 29, 2005
893088 Description of the Project 2003 post-Service Pack 1 hotfix package: January 28, 2005
893622 Description of the Project 2003 post-Service Pack 1 hotfix package: February 10, 2005
894477 Description of the Project 2003 post-Service Pack 1 hotfix package: February 19, 2005
894922 Description of the Project 2003 post-Service Pack 1 hotfix package: February 26, 2005
895120 Description of the Project 2003 post-Service Pack 1 hotfix package: March 11, 2005
896104 Description of the Microsoft Office Project 2003 post-Service Pack 1 hotfix package: March 18, 2005
897709 Description of the Project 2003 post-Service Pack 1 hotfix package: April 20, 2005

Issues that were not previously documented in the Microsoft Knowledge Base

A blank Visio chart is created when you run the Launch Wizard in Project Professional 2003

Consider the following scenario. Microsoft Office Visio Professional 2003 is installed on the computer. You run the Launch Wizard that is contained in the Visio WBS Chart Wizard in Microsoft Office Project Professional 2003. In this scenario, a Visio chart is created in which the task names have the wrong characters. Or, a blank Visio chart is created.

Local resources are duplicated every time that you save the project

Local resources that have the same name are duplicated every time that you save the project.

The duration of the task may be shortened when you enter "0" for a day's actual work in Project Professional 2003 and enter "0" for another day's actual work in PWA 2003

Consider the following scenario. You enter 0 for a day's actual work in Project Professional 2003. Then, you enter 0 for another day's actual work in Microsoft Office Project Web Access (PWA) 2003. In this scenario, the duration of the task may be unexpectedly shortened.

Unavailable time may be unexpectedly added to the actual work in an administrative project

After you use the "Notify your manager of time that you will not be available for project work" feature to notify your manager that you are unavailable for an administrative project in PWA 2003, unavailable time may be unexpectedly added to the actual work.

If you clear the baseline for Baseline 1 to Baseline 10, the time-phased data for the baseline is removed

When you review the task usage view and the time-phased baseline details of a project, you notice that the baseline details have been removed. Additionally, if you clear the baseline for Baseline 1 to Baseline 10, the time-phased data for the baseline is removed.

The remaining work time is not updated in Project Professional 2003 when you update the remaining work time in PWA 2003

When you update the remaining work time in PWA 2003, the remaining work time is not updated in Project Professional 2003. Additionally, if you refresh the PWA 2003 session, the remaining work time changes back to original value that existed before you updated the remaining work time in PWA 2003.

The work time values in an imported task are different depending on whether you import the task into an existing project or into a new project

Consider the following scenario. You import a task from an Excel spreadsheet into a new project. The task contains resources that have work time values. In this scenario, the work time values in the project differ from the work time values that appear when you import the task from an Excel spreadsheet into an existing project.

Custom enterprise formulas can cause incorrect values to be rolled up into the totals of dependent projects

If you have a custom enterprise formula that refers to a project level field, external tasks, such as cross-project linked tasks, may cause incorrect values to be rolled up into the totals of the dependent projects.

You receive a message that refers to the enterprise global instead of the resource pool when you use Project Professional 2003 with a local resource pool

When you use Project Professional 2003 with a local resource pool, you receive the following message:
The currency of this project is different from the currency specified in the enterprise global. To maintain consistency in the enterprise-level reports, you should use the same currency as the enterprise global. Do you want to overwrite the project's currency setting with that of the enterprise global? Click Yes to overwrite this project's currency setting, or click No to keep this project's currency setting.
You expect the message to refer to the resource pool instead of the enterprise global.

A duplicate resource is created when you assign a resource to a project

Consider the following scenario. You are using the Turkish version of Project Professional 2003. You assign a resource to a project. The name of the resource starts with an uppercase "I". In this scenario, a duplicate resource is added to the project. The name of the duplicate resource starts with a lowercase "i".

When you publish a project that has a long hyperlink address in Project 2003, the hyperlink address is truncated in PWA 2003

When you publish a project plan that has a long hyperlink address in Project Server 2003, the hyperlink address is truncated in PWA 2003.

You receive an HTTP 405 error when you enter an incomplete Project Server 2003 URL

When you enter an incomplete Microsoft Project Server URL, you receive an unexpected server response error. If you click View in this error, you receive the following error message on a Microsoft Internet Explorer Web page:
HTTP 405 - Resource not allowed Internet Information Services
After you apply Project 2003 SP2, you must test a URL before you can use it. Therefore, this behavior no longer occurs because you cannot enter an incomplete Project Server URL. After you change a Project Server URL in Project 2003 SP2, you must click Test Connection before you click OK. If you click OK before you click Test Connection, you receive the following message:
You have not tested your connection to the server. Please click the Text Connection button before clicking OK.

A Task's duration is changed to 60 minutes if you assign a material resource to the task and save the project as an .xml file

Consider the following scenario. A task's duration is less than 60 minutes. You assign a material resource to the task. Then, you save the project as an .xml file. In this scenario, the task's duration is changed to 60 minutes. Additionally, the Units value on the material resource assignment is changed.

The Risks command does not appear on the Commands tab in the Toolbar customization dialog box

In the Toolbar customization dialog box, the Risks command does not appear under Collaborate on the Commands tab.

You cannot open an .mpp file if the .mpp file has a password that has 17 characters

You cannot open an .mpp file if the .mpp file has a password that has 17 characters or more. This problem occurs even when you enter the correct password for the .mpp file.

Note The maximum number of characters that you can have in a password is 17.

If you call the "ActiveWindow.Refresh" method after you change a saved .mpp file, you cannot see the changes

Consider the following scenario. You create a macro that includes a call to the ActiveWindow.Refresh method. You change a saved .mpp file. Then, you run the macro. In this scenario, you cannot see the changes. This problem occurs because window that contains the changes is not updated even though the file has been updated.

The task's work remains unchanged after you set the calculation mode to Manual and then save the project as an .xml file

Consider the following scenario. You set the calculation mode to Manual. You save the project as an .xml file. Then, you reopen the .xml file. In this scenario, the task's work remains unchanged.

Project 2003 may stop responding when you open an .xls file

When you open an .xls file in Project 2003, Project 2003 may stop responding. This issue occurs in Project Professional 2003 and in Project Standard 2003.

The changes are not saved when you change a custom field formula in an enterprise project if the formula is defined in the local Global Template file

Consider the following scenario. You change a custom field formula in an enterprise project. The same custom field is defined in the local Global Template file. You save the changes and close the file. Then, you open the file. In this scenario, you notice that the changes are not saved.

Work values on the sheet side may differ from the work values on the time-phased side

Consider the following scenario. You enter actual work values on non-working days. Then, you delete the actual work values that you entered from the aggregate sheet-side value. In this scenario, the work values on the sheet side may differ from the work values on the time-phased side. This issue occurs when a work resource and a material resource are assigned to the same task.

You cannot make an inactive resource active in Project Professional 2003

When you try to make an inactive resource active in Project Professional 2003, you receive an error message that is similar to the following error message:
Project Server was unable to process the request. An invalid node name parameter was specified.

The Pjprint11.dll file is not updated when you use PWA to download updated controls to the client

If you apply Project Server 2003 SP1 to Project Server 2003, the PJClient.cab file is updated. When you use PWA to download the updated controls to the client, the PJPrint11.dll file is not updated. Instead, the new version of the PJPrint11.dll file is put into a Conflict.x folder.

Tasks may not be appear when you open a project in Project Professional 2003

In Project Professional 2003, when you open an enterprise project that was not saved correctly, tasks may not appear as expected.

The CODE_UID value in the MSP_CODE_FIELDS table is not updated after you delete a value in an outline code cell

Consider the following scenario. You delete a value in an outline code cell in a sheet view. Then, you save the project. In this scenario, the corresponding CODE_UID value in the MSP_CODE_FIELDS table is not updated as expected. You expect the CODE_UID value to be deleted.

A duplicate project is created in Project Server 2003 when a project is published more than one time

When a project is published more than one time, a duplicate project is created in Project Server 2003. Additionally, an event that has a description that is similar to the following description may be logged:
<Description><![CDATA[Attempted to insert duplicate PROJ_ID (41), PROJ_TIMESTAMP (D4070900020015000E000F0008000000), IN MSP_WEB_PROJECTS]]></Description>

If you call the "FilePageSetupPage" method in a macro, the method may reset the paper size

If you call the FilePageSetupPage method in a macro, the method may reset the paper size even if the PaperSize parameter is not supplied.

Resource events are not fired in enterprise projects

If you define resource events in a macro in an enterprise project, the events are not fired when you run the macro.

Project Professional 2003 crashes when you try to print or to print preview a Resource Graph view of a large project that has zoom level that is under three months

Consider the following scenario. You have a project that contains lots of data. You view this project in the Resource Graph view. You set the zoom level of the Resource Graph view to under three months. Then, you try to print or to print preview the Resource Graph view. In this scenario, Project Professional 2003 crashes. Additionally, you receive the following error message:
Microsoft Project has encountered a problem and needs to close. We are sorry for the inconvenience.
If you click What does this error report contain, the following text appears:
Error signature
 
AppName: winproj.exe    AppVer: 11.0.2003.816    AppStamp: 3f3dfb26
ModName: winproj.exe    ModVer: 11.0.2003.816    ModStamp: 3f3dfb26
fDefug: 0    Offset: 00342e26


You receive an "You have not identified this site as a trusted site in Internet Explorer" error message when you click Issues or Risks on the Collaborate menu in Project Professional 2003

When you click Issues or Risks on the Collaborate menu in Project Professional 2003, you receive an error message that is similar to the following error message:
The page is attempting to display information from the site <URL to issues or risks page>. You have not identified this site as a trusted site in Internet Explorer. Project cannot display pages from untrusted sites. If you want this information to display inside Project, you should make the site <URL to issues or risks page> a trusted site in Internet Explorer. You should only make a site trusted if you are sure of the site's identity and you trust the site will not attempt to damage your computer or your data. Note that when you trust a site in Internet Explorer, you are trusting the entire domain to which that site belongs. For example, if you trust the site http://www.microsoft.com/widgets, you are trusting the entire http://www.microsoft.com domain.
The Issues page or the Risks page does not appear.

To resolve this issue, install Project 2003 SP2, and then modify the registry as described in the following Microsoft Knowledge Base article:
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

Code runs slower if you use code to automate Project 2003 on a multiprocessor or on a hyperthreaded computer

If you use code to automate Project 2003 on a multiprocessor or on a hyperthreaded computer, the code runs much slower than when the code runs on a single processor computer.

The values in the Actual Duration, % Complete, and Duration columns may be incorrectly set in Project Professional 2003

If you change the actual work, the values in the following columns may be incorrectly set after you resync with the protected actual work:
  • Actual Duration
  • % Complete
  • Duration

The values of the Duration column and the Work column may be incorrectly increased when you create a new project by using an .xml file

Consider the following scenario. You save an .mpp file as an .xml file. Then, you create a new project by using the .xml file. In this scenario, the values in the Duration column and in the Work column may be incorrectly increased.

Project 2003 crashes when you try to save an updated resource pool

If you update a resource pool, Project 2003 crashes when you try to save the updated resource pool.

The ActualWorkProtected field is not updated when you update a project in Project Professional 2003

When you update a project in Project Professional 2003, the ActualWorkProtected field is not updated.

The actual work is not synched in Project Professional 2003

Consider the following scenario. You click sync to protected actuals to sync a task that is 100% complete. You reenter the task's actual work. Then, you resync the task. In this scenario, the actual work that you reentered is not synched.

The work contour of the material resource collapses

If you enter actual work in a work resource assignment, the work contour of the material resource collapses when you sync the actual work. The work contour of the material resource changes so that all work is contained in the first period.

The work contour may be changed every time that a sync occurs

If you click sync to protected actuals to sync the actual work for a summary task, the work contour may be changed every time that the sync occurs.

The value of the BCWP field decreases for consecutive days on a summary task that has a Fixed Cost field

The value of BCWP field decreases for consecutive days on a summary task that has a Fixed Cost field. The BCWP field represents the budgeted cost of work performed.

Note The BCWP field is a cumulative field.

Error signature details

You may receive an error message that is similar to the following error message when you use Project 2003:
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 error report contains an error signature that is similar to one of the following error signatures:
Collapse this tableExpand this table
Application NameApplication VersionModule NameModule VersionOffset
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.816001df0f5
Winproj.exe11.0.2003.816Pj11od11.dll11.0.2003.816000261cc
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.816000ccdc8
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.81600685c3d
Winproj.exe11.1.2004.1707Ntdll.dll5.1.2600.218000010f29
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.816002b6327
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.81600054135
Winproj.exe11.0.2003.816Pj11od11.dll11.0.2003.8160000729c
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.81600009274
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.81600252474
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.81600009f2b
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.81600086a2e
Iexplore.exe6.0.2800.1106Pjgrid11.ocx11.0.2003.816000243b4
Winproj.exe11.1.2004.1707Vbe6.dll6.4.99.72001095c5
Winproj.exe11.1.2004.1707Winproj.exe11.1.2004.1707001aae60
Winproj.exe11.1.2004.1707Winproj.exe11.1.2004.1707005c7010
Winproj.exe11.1.2004.1707unknown0.0.0.00000006d
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.816001d4546
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.816001d70a2
Winproj.exe11.0.2003.816Winproj.exe11.0.2003.816001d2042
Winproj.exe11.1.2004.1707Winproj.exe11.1.2004.17070000815a
Iexplore.exe6.0.2800.1106Pjgrid11.ocx11.1.2004.17070006e115
Winproj.exe11.1.2004.1707Winproj.exe11.1.2007.17070055bd60
Iexplore.exe6.0.3790.0Pjgrid11.ocx11.1.2007.1707000395b1
Winproj.exe11.0.2004.227Winproj.exe11.0.2004.22700084d9f
Winproj.exe11.1.2004.1707Winproj.exe11.1.2004.170700087839
Note The error signature may contain other program versions, module versions, and offsets.

Properties

Article ID: 906428 - Last Review: April 4, 2006 - Revision: 1.6
APPLIES TO
  • Microsoft Office Project Professional 2003
  • Microsoft Office Project Standard 2003
Keywords: 
kbtshoot kbfix kbupdate KB906428

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com