Microsoft Knowledge Base Email Alertz

Project Web Access does not correctly display Project Server 2003 custom field titles when you run Project Server 2003 on a server that is running SQL Server 2005

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Project Web Access does not correctly display Project Server 2003 custom field titles when you run Project Server 2003 on a server that is running SQL Server 2005

Article ID: 923803

On This Page

SYMPTOMS

Microsoft Office Project Web Access does not correctly display Microsoft Office Project Server 2003 custom field titles. This occurs when you run Project Server 2003 on a server that is running Microsoft SQL Server 2005.

Consider the following scenario. In Microsoft Office Project Professional 2003, you connect to the server that is running Project Server 2003. You rename the title of the Enterprise Project Text 1 field to My Custom Text Field. Then, you assign the renamed field to a custom Project Center view in Project Web Access. In this scenario, the renamed custom field has a random custom field name for the title. This new name does not match the name that you assigned to the field. Also, the name does not match the original field name.

Note This problem only affects implementations of Project Server 2003 that use SQL Server 2005.

RESOLUTION

This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest Project Server 2003 service pack, you do not have to install the hotfix.

Service pack information

This problem is corrected in Project Server 2003 Service Pack 3. To resolve this problem, obtain the latest service pack for Project Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
873458 How to obtain the latest service pack for Project Server 2003

Hotfix information

How to obtain the hotfix

This issue is fixed in the Office Project Server 2003 Hotfix Package. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
923802 Description of the Project Server 2003 post-Service Pack 2 hotfix package: August 15, 2006
After you apply the hotfix package to Project Server 2003, you must republish at least one project to update the Project Center views in Project Web Access. After you do this, the correct custom field titles appear in the Project Web Access Project Center views.

MORE INFORMATION

For more information about Project Server 2003 in a SQL Server 2005 environment, click the following article numbers to view the articles in the Microsoft Knowledge Base:
921116 Error message when you try to build an OLAP cube in a deployment of Project Server 2003 that uses SQL Server 2005 Analysis Services: "Could not connect to the OLAP server specified"
917401 Error messages when you run the Setup program for Project Server 2003: "Error 25624. Failed to execute SQL String" and "Installation ended prematurely"

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This problem was first corrected in Project Server 2003 Service Pack 3.

Properties

Article ID: 923803 - Last Review: October 9, 2011 - Revision: 3.0
Keywords: 
kbprojectserver2003sp3fix kbexpertiseinter kbqfe kbbug kbfix KB923803
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate