Cannot assign a Project Manager as a project owner

[oldbradfordian]

We are running PWA 2007 and have a very frustrating problem that is impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs to
change the project owner for each to a designated Project Manager once it is
determined who will be the project manager for the new project. There is also
an occasional need to change the project owner during a project as projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the project
owner. When a project manager is selected from the list of users (in the Edit
Project Properties screen), an "Unknown error has occurred" message is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the reasons why
not, we just aren't setup that way). [A related question I have: How does the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update and Save)
capabilities on project they own, but only to have Read (= Open) access to
projects they do not own (they need this to create cross-project links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and they
should not be able to save a project if they are not the project owner; but
they should be able to just open it in MS Project Pro so that they can create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[Jonathan Sofer [MVP]]

Have you installed SP1 and Infrastructure Update? Do you have any project
level custom fields with graphical indicators?

 

[Ben Howard]

Hello OldBradfordian,

Make sure that you are on the latest SP and Infrastructure Update, both for
server and client. Hopefully that will deal with the error you are getting.

In terms of how to change a PM, check out this link on my blog
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=4&ayear=2008

In terms of setting the correct PM permissions, you'll need to figure that
out - but this should get you started.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=5&ayear=2008

Check out the my org category and you'll find it is redundant if you have no
RBS set up.

 

[oldbradfordian]

Yes, we have SP1 and the Infrastructure update installed, and we have
enterprise custom fields defined that show up in all new projects. The field
values in the custom fields can be changed in the project's 'Edit Project
Properties' screen by the Admin who is still the project owner. The only
thing we cannot do is change the project owner.

I do notice that if I give the Project Managers the 'Save project to Project
Server' permission, then we can assign them as the owner of a new project;
but then they can also edit and save projects that they do not own, which is
bad!

Thanks.

Have you installed SP1 and Infrastructure Update? Do you have any project
level custom fields with graphical indicators?

We are running PWA 2007 and have a very frustrating problem that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs to
change the project owner for each to a designated Project Manager once it
is
determined who will be the project manager for the new project. There is
also
an occasional need to change the project owner during a project as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the project
owner. When a project manager is selected from the list of users (in the
Edit
Project Properties screen), an "Unknown error has occurred" message is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the reasons
why
not, we just aren't setup that way). [A related question I have: How does
the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update and
Save)
capabilities on project they own, but only to have Read (= Open) access to
projects they do not own (they need this to create cross-project links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and they
should not be able to save a project if they are not the project owner;
but
they should be able to just open it in MS Project Pro so that they can
create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[oldbradfordian]

Hi, Ben:

I already setup something similar to what you describe in your blogs.

I have two categories assigned to the Project Manager group:
Category 1: "My Projects" - Projects for which they are the Owner, matched
with comprehensive permissions to open and save projects, etc.
Category 2: "All Projects - restricted rights" - allowed to Open ALL
projects but not save them.

I can only assign them as a project manager for newly created project if I
enable the 'Save project' permission for Category 2. But that defeats what I
am trying to accomplish, and sets all the project managers to have the
Project Manager role for all projects!

Thanks for trying to help.

The Project Manager Template

Hello OldBradfordian,

Make sure that you are on the latest SP and Infrastructure Update, both for
server and client. Hopefully that will deal with the error you are getting.

In terms of how to change a PM, check out this link on my blog.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=4&ayear=2008

In terms of setting the correct PM permissions, you'll need to figure that
out - but this should get you started.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=5&ayear=2008

Check out the my org category and you'll find it is redundant if you have no
RBS set up.
--
Thanks, Ben.

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

We are running PWA 2007 and have a very frustrating problem that is impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs to
change the project owner for each to a designated Project Manager once it is
determined who will be the project manager for the new project. There is also
an occasional need to change the project owner during a project as projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the project
owner. When a project manager is selected from the list of users (in the Edit
Project Properties screen), an "Unknown error has occurred" message is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the reasons why
not, we just aren't setup that way). [A related question I have: How does the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update and Save)
capabilities on project they own, but only to have Read (= Open) access to
projects they do not own (they need this to create cross-project links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and they
should not be able to save a project if they are not the project owner; but
they should be able to just open it in MS Project Pro so that they can create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[Jonathan Sofer [MVP]]

I was aware of this as a bug pre-SP1 but I thought they fixed it with SP1

http://support.microsoft.com/kb/937908/
http://support.microsoft.com/kb/942387/en-us

Yes, we have SP1 and the Infrastructure update installed, and we have
enterprise custom fields defined that show up in all new projects. The
field
values in the custom fields can be changed in the project's 'Edit Project
Properties' screen by the Admin who is still the project owner. The only
thing we cannot do is change the project owner.

I do notice that if I give the Project Managers the 'Save project to
Project
Server' permission, then we can assign them as the owner of a new project;
but then they can also edit and save projects that they do not own, which
is
bad!

Thanks.

Have you installed SP1 and Infrastructure Update? Do you have any
project
level custom fields with graphical indicators?

message

We are running PWA 2007 and have a very frustrating problem that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs to
change the project owner for each to a designated Project Manager once
it
is
determined who will be the project manager for the new project. There
is
also
an occasional need to change the project owner during a project as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the
project
owner. When a project manager is selected from the list of users (in
the
Edit
Project Properties screen), an "Unknown error has occurred" message is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the
reasons
why
not, we just aren't setup that way). [A related question I have: How
does
the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update and
Save)
capabilities on project they own, but only to have Read (= Open) access
to
projects they do not own (they need this to create cross-project links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and
they
should not be able to save a project if they are not the project owner;
but
they should be able to just open it in MS Project Pro so that they can
create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[Gary L. Chefetz]

Oldbradfordian:

You have found one of the catch 22's in the system. You must enable the Save
permisison or you cannot change the owner value to that PM. I suggest that
you create a "change owner" category and have the Administrator move
projects into that category to enable a PM to take over the project. Not
much more manual work then you're already doing.

--
----------
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, Ben:

I already setup something similar to what you describe in your blogs.

I have two categories assigned to the Project Manager group:
Category 1: "My Projects" - Projects for which they are the Owner, matched
with comprehensive permissions to open and save projects, etc.
Category 2: "All Projects - restricted rights" - allowed to Open ALL
projects but not save them.

I can only assign them as a project manager for newly created project if I
enable the 'Save project' permission for Category 2. But that defeats what
I
am trying to accomplish, and sets all the project managers to have the
Project Manager role for all projects!

Thanks for trying to help.

The Project Manager Template

Hello OldBradfordian,

Make sure that you are on the latest SP and Infrastructure Update, both
for
server and client. Hopefully that will deal with the error you are
getting.

In terms of how to change a PM, check out this link on my blog.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=4&ayear=2008

In terms of setting the correct PM permissions, you'll need to figure
that
out - but this should get you started.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=5&ayear=2008

Check out the my org category and you'll find it is redundant if you have
no
RBS set up.
--
Thanks, Ben.

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

We are running PWA 2007 and have a very frustrating problem that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs to
change the project owner for each to a designated Project Manager once
it is
determined who will be the project manager for the new project. There
is also
an occasional need to change the project owner during a project as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the
project
owner. When a project manager is selected from the list of users (in
the Edit
Project Properties screen), an "Unknown error has occurred" message is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the
reasons why
not, we just aren't setup that way). [A related question I have: How
does the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update and
Save)
capabilities on project they own, but only to have Read (= Open) access
to
projects they do not own (they need this to create cross-project links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and
they
should not be able to save a project if they are not the project owner;
but
they should be able to just open it in MS Project Pro so that they can
create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[oldbradfordian]

Jonathan:

I think you are referring specifically to this issue listed as fixed in SP1:

"You cannot view all potential owners in the Owners list on the Edit Project
Properties page. You can see only the users who have permission to save
projects."

My problem is not that I cannot see the names of the project managers; their
names all appear in the selection list, but if I select one of them to be the
owner then I get an error when I try to save the change unless they have
permissions to save all projects.

Thanks.

I was aware of this as a bug pre-SP1 but I thought they fixed it with SP1

http://support.microsoft.com/kb/937908/
http://support.microsoft.com/kb/942387/en-us

Yes, we have SP1 and the Infrastructure update installed, and we have
enterprise custom fields defined that show up in all new projects. The
field
values in the custom fields can be changed in the project's 'Edit Project
Properties' screen by the Admin who is still the project owner. The only
thing we cannot do is change the project owner.

I do notice that if I give the Project Managers the 'Save project to
Project
Server' permission, then we can assign them as the owner of a new project;
but then they can also edit and save projects that they do not own, which
is
bad!

Thanks.

Have you installed SP1 and Infrastructure Update? Do you have any
project
level custom fields with graphical indicators?

message
We are running PWA 2007 and have a very frustrating problem that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs to
change the project owner for each to a designated Project Manager once
it
is
determined who will be the project manager for the new project. There
is
also
an occasional need to change the project owner during a project as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the
project
owner. When a project manager is selected from the list of users (in
the
Edit
Project Properties screen), an "Unknown error has occurred" message is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the
reasons
why
not, we just aren't setup that way). [A related question I have: How
does
the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update and
Save)
capabilities on project they own, but only to have Read (= Open) access
to
projects they do not own (they need this to create cross-project links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and
they
should not be able to save a project if they are not the project owner;
but
they should be able to just open it in MS Project Pro so that they can
create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[oldbradfordian]

Thanks, gary.

One drawback to this is that anytime anyone goes into change a category
there is always a risk that something will get messed up (inadvertently) -
all it takes is to click a wrong box, for example, in the complex web that is
permissions.

Do you know if category changes are reflected instantly across all existing
users and projects?

After assigning the PM as you describe, can or should the project then be
removed from this category?

I'll try this and see how it works.

Thanks.

Oldbradfordian:

You have found one of the catch 22's in the system. You must enable the Save
permisison or you cannot change the owner value to that PM. I suggest that
you create a "change owner" category and have the Administrator move
projects into that category to enable a PM to take over the project. Not
much more manual work then you're already doing.

--
----------
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, Ben:

I already setup something similar to what you describe in your blogs.

I have two categories assigned to the Project Manager group:
Category 1: "My Projects" - Projects for which they are the Owner, matched
with comprehensive permissions to open and save projects, etc.
Category 2: "All Projects - restricted rights" - allowed to Open ALL
projects but not save them.

I can only assign them as a project manager for newly created project if I
enable the 'Save project' permission for Category 2. But that defeats what
I
am trying to accomplish, and sets all the project managers to have the
Project Manager role for all projects!

Thanks for trying to help.

The Project Manager Template

Hello OldBradfordian,

Make sure that you are on the latest SP and Infrastructure Update, both
for
server and client. Hopefully that will deal with the error you are
getting.

In terms of how to change a PM, check out this link on my blog.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=4&ayear=2008

In terms of setting the correct PM permissions, you'll need to figure
that
out - but this should get you started.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=5&ayear=2008

Check out the my org category and you'll find it is redundant if you have
no
RBS set up.
--
Thanks, Ben.

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



:

We are running PWA 2007 and have a very frustrating problem that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs to
change the project owner for each to a designated Project Manager once
it is
determined who will be the project manager for the new project. There
is also
an occasional need to change the project owner during a project as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the
project
owner. When a project manager is selected from the list of users (in
the Edit
Project Properties screen), an "Unknown error has occurred" message is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the
reasons why
not, we just aren't setup that way). [A related question I have: How
does the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update and
Save)
capabilities on project they own, but only to have Read (= Open) access
to
projects they do not own (they need this to create cross-project links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and
they
should not be able to save a project if they are not the project owner;
but
they should be able to just open it in MS Project Pro so that they can
create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[Gary L. Chefetz]

Jonathan:

Just because it bugs the hell out of us, doesn't mean it's a bug. I'd call
it a design flaw and I'm not aware of any plans to change it.<g> What have
you heard?

--
----------
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

I was aware of this as a bug pre-SP1 but I thought they fixed it with SP1

http://support.microsoft.com/kb/937908/
http://support.microsoft.com/kb/942387/en-us

Yes, we have SP1 and the Infrastructure update installed, and we have
enterprise custom fields defined that show up in all new projects. The
field
values in the custom fields can be changed in the project's 'Edit Project
Properties' screen by the Admin who is still the project owner. The only
thing we cannot do is change the project owner.

I do notice that if I give the Project Managers the 'Save project to
Project
Server' permission, then we can assign them as the owner of a new
project;
but then they can also edit and save projects that they do not own, which
is
bad!

Thanks.

Have you installed SP1 and Infrastructure Update? Do you have any
project
level custom fields with graphical indicators?

message
We are running PWA 2007 and have a very frustrating problem that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs
to
change the project owner for each to a designated Project Manager once
it
is
determined who will be the project manager for the new project. There
is
also
an occasional need to change the project owner during a project as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the
project
owner. When a project manager is selected from the list of users (in
the
Edit
Project Properties screen), an "Unknown error has occurred" message is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the
reasons
why
not, we just aren't setup that way). [A related question I have: How
does
the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update and
Save)
capabilities on project they own, but only to have Read (= Open)
access to
projects they do not own (they need this to create cross-project links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and
they
should not be able to save a project if they are not the project
owner;
but
they should be able to just open it in MS Project Pro so that they can
create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[Gary L. Chefetz]

When you make changes to permissions, it sets off a queue job to synchronize
the users. When users are "in-session" on the system, they often need to log
off and close the application (either IE or Project) to pickup the new
permissions when they open and log back on. And, yes, the projects should be
removed from the category after the PM picks up the project.

--
----------
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

Thanks, gary.

One drawback to this is that anytime anyone goes into change a category
there is always a risk that something will get messed up (inadvertently) -
all it takes is to click a wrong box, for example, in the complex web that
is
permissions.

Do you know if category changes are reflected instantly across all
existing
users and projects?

After assigning the PM as you describe, can or should the project then be
removed from this category?

I'll try this and see how it works.

Thanks.

Oldbradfordian:

You have found one of the catch 22's in the system. You must enable the
Save
permisison or you cannot change the owner value to that PM. I suggest
that
you create a "change owner" category and have the Administrator move
projects into that category to enable a PM to take over the project. Not
much more manual work then you're already doing.

--
----------
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


message

Hi, Ben:

I already setup something similar to what you describe in your blogs.

I have two categories assigned to the Project Manager group:
Category 1: "My Projects" - Projects for which they are the Owner,
matched
with comprehensive permissions to open and save projects, etc.
Category 2: "All Projects - restricted rights" - allowed to Open ALL
projects but not save them.

I can only assign them as a project manager for newly created project
if I
enable the 'Save project' permission for Category 2. But that defeats
what
I
am trying to accomplish, and sets all the project managers to have the
Project Manager role for all projects!

Thanks for trying to help.

The Project Manager Template
:

Hello OldBradfordian,

Make sure that you are on the latest SP and Infrastructure Update,
both
for
server and client. Hopefully that will deal with the error you are
getting.

In terms of how to change a PM, check out this link on my blog.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=4&ayear=2008

In terms of setting the correct PM permissions, you'll need to figure
that
out - but this should get you started.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=5&ayear=2008

Check out the my org category and you'll find it is redundant if you
have
no
RBS set up.
--
Thanks, Ben.

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



:

We are running PWA 2007 and have a very frustrating problem that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs
to
change the project owner for each to a designated Project Manager
once
it is
determined who will be the project manager for the new project.
There
is also
an occasional need to change the project owner during a project as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the
project
owner. When a project manager is selected from the list of users (in
the Edit
Project Properties screen), an "Unknown error has occurred" message
is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the
reasons why
not, we just aren't setup that way). [A related question I have: How
does the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update
and
Save)
capabilities on project they own, but only to have Read (= Open)
access
to
projects they do not own (they need this to create cross-project
links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and
they
should not be able to save a project if they are not the project
owner;
but
they should be able to just open it in MS Project Pro so that they
can
create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[oldbradfordian]

Thank you, Gary. Very helpful info.

When you make changes to permissions, it sets off a queue job to synchronize
the users. When users are "in-session" on the system, they often need to log
off and close the application (either IE or Project) to pickup the new
permissions when they open and log back on. And, yes, the projects should be
removed from the category after the PM picks up the project.

--
----------
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

Thanks, gary.

One drawback to this is that anytime anyone goes into change a category
there is always a risk that something will get messed up (inadvertently) -
all it takes is to click a wrong box, for example, in the complex web that
is
permissions.

Do you know if category changes are reflected instantly across all
existing
users and projects?

After assigning the PM as you describe, can or should the project then be
removed from this category?

I'll try this and see how it works.

Thanks.

Oldbradfordian:

You have found one of the catch 22's in the system. You must enable the
Save
permisison or you cannot change the owner value to that PM. I suggest
that
you create a "change owner" category and have the Administrator move
projects into that category to enable a PM to take over the project. Not
much more manual work then you're already doing.

--
----------
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


message
Hi, Ben:

I already setup something similar to what you describe in your blogs.

I have two categories assigned to the Project Manager group:
Category 1: "My Projects" - Projects for which they are the Owner,
matched
with comprehensive permissions to open and save projects, etc.
Category 2: "All Projects - restricted rights" - allowed to Open ALL
projects but not save them.

I can only assign them as a project manager for newly created project
if I
enable the 'Save project' permission for Category 2. But that defeats
what
I
am trying to accomplish, and sets all the project managers to have the
Project Manager role for all projects!

Thanks for trying to help.

The Project Manager Template
:

Hello OldBradfordian,

Make sure that you are on the latest SP and Infrastructure Update,
both
for
server and client. Hopefully that will deal with the error you are
getting.

In terms of how to change a PM, check out this link on my blog.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=4&ayear=2008

In terms of setting the correct PM permissions, you'll need to figure
that
out - but this should get you started.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=5&ayear=2008

Check out the my org category and you'll find it is redundant if you
have
no
RBS set up.
--
Thanks, Ben.

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



:

We are running PWA 2007 and have a very frustrating problem that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs
to
change the project owner for each to a designated Project Manager
once
it is
determined who will be the project manager for the new project.
There
is also
an occasional need to change the project owner during a project as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the
project
owner. When a project manager is selected from the list of users (in
the Edit
Project Properties screen), an "Unknown error has occurred" message
is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the
reasons why
not, we just aren't setup that way). [A related question I have: How
does the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update
and
Save)
capabilities on project they own, but only to have Read (= Open)
access
to
projects they do not own (they need this to create cross-project
links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and
they
should not be able to save a project if they are not the project
owner;
but
they should be able to just open it in MS Project Pro so that they
can
create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[oldbradfordian]

Gary:

I implemented the new category, and it works if our IT PWA Administrator
follows the process of adding the new project to the new category, then
changing the project owner, then removing the project out of the new category.

However, when our Project Administrator (not full Admin rights, but close to
it) tries this procedure, they can open the Category page, select the new
project, and add it to the list on the right, BUT they cannot then save the
Category. Instead, they get a red error message "An unknown error...".

Can you tell me what other permissions our Project Admin needs in order to
be able to save the Category? They already have the "Manage Security"
permission explicitly enabled.

Many thanks in advance.

Thank you, Gary. Very helpful info.

When you make changes to permissions, it sets off a queue job to synchronize
the users. When users are "in-session" on the system, they often need to log
off and close the application (either IE or Project) to pickup the new
permissions when they open and log back on. And, yes, the projects should be
removed from the category after the PM picks up the project.

--
----------
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

Thanks, gary.

One drawback to this is that anytime anyone goes into change a category
there is always a risk that something will get messed up (inadvertently) -
all it takes is to click a wrong box, for example, in the complex web that
is
permissions.

Do you know if category changes are reflected instantly across all
existing
users and projects?

After assigning the PM as you describe, can or should the project then be
removed from this category?

I'll try this and see how it works.

Thanks.

:

Oldbradfordian:

You have found one of the catch 22's in the system. You must enable the
Save
permisison or you cannot change the owner value to that PM. I suggest
that
you create a "change owner" category and have the Administrator move
projects into that category to enable a PM to take over the project. Not
much more manual work then you're already doing.

--
----------
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


message
Hi, Ben:

I already setup something similar to what you describe in your blogs.

I have two categories assigned to the Project Manager group:
Category 1: "My Projects" - Projects for which they are the Owner,
matched
with comprehensive permissions to open and save projects, etc.
Category 2: "All Projects - restricted rights" - allowed to Open ALL
projects but not save them.

I can only assign them as a project manager for newly created project
if I
enable the 'Save project' permission for Category 2. But that defeats
what
I
am trying to accomplish, and sets all the project managers to have the
Project Manager role for all projects!

Thanks for trying to help.

The Project Manager Template
:

Hello OldBradfordian,

Make sure that you are on the latest SP and Infrastructure Update,
both
for
server and client. Hopefully that will deal with the error you are
getting.

In terms of how to change a PM, check out this link on my blog.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=4&ayear=2008

In terms of setting the correct PM permissions, you'll need to figure
that
out - but this should get you started.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=5&ayear=2008

Check out the my org category and you'll find it is redundant if you
have
no
RBS set up.
--
Thanks, Ben.

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



:

We are running PWA 2007 and have a very frustrating problem that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and then needs
to
change the project owner for each to a designated Project Manager
once
it is
determined who will be the project manager for the new project.
There
is also
an occasional need to change the project owner during a project as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change the
project
owner. When a project manager is selected from the list of users (in
the Edit
Project Properties screen), an "Unknown error has occurred" message
is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into the
reasons why
not, we just aren't setup that way). [A related question I have: How
does the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open, Update
and
Save)
capabilities on project they own, but only to have Read (= Open)
access
to
projects they do not own (they need this to create cross-project
links
between their own project and another project they don't own but are
dependent on). They should not be able to create a new project, and
they
should not be able to save a project if they are not the project
owner;
but
they should be able to just open it in MS Project Pro so that they
can
create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[oldbradfordian]

Gary,

We still get the following error when our Project Admin clicks 'Save' to
save the Change Project Owner category:

"The category could not be saved due to the following reasons:
An unknown error has occured "

We do not see any ULS log entries generated when the error occurs. We have
SharePoint diagnostics logging set to High.

Using the Effective Rights tool shows the following rights for the 2 groups
the Project Admin belongs to:
Group Name 'Project Managers' = blank
Group Name 'Project Management Admins' = Allow
But the Effective Right shows as 'Deny'. Why is this? The are two settings,
one is explicit Allow and the other is blank.

This is not making sense to me.

Thanks for your support.

It would be easier to determine what's going on if you had a look at the ULS
logs when the user takes this action. You might want to run the effective
rights tool, or experiment by enabling other permission combinations.
Without knowing the full secuirty setup, it's impossible to speculate.

--
----------
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

Gary:

I implemented the new category, and it works if our IT PWA Administrator
follows the process of adding the new project to the new category, then
changing the project owner, then removing the project out of the new
category.

However, when our Project Administrator (not full Admin rights, but close
to
it) tries this procedure, they can open the Category page, select the new
project, and add it to the list on the right, BUT they cannot then save
the
Category. Instead, they get a red error message "An unknown error...".

Can you tell me what other permissions our Project Admin needs in order to
be able to save the Category? They already have the "Manage Security"
permission explicitly enabled.

Many thanks in advance.

Thank you, Gary. Very helpful info.

:

When you make changes to permissions, it sets off a queue job to
synchronize
the users. When users are "in-session" on the system, they often need
to log
off and close the application (either IE or Project) to pickup the new
permissions when they open and log back on. And, yes, the projects
should be
removed from the category after the PM picks up the project.

--
----------
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


message
Thanks, gary.

One drawback to this is that anytime anyone goes into change a
category
there is always a risk that something will get messed up
(inadvertently) -
all it takes is to click a wrong box, for example, in the complex web
that
is
permissions.

Do you know if category changes are reflected instantly across all
existing
users and projects?

After assigning the PM as you describe, can or should the project
then be
removed from this category?

I'll try this and see how it works.

Thanks.

:

Oldbradfordian:

You have found one of the catch 22's in the system. You must enable
the
Save
permisison or you cannot change the owner value to that PM. I
suggest
that
you create a "change owner" category and have the Administrator move
projects into that category to enable a PM to take over the project.
Not
much more manual work then you're already doing.

--
----------
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


message
Hi, Ben:

I already setup something similar to what you describe in your
blogs.

I have two categories assigned to the Project Manager group:
Category 1: "My Projects" - Projects for which they are the Owner,
matched
with comprehensive permissions to open and save projects, etc.
Category 2: "All Projects - restricted rights" - allowed to Open
ALL
projects but not save them.

I can only assign them as a project manager for newly created
project
if I
enable the 'Save project' permission for Category 2. But that
defeats
what
I
am trying to accomplish, and sets all the project managers to have
the
Project Manager role for all projects!

Thanks for trying to help.

The Project Manager Template
:

Hello OldBradfordian,

Make sure that you are on the latest SP and Infrastructure
Update,
both
for
server and client. Hopefully that will deal with the error you
are
getting.

In terms of how to change a PM, check out this link on my blog.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=4&ayear=2008

In terms of setting the correct PM permissions, you'll need to
figure
that
out - but this should get you started.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=5&ayear=2008

Check out the my org category and you'll find it is redundant if
you
have
no
RBS set up.
--
Thanks, Ben.

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



:

We are running PWA 2007 and have a very frustrating problem
that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and then
needs
to
change the project owner for each to a designated Project
Manager
once
it is
determined who will be the project manager for the new project.
There
is also
an occasional need to change the project owner during a project
as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to change
the
project
owner. When a project manager is selected from the list of
users (in
the Edit
Project Properties screen), an "Unknown error has occurred"
message
is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into
the
reasons why
not, we just aren't setup that way). [A related question I
have: How
does the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open,
Update
and
Save)
capabilities on project they own, but only to have Read (=
Open)
access
to
projects they do not own (they need this to create
cross-project
links
between their own project and another project they don't own
but are
dependent on). They should not be able to create a new project,
and
they
should not be able to save a project if they are not the
project
owner;
but
they should be able to just open it in MS Project Pro so that
they
can
create
cross-project links to its tasks.

How can this be accomplished with minimum pain?

Thank you for any help you can provide.

 

[oldbradfordian]

Explicit allow for:

Admin:
Manage Security
Manage Status Reports
Manage Users and Groups
Manage Windows SharePoint Services
General:
(all items)
Project:
Build Team on New Project
Change Project State
New Project
Open Project Template
Save Unprotected Baseline
Resource:
(all items)
Status Reports:
(all items)
Time and Task Management:
(all items except Manage Rules)
Views:
all items

Seems like this should allow them to change and save the category.

???

What is the Global permission set you gave to the Project Admins Group?

--
----------
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

Gary,

We still get the following error when our Project Admin clicks 'Save' to
save the Change Project Owner category:

"The category could not be saved due to the following reasons:
An unknown error has occured "

We do not see any ULS log entries generated when the error occurs. We have
SharePoint diagnostics logging set to High.

Using the Effective Rights tool shows the following rights for the 2
groups
the Project Admin belongs to:
Group Name 'Project Managers' = blank
Group Name 'Project Management Admins' = Allow
But the Effective Right shows as 'Deny'. Why is this? The are two
settings,
one is explicit Allow and the other is blank.

This is not making sense to me.

Thanks for your support.

It would be easier to determine what's going on if you had a look at the
ULS
logs when the user takes this action. You might want to run the effective
rights tool, or experiment by enabling other permission combinations.
Without knowing the full secuirty setup, it's impossible to speculate.

--
----------
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


message
Gary:

I implemented the new category, and it works if our IT PWA
Administrator
follows the process of adding the new project to the new category, then
changing the project owner, then removing the project out of the new
category.

However, when our Project Administrator (not full Admin rights, but
close
to
it) tries this procedure, they can open the Category page, select the
new
project, and add it to the list on the right, BUT they cannot then save
the
Category. Instead, they get a red error message "An unknown error...".

Can you tell me what other permissions our Project Admin needs in order
to
be able to save the Category? They already have the "Manage Security"
permission explicitly enabled.

Many thanks in advance.

:

Thank you, Gary. Very helpful info.

:

When you make changes to permissions, it sets off a queue job to
synchronize
the users. When users are "in-session" on the system, they often
need
to log
off and close the application (either IE or Project) to pickup the
new
permissions when they open and log back on. And, yes, the projects
should be
removed from the category after the PM picks up the project.

--
----------
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


message
Thanks, gary.

One drawback to this is that anytime anyone goes into change a
category
there is always a risk that something will get messed up
(inadvertently) -
all it takes is to click a wrong box, for example, in the complex
web
that
is
permissions.

Do you know if category changes are reflected instantly across all
existing
users and projects?

After assigning the PM as you describe, can or should the project
then be
removed from this category?

I'll try this and see how it works.

Thanks.

:

Oldbradfordian:

You have found one of the catch 22's in the system. You must
enable
the
Save
permisison or you cannot change the owner value to that PM. I
suggest
that
you create a "change owner" category and have the Administrator
move
projects into that category to enable a PM to take over the
project.
Not
much more manual work then you're already doing.

--
----------
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


in
message
Hi, Ben:

I already setup something similar to what you describe in your
blogs.

I have two categories assigned to the Project Manager group:
Category 1: "My Projects" - Projects for which they are the
Owner,
matched
with comprehensive permissions to open and save projects, etc.
Category 2: "All Projects - restricted rights" - allowed to
Open
ALL
projects but not save them.

I can only assign them as a project manager for newly created
project
if I
enable the 'Save project' permission for Category 2. But that
defeats
what
I
am trying to accomplish, and sets all the project managers to
have
the
Project Manager role for all projects!

Thanks for trying to help.

The Project Manager Template
:

Hello OldBradfordian,

Make sure that you are on the latest SP and Infrastructure
Update,
both
for
server and client. Hopefully that will deal with the error
you
are
getting.

In terms of how to change a PM, check out this link on my
blog.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=4&ayear=2008

In terms of setting the correct PM permissions, you'll need to
figure
that
out - but this should get you started.
http://appleparkltd.spaces.live.com...ogview&_c=BlogPart&partqs=amonth=5&ayear=2008

Check out the my org category and you'll find it is redundant
if
you
have
no
RBS set up.
--
Thanks, Ben.

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



:

We are running PWA 2007 and have a very frustrating problem
that is
impacting
our roll-out of PWA.

Our project management admin creates all new projects and
then
needs
to
change the project owner for each to a designated Project
Manager
once
it is
determined who will be the project manager for the new
project.
There
is also
an occasional need to change the project owner during a
project
as
projects
are re-assigned (this is not very often, but it happens).

After creating a new project, the admin is not able to
change
the
project
owner. When a project manager is selected from the list of
users (in
the Edit
Project Properties screen), an "Unknown error has occurred"
message
is
displayed and the owner cannot be changed.

We are not using RBS in our company (no need here to go into
the
reasons why
not, we just aren't setup that way). [A related question I
have: How
does the
'My Organization' category work if no RBS is in place?]

Ultimately, we need project managers to have full (= Open,
Update
and
Save)
capabilities on project they own, but only to have Read (=
Open)
access
to
projects they do not own (they need this to create
cross-project
links
between their own project and another project they don't own
but are
dependent on). They should not be able to create a new
project,
and
they
should not be able to save a project if they are not the
project