Lookup table values changing to "1"

M

Mike

In our Project Server 2007 environment (SP1 only), we're starting to
have issues with our lookup tables. When either creating a new lookup
table, adding new options to existing tables, or modifying existing
values, the entered value is being changed to a "1". Also, we are
unable to indent/outdent lookup tables. What's interesting is that
we're still able to use custom fields with lookup tables just fine (in
Proj Pro or PWA) and the selected values are being pushed to the
Reporting Database. So it seems our only problem is maintining lookup
tables.

I have saved one lookup table after seeing this issue (thinking it's
only a display problem). Unfortunately, after saving, all values in
that lookup table were promptly deleted. Lucky for me, it was a new
lookup table that wasn't being used yet.

I did take the 4 Project Server databases and created a new instance
in a VPC environment and sure enough, I can maintain lookup tables as
expected and all the values exist just fine (indent/outdent, add new,
etc.. no problem). So, I'm not sure that the issue is with the
Project Server databases/tables.

We're also getting ready to install the Infrastructure Update but I'd
like to see this resolved before we do that. Frankly, I'm reluctant
to do much to the environment without getting a clear understanding to
what this problem is and seeing it fixed.

Has anyone seen this before and/or is there a resolution?

Thanks!
-- Mike
 
M

Mike

Hi Gary..

Thanks for the suggestion. I went ahead and deleted the cache files
(that Proj Pro uses), all the IE cache/cookie files, and removed and
reinstalled the Project Server ActiveX controls. Unfortunately, the
problem persists.

-- Mike
 
G

Gary L. Chefetz

Mike:

Start > Run (Start > Search on Vista)
Enter %appdata%
Navigate to Microsoft > MS Project
Delete everything under that folder

Did you do this?

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com


Hi Gary..

Thanks for the suggestion. I went ahead and deleted the cache files
(that Proj Pro uses), all the IE cache/cookie files, and removed and
reinstalled the Project Server ActiveX controls. Unfortunately, the
problem persists.

-- Mike
 
G

Gary L. Chefetz

Mike:

I'm fairly certain that these issues were all resolved by the August update.
You should move off of SP1 and get the latest, December Cumulative Update.
Expect another update later this month.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com


Yes, I did do exactly that. BTW, the problem is within PWA. Aren't
the %appdata% cache files used solely by Project Pro? Also, for more
fun, I tried checking on the lookup tables directly from the App
server in PWA. Same issue there as well.

I see someone else has this same issue, unfortunately, no resolution/
update:
http://www.microsoft.com/communitie...048-8604-7408dbe2a873&lang=en&cr=US&sloc=&p=1

-- Mike
 
B

Ben Howard

Hi Mike,

This is an issue seen alot in Pro, which is why Gary took you down this
route. Clearing the cache effects Pro only as you've stated. There were
certainly some display bugs pre-sp1, but it appears you may have something a
little more in-depth issues with actual data corruption. I would install the
IU and test after that, the problem may we resolve itself.


--
Thanks, Ben.

Please rate this post if it helped.
http://appleparkltd.spaces.live.com/
 
M

Mike

Thanks Gary and Ben..

We definately want to install the current updates. It sounds like you
both agree that they could be installed successfully even with this
issue in place as it is today. I've ran into other issues when
installing updates with known system problems in the past (hence my
reluctance to just throw an update at the problem).

We currently have downtime scheduled for the update about 2 weeks from
now. I'll post back afterwards to how the update went and if our
issues are fixed.

Thanks again guys!
-- Mike
 
M

Mike

Quick update here.. after further analysis, turns out not all tables
in the databases are at the same version (using "select * from
versions"). A hotfix was applied back in December that seems to be
the culprit. We'll be applying the Infrastructure Update later this
week to get everything back in line. I'll post back our results when
we're done. Wish us luck! :)

-- Mike
 
M

Mike

Success! Applying the Infrastructure Update got our system back in
line. The lookup tables can now be modified and don't change new
values to a "1" anymore. Also, the database versions are now at the
same level.

-- Mike
 
G

Gary L. Chefetz

Mike:

Glad to hear it. Think about changing your pace at keeping up with the
updates to Project Server. This is one application where the benefits of
being aggressive about this seem to consistently outweigh the risk.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com


Success! Applying the Infrastructure Update got our system back in
line. The lookup tables can now be modified and don't change new
values to a "1" anymore. Also, the database versions are now at the
same level.

-- Mike
 
M

Mike

Hi Gary..

I completely agree! So many nice fixes have come to us through these
update packages (and they just keep getting better and better).

Thanks again!
-- Mike
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top