Problems with Local Cache?

[Michael Brown]

I've run across an interesting issue. I have a project plan that i've opened
in Pro. I made some changes to the plan, saved it and also republished it,
and then closed the plan out. The changes were appropriately noted in PWA.
So far so good. When I go back to Pro and try to re-open the plan, I get a
message indicating the plan is (still) checked out, and I can only view it in
Read-only mode. No one else has the plan checked out, nor does it appear to
be checked out when viewing in PWA. My assumption is the local cache copy is
not being flagged as checked in. When I clear the local cache, all is fine
again. Anyone run across this one?

 

[Michael Brown]

Ben,
Thanks for the quick response! I take great comfort in knowing i'm not
crazy - nor the only one noticing these things ) Local cache is a great
idea, but hopefully these quirks will be cleaned up with the 1.1 hot fix!

 

[Dale Howard [MVP]]

Michael --

In addition to Ben's sage advice, I have seen the exact same problem with
the Local Cache. Occasionally the project simply gets "stuck" in the Local
Cache and then you to delete the cached copy to check it out again. In
addtion, there is another problem. When the Project Server administrator
deletes a project from the Project Server database, the cached copy remains
in the Local Cache, except you cannot open it. It is really confusing to
open Project Professional 2007, click File - Open, and then see a file
listed that you KNOW was deleted! Hope this helps.

 

[Michael Brown]

Dale,

can't WAIT to read your books! It's got to be wonderfully fun trying to
write a good manual with all these quirks! )

 

[Jonathan B]

I don't need a book that explains all the bugs in the software. What we need
is software that consistently executes core functionality (oh like "saving a
scheduled"). My end users are not going to clear the local cache every time
this software fails. We are out of BETA aren't we? Only kidding...

 

[Dale Howard [MVP]]

Jonathan --

Your points are well taken. I didn't write the software, and had nothing to
do whatsoever with writing the software. I AM collaborating with Gary
Chefetz on writing our first two books on Project Server 2007, and I can
tell you we have uncovered many troublesome bugs in the software as we write
the books. Your comment on being out of beta is sage. Sometimes it feels
like we are working with beta software, doesn't it. Hope this helps.

 

[Eric Norman]

Michael,

I am experiencing the same problem almost every time I open projects.
Unfortunately I have been unable to isolate the difference between the times
i get the error and the time I don't.

Were you able to find a solution?

 

[Kyle Reese]

It's a bug within the Project Pro 2007 client. The local cache issue is
addressed with this hotfix as far as I can determine:
http://support.microsoft.com/kb/939595/en-us

Be sure to delete your local cache first before installing this one. Yes, I
know it makes no mention of local cache fixes, but trust me it does.

 

[Eric Norman]

Thanks Kyle, I'll look into it.

It's a bug within the Project Pro 2007 client. The local cache issue is
addressed with this hotfix as far as I can determine:
http://support.microsoft.com/kb/939595/en-us

Be sure to delete your local cache first before installing this one. Yes, I
know it makes no mention of local cache fixes, but trust me it does.