Can't rename project or change owner?

[scubaal]

Running Project Server 2007.
Trying to rename project and change owner through:

Edit Project Properties in PWA.

Hit Save and/or "save and Publish" and

......nothing happens!

Is this a known bug? How can we rename and enterprise project that ahs
been misnamed (and has the worng owner)?
Indicentally - changing custom fields on the same screen and hitting
save works just fine.

Al

 

[supercoolmanchu123]

Just got the exact same error myself. Arg.

 

[Ben Howard]

Hi,

From memory...

To rename the project, open Project Pro, as the current owner. Then, in the
fileopen dialogue, right click on the project, and click rename.

To change the owner, log into PWA as the current owner, and change the owner
through PWA. Then, as the new owner, open the Project in Project Pro, save
and publish.

 

[nedjohn]

Running Project Server 2007.
Trying to rename project and change owner through:

Edit Project Properties in PWA.

Hit Save and/or "save and Publish" and

.....nothing happens!

Is this a known bug? How can we rename and enterprise project that ahs
been misnamed (and has the worng owner)?
Indicentally - changing custom fields on the same screen and hitting
save works just fine.

Al

We have seen the same issue and found that repopulating ALL fields on
the Edit Project Properties scree in PWA allows the project name and
owner to be modified. So you literally re-populate all fields. In
many cases you are reselecting all pull down menu items and/or
retyping the same content in text fields - including the custom
fields. WIth all fields repopulated Save and Publish works for us.

It's not pretty but it seems to be a workaround.

 

[Nik003]

This is a known bug, to be fixed in SP1. For now, the workaround is to change
at the same time any of the fields in the Project Custom Fields.

 

[Dale Howard [MVP]]

Al --

Yes, this is a known bug which has been reported to Microsoft. The only way
to get the changes to save is to change the Owner field value (or Project
Name) AND one other custom field value as well. Use Ben Howard's steps to
rename the project in the Project Professional 2007 application. Hope this
helps.

 

[Dale Howard [MVP]]

Nik003 --

Out of curiosity, how do you KNOW this will be fixed in SP1? Or are you
only speculating?

 

[Nik003]

This was one of the questions to microsoft tech support during one of our
calls. They stated it's a known bug, and the fix should be available in SP1.
Still no final date on that yet though.

Hope this helps.

 

[Dale Howard [MVP]]

Nik003 --

At least you got the information from someone at Microsoft; however, I'm not
convinced that Microsoft tech support is qualified to state whether any bug
will be fixed in SP1. Thanks for sharing!

 

[Nik003]

I know exactly what you mean. I take anything coming from them with a grain
of salt. However, we can only hope, since it's been known for quite some
time, and it should not be that much extra coding to fix it. It's not
impacting functionality in a major way like other issues we've raised (the
multi-level custom fields, the incosistencies in caching, and a bunch of
others).