Corrupt Database in Project Server

[Lindy]

Hi,

We're using Project Pro 2007 w/PWA and started seeing some problems as soon
as we began using Task Updates:

Saving from the client to the server takes a long time (>4 min) - it seems
to get stuck at 84% for several minutes. Then when we click Publish it often
tells us we need to Save before we can Publish - sometimes we have to go thru
this cycles 4 times to publish!

Our user's Notes from PWA doesn't alway make it over to the Project client
when we accept task updates.

The Preview function doesn't work at all in Task Updates - it highlights
tasks that have nothing to do with the Update.

And strangest of all - when we open the project on the client, the Finish
dates for certain COMPLETED tasks are changed to dates way in the future like
2012. We correct those dates, Save, Publish... and then sometime later when
we open the project on the client the same completed tasks have changed
Finish dates again!

Our IT guy says it's a corrupt db and advised us to re-create the Project
Plan from scratch and republish it. That's a lot of work. We wouldn't mind if
we knew it would solve the problem, but we're afraid we'll see the same
issues in the new version.

Any advice?

Many thanks,

 

[Marc Soester [MVP]]

Hi Lindy,

I personally believe that there is something generally wrong with your
Project Server environment. There are a couple of things I would check.
- Ensure that Service Pack 1, Infrastructure Update and December Cumulative
update is installed on both Server and all clients.
- Your IT staff should check out the event logs and the project server
queues. I am sure they will have error messages in there which need to be
addressed.

If the problem persists, I would recommend bringing in an expert to check
out your environment. This will at least ensure that the environment is
either set up correctly, or will be amended to work. The amount of time it
takes to save a project would concern me as well. Project Server 2007
generally works very fast und given that the infrastructure and installation
was planned and executed correctly, you would not experience these time
delays ever.
I hope this will give you some ideas on how to approach the issues at hand.
Please let me know if you have further questions.

 

[Lindy]

Many thanks, Marc. I will inform our IT staff of your recommendations.

 

[Gary L. Chefetz]

Lindy:

This also might be the result of garbage in the plan itself. Project doesn't
usually push dates out unless there are scheduling conflicts, which are
usually found in the plan itself.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com