*** Update - thanks to all who corrected me on the title - don't know how many times I must have read that and not noticed - yes, this is for 2007 and not 2003... ***
I’ve posted over on the admin blog - http://blogs.technet.com/b/projectadministration/archive/2011/10/28/project-server-2007-service-pack-3-and-the-october-2011-cu-announced.aspx so go there for more details.
*** Update – just heard there are a couple of issues being investigated with the 2007 Office packages – this affects the MOSS Server package 2596540 (which is the roll up that also includes the Project Server 2007 fix below), and a Project 2007 fix that was specifically aimed at implementations of Project 2007 and Office 2010 where Visual Reports would not work. Also corrected the description below from 2010 to 2007 – sorry… Both of the updates below are unaffected. *** All affected fixes have been re-released 11/1/2011
There is a slight delay on the release of the 2010 October 2011 Cumulative Updates – more details when I have them.
Don’t miss the next Cumulative Update webcast where we (or more correctly, Adrian) will also talk about SP3 (briefly – as there isn’t much to say)
Pink Floyd are not the only ones re-releasing their back catalog this month – we have re-released the SharePoint Foundation 2010 August Cumulative Update. As this is also contained in the roll-up packages then these too have been re-released. Unfortunately the title of the Project Server package has also been updated to reflect this new release date and it could make it look like the October Cumulative update released early – so take care!
The re-released Project Server package at http://support.microsoft.com/kb/2553049 is still the August Cumulative Update, although it is labeled Description of the Project Server 2010 cumulative update package (Project server-package): October 13, 2011. This is NOT the October CU coming early! The version has been incremented to 14.0.6109.5005 to reflect the new build, but it is just the SharePoint Foundation component that has been updated. The Project Server only package at http://support.microsoft.com/kb/2553047 is still showing the original date and version, as it was not rebuilt as it does not contain the SharePoint Foundation component. (sts-x-none.msp).
I think the change in the SharePoint package is support for updates to Russia, Fiji and Samoa daylight saving time (DST) settings in SharePoint Foundation 2010 – I’ll see if I can get confirmation.
I was going to use the title asking ‘why are people still deleting the cache?’ until my colleague Corrie came up with this much better one! Rather than asking why you are still doing it – I am telling you not to!
I know there is a lot of history behind this one, and for those of you that used Project Server 2007 in its early days there were some challenges such as the ‘check-in pending’ saga that got people in to the habit of deleting the project cache. We fixed the problem, then we fixed it again (and again) and you should not generally be seeing any issues with leaving your cache alone to do its job. However, many customers I talk to are routinely deleting the project from the local cache before they open it and then again after they close it! Why!?! Its job is an important one – it saves you having to pull that data from the server again – which will reduce network traffic, the hit on both the web services and the database, which means they can be getting on and doing useful stuff.
I’ll also address a miss-conception misconception (thank you Trevor - not addressing the misconception that I can spell...) here that I have heard from a number of customers – the choice of where to load the project from – cache or server? You don’t have a choice – Project will load it from the cache if it is there, and then load any incremental pieces it needs from the server, to get you the current version of that plan. In the screen shot below:
the line actually reads ‘Retrieve the list of all projects from Project Server’. It does not also read – ‘…and open any I might choose after clicking this link from the server and ignore the local cache’. You don’t get the choice and you don’t need to choose.
I’m sure many of you will not have read this far before clicking the comments option to tell me of all the problems you are having.(and I’m sure some of you are still having problems). First check that you have the latest cumulative updates and service packs. If you are still really having issues unless you delete the local cached copy then we certainly need to hear about it so we can fix the problem rather than have you waste your time and system resources doing things that you should not need to do.
I will admit that there can be times when as support engineers we will ask you to remove your local cache to troubleshoot specific scenarios. The cache itself also has intelligence that allows it to decide that it may have some bad stuff – and it will get a new clean copy of data from the server (symptom of this will be several files in the cache directory with 1,2,3 etc. at the end). There have also been a few bugs we have worked on recently which ONLY surface when the user has cleared their cache!
So please, if you have been deleting your cache as a matter of routine, then either stop – or speak to your PMO or IT people and ask why they have you do this – and if we need to fix something else then we can take a look.