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

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

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 Project Server 2003 Service Pack 2a, click the following article number to view the article in the Microsoft Knowledge Base:

  887621 Description of 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 Project Server 2003 with Service Pack 2a or Project Server 2003 with Service Pack 1. However, we have tested this hotfix more extensively on Project Server 2003 with Service Pack 2a than on Project Server 2003 with Service Pack 1. If you install this hotfix on a computer that is running 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

To use one of the hotfixes in this package, you must either create a registry key or modify a registry key. For more information about the registry key, click the following article number to view the article in the Microsoft Knowledge Base:

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 to Project Server 2003, follow these steps:

1. Run the self-extracting package to extract the files in a temporary folder.
2. 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, as appropriate for your situation:
   • If you are using Microsoft SQL Server as the back end for Project Server, follow these steps:
     1. On the main server 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 executing, exit 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:
     1. On the main server 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 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 that has another user name that has system administrator permissions on the server.
     2. At the password prompt, type the password for the account that you used the command in step A, and then press ENTER. The SQL query file that you specified in step A 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 are listed in this article.

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-kb923728-glb.exe	11.0.8102.0	4,268,352	15-Aug-2006	22:01	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	21:48	Not applicable

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

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

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 differences between the two .msp files, see the "Strategies for Updating Office 2003 Installations" topic. To see this topic, visit the following Microsoft Web site:

  http://office.microsoft.com/en-us/assistance/HA011525741033.aspx

For more information about the terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base: