Microsoft KB Archive/886964

= Description of the Microsoft Office Project Server 2003 hotfix package: October 6, 2004 =

Article ID: 886964

Article Last Modified on 4/7/2006

-

APPLIES TO


 * Microsoft Office Project Server 2003

-





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 the hotfix package fixes
 * 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



Article contents

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



INTRODUCTION
This article describes the Microsoft Office Project Server 2003 issue that is fixed in the Microsoft Office Project Server 2003 hotfix package that is dated October 6, 2004.

back to the top

Issues that are fixed in the hotfix package
The following issue is fixed in this hotfix package but was not previously documented in a Microsoft Knowledge Base article:
 * Resource availability is only published for a subset of resources when you publish large date ranges. However, resource availability publishes successfully for all resources for small date ranges.

Note This issue can occur when there are many Enterprise Resources in the Enterprise Resource pool. For example, this issue can occur if there are more than 2500 Enterprise Resources and if the date range to be published for resource availability is over 6 months. The issue can show up even if you have less than 2500 Enterprise Resources. Additionally, this issue can occur if the date range that is specified for publishing resource availability is over a very long time span. An example of a very long time span is 12 months or longer.

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 2003 Server 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
There are no prerequisites for installing this hotfix.

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 activate 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 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, 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 Microsoft 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 Microsoft 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 (SA) account. You can also run the osql command with another user name that has SA permissions on the server.</li> At the Password prompt, 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. <pre class="fixed_text">Date       Time    Size        File name - 06-Oct-2004    22:47   4,403,200   Projectserver2003-kb886964-fullfile.msp 31-Aug-2004    20:54         342   Hfps111.sql 07-Sep-2004    22: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 - 06-Oct-2004    22:41               1,776   Build.inc 06-Oct-2004    22:41              32,072   Comcont.js 06-Oct-2004     22:41              40,819   Dbname.inc 06-Oct-2004    22:42              36,670   Newtskpg.asp 06-Oct-2004    22:42   11.2004.0.1830  1,252,096   Pds.dll 06-Oct-2004    22:42   11.1.2004.2005    924,536   Pj11od11.dll 06-Oct-2004    22:42   11.1.2004.2005    265,472   Pj11tm11.dll 06-Oct-2004    22:42   11.1.2004.1813    326,400   Pjbusobj.dll 06-Oct-2004    22:43             655,676   Pjclient.cab 06-Oct-2004    22:43   11.1.2004.1813    326,400   Pjmsghlr.dll 06-Oct-2004    22:43   11.1.2004.1907    195,328   Pjnpe.dll 06-Oct-2004    22:43   11.1.2004.2005  4,230,400   Pjoledb.dll 06-Oct-2004    22:43   11.2004.0.1830    158,464   Pjsvradc.dll 06-Oct-2004    22:44   11.1.2004.1907    998,144   Pjsvrutl.dll 06-Oct-2004    22:44               9,547   Rmndfunc.asp 06-Oct-2004    22:44   11.1.2004.2005    641,912   Serconv.dll 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">