PWA Views Column Headings Issue After Upgrading

[Charles Simpson]

Hello all

After upgrading our system to Project Server SP2a and SQL Server 2005 I have
the following issue:

For all of my views in PWA (Project Center, Resource Center, etc.) the
column headings displayed in each view that uses a custom field displays that
custom fields generic name instead of the name that I gave the columns via
the Rename button.

In our old environment, the columns would display the renamed column name.
For instance:

We created a custom column in Enterprise Global that captures a unique ID
number for each project called "Project ID." I used "Enterprise Project
Text3" to hold this project ID number. In the old environment (which has SQL
Server 2000 SP3a and Project Server without any service packs) this column
would show up in my PWA views as "Project ID."

In the new environment this same column shows up as "Enterprise Project
Text3" as the column heading on every view in PWA. If I go to edit/modify
the view, it looks correct, "Enterprise Project Text3 (Project ID)" just as
it does in the old environment.

Any help would be appreciated.

Thanks!

 

[Samer Beano]

Charles,

I faced this problem in my EPM 2003 SQL2000 environment. What made this
behaviour appear was that I created a new enterprise filed After I had my EPM
running for while (ie. had projects running for th epast 6 months). Now to
overcome this problem all I had to do was to build the olapcube and then
republish one project.

Let me know if this solves it

regards,

Samer Beano
Lead EPM Consultant

 

[Charles Simpson]

Thanks for the information and quick response Samer.

My OLAP cube is building successfully once every night and I have published
several projects to this new environment over the past few weeks. But, I did
try it again just to be sure and no luck :-(

Upon further investigation, it looks like my enterprise fields are skewed.
The Project ID field that I mentioned should be "Enterprise Project Text3
(Project ID)" and it is thus in Admin/Manage Views/Modify View section. But
on the PWA view in the Project Center the column that holds that data is
"Enterprise Project Number1" which is wrong!

All of my custom enterprise fields are wrong in the PWA views. And if I try
to create a new view and I add the column "Enterprise Project Text3 (Project
ID)" to this new view, in PWA the view shows up with the "Enterprise Project
Number1" field but with the correct data. This is weird.

Anyone have any ideas?

 

[Samer Beano]

Charles,

Are you sure you have installed SP2a rather than SP2?!!
I know that some weird behaviours occured because of SP2, some just like
what you have described.

 

[Charles Simpson]

Well ... all I can say is that I downloaded it via the SP2a page on the
Microsoft site. The filename was:
ProjectServer2003SP2a-KB887621-v2-FullFile-ENU.exe

*sigh* This really bothers me and may be a showstopper on our upgrade.

I'm going to try to backup Global from the old environment and retore it to
the new one, and restart the OLAP cube and see if that makes a difference.

 

[Gary L. Chefetz [MVP]]

Charles:

There are two other files that you must download and run. The first step in
applying SP2a is to run an SQL script to update the database structures. If
you missed this step, we'd expect all kinds of strange behavior like you're
describing. The third step is to download and install the updates for WSS.
Three separate installation steps = One Service pack applied.

 

[Charles Simpson]

Thanks Gary

Yes I applied SP2a per the instructions provided by Microsoft which included
the following files:

ProjectServer2003-KB887621-WSSFILE-ENU.EXE
ProjectServer2003SP2a-KB887621-v2-FullFile-ENU.exe
ProjectServer2003SP2-KB887621-SQLFile-ENU.EXE
wsswizup.msi

It could be that one of these steps did not "take" or I applied them
incorrectly. Here are the steps that I followed:

Instructions
Upgrade the database
It is advised that you back up your database before applying any updates. If
you do not update your database, you may experience errors when using Project
Server 2003. For more information, see the Microsoft Knowledge Base article
(903093): You receive error messages when you publish a plan or an assignment
when you work with Project Server 2002 or with Project Server 2003.

Note: You must follow the steps below for each Microsoft SQL Server and
database.
Download the SQL patch, ProjectServer2003-KB887621-SQLFile-ENU.exe or
equivalent language from the bottom of this page.
Double-click on the file to extract the files to a temporary folder.
To apply the files, Osql.exe is required in the same directory from where
Upgdb112.cmd is run or in the system path. If you are running Upgdb112.cmd
directly on the machine where the database resides, this file should already
be present. It is also available on the Project Server 2003 CD in the
\support\database folder.
Run Upgdb112.cmd against the Project Server 2003 database. If the database
is a partitioned database, run the script against each of the Project Server
2003 databases. Run Upgdb112.cmd from a command line with the following
parameters. To run from a command line, click Start > Run and type cmd in the
dialog box and click OK.

Upgdb112.cmd <sql server name> <database name> <login> <password>

OR if using Microsoft Windows authentication to SQL Server as the currently
logged in user:

Upgdb112.cmd <sql server name> <database name>


Note: By leaving off the system administrator account login and password,
the command file will assume Windows authentication to SQL Server. If you
supply only the SQL Server name, it is assumed the database name is
ProjectServer.


Install the Project Server 2003 service pack
Download the ProjectServer2003SP2a-KB887621-FullFile-v2-ENU.exe from the
bottom of the page to the Project Server 2003 machine.
Install the service pack by double-clicking on the file and following
instructions. If Project Server is distributed over multiple machines, this
update must be installed on every machine with Project Server installed.


Update the Project template files on Windows® SharePoint® Services.
If you are using Windows SharePoint Services (WSS) 2.0 with Project Server
and you have not already upgraded to Project Server 2003 SP1, you will also
want to update the Project Server template files on every server running
Windows SharePoint Services.

Download ProjectServer2003-KB887621-WSSFILE-ENU.exe from the bottom of this
page.
Double-click on the file to extract the files to a temporary folder.
From the temporary folder double-click on WSSwizup.msi to update the
template files.

Note: You do not need to update the template files if you have already done
so as part of your SP1 installation
Instructions for use:

After you install this update, use Project Server as you typically would.

 

[Gary L. Chefetz [MVP]]

Charles:

When you ran the SQL update, did you see the screen with the all the
feedback scrolling by?

 

[Charles Simpson]

Yeah ... and this update took some time to complete (about 15 minutes
according to my notes). I have a screenshot that states the following:

"Project schema tables successfully upgraded to Project Server 2003 SP2
Web schema tables successfully upgraded to Project Server 2003 SP2
View schema tables successfully upgraded to Project Server 2003 SP2

UpgDB112.cmd completed successfully!

Press any key to continue . . ."


So, I'm stumped. But I do think that this is where the problem is
regardless if it is a problem with how I did it or something on Microsofts'
end.

Thanks

 

[Gary L. Chefetz [MVP]]

Charles:

You might also try installing the Post Service Pack 2 hotfix that was
recently released. Perhaps you have a system that could use this update.
Also, make sure that you haven't used nonalphanumeric characters in your
field names or Outline code values.

 

[Renke Holert [MVP]]

Hi all,

this issue seems to be related to Project Server 2003 running on SQL Server
2005. We have the same issue. I will raise a support call.

Renke

Renke Holert, Project MVP Germany

Allocatus - Linking MS Project with Outlook and Lotus Notes
http://www.allocatus.com

 

[Gary L. Chefetz [MVP]]

Renke:

We recently ran into this problem with 2005 as well. As far as I can tell,
there isn't a fix for this yet. I think it's just hitting the radar.

 

[PJC]

A hotfix will be available in the very near future.

 

[Renke Holert [MVP]]

Hi Gary,

I just got feedback from the Microsoft engineer. The hotfix is now
available. They have created a Knowledge Article as well:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;923803

Looking forward to seeing you @ the next Project Conference,

Renke

Allocatus - Linking MS Project with Outlook and Notes
http://www.allocatus.com

Project - Das Profibuch
http://www.holert.com/project/profibuch

 

[Gary L. Chefetz [MVP]]

Renke:

Thanks.

Hi Gary,

I just got feedback from the Microsoft engineer. The hotfix is now
available. They have created a Knowledge Article as well:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;923803

Looking forward to seeing you @ the next Project Conference,

Renke

Allocatus - Linking MS Project with Outlook and Notes
http://www.allocatus.com

Project - Das Profibuch
http://www.holert.com/project/profibuch