This article describes the Microsoft Office Project Server 2003 issues that are fixed in the Project Server 2003 post-Service Pack 3 hotfix package that is dated January 24, 2008.
List of issues fixed
This hotfix package fixes the following issue:
935758Â
(http://kbalertz.com/Feedback.aspx?kbNumber=935758/
)
Error message when you try to build an OLAP cube on the Project Server 2003 server that is running SQL Server 2005 Analysis Services: "Errors in the OLAP storage engine: The attribute key cannot be found"
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
An error is logged in the Application log when you use PWA to synchronize a domain group that contains empty nested groups
When you work in an Active Directory environment in which there are empty nested groups in a domain group, and you use Microsoft Office Project Web Access (PWA) to synchronize the domain group, the synchronization is completed successfully. However, the following unexpected error is logged in the Application log:
Description: <Description><![CDATA[Accessing AD group LDAP://CN=PSAdministrators,CN=Users,DC=Domain,DC=com failed due to error -2147463155-The directory property cannot be found in the cache.
]]></Description>
Description: <Description><![CDATA[Accessing AD group ProjectServerUsers partially failed]]></Description>
A custom outline code that is blank after you edit it does not show in a custom view
Consider the following scenario:
- You create a custom view in Microsoft Office Project Web Access (PWA).
- You add a custom outline code as a resource. This custom outline code is a required field.
- You edit the resource in the Resource Center.
- You do not add a value in the custom outline code.
- The custom outline code field is blank.
- You save and close the resource, and then you open the custom view.
In this scenario, the blank edited resource does not appear as expected.
The text areas in a status report appear as red Xs on a Windows Vista-based computer
When you create a status report in Microsoft Office Project Web Access (PWA), and then you run PWA on a Windows Vista-based computer, the text areas in the status report do not appear as expected. Instead, these text areas appear as red Xs. Or, in the text area, you receive a message that states that the object cannot be loaded.
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
This hotfix package is a post Project Server 2003 Service Pack 3 hotfix package. To install the hotfix package, you must have Project Server 2003 Service Pack 3 installed.
For more information about Project Server 2003 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
873458Â
(http://kbalertz.com/Feedback.aspx?kbNumber=873458/
)
How to obtain the latest service pack for Project Server 2003
Restart information
You do not have to restart the computer after you apply this hotfix package.
Hotfix replacement information
This hotfix package is not replaced by any later hotfix package.
Registry information
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
File information
This hotfix package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to correct the issues that are listed in this article.
The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the 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
Collapse this tableExpand this table
| File name | File version | File size | Date | Time |
|---|
| Office2003-kb940809-glb.exe | 11.0.8203.0 | 4,358,712 | 24-Jan-2008 | 22:20 |
Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
| File name | File size | Date | Time |
|---|
| Prjsvr.msp | 4,871,680 | 24-Jan-2008 | 22:20 |
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:
Collapse this tableExpand this table
| File name | File version | File size | Date | Time |
|---|
| Addmod.asp | Not Applicable | 71,325 | 29-May-2007 | 05:04 |
| Build.inc | Not Applicable | 1,838 | 29-May-2007 | 05:52 |
| Comcont.asp | Not Applicable | 102,055 | 29-May-2007 | 05:04 |
| Comcont.js | Not Applicable | 32,363 | 29-May-2007 | 05:04 |
| Entstrep.asp | Not Applicable | 53,338 | 21-Sep-2007 | 18:42 |
| Func.inc | Not Applicable | 3,885 | 21-Sep-2007 | 18:42 |
| Grid.asp | Not Applicable | 17,477 | 14-Jul-2006 | 15:48 |
| Instsk.asp | Not Applicable | 15,584 | 21-Sep-2007 | 18:42 |
| Newtskpg.asp | Not Applicable | 37,326 | 29-May-2007 | 05:05 |
| Olapname.asp | Not Applicable | 7,328 | 14-Jun-2006 | 05:15 |
| Paststrp.asp | Not Applicable | 38,612 | 21-Sep-2007 | 18:42 |
| Pds.dll | 11.2007.0.3921 | 1,262,680 | 21-Sep-2007 | 22:32 |
| Pj11od11.dll | 11.3.2007.1921 | 951,504 | 21-Sep-2007 | 22:32 |
| Pj11tm11.dll | 11.3.2007.1529 | 280,496 | 29-May-2007 | 06:48 |
| Pjbusobj.dll | 11.3.2007.1529 | 329,136 | 29-May-2007 | 06:48 |
| Pjclient.cab | Not Applicable | 666,836 | 29-May-2007 | 06:52 |
| Pjoledb.dll | 11.3.2007.1921 | 4,322,904 | 21-Sep-2007 | 22:32 |
| Pjreport.asp | Not Applicable | 43,606 | 14-Jul-2006 | 15:48 |
| Pjsvradc.dll | 11.2007.0.3921 | 164,952 | 21-Sep-2007 | 22:31 |
| Portview.asp | Not Applicable | 41,280 | 29-May-2007 | 05:05 |
| Prjres.dll | 11.3.2007.1529 | 1,738,160 | 29-May-2007 | 08:02 |
| Projolap.dll | 11.2007.0.3529 | 304,560 | 29-May-2007 | 06:48 |
| Qylibstd.sql | Not Applicable | 80,250 | 27-Sep-2005 | 22:22 |
| Resregvw.asp | Not Applicable | 34,922 | 29-May-2007 | 05:05 |
| Restempl.htm | Not Applicable | 3,422 | 30-Apr-2007 | 22:36 |
| Restpchs.htm | Not Applicable | 3,651 | 30-Apr-2007 | 22:36 |
| Serconv.dll | 11.3.2007.1529 | 685,608 | 29-May-2007 | 08:02 |
| Shelfunc.js | Not Applicable | 8,534 | 14-Jul-2006 | 15:48 |
| Shell.asp | Not Applicable | 54,296 | 21-Sep-2007 | 18:42 |
| Svrdbdl.asp | Not Applicable | 51,726 | 17-Jan-2006 | 07:02 |
| Tredtcon.asp | Not Applicable | 3,464 | 21-Sep-2007 | 18:42 |
| Tskpage.asp | Not Applicable | 51,034 | 29-May-2007 | 05:05 |
| Tsktrans.asp | Not Applicable | 23,235 | 14-Jul-2006 | 15:48 |
| Visonvw.asp | Not Applicable | 41,149 | 29-May-2007 | 05:05 |
| Webclvw.asp | Not Applicable | 49,102 | 29-May-2007 | 05:05 |