Microsoft KB Archive/896103

= Description of the Microsoft Office Project Server 2003 post-Service Pack 1 hotfix package: March 18, 2005 =

Article ID: 896103

Article Last Modified on 4/7/2006

-

APPLIES TO


 * Microsoft Office Project Server 2003

-





SUMMARY
''Microsoft has released the Microsoft Project Server 2003 post-Service Pack 1 hotfix package for Microsoft Office Project Server 2003. This article describes the following information about the hotfix package:''


 * Issues that the hotfix package fixes
 * Prerequisites for installing the hotfix package
 * Information about whether you must restart your computer after you install the hotfix package
 * Information about whether the hotfix package is replaced by any other hotfix package
 * Information about whether you must make any registry changes to use one or more of the hotfixes in the package
 * Files that the hotfix package contains



Article contents
 INTRODUCTION  === Issues that the hotfix package fixes ===   MORE INFORMATION  === Hotfix information ===

 ==== Prerequisites ====  ==== Restart information ==== </li> ==== Hotfix replacement information ==== </li> ==== Registry information ==== </li> ==== The SQL stored procedure update that you must run to install all Project Server updates ==== </li> ==== Hotfix file information ==== </li></ul> </li></ul> </li> REFERENCES</li></ul>

<div class="summary_section">

INTRODUCTION
This article describes the Microsoft Office Project Server 2003 issues that are fixed in the Project Server 2003 post-Service Pack 1 hotfix package that is dated March 18, 2005.

back to the top

Issues that the hotfix package fixes
This hotfix package fixes the following issue:  

894478 Total availability for all resources is incorrectly calculated and displayed in Microsoft Project Web Access

</li></ul>

This hotfix package also fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:  Tasks are assigned to a resource. When the resource views these tasks in Microsoft Project Web Access, duplicate tasks are assigned to the resource. Additionally, the duplicate tasks may have an incorrect Actual Work value. This problem may occur if the following conditions are true:  The resource assigns the task to himself in Microsoft Project Web Access.</li> The project manager assigns the task to the resource in Microsoft Office Project 2003 and then republishes the project plan.</li></ul> </li>  You try to save and to publish a project plan that contains a task that has many interruptions. (This kind of task is known as a split task.) However, the project plan is not published. Additionally, the following event is logged in the Project Server 2003 event log: Event Type: Error

Event Source: Microsoft Project Server Tracing Event log Provider

Event Category: None

Event ID:

Date:

Time:

User: NT AUTHORITY\LOCAL SERVICE

Computer:

Description:

File: C:\Office\dev\project\WebClient\source\utility\pjadorsutil2.cpp

Line: 438

Error Number: 0x80040e2f

Description: Assert Detected. The error code was also included.

___________________________________

Component: Microsoft OLE DB provider for SQL Server

Description: Cannot insert duplicate key row in object 'MSP_VIEW_PROJ_TASKSPLITS' with unique index 'PK_MSP_VIEW_PROJ_TASKSPLITS'. </li> You use the PDSTest tool to update a project plan. To do this, you use the AssignmentCalls method instead of the PDSCalls method. The project manager has already accepted some updates. However, these updates are included again in the task changes that are submitted by the project plan resources.</li> When you try to group your assigned tasks in Microsoft Project Web Access by using a custom enterprise task outline code field, the tasks are moved to the bottom of your assigned tasks list. The tasks are arranged in no particular order.</li> <li> When you click Update Now to synchronize an Active Directory group with the enterprise resource pool in Project Server 2003, Active Directory users who have either an opening bracket ([) or a closing bracket (]) in their display name are not synchronized. When this behavior occurs, you receive the following error message:

The Active Directory group partially failed to synchronize with the Enterprise Resource Pool on  at

Additionally, the following event is logged in the Project Server 2003 event log of each user whose display name did not synchronize: Event Type: Warning

Event Source: Microsoft Project Server Tracing Event log Provider

Event Category: None

Event ID: 1

Date:

Time:

User: NT AUTHORITY\LOCAL SERVICE

Computer:

Description:

Component: AD Connector

File: AutoADProcess

Line: -1

Description: AD Res Pool Sync - PDS ADD Res failed : ADDISPLAYNAME </li> <li>When you view your assigned tasks in Microsoft Project Web Access, you may see duplicate assigned tasks. This issue may occur after the Project Server 2003 post-Service Pack 1 hotfix package that is dated February 10, 2005 is applied to your Project Server 2003 computer.</li></ul>

back to the top

<div class="moreinformation_section">

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.

back to the top

Prerequisites
You must have Microsoft Office Project Server 2003 Service Pack 1 (SP1) installed to apply this hotfix.

For more information about how to obtain Microsoft Office Project Server 2003 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

873458 How to obtain the latest service pack for Project Server 2003

back to the top

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

back to the top

Hotfix replacement information
This hotfix is not replaced by any later hotfix.

back to the top

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

back to the top

The SQL stored procedure update that you must run to install all Project Server updates
To make sure that all the fixes that this update contains are applied correctly on Project Server 2003, follow these steps: <ol> <li>Run the self-extracting package to extract the files in a temporary folder that you select.</li> <li>For each SQL query file, such as the Websps.sql file, that is extracted to the temporary folder that you selected in step 1, use one of the following steps: <ul> <li>If you are using Microsoft SQL Server as the back end for Project Server, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>On the main SQL server in your configuration, run SQL Query Analyzer.</li> <li>In the Database box, click the ProjectServer database.</li> <li>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.</li> <li>On the Query menu, click Execute.</li> <li>When the query has finished running, quit SQL Query Analyzer.</li></ol> </li> <li>If you are using SQL Server Desktop Engine, also known as MSDE 2000, as the back end for Project Server, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>On the main SQL server in your configuration, click Start, click Run, type osql -i \ .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 SA account. You can also run the osql command with another user name that has SA permissions on the server.</li> <li>When you are prompted for 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.</li></ol> </li></ul> </li></ol>

back to the top

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 <pre class="fixed_text">  Date         Time   Version         Size       File name --  18-Mar-2005  06:23  11.0.2005.7517  4,359,920  Projectserver2003-kb896103-fullfile.exe

Microsoft Windows Installer .msp file information <pre class="fixed_text">  Date         Time   Size       File name --  18-Mar-2005  06:22  4,531,200  Projectserver2003-kb896103-fullfile.msp 28-Jan-2005 00:20      1,034  Hfps111.sql 07-Feb-2005 21:16  1,216,339  Websps.sql After you install the hotfix, the global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. <pre class="fixed_text">  Date         Time   Version         Size       File name ---  18-Mar-2005  06:14                      1,776  Build.inc 18-Mar-2005 06:14                     32,072  Comcont.js   18-Mar-2005  06:15                     40,819  Dbname.inc 18-Mar-2005 06:15                     53,317  Entstrep.asp 18-Mar-2005 06:15                     36,670  Newtskpg.asp 18-Mar-2005 06:15  11.2005.0.1301  1,252,104  Pds.dll 18-Mar-2005 06:15  11.1.2005.1127    924,544  Pj11od11.dll 18-Mar-2005 06:16  11.1.2004.2216    265,472  Pj11tm11.dll 18-Mar-2005 06:16  11.1.2004.1813    326,400  Pjbusobj.dll 18-Mar-2005 06:16                    656,186  Pjclient.cab 18-Mar-2005 06:16  11.1.2005.1317    326,408  Pjmsghlr.dll 18-Mar-2005 06:17  11.1.2004.1907    195,328  Pjnpe.dll 18-Mar-2005 06:17  11.1.2005.1310  4,230,408  Pjoledb.dll 18-Mar-2005 06:17  11.2005.0.1301    158,472  Pjsvradc.dll 18-Mar-2005 06:17  11.1.2004.1907    998,144  Pjsvrutl.dll 18-Mar-2005 06:17  11.2005.0.1218    293,640  Projolap.dll 18-Mar-2005 06:18                      9,547  Rmndfunc.asp 18-Mar-2005 06:18  11.1.2004.2216    641,912  Serconv.dll 18-Mar-2005 06:18                     23,464  Tsapp.asp 18-Mar-2005 06:18                     50,846  Tskpage.asp 18-Mar-2005 06:19                     19,075  Tssum.asp Note For more information about how to install this hotfix, see the Readme.txt file that is included in the package.

back to the top

<div class="references_section">