Proj Pro Error with Local Resource

N

Newbie

I have a project file that is currently published to the server and has been
for a few months, than all of a sudden, it has listed a resource name on the
resource sheet and also shows in the "Build a Team" section over 50,000
times. Same resource name and type. I've tried to delete it, but when when
I try to save, close, publish, the names repopulate in the project again.
This causes the file to be extremely large so we are having difficulty even
opening it.

Any thoughts?
 
D

Dale Howard [MVP]

Newbie --

I believe this indicates project corruption. To resolve the corruption, you
must do the following:

1. Save the project as an .xml file.
2. Delete the project from the Project Server database.
3. Open the .xml file and delete any extra resources, if present.
4. Save the .xml file as an .mpp file.
5. Import the .mpp file back into the Project Server database.

If the project has Risks, Issues, or Documents associated with it, refer to
the following FAQ for information on how to delete the project but preserve
its WSS subweb:

http://www.projectserverexperts.com/Shared Documents/DeleteProjectWithoutSubweb.htm

Hope this helps.
 
N

Newbie

Thank you Dale ~
I just want to be sure that deleting the project from the database and then
restoring it will still reflect the time already reported against task items.
Also, since this project was still accessible via PWA, what about the time
submitted that has not yet been approved by the PM? We have been unable to
accept time submitted due to the inablity to open and save the project in
project pro.

Thanks again!
 
D

Dale Howard [MVP]

Newbie --

When you save, delete, and reimport the project, you will not lose any
actuals reported against the project. You will lose any pending updates on
team member's timesheets or on the manager's Updates page in PWA. So, to
avoid losing this information, ask every team member to immediately update
progress to their PM, and ask the PM to process the updates into the
Microsoft Project plan. Also, refer to the previously referenced FAQ about
how to preserve the project's WSS subweb if the project has associated
Risks, Issues, or Documents. Hope this helps.
 
Top