Solved

PWA 2003 Baseline Start and Finish Columns Empty in PWA but Populated in ProjectPro

Posted on 2011-02-16
5
704 Views
Last Modified: 2013-11-15
Our PWA 2003 has several views which include a column for Baseline Start and Baseline Finish.  These are correctly populated in the MS Project 2003 client.  However, when viewed via PWA, they are empty.

These columns were working correctly until .NET 3.5 SP1 was installed.  That has since been removed (per kb  957254) and .NET 2.0 SP1 is the "highest" level of .NET installed in the farm (1 server running WSS 2.0 another running SQL Sever 2000).

Any guidance will be much appreciated.
0
Comment
Question by:mderk
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
5 Comments
 
LVL 19

Expert Comment

by:Richard Daneke
ID: 34916485
Should you have a project file with the correct baselines, re-publish to the PWA.   They appear to have been dropped in the .Net updates.
0
 

Author Comment

by:mderk
ID: 34916858
The projects have been re-published.  Those columns still are not populated in PWA.

In addition, project team members are unable to see any tasks when going to the "My Tasks" page.  Yet, the tasks are properly assigned to Enterprise Resources and are visible when viewing the entire project in PWA, as well as, in ProjectPro 2003.
0
 
LVL 1

Expert Comment

by:PrplHaz4
ID: 35092235
I don't believe the baseline values will show if the resource was not assigned to the task when the baseline was taken.

If tasks are not showing up, there are usually a few causes:
- enterprise resource booking type is set to "Proposed" on the resource sheet
- enterprise resource workgroup is set to "None" on the resource sheet
- resource My Tasks view is configured incorrectly (a filter is set, viewing "Current tasks" only...etc)
0
 

Accepted Solution

by:
mderk earned 0 total points
ID: 35415576
I appreciate the comments and suggestions.  However, nothing worked.  

So, I created a new PWA instance and had the malfunctioning projects rebuilt from scratch.  Now, tasks are visible and everything seems to be working fine.
0
 

Author Closing Comment

by:mderk
ID: 35452262
It was my own solution - start over.  That is not an excellent solution but it did work.  The key was to have the projects rebuilt, not cut & paste.  With cut & paste, the issue remained.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The vision: A MegaMenu for a SharePoint portal home page The mission: Make it easy to maintain. Allow rich content and sub headers as well as standard links. Factor in frequent changes without involving developers or a lengthy Dev/Test/Prod rel…
In case you ever have to remove a faulty web part from a page , add the following to the end of the page url ?contents=1
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question