File in Server 2010 refuses to open if found in cache

Question

We have at least two files in our Project Server v2010 SP2 that refuse to open if you have the file in your cache.  The hour glass will sit there for about a minute, then the nominal cursor is returned.  Sometimes, you at least get the dignity
of a message at the bottom that begins "Closing file...".  You can clear the file from the cache and then it will open.
Yes, we have done a "Save for Sharing" exercise with these files.
With the one file, we have gone through several iterations of schedules.  We at first concluded that the file was impossibly corrupt because it wouldn't open at all.  It wasn't until later that we concluded that the file would open if you cleared
it from the cache. 
It should be noted that I was dragged into the forensics this morning and the first version that I was asked to open from the Server would not open at all.  I can't blame the cache on that issue because the file was not yet in my cache.  I
took an offline version of the file, saved it to the Server, then immediatly did a "Save for Sharing".  I then saved it back to the Server and published.  I closed, then attempted to reopen but failed in the attempt.  It was later
that we concluded that this new version of the file only opens if it is not in your cache.  Other people have verified the same results.
Any thoughts for clearing this issue would be appreciated.

Answer 1

Hi Mike -
We tell our people over and over not to do cut & paste, but they do it all the time.  It winds up orphaning SharePoint Deliverables and Dependencies.  I am making a nice living just cleaning up the mess that people are making by refusing to
take that suggestion.  In reality, I would really prefer doing some more meaningful work.
But back to your suggestion, everbody is on a common service pack here.  We are on a government network and we don't own admin rights to the network.  We are on SP2.  The only other thing that I would mention is that most people here access
the Project Server via thin client.  I have had my suspicions that we are seeing time-outs.
What still has me confused is why the schedule would not open in one project server, but it would open in another project server.  From a fish-bone analysis, half the blame has to be placed on the file because 99% of the other files open just fine,
but the other half of the blame has to go to the server instance if another server instance opens the file.
At the current moment, the file is opening from cache, which has me happy, but the one thing that is different is that they have declared this file as a subproject to another file in the Server.  We still need to see if we can replicate that corruption
clearing process.
Chris