Description of the Project Server 2003 post-Service Pack 1 (SP1) hotfix package: August 18, 2004

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

On This Page

SUMMARY

Microsoft has released the Project Server 2003 post-Service Pack 1 hotfix package for Microsoft Office Project Server 2003. This article describes the following items about the hotfix package:
  • Issues that are fixed in the hotfix package
  • 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

INTRODUCTION

This article describes the Microsoft Office Project Server 2003 issues that are fixed in the Project Server 2003 post-Service Pack1 (SP1) hotfix package that is dated August 18, 2004.

Issues that are fixed in the hotfix package

The following issues are fixed in this hotfix package:
  • 838347 Other project plans are missing in Project Center after you publish your project plan to Microsoft Office Project Server 2003
  • 872819 Project Center view takes longer than expected to display projects in Microsoft Project Web Access
  • 873330 Proposed resources receive e-mail notifications from Project Sever 2003
The following issues are also fixed in this hotfix package but were not previously documented in a Microsoft Knowledge Base article:
  • Incorrect time period settings appear on the View my tasks page when you use the Managed Periods feature

    When you use the Managed Periods feature in Microsoft Project Web Access to specify time periods that resources use to report their hours worked, incorrect time period settings appear for some users who log on to Microsoft Project Web Access and view the View my tasks page in Timesheet view. This problem occurs if the user changes the time zone settings on their client computer to use a different time zone.
  • Enterprise project outline code values for a master project are incorrect when you change the master project in Microsoft Project Web Access

    When you publish a master project to Project Server 2003, log on to Microsoft Project Web Access, and then click Edit on the Project Center page, you may find that the enterprise project outline code values of the master project are unexpectedly changed to use the enterprise project outline code values of the subproject.
  • Some users are not added to Project Server 2003 when you synchronize the Enterprise Resource Pool with an Active Directory group

    After you synchronize the Enterprise Resource Pool with an Active Directory group, you may find that some users are not added to Project Server 2003. Event messages that are similar to the following are logged in the Application event log:
    Source Microsoft Project Server
    Category: None
    Type: Error
    Event ID: 2
    Description:
    Component: AD Connector
    File: AutoADProcess Line: -1
    Description: <Description><![CDATA[Accessing AD GroupName fails partially because group member -CN=UserName, cn=Users, servername, DC=com can't be resolved by LDAP]]></Description
    Source Microsoft Project Server
    Category: None
    Type: Error
    Event ID: 2
    Description:
    Component: AD Connector
    File: AutoADProcess Line: -1
    Description: <Description><![CDATA[Accessing AD group GroupName partially failed]]></Description
    This problem occurs if the group contains one or more users whose name contains a "/" character (without the quotation marks).
  • "SYSTEM ERROR (0x80004005)" error message in the Microsoft Office Project Server Spooler dialog box when you publish a project

    When you publish a project to Project Server 2003, and you use the Publish New and Changed Assignments option, you may find that a flashing red exclamation mark appears next to the Microsoft Office Project Server Spooler icon in the notification area at the far right of the taskbar. When you double-click the icon, you receive an error message that is similar to the following error message in the Error column:
    SYSTEM ERROR (0x80004005)
    Additionally, an event error message that is similar to the following may be logged in the Application event log:
    Source Microsoft Project Server
    Type: Error
    Category: None
    Description:
    Component: PjMsgHlr
    File: Path\pjmsghlr\Msghandler.cpp
    Description: <Description><![CDATA[Assert Detected. The error code was also included.]]></Description
  • Tasks are not displayed in a hierarchical structure in Microsoft Project Web Access when you use the Make the new task a subtask of option to create tasks

    When you create new tasks for a project on the Create a new task page of Microsoft Project Web Access, and you use the Make the new task a subtask of option, the tasks are not displayed in a hierarchical structure according to the outline levels of the tasks. When you view the tasks in Microsoft Project Web Access, the tasks appear to belong to the same outline level, although the tasks actually belong to different outline levels. Therefore, it may be difficult to identify the tasks that belong to different outline levels if some of the tasks have the same names or have similar names.
  • Subprojects in a master project are grouped incorrectly if you arrange the subprojects by enterprise outline code when you open the master project

    When you open a master project, and you specify that you want to arrange the subprojects in the master project by enterprise project outline code, the subprojects are grouped incorrectly in the list. This problem occurs if the subprojects in the master project use different project enterprise outline codes.

MORE INFORMATION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Office Project Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

  • This hotfix is a Project Server 2003 post-Service Pack 1 (SP1) hotfix. To install the hotfix, you must have Project Server 2003 SP1 installed.

    For more information about Project Server 2003 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
    837241 Description of Project Server 2003 Service Pack 1

Restart information

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

You do not have to create or modify any registry keys to activate any hotfixes that are contained in this package.

SQL stored procedure update that you must run to install all Microsoft Project Server updates

To make sure that all the fixes that this update contains are applied correctly on Project Server 2003, follow these steps:
  1. Run the self-extracting package to extract the files in a temporary folder that you select.
  2. For each SQL query file (such as Websps.sql) that is extracted to the temporary folder that you selected in step 1, use one of the following methods:
    • If you are using Microsoft SQL Server as the back end for Project Server 2003, follow these steps:
      1. On the main SQL server in your configuration, run SQL Query Analyzer.
      2. In the Database box, click the ProjectServer database.
      3. On the File menu, click Open, locate the SQL query file in the temporary folder that you selected in step 1, and then open the file.
      4. On the Query menu, click Execute.
      5. When the query has finished running, quit SQL Query Analyzer.
    • If you are using SQL Server Desktop Engine (also known as MSDE 2000) as the back end for Project Server 2003, follow these steps:
      1. On the main SQL server in your configuration, click Start, click Run, type osql -i tempdir\queryfile.sql -U sa in the Open box, and then click OK.

        For example, if you extracted the files in step 1 to the C:\Temp folder and the name of the query file is Websps.sql, type osql -i c:\temp\websps.sql -U sa.

        This command connects you to the local default instance of MSDE 2000 by using the system administrator (SA) account. You can also run the osql command with another user name that has SA permissions on the server.
      2. When you are prompted to enter your password, type the password for the account that you used in step a, and then press ENTER. The SQL query file that you specified in step a runs.

Hotfix file information

This hotfix contains only those files that you must have to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Download information:
  Date         Time   Size    File name
---------------------------------------------------------------------
18-Aug-2004  21:05  2,275,328  Projectserver2003-kb838882-fullfile.msp
11-Aug-2004  04:29  1,216,216  Websps.sql

Microsoft Windows Installer MSP file information:
   Date         Time   Size       File name
----------------------------------------------------------------------
18-Aug-2004  21:05  2,275,328  Projectserver2003-kb838882-fullfile.msp 


After you install the hotfix, the global version of this fix has the file attributes (or later file attributes) that are listed in the following table:
   Date         Time   Version            Size    File name
-----------------------------------------------------------
18-Aug-2004  20:59                      1,776  Build.inc
18-Aug-2004  21:00                     32,072  Comcont.js
18-Aug-2004  21:00                     40,819  Dbname.inc
18-Aug-2004  21:00                     36,670  Newtskpg.asp
18-Aug-2004  21:00  11.2004.0.1813  1,252,096  Pds.dll          
18-Aug-2004  21:01  11.1.2004.1813    924,536  Pj11od11.dll     
18-Aug-2004  21:01  11.1.2004.1813    265,472  Pj11tm11.dll     
18-Aug-2004  21:01  11.1.2004.1813    326,400  Pjbusobj.dll     
18-Aug-2004  21:01                    655,676  Pjclient.cab
18-Aug-2004  21:01  11.1.2004.1813    326,400  Pjmsghlr.dll     
18-Aug-2004  21:02  11.1.2004.1813    195,328  Pjnpe.dll        
18-Aug-2004  21:02  11.2004.0.1813    158,464  Pjsvradc.dll     
18-Aug-2004  21:02                      9,547  Rmndfunc.asp

Additional notes

  • For more information about installing this hotfix, see the Readme.txt file that the package contains.

REFERENCES

For more information about the terminology that Microsoft uses when correcting software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 838882 - Last Review: April 7, 2006 - Revision: 4.3
APPLIES TO
  • Microsoft Office Project Server 2003
Keywords: 
kboffice2003presp2fix kbqfe kbhotfixserver kbupdate kberrmsg kbprojectserver2003sp1fix kbbug kbfix kbhotfixrollup KB838882

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