Microsoft KB Archive/891296

= Description of the Microsoft Project Server 2003 post-Service Pack 1 hotfix package: December 16, 2004 =

Article ID: 891296

Article Last Modified on 4/7/2006

-

APPLIES TO


 * Microsoft Office Project Server 2003

-





SUMMARY
''Microsoft has released the Microsoft Office Project Server 2003 post-Service Pack 1 hotfix package for 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

 * SUMMARY
 * Issues that are fixed in the hotfix package
 * Hotfix information
 * Prerequisites
 * Restart information
 * Hotfix replacement information
 * Registry information
 * SQL stored procedure update that you must run to install all Project Server updates
 * Hotfix file information
 * REFERENCES



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

back to the top

Issues that the hotfix package fixes
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
 * When you run a query on an Enterprise database that contains a Project Enterprise Cost custom field that has a value of 21,400,000.00 or more, the query may not return records that contain the custom field.


 * When you type information in a status report in Microsoft Project Web Access, the name of the status report does not appear on the EnterStatusReport.asp page. For example, this issue may occur when you type information in a past due status report.

back to the top



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
To install this hotfix, you must have Microsoft Project Server 2003 Service Pack 1 (SP1) installed.

For additional information about how to obtain Microsoft 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 to modify any registry keys to enable any hotfixes that are contained in this package.

back to the top

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 Office Project Server 2003, follow these steps:  Run the self-extracting package to extract the files in a temporary folder that you select. For each SQL query file that is extracted to the temporary folder that you selected in step 1, use one of the following procedures.

Note For example, Websps.sql is a SQL query file.  If you are using Microsoft SQL Server as the back end for Project Server, follow these steps:  On the main SQL server in your configuration, run SQL Query Analyzer. In the Database box, click the ProjectServer database. 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> On the Query menu, click Execute.</li> When the query has finished running, quit SQL Query Analyzer.</li></ol> </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;"> 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 System Administrator account. You can also run the osql command by using another user name that has System Administrator permissions on the server.</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 --  16-Dec-2004  21:24  11.0.2004.7216  4,267,240  Projectserver2003-kb891296-fullfile.exe MSP file information <pre class="fixed_text">  Date         Time   Size       File name --  16-Dec-2004  21:23  4,433,920  Projectserver2003-kb891296-fullfile.msp 31-Aug-2004 18:54        342  Hfps111.sql 07-Sep-2004 20:24  1,216,250  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 ---  16-Dec-2004  21:16                      1,776  Build.inc 16-Dec-2004 21:16                     32,072  Comcont.js   16-Dec-2004  21:17                     40,819  Dbname.inc 16-Dec-2004 21:17                     53,317  Entstrep.asp 16-Dec-2004 21:17                     36,670  Newtskpg.asp 16-Dec-2004 21:17  11.2004.0.2105  1,252,096  Pds.dll 16-Dec-2004 21:17  11.1.2004.2216    924,536  Pj11od11.dll 16-Dec-2004 21:18  11.1.2004.2216    265,472  Pj11tm11.dll 16-Dec-2004 21:18  11.1.2004.1813    326,400  Pjbusobj.dll 16-Dec-2004 21:18                    656,186  Pjclient.cab 16-Dec-2004 21:18  11.1.2004.1813    326,400  Pjmsghlr.dll 16-Dec-2004 21:18  11.1.2004.1907    195,328  Pjnpe.dll 16-Dec-2004 21:19  11.1.2004.2216  4,234,496  Pjoledb.dll 16-Dec-2004 21:19  11.2004.0.2105    158,464  Pjsvradc.dll 16-Dec-2004 21:19  11.1.2004.1907    998,144  Pjsvrutl.dll 16-Dec-2004 21:19                      9,547  Rmndfunc.asp 16-Dec-2004 21:19  11.1.2004.2216    641,912  Serconv.dll 16-Dec-2004 21:20                     23,464  Tsapp.asp 16-Dec-2004 21:20                     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">