Description of the Project Server 2003 post-Service Pack 2 hotfix package: August 15, 2006 (923802)

INTRODUCTION

This article describes the Microsoft Office Project Server 2003 issues that are fixed in the Project Server post-Service Pack 2 hotfix package that is dated August 15, 2006.

Issues that the hotfix package fixes

This hotfix package fixes the following issue:

923803 Project Web Access does not correctly display Project Server 2003 custom field titles when you run Project Server 2003 on a server that is running SQL Server 2005

This hotfix package fixes the following issue that was not previously documented in a Microsoft Knowledge Base article:
You follow these steps:

You add three resources to a new Project plan.
You assign two of those resources to the same task in the plan.
You publish the plan to a server that is running Project Server 2003.
You then log on to Project Web Access as an administrator. Under Global Permissions, you click to select the Allow check box for Delegate Tasks, and then click Save Changes.
You grant All current and future resources in the Project Server database permission to the My Tasks Category.
You log off Project Web Access, and then log on as the first resource that is assigned the task that you created in step 2.
You delegate the task to the third resource that was added in step 1.
You accept the updatee message from the resource, and then you publish the plan.
You log off as the first resource, and then log on as the second resource.
You delegate the task to the third resource that was created in step 1.
You accept the update emessage from the resource, and then you publish the plan.

When you do this, you receive spooler error 80004005.

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

The following list contains prerequisites for the hotfix package:

The optimized version of this hotfix is a post-Microsoft Office Project Server 2003 Service Pack 2a hotfix. To install the hotfix, you must have Office Project Server 2003 Service Pack 2a installed. For more information about Office 2003 SP2, click the following article number to view the article in the Microsoft Knowledge Base:
887621 Description of Office Project Server 2003 Service Pack 2a
The full-file version of this hotfix is also the administrative version of this hotfix. You can install this version of the hotfix on a computer that is running Office Project Server 2003 with Service Pack 2a or Office Project Server 2003 with Service Pack 1. However, we have tested this hotfix more extensively on Office Project Server 2003 with Service Pack 2a than on Office Project Server 2003 with Service Pack 1. If you install this hotfix on a computer that is running Office Project Server 2003 with Service Pack 1, some file conflicts might occur. We support this configuration, but we do not recommend it.

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 any registry keys or modify any registry keys to use any hotfixes that this package contains.

SQL Server stored procedure information

To make sure that all the hotfixes that this hotfix package contains are applied correctly to Project Server 2003, you must run a Microsoft SQL Server stored information update to install all Project Server updates. To do this, follow these steps:

Run the self-extracting package to extract the files to a temporary folder that you select.
If you are using SQL Server as the back end for Project Server, follow these steps for each SQL Server query file (such as Websps.sql) that is extracted to the temporary folder that you selected in step 1.
1. On the main computer that is running 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, you can exit SQL Query Analyzer.
If you are using Microsoft SQL Server 2000 Desktop Engine as the back end for Project Server, follow these steps for each SQL Server query file (such as Websps.sql) that is extracted to the temporary folder that you selected in step 1.
1. On the main computer that is running 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 if 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 SQL Server 2000 Desktop Engine by using the System Attendant account. You can also run the osql command together with another user name that has System Attendant permissions on the server.
2. When you are prompted for a password, type the password for the account that you used in step 3a, and then press ENTER. The SQL query file that you specified in step 3a runs.

Hotfix file information

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

The global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and 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.
Download information

File name	File version	File size	Date	Time	Platform
Office2003-kb923802-glb.exe	11.0.8103.0	4,268,352	15-Aug-2006	22:58	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Prjsvr.msp	Not applicable	4,808,704	15-Aug-2006	22:54	Not applicable
Secviews.sql	Not applicable	94,644	26-Apr-2005	23:26	Not applicable
Websps.sql	Not applicable	1,224,301	09-Aug-2006	18:39	Not applicable

After the hotfix package is installed, the global version of this hotfix package has the file attributes, or later file attributes, that are listed in the following table.

File name	File version	File size	Date	Time
Addmod.asp	Not applicable	71,325	14-Jun-2006	05:15
Build.inc	Not applicable	1,838	17-Jan-2006	07:46
Comcont.asp	Not applicable	114,521	14-Jul-2006	15:48
Comcont.js	Not applicable	32,363	03-Aug-2006	05:30
Entstrep.asp	Not applicable	53,307	17-Jan-2006	07:02
Grid.asp	Not applicable	17,477	14-Jul-2006	15:48
Newtskpg.asp	Not applicable	45,420	14-Jul-2006	15:48
Olapname.asp	Not applicable	7,328	14-Jun-2006	05:15
Pds.dll	11.2006.0.3117	1,260,296	17-Jan-2006	20:48
Pj11od11.dll	11.2.2006.1714	924,616	14-Jul-2006	20:56
Pj11tm11.dll	11.2.2006.1714	269,648	14-Jul-2006	19:37
Pjbusobj.dll	11.2.2006.1117	326,920	17-Jan-2006	20:48
Pjclient.cab	Not applicable	656,620	17-Jan-2006	22:15
Pjoledb.dll	11.2.2006.1714	4,238,672	14-Jul-2006	19:37
Pjreport.asp	Not applicable	43,606	14-Jul-2006	15:48
Pjsvradc.dll	11.2006.0.3117	162,568	17-Jan-2006	20:48
Portview.asp	Not applicable	45,301	14-Jul-2006	15:48
Prjres.dll	11.2.2006.1117	1,735,552	17-Jan-2006	21:52
Projolap.dll	11.2006.0.3803	301,904	03-Aug-2006	07:23
Qylibstd.sql	Not applicable	80,250	27-Sep-2005	22:22
Resregvw.asp	Not applicable	41,349	14-Jul-2006	15:48
Serconv.dll	11.2.2006.1714	641,992	14-Jul-2006	20:56
Shelfunc.js	Not applicable	8,534	14-Jul-2006	15:48
Shell.asp	Not applicable	62,029	14-Jul-2006	15:48
Svrdbdl.asp	Not applicable	51,726	17-Jan-2006	07:02
Tskpage.asp	Not applicable	56,602	14-Jul-2006	15:48
Tsktrans.asp	Not applicable	23,235	14-Jul-2006	15:48
Visonvw.asp	Not applicable	40,999	14-Jun-2006	05:16
Webclvw.asp	Not applicable	49,102	17-Jan-2006	07:02

Additional notes:

For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.

For more information about the terminology that Microsoft uses for software that is corrected 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