Save to different name error message

[Reuter]

Using MSP2003ENT

Opened a project file from my hard drive and tried to save it to a different
name and this message came up “Outline Code must be cleared; this project is
from a different project server which has different outline code tables. All
outline codes must be cleared before performing the saved. Do you want to
continue, once cleared this is permanent."
I have done this before with no issues. Any idea on what I missed or what
I am doing wrong?

 

[Gary L. Chefetz [MVP]]

Reuter:

Where did the project orgininate? This indicates that it may have started
life as a clone of a plan that lived on your sever when it was configured
differently, or it was cloned from a plan or is a plan from another instance
of Project Server.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Reuter]

Yes, the project started life as a clone. Because 2003 has only 1 undo this
was saved (just in case). I went ahead and clicked OK; all seems to be
working fine. I was just curious on why-now I was getting this message
because I've done this several times in the past with no issues. Going
forward and taking into account other users, is this a message that I should
be concerned about? If a user contacts me with this message “Outline Code
must be cleared; this project is from a different project server which has
different outline code tables. All outline codes must be cleared before
performing the saved. Do you want to continue, once cleared this is
permanent." What should my response be ????

Thanks

 

[Gary L. Chefetz [MVP]]

Reuter:

You should do what the software suggests, but my best practice
recommendation is to not clone projects this way.The only way you can save
the enterprise values in the local plan and bring them back into server is
if you're working on the same system with the same configuration, but again,
this is not a best practice. Any project you clone from an existing plan
will always have crappola left behind. For instance, Project Server will
never see a clone as an unpublished project, even if you're starting from
the beginning. The first publish, therefore, requires a republish. Always
start new projects and new project templates from virgin files whenever
possible, and always copy only textual data between plans.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com