Cannot Save Baselines

[pheslar]

We are using Project Server 2007 and have an enterprise template that we have
used for several months without issue. After I recently made some changes
to this template (adding tasks and changing predecessors) and resaved,
project managers can now no longer save protected baselines on a project they
create from this template. They get an error that says: "Cannot clear or
save baselines 0-5. You do not have adequate permissions." I did not alter
their permissions in any way, and they are still able to save baselines on
any other project, just not ones they create from the newest version of this
enterprise template. I checked to make sure there was no baseline data in
the template, and there was not. Even so, I tried checking the box to omit
any existing baseline data and then resaving, but that did not help. Any
ideas what I may have done and how I can fix it?

 

[Jonathan Sofer]

Is it a specific set of users that cannot save baseline 0-5? What happens
when you attempt to save baseline 0-5 on these new projects as an
administrator?

Since "Save Protected Baseline" is a category permission, I could see how it
could only apply to certain projects for a user and not all projects. If I
were you, I would do some analysis of your group/category permissions for
those users and see why the "Save Protected Baseline" is not Allowed for
them on the new project created from the template. It could be that they
are not marked as the owners of the new projects or they are not members of
the project team or do not have assignments, etc.

Jonathan

 

[pheslar]

This affects all users in our Project Managers group. The permission "Save
Protected Baseline" is allowed for the category associated with the Project
Managers group. The category allows this for all projects where "the user is
the project owner or the user is the Status Manager on assignments within the
project". I confirmed, via Project Center, that the users are the "Project
Owner" on the appropriate projects. I did not alter the permissions, but
altered the template itself when the issue began. It's still allowing them
to do other things that are only allowed by the "the user is the project
owner..." relationship within the same category (open, save, publish, etc.).

As administrator, I can save a protected baseline from a project created
with this template. I can also cause the PM to able to do so by changing
their category project list from "the user is the project owner..." to "all
current & future projects..." This implies to me that they are not actually
the Project Owner, but then how are they managing to open, save, publish,
etc.?

 

[Jonathan Sofer]

I can't begin to analyze your security setup as it can get very complicated
very quickly. What I can say is that there was a known bug around the
"Owner" field category rule for some of the category permissions so maybe
you are encountering this bug with the "Save Protected Baseline" rule in the
PM group.

Things to consider:
1) Have you validated that other then the PMs being the "Owners", are they
the Status Manager of at least one assignment in the projects? They might
not be if the project was created from the template, which was another know
bug.
2) When you say that you altered the template itself but not the
permissions, makes me wonder if you have not yet applied the new template to
the PM/My Project relationship. Changing the template alone will not do
anything.
3) The fact that they can Open, Save, Publish, etc, does not mean that they
are able to do this because of their PM group membership. They could be
assigned to other security groups that give them these rights, (i.e Team
Members, Resource Managers, Executives, Portfolio Managers, etc). Or they
could have permissions assigned to them at the user level. Be sure users
don't have permissions at the user level or category associations at the
user level as this will complicate things for you.

Jonathan

 

[Dale Howard [MVP]]

pheslar --

A long time ago I noticed that the My Personal Projects category seems to
interfere with the Save Protected Baseline permission. I would recommend
that you remove the My Personal Projects category from the Project Managers
group and see if this resolves the issue. Let us know what you find.

 

[pheslar]

Thank you guys for all of your suggestions. I was not able to solve the
issue so I finally developed a workaround by creating a new category/group
that allows PMs to save baselines on any project. Since our environment only
allows the owner to open a project, it's impossible for someone to save a
baseline on a project they shouldn't.