corrupt Master Project in MSP 2007

Y

yair o

Hi,
I have an urgent problem in production environment:
I have a Master Project conatining 9 sub-projects in Ms Project server 2007.
When I try to collapse one specific project it causes the whole application
to fail.
This project was migrated using Microsoft migration tool from server 2003 to
server 2007. I've tried to repair this specific sub-project in numerous ways
without luck.
Can anyone assist?
Is it possible to save as XML and import as in Poject 2003 in order to repair?

Thanks in advance
Yair
 
D

Dale Howard [MVP]

Yair O --

I would strongly recommend that you open the potentially-corrupt project and
save it as an XML file outside your Project Server 2007 system. Close the
XML file and ask the Project Server administrator to delete the enterprise
project. Then import the XML file into your Project Server database to see
if this resolves the potential corruption. Hope this helps.
 
Y

yair o

Hi Dale,
Thanks for your quick response.
After working on it for a whole day - it seems saving it as mpp then
importing with the import wizard did the job. However the import processes
caused 3 local resources to become enterprise ones without me asking for it.
are you aware of this bug?
I'll try your xml suggestion right now to see if it works.
Do you know of a bug regarding the renaming of a project - it doesn't seem
to work for us.
 
Y

yair o

I tried the xml method.
It seemed to change a lot of task fields.
Fixing it is a lot of work so I will try working with the file I have unless
it fails again.

I have a fey more questions:
Anyone know anything about the "import wizard from mpp" behaving stranagely?
How about project renaming not working?
How would you recommend importing files from 2003 MPPs to Project 2007 server?

thanks.
 
D

Dale Howard [MVP]

yair o --

The Import Project wizard is definitely the recommended way to import
projects from outside of Project Server 2007, but I cannot confirm that it
automatically converts local resources to enterprise resources unless you
actually match the local resources with enterprise resources. Did you
actually do that step of the Wizard? One of the big issues with importing
projects into Project Server 2007 that were created in Project Server 2003
is that the system imports the 2003 custom field values into 2007. This is
a known and reported bug, and it has yet to be seen if Microsoft fixes this
in SP1.

To answer your further questions:

1. There are some bugs associated with the Import Project wizard that have
been addressed through the Hotfixes available for Project Professional 2007
and Project Server 2007. Have you acquired and installed any of these
Hotfixes yet? If not, do so.

2. Several users have reported that the project renaming feature does not
work for them in 2007. What steps are you using to rename the project?

3. See my first paragraph for the issues you will confront is you import
Project Server 2003 projects into 2007 using the Import Project Wizard.

Hope this helps.
 
M

Mike Mahoney

yair o --

The Import Project wizard is definitely the recommended way to import
projects from outside of Project Server 2007, but I cannot confirm that it
automatically converts local resources to enterprise resources unless you
actually match the local resources with enterprise resources. Did you
actually do that step of the Wizard? One of the big issues with importing
projects into Project Server 2007 that were created in Project Server 2003
is that the system imports the 2003 custom field values into 2007. This is
a known and reported bug, and it has yet to be seen if Microsoft fixes this
in SP1.

To answer your further questions:

1. There are some bugs associated with the Import Project wizard that have
been addressed through the Hotfixes available for Project Professional 2007
and Project Server 2007. Have you acquired and installed any of these
Hotfixes yet? If not, do so.

2. Several users have reported that the project renaming feature does not
work for them in 2007. What steps are you using to rename the project?

3. See my first paragraph for the issues you will confront is you import
Project Server 2003 projects into 2007 using the Import Project Wizard.

Hope this helps.









- Show quoted text -
Click to expand...

yair

The import does have this behaviour and can seriously mess up your
resource pool. It is also very ponderous, and if you cannot resolve
all the faults during the import you waste a lot of time. Save As
works equally well in my view, you may have to do some post migartion
cleanup but no more than with import wizard.

If you have not applied any hotfixes then renaming (using edit project
properties) fails unless you change a project custom field at the same
time as you rename the project! There is a hotfix which resolves this.

regards

Mike
 
Y

yair o

Hi,
Regarding the renaming of a project these are the steps I made:
Open Project professional->File open-> retrieve->right mouse click->rename

However the name never changed.
 
N

Nir Shiffer

"If you have not applied any hotfixes then renaming (using edit project
properties) fails unless you change a project custom field at the same
time as you rename the project! There is a hotfix which resolves this."

Hi Mike. I've looked at the Hotfix listing and could not find any hotfix
that adresses the renaming issue. Do you by any chance remember it's number?
 
M

Mike Mahoney

"If you have not applied any hotfixes then renaming (using edit project
properties) fails unless you change a project custom field at the same
time as you rename the project! There is a hotfix which resolves this."

Hi Mike. I've looked at the Hotfix listing and could not find any hotfix
that adresses the renaming issue. Do you by any chance remember it's number?






- Show quoted text -
Click to expand...

This was by a previous correspondent

http://groups.google.com/group/micr...c/6e2da3a409d43112?hl=en&lnk=gst&q=hot+fixes#

regards

Mike
 
Top