new project name appears on server, but not on PWA Project Center

[Bob Zapf]

I did a "Save As" to save an image of a project on the server in order to
make some adjustments to the schedule. After completing the "Save As"
operation, I was in the new image of the project (I could see the new name at
the top of the screen). I then published all information from the
Collaborate / Publish" tab, clicked the "Save" icon, then did a "File /
Close".

I launched PWA and went to the Project Center, and selected the Summary View
to see all projects on the server. However, the new project name does not
appear in the list. So, I go back to the Server and do an "Open" and see the
list of projects. I see the new name in this list, AND the new project is
still checked out to me even though I had closed it. I go back to PWA, click
"Check in my projects" and check it in. Still can not see it in Project
Center. I then go to Admin and "Clean up Project Server data base". I find
the new project name is in this list, and delete it.

What could be going wrong that I do not see the new project in Project
Center? What do I need to do to get this fixed?

 

[Dale Howard [MVP]]

Bob --

Did you save the project as an alternate version? By this I mean that when
you clicked File - Save As, you selected an alterate version from the
Version pick list. If this is the case, you must click Collaborate -
Publish - Project Plan to force the new version to appear in the Project
Center page in PWA. Let us know if this helps.

 

[Bob Zapf]

Dale, Thank you for the prompt reply as this appears to be a problem of
increasing frequency. We are not using versioning, so the only item in my
Version pick list is Published. However, I did try Collaborate - Publish -
Project Plan, it did not work, I still don't see it in Project Center.

Incidently, any time I go into the new project and save it, then do File -
Close, the server leaves the project checked out to me.

 

[Gary L. Chefetz [MVP]]

Bob:

Are you doing this Save As operation on a plan that already exists in
Project Server? If so, you're taking an action you shouldn't take. If this
is the case, please explain why you're doing this and the business problem
this action is intended to solve, and perhaps we can recommend a better
approach.

 

[Bob Zapf]

Hello Gary, Thank you for replying. Yes, this Save As operation is on a plan
that already exists on the server. Had no idea this is an action I shouldn't
take as our implementation vendor trained us in this method to replan and
re-baseline a project. We use Earned Value Management, and sometimes the
project under goes so many changes that the Performance Management Baseline
needs to be updated in order to measure performance. So, the project manager
must continue to measure performance in the currently executing schedule
while at the same time posturing a re-planned schedule. Making a copy of the
currently executing resource loaded schedule to use as a starting point for
the replan is quite handy.

Could you provide technical background for why this isn't a good action and
recommend a better approach? Also, is there a workaround or solution for our
present predicament?

Thanks again!

 

[Gary L. Chefetz [MVP]]

Bob:

My problem with this approach is that the binary record of a cloned project
forever reflects its origins. The system recognizes clones as "previously
published" projects. It makes me nervous having two "dot-published" versions
of the same project in the system. I'm more in favor of using either an mpp
file or an official version in the system for replanning. Call your system
version "Replan" Use the more tedious delete the old, and bring in the new
approach using Import Project to Enterprise which allows you to preserve
your project name as well. I also recommend a baseline preservation
methodology leveraging the multi-baseline capability in Project.

So, to solve your immediate issue, try Collaborate > Publish > Republish all
assignments selecting to overwrite the actual work in the timesheets. Make
sure your remove the prior version of the plan before you republish the new.
You might want to uncheck the notify resources check box. Keep in mind that
your new project, as far as the system is concerned, is a previously
published project, so it doesn't see the assignments in the plan as
requiring any publish action even though you changed the name of the
project.

 

[Bob Zapf]

Gary:

Thank you for the information. Where does one get this type of information
- I have the wall charts of the MS Project server and client data
structures, but where/how might one get their hands on a "principles of
operation" manual?

I tried the Collaborate > Publish > Republish, but the project still does
not show in the Project Center directory list, and it still remains checked
out to me no matter what. What might we try next?

 

[Gary L. Chefetz [MVP]]

Bob:

I'd try saving as an mpp file, deleting the project on the server, and then
use the import wizard to bring the project back onto the server. Use the
republish on it and let us know how that goes.

 

[Bob Zapf]

Gary,

We couldn't delete the project on the server because it is the currently
executing project. Too much risk exposure if we messed that one up. So I
renamed a version of the project that had been saved the first week of May
and imported it OK. It was not left checked out to me, and I could see it in
the Project Center. That went so well that I deleted it off the server, and
tried the same thing with a the version that had been saved the second week
of May to get a little closer to the current state of the project - but the
problems surfaced again. So, I deleted that one, and reimported the version
that worked. However, just prior to reimporting the project file that worked
OK, I exited out of MS Project Pro and relaunched it. I have to wonder
wheither it would have still imported OK had I not bounced the application on
my desktop. Anyhow, that's where we are now. Thanks for all your attention,
information, and help. Regards!