Checkout Problem

[Sascha]

Hi,
at a client side we have a strange Problem with some Projects.

Environment:
Project Server 2007 Farm with 4 servers all with SP1 and Infrastructure
Update.
SQL 2005 Sp2 Cluster
Project Pro is SP1 and Infrastrukture Update is installed, too

Issues:
The following Issue is notived on Project A in Produktiv System.
Not noticed on Project A in Preproductiv.
Noticed on Project B in Preporductive.

PM is opening Project A in Project Pro.
After this he saves the Project plan and closes the Project.
when he now immediate reopens the Projectplan every thing works fine. If he
closes Project Professional and restart it, in the Local Project Cache the
Project is NOT checked out for him. In the PWA the Project is checked in (
Force Check-in Enterprise Objects ) too.
Queue is emptry too
Then he tries to reopen the Project (Retrieve list of Projects from Server)
not the Chached one he gets the mesage that the Project is Checked out to him
and he can open the Project only in readonly mode. When he opens the Project
in readonly mode the Project is marked as Checked out in Project Pro and in
the PWA.

Actual Workarrount the User has to ceanup the Cache before he opens that
Project and then he can reopen it.

Does anybody has a other solution for this Problem rather then delete every
time the Cache?
Is this issue recorded somewhere or happening by somebody too?
Is this a bug in the tool?

Thanks
Sascha

 

[Gary L. Chefetz]

Sascha:

I wouldn't call it a bug as much as I'd call it a design vulnerablility.
Your users is taking these actions in too rapid of a succession for the
system. Just becasue the user closed the project, doesn't mean that the
system is done with its updates. Have your users make sure that they close
the project only when the status bar indicates that the save and/or publish
operations are complete and to never close the Project application until the
systems completes it work. This should avoid the troubles.


----------
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

 

[Sascha]

Gary:
We are waiting till everything is finished. Can you explain why the Problem
is not Happening in Preproductiv with the Same Project. There we have the
issue with a new Test Project only.

 

[ProjmanZA]

Gary:
We are waiting till everything is finished. Can you explain why the Problem
is not Happening in Preproductiv with the Same Project. There we have the
issue with a new Test Project only.








- Show quoted text -

Gary,

I might be wrong here but, isn't this one of the issues that the
Infrastructure Updates solves ? As far as i know a "Syncronising "
dialog should come up if you close the plan and MSP is still busy
with adding a job to the queue ?

 

[Sascha]

Yes it is a smaller one.
But there I have the same Issue with a new Test Project.

 

[Sascha]

Gary,
I do not think that this is the problem. As I mentioned the Problem is only
happening on certain Projects.
I waited 20 Minutes and checked the Queue and it happened again.

Sascha

 

[ProjmanZA]

Gary,
I do not think that this is the problem. As I mentioned the Problem is only
happening on certain Projects.
I waited 20 Minutes and checked the Queue and it happened again.

Sascha








- Show quoted text -

Sascha ,

Do you have the infrasrtucture update installed for MSP aswell ?

 

[Sascha]

I we have.
Meanwhile I have found the Solution:
It is not enoght to ceanup the Cache in Project Pro. You have to delete the
Cache Folder in the Filesystem after that it is working fine