Article ID: 885837
Article Last Modified on 4/7/2006
APPLIES TO
- Microsoft Project Server 2002
SUMMARY
Microsoft has released the Microsoft Project Server 2002 post-Service Pack 1 hotfix package for Microsoft Project Server 2002. This article describes the following items about the hotfix package:
- The issues that the hotfix package fixes
- The 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
- An SQL stored procedure update that you must run to install this Project Server update
- The files that the hotfix package contains
INTRODUCTION
This article describes the Project Server 2002 issue that is fixed in the Project Server 2002 post-Service Pack 1 hotfix package that is dated September 18, 2004.
back to the top
Issues that the hotfix package fixes
The following issue is fixed in this hotfix package. This issue was not previously documented in a Microsoft Knowledge Base article.
- Resource availability information is not updated for certain resources
You update resource availability information on the Update resource tables and OLAP cube page of Microsoft Project Web Access 2002. When you view resources on the Resource Center page, resource availablity information is not updated for certain resources. You may notice that resource availability information is not updated for resources that have higher Unique ID values. If you reduce the date range for retrieving resource availability information to a shorter time period, you no longer experience these symptoms. For example, if you reduce the date range to 6 months, you no longer experience these symptoms.
This problem occurs if the number of rowsets in the database table exceeds the maximum number of 1,048,001 elements. In this situation, Project Server 2003 does not successfully complete the update operation. This problem may occur when the both the following conditions are true:
- The date range is set to a long time period, such as 12 months.
- Lots of data must be gathered for processing.
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 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:
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
- This hotfix is a post-Project Server 2002 Service Pack 1 (SP1) hotfix. To install the hotfix, you must have Project Server 2002 SP1 installed. For additional information about Project Server 2002 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
830240 Description of Microsoft Project Server 2002 Service Pack 1
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 2002 updates
To make sure that all the fixes that this update contains are applied correctly on Project Server 2002, 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 an SQL query file.- If you are using Microsoft SQL Server as the back end for Project Server 2002, 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.
- On the Query menu, click Execute.
- When the query has finished executing, quit SQL Query Analyzer.
- If you are using SQL Server Desktop Engine (also known as MSDE 2000) as the back end for Project Server 2002, follow these steps:
- 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 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 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. - 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.
- On the main SQL server in your configuration, click Start, click Run, type osql -i
- If you are using Microsoft SQL Server as the back end for Project Server 2002, follow these steps:
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.
Date Time Size File name ----------------------------------------------------------------------- 18-Sep-2004 01:50 4,613,632 Projectserver2002-kb885837-fullfile.msp
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.
Date Time Version Size File name ----------------------------------------------------------- 16-Jul-2004 18:42 24,992 Mansts.asp 22-Apr-2004 15:47 10.2104.0.422 658,160 Pds.dll 17-Sep-2004 22:53 10.0.2104.1916 899,920 Pj10od10.dll 17-Sep-2004 23:13 10.0.2104.1916 265,456 Pj10tm10.dll 30-Aug-2004 18:42 1,336,992 Pjclient.cab 17-Sep-2004 23:13 10.0.2104.1916 4,127,984 Pjoledb.dll 22-Apr-2004 15:47 10.0.2104.1422 240,880 Pjsvrsec.dll 22-Apr-2004 15:47 10.0.2104.1422 904,432 Pjsvrutl.dll 16-Jul-2004 18:43 9,190 Rmndfunc.asp 17-Sep-2004 22:53 10.0.2104.1916 654,160 Serconv.dll 30-Aug-2004 17:45 1,106,847 Websps.sql
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
REFERENCES
For additional 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
Keywords: kbbug kbfix kbqfe kbhotfixrollup kbprojectserver2002presp2fix kbhotfixserver KB885837
