Project Server 2013
Project 2013
Project Server 2010
*** Update 5/14 Turns out that wasn't all you needed to know - and there are some conditions where either the April CU referenced below (original post - not the new one in this section) would not install (expected product not found) or it would install but the database updater would not be triggered and the April CU database updates not get applied - most importantly the 'lost resource' fixes. So if you have loaded and your database version was not updated to at least 15.0.4605.1000 then you should load the new full April CU that also contains the missing fixes - http://support.microsoft.com/kb/2880484 . There are a couple of typos that say 2010 in the current article - and we have a request to get the list of fixes added - once this is complete I will post a new 'all you need to know' posting - but wanted to get this information out there. ***
I think we have thoroughly confused people with the Service Pack 1 (SP1) for Project Server 2013 and SharePoint Server 2013 release, re-release and the partial release of the April 2014 Cumulative Update (CU) for Project Server and SharePoint. So here is a post with no more links to go read other stuff (apart from the links to the latest downloads and SharePoint info) and has all the questions I think people are needing answer to:
Q1. I already downloaded and installed the original SP1 (KB 2817434) – what should I do with the new SP1? A1. You can install the new Project Server 2013 SP1 (KB2880553) right over the original one. No rush to do this – nothing is changed just the ability to apply further patches. So might be easiest to plan the install of this new release when you next need to patch (April or June CU perhaps, and load SP1 first – the config wizard can be run after all patches have been applied) Q2. I already downloaded and installed the April CU for Project Server 2013 (KB 2863881) what should I do with the new SP1? A2. It will install right over the current April CU. Again, no rush – nothing in SP1 that you won’t already have with the April CU. Installing when you next patch (the remaining pieces of the April CU, see below, or the June CU – again SP1 first as mentioned in Q1) Q3. I already downloaded both the SP1 and April CU? What do I do next? A3. As for Q1 and 2 – no rush – but apply the new SP1 release before your next update. Q4. If I’m not updating to the April CU just yet but will (or have) loaded SP1 - should I do the fix for the ‘lost resources’ issue? (KB 2933444) A4. Yes, applying SP1, either the original or re-release will have replaced the ‘old’ stored procedures – please action KB 2933444 – even if you hadn’t before. Unless you do this you are vulnerable to the lost resources issue until you apply the April CU. Q5. What did you say about the remaining April CU fixes? What fixes didn’t we get so far? A5. There is another patch that has not yet been released and I don’t have an ETA just yet – but it contained fixes for timesheet view load issues, status updates for master projects, unprotected baseline issues and grouping in views. Q6. Where are the ‘uber’ packages for SharePoint and Project? A6. Due to certain packages being delayed the roll-up packages were not released. At this time I am not sure if they will get released along with the ‘missing’ patches or not. Hopefully normal service will be resumed in June with the usual line up of patches. You can install all the individual patches you need before running the configuration wizard. Q7. Do I need to run the configuration wizard after loading the new SP1? A7. Yes. Q8. I haven’t applied any of this yet – where should I start? A8. If you are waiting for a specific fix that is in the released April CU then I’d get that patched, along with the re-release SP1 (order does not matter). If you need one of the other fixes that are mentioned in Q5 and not desperate for any other fixes then you could wait – but worth making sure you action KB 2933444 for the lost resources issue. Q9. What about SharePoint? A9. Much the same answers – they have a re-released Service Pack too and the same applies as I have mentioned above. Stefan’s blog covers the details of the other packages.
Q1. I already downloaded and installed the original SP1 (KB 2817434) – what should I do with the new SP1?
A1. You can install the new Project Server 2013 SP1 (KB2880553) right over the original one. No rush to do this – nothing is changed just the ability to apply further patches. So might be easiest to plan the install of this new release when you next need to patch (April or June CU perhaps, and load SP1 first – the config wizard can be run after all patches have been applied)
Q2. I already downloaded and installed the April CU for Project Server 2013 (KB 2863881) what should I do with the new SP1?
A2. It will install right over the current April CU. Again, no rush – nothing in SP1 that you won’t already have with the April CU. Installing when you next patch (the remaining pieces of the April CU, see below, or the June CU – again SP1 first as mentioned in Q1)
Q3. I already downloaded both the SP1 and April CU? What do I do next?
A3. As for Q1 and 2 – no rush – but apply the new SP1 release before your next update.
Q4. If I’m not updating to the April CU just yet but will (or have) loaded SP1 - should I do the fix for the ‘lost resources’ issue? (KB 2933444)
A4. Yes, applying SP1, either the original or re-release will have replaced the ‘old’ stored procedures – please action KB 2933444 – even if you hadn’t before. Unless you do this you are vulnerable to the lost resources issue until you apply the April CU.
Q5. What did you say about the remaining April CU fixes? What fixes didn’t we get so far?
A5. There is another patch that has not yet been released and I don’t have an ETA just yet – but it contained fixes for timesheet view load issues, status updates for master projects, unprotected baseline issues and grouping in views.
Q6. Where are the ‘uber’ packages for SharePoint and Project?
A6. Due to certain packages being delayed the roll-up packages were not released. At this time I am not sure if they will get released along with the ‘missing’ patches or not. Hopefully normal service will be resumed in June with the usual line up of patches. You can install all the individual patches you need before running the configuration wizard.
Q7. Do I need to run the configuration wizard after loading the new SP1?
A7. Yes.
Q8. I haven’t applied any of this yet – where should I start?
A8. If you are waiting for a specific fix that is in the released April CU then I’d get that patched, along with the re-release SP1 (order does not matter). If you need one of the other fixes that are mentioned in Q5 and not desperate for any other fixes then you could wait – but worth making sure you action KB 2933444 for the lost resources issue.
Q9. What about SharePoint?
A9. Much the same answers – they have a re-released Service Pack too and the same applies as I have mentioned above. Stefan’s blog covers the details of the other packages.
If you have any questions – and I’m sure I missed some obscure scenarios - then either ask them here – or open a support incident and I am sure we can get you sorted. Thanks to Vincent Capitaine (MVP) from Campana and Schott for suggesting this post.
Thanks to everyone who joined the Getting Started with Project Online webcast yesterday, and to my co-presenter Aik Chen, and Heather Correa for the great logistical support. As promised I am repeating the answers to questions we had at the end of the session – and also including the link to the recording and other useful getting started content.
When the recording is posted (shortly) it will be found on the YouTube Microsoft Office365 playlist for the support webcast series - https://www.youtube.com/playlist?list=PL_BmUqQrmneYR68U0rkIDuYxdUlEvPyD8.
The questions:
Q, David - Can Government or GCC customers purchase? That is, can it be added to G3? A. Yes, it can be added to GCC G3. It cannot be added to Medium or Personal level subscriptions.
Q, David - Can Government or GCC customers purchase? That is, can it be added to G3?
A. Yes, it can be added to GCC G3. It cannot be added to Medium or Personal level subscriptions.
Q. Lou - How do you get other PWA sites to show on the top menu bar drop down?
A. Unfortunately we do not have a way to add or change where the Projects link from the toolbar navigates to – it will be your default /sites/pwa Url. I believe SharePoint may be adding some ability to modify the toolbar – not sure if this might give what you need.
Q. Eswara I have a Project Manager who uses Project Professional 2013 desktop version to manage his project - how can I make his project available through PWA? I have Project online with Project Pro for Office 365. A. Project Professional 2013 and Project Pro for Office 365 are really identical from the functional side – just the Office 365 version delivered as a subscription. So your PM can use Project Professional 2013 to connect to a Project Online PWA by using the Url when they set up the profile to connect.
Q. Eswara I have a Project Manager who uses Project Professional 2013 desktop version to manage his project - how can I make his project available through PWA? I have Project online with Project Pro for Office 365.
A. Project Professional 2013 and Project Pro for Office 365 are really identical from the functional side – just the Office 365 version delivered as a subscription. So your PM can use Project Professional 2013 to connect to a Project Online PWA by using the Url when they set up the profile to connect.
Q, David - Are there API’s or connectors that allow departments with existing PPM tools like Clarity, to export their portfolio date to Project Online?
A. We have OData and REST API’s to be able to interact with Project Data – really depends exactly what you are needing to do David. By all means contact me offline to see if the data you need access to is available.
Q. Chad - Can you talk about the Project Lite SKU?
A. The Project Lite SKU was announced at the Project Conference 2014 and is a lower priced subscription aimed at the team member. The team member will be able to use the task and timesheet functionality – collaborate on the project site and can access everything that the team member permission would normally confer. They will be able to view some project information but not for example edit in the schedule web part.
Q. David - Are there quick start implementation services, or recommended partners to do that? A. The Find a Partner link will take you to http://blogs.office.com/2013/09/03/microsoft-project-online-partner-led-trial/ which helps find active partners in the Project Online community. Also worth reviewing the Project Conference 2014 presentations – many of these were from partners. These can be found on http://channel9.msdn.com/Events/Project/2014/ and if you search for Project Online there was a fast track implementation session. I also did a session on supporting Project Online – if you are interested it is First Impressions supporting Project Server 2013 and Project Online
Q. David - Are there quick start implementation services, or recommended partners to do that?
A. The Find a Partner link will take you to http://blogs.office.com/2013/09/03/microsoft-project-online-partner-led-trial/ which helps find active partners in the Project Online community. Also worth reviewing the Project Conference 2014 presentations – many of these were from partners. These can be found on http://channel9.msdn.com/Events/Project/2014/ and if you search for Project Online there was a fast track implementation session. I also did a session on supporting Project Online – if you are interested it is First Impressions supporting Project Server 2013 and Project Online
Q. Eswara - Where is this presentation posted? A. On YouTube
Q. Eswara - Where is this presentation posted?
A. On YouTube
Some useful links we mentioned in the session:
On the 6th of May please join myself and Aik again for Getting Started with Project Pro for O365 and using it with Project Online. For the full list of Ignite events see http://ignite.office.com/events.
And finally… We (myself and Adrian) are looking to resume the Cumulative Update release webcasts – watch this space!
I am very pleased to announce the release of the April 2014 Cumulative Update (CU) for Project, Project Server and SharePoint for 2010 and 2013. Feel free to open a support case if you have any questions around this or need assistance getting these patches deployed. Remember that this release for the 2010 products, like all CUs since the August 2012 Cumulative Update, has a hard requirement on Service Pack 1 – see notes below. In most of the KB articles the term hotfix is used in place of Cumulative Update. They tend to be interchangeable terms – a Cumulative Update is just a hotfix built to a schedule. I should also point out that the individual Project Server packages are only ‘individual’ in the sense that they do not include the SharePoint patches – they are still cumulative and the April CU will contain all previous CU releases (at least back to the applicable baseline Service Pack (SP1 for 2010 and March PU in the case of Project Server 2013). The April CU for Project and Project Server 2013 also include fixes that were included in SP1.
An important point for Project Server 2013, as was the case also for the April, June, August and October CU, is the requirement to load the March 2013 Public Update – or, Service Pack 1. As you may have seen with other posts there is currently an issue with Project Server 2013 and SharePoint Server 2013 Service Pack 1 and it is not currently possible to download SP1. There will be a re-release of SP1 but I don’t currently have an ETA for the re-release. In my tests the April CU will load fine over the existing SP1, but the re-release can also re applied over any existing SP1 which will then ensure that other patches will not have any issues loading (I understand that the WAC patch will not load on SP1, and there are other patches currently being held back that also have issues – one of which is a localization patch for Project that has some key fixes – see below).
*** Update 4/22 SP1 re-release
Stefan's blog has the full download links for SP1 http://blogs.technet.com/b/stefan_gossner/archive/2014/04/22/sp1-for-sharepoint-2013-has-been-rereleased.aspx
And patch again to avoid the lost resources issue - unless you also load April CU. http://support.microsoft.com/kb/2933444
***
Another important point to add here is that there was an issue with running the SharePoint Configuration Wizard on a server with Project Server 2013 installed – this is fixed by applying the April or June CU – so a good practice would be to load the March PU, then the December CU and then run the configuration wizard (if you didn’t already load the April, June, August or October CU).
Finally, the April 2014 for Microsoft Project and Project Server 2010, can be installed with Microsoft Project and Project Server 2010 SP2 – and overcomes the issues seen with the August 2013 CU under certain conditions where the database upgrader would fail.
Project and Project Server 2013
This include a number of fixes, so Microsoft strongly recommends that you test this in a test environment based on your production environment before putting this fix live in production.
The article below provides information on how to deploy the Project Server Cumulative Update.
You can read about the fixes included in the Project and Project Server April CUs from the following articles:
There is no server rollup package this month. For details of the other Office 2013 package that you might want to load if you are running other SharePoint workloads please see http://support.microsoft.com/kb/2953733 - Office 2013 cumulative update for April 2014
Description of the Project Server 2013 hotfix package (Projectserverwfe-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863881
There are some further fixes that I know many of you are waiting for relating to timesheet view load issues, status updates for master projects, unprotected baseline issues and grouping in views – these are all part of a localization patch that has been delayed due to the SP1 issues – more information when I have it, or if you are expecting a fix and have a case open contact the support person you are dealing with.
The dbo.Versions table should show 15.0.4605.1000 after applying April CU. This is the same as the April CU client and this version can safely be used to control client access without affecting the server side scheduling.
Description of the Project 2013 hotfix package (Project-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2878276
The client version number will be 15.0.4605.1000 if you want to restrict the client version that can connect to the server. See Project Server 2013- Controlling the version of connecting clients–and PWA edits- for more details – but this version is good for both the client and server – don’tset if you have only updated the client as the server scheduling will then not work.
We are working on the specific CU installation documentation for 2013, but the process hasn’t changed from 2010 – so if you are familiar with 2010 patching or read the 2010 instructions below you should be good to go.
Also note that Click to Run installations will be automatically patched, usually within a month. Installations in Enterprise Environments that have been modified will be deployed based on the schedule determined by your Administrator.
An overview of all the Office 2010 releases for April 2014 can be found here - http://support.microsoft.com/kb/2953732 - Office 2010 cumulative update for April 2014
Server Rollup Package(Recommended):
There is no rollup package for Project Server 2010 released yet this month – for the other patches for SharePoint Server 2010 and SharePoint Foundation 2010 see the Office article above – and I will update when the rollup is released..
Individual Project Server Package (Cumulative – but only the Project Server patches):
Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2878259
There are also some fixes in the localization pack (also applicable to base language such as English US)
Description of the Project Server 2010 hotfix package (Pjsrvmui-<Language-Code>.msp; Pjsrvwfe-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2878266 (This page doesn’t look to be active yet)
The Project Server databases will be updated to version 14.0.7121.5000
Project 2010 Client Package:
Description of the Project 2010 hotfix package (Project-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2878263
The client version number is 14.0.7121.5000, in case you want to limit the connection of certain patched release to Project Server 2010.
More information on deploying the Cumulative Update:
Updates for Project Server 2010
http://technet.microsoft.com/en-us/projectserver/gg176680.aspx
As Project Server 2010 is now based on SharePoint Server 2010 we strongly recommend that you install the Project Server 2010 Server Rollup Package as there are a large number of individual server packages for SharePoint Server. The Project Server 2010 Server Rollup Package contains all the patches released in this Cumulative Update for SharePoint Foundation Server 2010, SharePoint Server 2010 and Project Server 2010.
As mentioned above, and at http://blogs.msdn.com/b/brismith/archive/2012/07/18/project-server-2010-from-august-2012-cumulative-update-onwards-you-will-also-need-to-load-sp1.aspx – the August Cumulative Update requires your client and server to already be at the Service Pack 1 (SP1) level – if you get a message saying the patch does not apply to your system then this may be the reason.
SP1 for the Project Server 2010 can be found at http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=26636 or SP2 from http://www.microsoft.com/en-us/download/details.aspx?id=39657
SP1 for the Project Professional 2010 client can be found at http://www.microsoft.com/en-us/download/details.aspx?id=26635 for the 32-bit and http://www.microsoft.com/en-us/download/details.aspx?id=26627 for the 64-bit or SP2 can be found at Service Pack 2 for Microsoft Project 2010 (KB2687457) 32-Bit Edition and Service Pack 2 for Microsoft Project 2010 (KB2687457) 64-Bit Edition.
Client Installation:
The instructions for installing the client patch are below.
NOTE: Microsoft strongly recommends testing within a NON-Production environment prior to rollout.
1. Download the hotfix from the link in the KB Article.
2. Extract the patch package by running the .exe file that you downloaded.
3. Run the extracted .exe file to apply the patch to your Project Professional/Standard client.