Microsoft has released the Microsoft Office 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 the 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
This article describes the Project Server 2003 issues that are fixed in the Project Server 2003 post-Service Pack 1 hotfix package that is dated April 20, 2005.
Issues that the hotfix package fixes
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
- Consider the following scenario. You create a new enterprise resource for an existing task. The task was created for a project that contains several unsubmitted timesheet reports that have been closed.
You then view the Tasks section on the home page of the enterprise resource. Several of the closed entries that go as far back as three months in the Tasks section display the following error message:
Your timesheet has not been submitted for the period date_range_for_time_period.
- Consider the following scenario. You create two new Resource Enterprise multivalue fields as follows:
- ResourceEnterpriseRMV2ID_#ID
- ResourceEnterpriseRMV2ID_#+1ID
When you use the ResourceCodeValuesUpdate Project Data Services (PDS) method and when you add the <AutoCheckin>1</AutoCheckin> XML tag to the ResourceCodeValuesUpdate Project Data Services (PDS) method, the ResourceEnterpriseRMV2ID_#ID field is correctly updated. However, at the same time, the ResourceEnterpriseRMV2ID_#+1ID field is incorrectly updated. Only the first field should be updated.
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:
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
- This hotfix is a post-Microsoft Office Project Server 2003 Service Pack 1 (SP1) hotfix. To install the hotfix, you must have Microsoft Office Project Server 2003 SP1 installed.
For more information about Microsoft Office Project Server 2003 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
837241Â
(http://kbalertz.com/Feedback.aspx?kbNumber=837241/
)
Description of Project Server 2003 Service Pack 1
Restart information
You do not have to restart the computer after you install this hotfix.
Hotfix replacement information
This hotfix is not replaced by any later hotfix.
Registry information
You do not have to create or modify any registry keys to enable any hotfixes that this package contains.
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 correctly applied to 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 procedures:
- If you are using Microsoft SQL Server as the back end for Project Server, follow these steps:
- On the main computer that is running 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, you can quit SQL Query Analyzer.
- If you are using SQL Server Desktop Engine, also known as MSDE 2000, as the back end for Project Server, follow these steps:
- 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 MSDE 2000 by using the System Administrator (SA) account. You can also run the osql command together with another user name that has SA permissions on the server. - 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.
Hotfix file information
This hotfix contains only those files that are required 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
Date Time Size File name
----------------------------------------------------------------------
20-Apr-2005 23:22 4,532,224 Projectserver2003-kb897706-fullfile.msp
After the hotfix is installed, 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
-----------------------------------------------------------
20-Apr-2005 23:14 1,776 Build.inc
20-Apr-2005 23:14 32,072 Comcont.js
20-Apr-2005 23:14 40,819 Dbname.inc
20-Apr-2005 23:14 53,317 Entstrep.asp
20-Apr-2005 23:15 36,670 Newtskpg.asp
20-Apr-2005 23:15 11.2005.0.1420 1,252,104 Pds.dll
20-Apr-2005 23:15 11.1.2005.1420 924,544 Pj11od11.dll
20-Apr-2005 23:15 11.1.2004.2216 265,472 Pj11tm11.dll
20-Apr-2005 23:16 11.1.2004.1813 326,400 Pjbusobj.dll
20-Apr-2005 23:16 656,186 Pjclient.cab
20-Apr-2005 23:16 11.1.2005.1317 326,408 Pjmsghlr.dll
20-Apr-2005 23:16 11.1.2004.1907 195,328 Pjnpe.dll
20-Apr-2005 23:17 11.1.2005.1328 4,234,504 Pjoledb.dll
20-Apr-2005 23:17 11.2005.0.1420 158,472 Pjsvradc.dll
20-Apr-2005 23:17 11.1.2004.1907 998,144 Pjsvrutl.dll
20-Apr-2005 23:17 11.2005.0.1218 293,640 Projolap.dll
20-Apr-2005 23:17 9,547 Rmndfunc.asp
20-Apr-2005 23:18 11.1.2004.2216 641,912 Serconv.dll
20-Apr-2005 23:18 23,464 Tsapp.asp
20-Apr-2005 23:18 50,846 Tskpage.asp
20-Apr-2005 23:18 19,075 Tssum.asp
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 the software is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates