Problem with Project local cache

[Vicente]

Hi,

I have a problem to open projects with the local cache of Project
Proffesional 2007.

The sequence is:

1. Open project for the first time

2. Make changes, save and publish

3. Close project and protect

4. Open for the second time the project

5. The message returned is:

THE PROJECT CAN ONLY BE OPEN MODE READ.

To open it in edit mode needs to be removed from the local cache, but this
process is tedious and cumbersome.

Project Proffesional is SP2 and kb951547 cant´be installed in Project
Proffesioanl station (XP with SP3)


Any idea?

 

[Andrew Lavinsky]

The IU you allude to and SP2 for Project Server did a lot to resolve these
checked in issues. What level is your server patched to, and is your client
patched to the same level?

Also, when you delete the project from the cache, are you using the MS
Project functionality to delete it, or navigating to the actual cache folder
using Windows Explorer?

The latter is the recommended approach.

 

[Vicente]

Project Server and Project Proffesional have SP2 installed and delete the
project from the cache using the MS Project

Thanks

 

[.jussi]

Hi Andrew,

Regarding the recommended way to clear the cache, this was the first time I
heard anyone suggest clearing the cache folder manually. Would you care to
elaborate on why this is the preferred way to do it instead of using Project
Professional's integrated tool for it?

Thanks,
- Jussi

 

[Dale Howard [MVP]]

jussi --

Clearing the Local Cache using Tools - Local Project Cache - Clean Up Cache
only partially removes the contents of the Local Cache. In spite of two
Service Packs and numerous Cumulative Updates and Hotfixes, the problems
with the Local Cache continue to torment users. Refer to the following FAQ
for the method to completely delete the contents of the Local Cache:

http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/LocalCacheCorruption.aspx

Hope this helps.

 

[Gary Chefetz]

Vicente:

What do you mean by "close project and protect" in step 3? I'm particularly
interested in what "protect" means in your statement. The most common reason
for this behavior is how the user closes the project. Using File > Save an
File > Close as a regular practice eliminates 95%+ of these type of
occurrences which are generally caused by users closing the file with the X
button or closing the application with a file open or while an operation is
still completing.

 

[Vicente]

Hi,

Protect is checkin.

When I close the project and appears the menu for closing there are the
options to save changes or not, and check it or not . Then we choose to check
in.

This issue is random

Thanks