Enterprise fields display wrong name

[Adrienne]

Hello,

This issue involves Project Server 2003. The back end is SQL Server 2005
and the server is Windows 2003 SP2.

Here is the problem:
1. A project admin created Enterprise custom fields (Enterprise Text 1
under name “Review by†and Enterprise Task Outline Code 1 under name “Reviewâ€
).
2. The project admin added these columns to a work plan and assigned values
to them (i.e. Review and Review By).
3. The project admin saved and published the plan. However, when the
Timesheet view was opened in PWA, the names of the Enterprise columns were
incorrect:
instead of “Review†and “Review by†there are “Finish7†and “Number19â€.


Here are the steps I've taken to try to solve the problem:
Part 1: Create and add enterprise fields

1. Ensured that the custom fields were created in the global template
(Global.mpt)
2. Ensured that the fields were added to the plan (Tracking Gantt view)
3. Ensured that the fields were added to the Timesheet View via PWA
4. Ensured that the Custom Fields were included for the work plan (Tools >
Customize > Published Fields > Ensured fields are added to 'Fields in the
Tasks View')

Part 2: Unprotect timesheets

1. Opened Admin - Server Configuration
2. In the section "Select the features that you want to make available to
users in Project Web Access", unchecked the Approve checkbox and checked the
Deny checkbox for the following actions:
a. "Approve time sheets for resources"
b. "Timesheet Approval"
3. Saved changes.
4. Opened Admin - Customize Project Web Access
5. In the section "Time period settings", selected the "Non Managed
Periods" radio button
6. Clicked Save Changes

Part 3: Republish assignments

1. From Projects, opened the MSPP file
2. Clicked on Collaboration - Publish - Republish Assignments. Clicked OK
to save the project first.
3. Made sure "Overwrite actual work entered by resources" was checked.
4. Clicked OK.

Part 4: Reprotect timesheets

1. Go back to PWA - Under Admin - Server Configuration, switch the check
boxes from Deny to Approve for
a. "Approve time sheets for resources"
b. "Timesheet Approval"
2. Saved changes, then open Admin - Customize PWA.
3. In the section "Time period settings", selected the "Managed Periods"
radio button.
4. Saved changes.

I saw a similar post from 2006 where Dale said that this might be related to
SQL Server 2005. I haven't been able to find any follow-up information on
this.

Any and all help would be greatly appreciated. Thanks in advance.

 

[Jack Dahlgren]

Which Project Server service pack is installed?

-Jack Dahlgren

 

[Adrienne]

It's MSPP 2003 Service Pack 3.

 

[Dale Howard [MVP]]

Adrienne --

I think you went to way too much work trying to fix this problem, but your
persistence will be rewarded because you posted your problem in this
newsgroup. The problem is due to your organization's use of SQL Server
2005 with Project Server 2003. Refer to the following URL for the fix
needed from Microsoft:

http://support.microsoft.com/kb/923803/en-us

Hope this helps.

 

[Adrienne]

Haha, thanks Dale!
The strangest thing is, it worked once, and then when I logged back in to
show someone else how I fixed the problem, the column names had changed back.
(I had a screen shot to prove that I had fixed it, so I didn't look like a
total idiot...)
Anyway, I don't have enough permissions on the actual server itself to look
at the Project Server service pack level. I could only look at the MSPP 2003
service pack level.

 

[Dale Howard [MVP]]

Adrienne --

I believe you. Contact your network people ASAP to determine the latest SP
level for your Project Server 2003 system. SP3 is current and should be
installed on both Project Server 2003 and Project Professional 2007, if not
currently installed. Hope this helps.

 

[Adrienne]

Project Professional 2003 already has SP3. However, the server team ran into
some problems installing Project Server 2003 SP3, so they had to roll back to
SP2a. They're going to readdress the issue within the next few business
days, so hopefully they'll get it right the second time. Thanks for all of
your help with this!

 

[Dale Howard [MVP]]

Adrienne --

I think this probably explains the source of the problem! You are more
than welcome for the help, my friend.

 

[BJMillerPWA]

All,
I have had the same situation as Adrienne, except as the administrator I was
able to install the SP3 update on Project Server 2003 last night without a
snag. However, the issue of it displaying the wrong columns where enterprise
fields are supposed to be still exists. Any other ideas? Does something
need to happen after the upgrade? I followed the instructions on the MS site
for downloading and installing (i.e. I downloaded the upgdb113.cmd and
relevant .sql files and upgraded our databases to sp3, then ran the sp3
upgrade on PS2k3 which had sp2 on it up until now).
Thank you in advance!
-BJ

 

[BJMillerPWA]

I answered my own question...just in case anyone else has this problem I'll
post what I did. All I had to do was publish a project and the fields went
back to normal (post SP3 upgrade). I tried that because the MS site said
that some have noticed that publishing had problems after the SP3 upgrade, so
I tried it, checked, and the columns went back to normal.
Thanks!
-BJ