Description of the Project Server 2003 post-Service Pack 2a hotfix package: June 16, 2006 (921115)

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 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 Project Server 2003 Service Pack 2a hotfix. To install the hotfix, you must have Project Server 2003 Service Pack 2a installed. For more information about Project Server 2003 Service Pack 2a, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart your computer after you apply this .

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

You do not have to create any registry keys or modify any registry keys to use any hotfixes that this package contains.

Information about the SQL stored procedure update that you must run to install all Project Server 2003 updates

To make sure that all the fixes that this hotfix contains are applies correctly to Project Server 2003, follow these steps:

1. Run the self-extracting package to extract the files to a temporary folder that you select.
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 2003, follow these steps:
     1. On the main SQL Server server in your configuration, run SQL Query Analyzer.
     2. In the Database box, click ProjectServer.
     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 SQL Server server in your configuration, click Start, click Run, type osql -iTemporaryFolderName\SQLQueryFileName .sql -U sa in the Open box, and then click OK .
        
        For example, suppose that you extract the files in step 1 to the C:\Temp folder, and that the name of the query file is Websps.sql. In this scenario, type osql -i c:\temp\websps.sql -U sa.
        
        This command connects you to the local default instance of MSDE 2000 by using the sa account. You can also run the osql command by using another user name that has sa permissions on the server.
     2. When you are prompted for the 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.

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 this article lists.
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
Office2003-kb921115-glb.exe	11.0.8031.0	4,156,224	16-Jun-2006	21:16

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time
Prjsvr.msp	Not applicable	4,628,992	16-Jun-2006	21:15
Secviews.sql	Not applicable	94,644	27-Apr-2005	01:26
Websps.sql	Not applicable	1,224,247	13-Jun-2006	16:31

After the hotfix is installed, the global version of this hotfix 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
Addmod.asp	Not applicable	71,325	14-Jun-2006	07:15
Build.inc	Not applicable	1,838	17-Jan-2006	09:46
Entstrep.asp	Not applicable	53,307	17-Jan-2006	09:02
Olapname.asp	Not applicable	7,328	14-Jun-2006	07:15
Pds.dll	11.2006.0.3117	1,260,296	17-Jan-2006	22:48
Pj11od11.dll	11.2.2006.1517	924,616	17-May-2006	20:13
Pj11tm11.dll	11.2.2006.1517	269,648	17-May-2006	18:57
Pjbusobj.dll	11.2.2006.1117	326,920	17-Jan-2006	22:48
Pjclient.cab	Not applicable	656,620	18-Jan-2006	00:15
Pjoledb.dll	11.2.2006.1614	4,231,680	14-Jun-2006	08:09
Pjsvradc.dll	11.2006.0.3117	162,568	17-Jan-2006	22:48
Prjres.dll	11.2.2006.1117	1,735,552	17-Jan-2006	23:52
Projolap.dll	11.2006.0.3614	290,816	14-Jun-2006	08:09
Qylibstd.sql	Not applicable	80,250	28-Sep-2005	00:22
Serconv.dll	11.2.2006.1517	641,992	17-May-2006	20:13
Svrdbdl.asp	Not applicable	51,726	17-Jan-2006	09:02
Visonvw.asp	Not applicable	40,999	14-Jun-2006	07:16
Webclvw.asp	Not applicable	49,102	17-Jan-2006	09:02

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 terminology that Microsoft uses for software that is corrected after it is released, click the following article number to view the article in the Microsoft Knowledge Base: