We get this question quite a bit – and to be clear I am only talking about the Service Packs and Cumulative Updates – we do not support Project Professional 2010 connecting to Project Server 2013 or Project Professional 2013 connecting to Project Server 2010. But do I need to have my client at the same Cumulative Update level as my server? Or if I update the server (Project Server 2010 or Project Server 2013) then do I also need to update the client software (Project Professional 2010 or Project Professional 2013). There is no requirement to do this – any Cumulative Update (CU) or Service Pack (SP) level of the client will work with any CU or SP level of the server. That said you may wish to be at least at a certain level for all clients that connect to your server to avoid certain issues that we have fixed – so it is not a bad idea to control this through the Server Settings options. Our support lifecycle also requires certain patch levels to be in use – for example the initial release of Project 2010 went out of support around a year after SP1 was released. I know certain consultants and partners tend to keep versions in sync as a ‘best practice’ – and certainly it is not wrong to do this – but nothing will break if you don’t. In the very rare circumstance that we released a fix that affected both client and server and required that both were patched then we would document this in the KB article.
The October 2013 Cumulative Update (CU) for Project 2010 and Project 2013, and Project Server 2010 and Project Server 2013 is now released (mostly). A slight delay with the roll-up package for the 2013 Server – hopefully out in a week or so. If you want to test a specific Project Server fix then the individual cumulative update for Project Server 2013 is available – it is fully cumulative but does not contain the SharePoint fixes. See Microsoft Project Server 2010 and 2013 October 2013 CU Announcement for the full details.
In case you are not subscribing to the Project Support blog – just making sure these didn’t pass you by.
Project Online – Provisioning new PWA instances in languages other than English can take a little while until all is seen in the other language – and we appear to have some issues where some things are just stuck in English – just with some languages - Project Online- Provisioning a PWA in another language- Tips and tricks
Another item I covered – actually last week – was the way we control versions of connecting clients – and the fact that Project Server actually reports itself as a client (when you edit a schedule in PWA) and may have a lower version number that the Project Professional 2013 clients you are expecting to connect - Project Server 2013- Controlling the version of connecting clients–and PWA edits-
Registration is now open for the Project Conference 2014!
Go to http://www.msprojectconference.com/ for full details, as well as the announcement on the Project Blog – and there are still a few days left if you want to suggest content or session ideas! Ends September 30th! I hope to be presenting if my session suggestions get accepted. More troubleshooting stuff – as well as plenty more information on Project Online.
Also coming up we have some regional Office and Project Ignite Summits!
The Ignite Summits are a series of 3 day workshops for Microsoft's most valued customers and partners providing deep-dive technical readiness on all productivity workloads from Microsoft product experts.
Tracks include Office 365, Developer, Exchange, Project, SharePoint, Visio/Visio Services and Yammer. During the Summit, you will also have the opportunity to interact and learn from your industry peers and representatives from Microsoft.
I have the good fortune to be presenting the Project stream at the Dubai event. Looking forward to seeing friends old and new at the Project Conference and the Ignite Summit. And if you are not able to get to either we do have recorded content from the previous run of Ignite trainings - http://technet.microsoft.com/en-US/projectserver/jj906608. 11 modules and nearly 60 videos taking you right through Project 2013, Project Server 2013 and Project Online.
I’ve updated the relevant blogs and posted a new one at http://blogs.technet.com/b/projectsupport/archive/2013/09/13/project-server-2010-august-2013-cumulative-update-installation-latest.aspx but wanted to be sure my subscribers see this too. The core of the issue is that if SP2 needs to make DB updates (usually needed – but not if June CU was installed) then the August CU will get confused by the version number that SP2 writes into the published DB versions table and fail during the configuration wizard. See the link above for your options to avoid or recover from this.
Repeating the error here just to help the search engines:
and from the Upgrade Log: