Cascade Skyline - with Microsoft Logo and Project Support header - author Brian Smith

Project Server 2007: Cumulative Update for February 2009

Project Server 2007: Cumulative Update for February 2009

  • Comments 39

The Cumulative Updates for February 2009 for both the Office server and client components are now available (well it is only Feb 41st :))  Thanks Rob for putting these details together.  I will have another posting shortly which explains the deployment process you should adopt with the new server rollup packages first introduced in December.  Here are the February Cumulative update details:-

You can read about the fixes included in the February CU Server Rollup Packages from the following articles:

Description of the Windows SharePoint Services 3.0 cumulative update package: February 24, 2009

http://support.microsoft.com/kb/961755

Description of the SharePoint Server 2007 cumulative update package (MOSS server-package): February 24, 2009

http://support.microsoft.com/kb/961756

Note:  The Project 2007 client patch is not included in the Server Rollup Packages so you will need to deploy the individual client patch.

These KB Articles list the fixes included in the Individual Cumulative Update Package for Project Server and Project 2007:

Description of the Project Server 2007 hotfix package : February 24, 2009

http://support.microsoft.com/kb/968271

Description of the Project 2007 hotfix package (Project.msp): February 24, 2009
http://support.microsoft.com/kb/966308

Note:  KB Articles may not be released at the time of the CU release but we should see then publically available within a week or two of the CU release.

At the time of writing, 7am PST on 3/13/09 only the first KB listed above gives a good link and I would urge you to wait and see what is fixed before loading.  But if you are too impatient and want to test these out in a non-production system (which you always do – right?) then using links like the following will get you to the downloads.  This one is for KB961756 – so substitute any of the other KB numbers above to get to others.

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961756&kbln=en-us

Leave a Comment
  • Please add 6 and 3 and type the answer here:
  • Post
  • Thanks again to Rob for putting these words together on the different versions of packages in the cumulative

  • Brian,

    Do the December updates need to be installed prior to the February package, or does February contain everything from December?

    Cheers - Larry

  • Hi Larry,

    The cumulative updates are cumulative from the last Service Pack - so yes, Feb contains everything since SP1, including those items in the December CU.

    Best regards,

    Brian.

  • So do the Project Server 207 Patches exsist now ? or have they been recalled..

    Unlike prevoius updates, this time I have aonly really found info ont he the WSS and the MOSS updates.. Are the Project Server fixes part of those ?

    Is there anywhere you can point me to see a list of things that have been fixed / added to project server since the July Updates ?? Not even the MS Project Blog has any info on the Feb patches...

  • I am sorry to add to some confusion, or maybe it is just my confusion.  As I see it, you are saying the following is the plan for implementation of the patches for Project Server 2007:

    Install Project Server, then SP1, then Infrastructure Update, then the February 2009 update.  Or am I missing another patch package?

  • Does Cumulative Update for February 2009 include Infrastructure Update?

  • If using the Individual Cumulative Update Package for Project Server, KB966308, is the updated WSS binaries included in that or is there a separate Individual Cumulative Update Package for WSS that you are supposed to install prior to KB966308?

  • Brian,

    Regarding your comment "The cumulative updates are cumulative from the last Service Pack - so yes, Feb contains everything since SP1, including those items in the December CU."

    Is this referring to the sharepoint package or the Project Server 2007 package?

    If it applies to the Project Server 2007 package: Does this mean if I install SP1, the infrastructure update and the kb/968271 my Project Server 2007 will be completely up to date?

    If not, what can I do to make sure my Project Server 2007 deployment is completely up to date? Is there some way that is not digging through all these KB articles and broken links to find what I have and don't have?

    Thanks!

  • Hi Dan,

    All the fixes are available using the links given above.  MOSS Server patch also contain Project Server CU.  The articles are also now live and contain the list of items fixed.  To see all fixes since July you would need to review the articles for August, October and December also.

    Best regards,

    Brian.

  • Hi Jesse,

    All Cumulative Updates, starting in December 2008 also include the Infrastructure Update - so in your example you don't need to install the IU - just SP1 and Feb CU.  As this also applies to WSS and SharePoint you are best to load the WSS CU, and if you have MOSS, the Office Server CU (MOSS Server package) which will update MOSS and PS and contains the IU for both.  You should also load the Feb CU for all clients as there is a dependancy introduced in the IU in the way Fixed Duration tasks was handled.  There is a new TechNet article on its way through review - I will post to my blog when this is published.

    Best regards,

    Brian.

  • Hi Ksu - as per the answer above - Yes, it does include IU.

    Best regards,

    Brian.

  • Hi Peter,

    The 966308 fix is for the Project client.  968271 is for the server, but does not include WSS.  WSS Feb CU is 961755, but is not a pre-requisite of 968271, but it makes sense to keep all the packages up to date.

    Best regards,

    Brian

  • Hi Rist,

    The Project Server February CU (968271)contains all updates since SP1 - including the IU - so just SP1 and Feb CU required and you are good to go for project.  If you want then also do the same for WSS (and you will need to load SP1 as I think it is a pre-req for Project Server SP1) then .

    If you have MOSS then you can substitute the MOSS Server packages for the Project Server packages and this will update MOSS and Project Server - again just SP1 + Feb CU (961756).

    As I mention above - as there was a client/server fix that depend on each other in the IU you also need to make sure that the clients are patched at least to IU - prefereably to Feb CU (966308).

    Best regards,

    Brian.

  • Hello Brian,

    I think I have found a reproducable problem with this Update.

    When the CU 02/2009 is applied, I can not create a new PWA site any more.

    I receive this error message:

    A runtime exception was detected. Details follow.

    Message: Cannot insert duplicate key row in object 'dbo.Objects' with unique index 'IX_Objects_ClassId_ParentId_Name'.

    The statement has been terminated.

    Techinal Details:

    System.Data.SqlClient.SqlException: Cannot insert duplicate key row in object 'dbo.Objects' with unique index 'IX_Objects_ClassId_ParentId_Name'.

    The statement has been terminated.

      at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

      at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

      at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

      at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

      at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

      at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

      at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

      at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

      at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

      at Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command)

      at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)

      at Microsoft.SharePoint.Administration.SPConfigurationDatabase.PutObject(SPPersistedObject obj, Boolean ensure)

      at Microsoft.SharePoint.Administration.SPPersistedObject.Update()

      at Microsoft.SharePoint.Administration.SPJobDefinition.Update()

      at Microsoft.Office.Project.Server.Administration.ProjectPSISharedApplicationTimerJob.UpdateName()

      at Microsoft.Office.Project.Server.Administration.ProjectPSISharedApplicationTimerJob.Execute(Guid targetInstanceId)

    I created a fresh system with SP1, created a site, updated to CU12, created a site, updated to CU02/2009 and now creating the site fails.

    Best regards

    Christoph

  • Hi Christoph,

    I've had a few people on the team check this out and we do not see any issues after Feb CU - provision is working as expected.  It may be that something was already affected in your server and the CU was a coincidence.  I'd suggest opening a support incident to get to the bottom of the problem - but looks like a problem with duplicate data.  Has a previous provision failed and not been succesfully removed?

    Best regards,

    Brian.

Page 1 of 3 (39 items) 123