Cannot save the same project file

[Joe]

I have a user who modified a project file residing on the project server
2003. After the updates were completed, she couldn't import it back to the
project server. An error message comes up saying:
"You cannot overwrite the default version (Published) of a project. To save
this project, type a new project name or save the project as a version other
than the default. Users always updated schedule, hours and tasks and we never
saw any issues in the past. Is it possible the same project file still
remains on the server? I checked the Project Center as well as PWA and the
file is not visible.

Any help or suggestion?

Thanks

 

[Dale Howard [MVP]]

Joe --

Out of curiosity, are you using the built-in versioning functionality in the
tool? I have seen this exact behavior when a PM opens an alternate Version
of a project, manually updates progress in the project, clicks File - Save
As, and attempts to save the alternate Version as the Published version.
Let us know.

 

[Joe]

Hi Dale,

Thanks for getting back to me. The PM uses the same built-in functionality
which is nothing new to them. The thing is a project is opened using project
professional 2003, modified and then using the import tool to publish it back
to the enterprise, it comes up with the error message as stated in my
previous message. PMs can't keep changing the project name if this continues
so I wanted to know what causes this and what is workaround it. When I check
the project center, the project is not visible neither through Project Center
nor PWA. I searched Internet and noticed this is a common issue with project
program which in this case I'm not sure if its project professional or
project server. Some say there is a ghost file remaining on the server that
has to be removed but how.

Any help would be great.

Joe

 

[Dale Howard [MVP]]

Joe --

Wait a minute. Why doesn't the PM simply open the project, edit, and save
it? What is this business about opening it, modifying it, and USING THE
IMPORT TOOL to publish it back? That makes no sense whatsoever as it is
totally the wrong way to use this software. Please explain further.

 

[Joe]

Dale,

I have no idea why they're not using it the right way? There are over 300
users and 120 project managers working on a large project. Today I found out
that one of PM deleted the project from the server by using PWA clean project
option in the admin page and she immediatly tried to published the same one
with the same name by importing it back to the server using wizard. All I
know that the delete was not executed properly therefore, it left a foot
print in the project center. I also used PsFile.exe tool from MS to see if
the file is locked by another process but there was Zero item. So, here where
I need to delete the ghost file so that I can let them know they can save
under the same name rathern than naming it constantly.

Sounds crazy but this is where I need your expertiese on this. Any help
would be appreciated.

Thanks

 

[Dale Howard [MVP]]

Joe --

Well, not to muddy this problem any further, but why did you grant
permissions for project managers to access the Admin page in PWA? That is
ultimately the source of this problem. And when the PM did the deletion,
did she select the option to delete the SharePoint workspace site as well?
If not, you now have an orphaned project workspace in WSS.

I'm not a technical guru, so I hesitate to suggest a fix to your problem.
Perhaps the technical folks in this newsgroup would offer you an opinion.
At the least, I suspect you will need to enlist the aid of a DBA in your
company, and perhaps the network administrator who handles WSS operation as
well. Hope this helps.