none
Project Server 2010 December CU Errors RRS feed

  • Question

  • I have a SharePoint Server 2010 with Project Server 2010 environment with 1 web, 1 app, and 1 database server.  A few days ago, I attempted to deploy the December 2010 Cumulative Update patches referenced in Brian's blog - SharePoint Foundation first, followed by SharePoint Server with Project Server rollups.  Following the installation of those fixes on both my web and app servers, I ran the  SharePoint 2010 Products Configuration Wizard to complete the upgrade.  The wizard failed with the following errors:

    Upgrade-date-error.log:
    Feature upgrade incomplete for Feature 'PWSFields' (Id: 'f386a1b6-b0f4-46d2-a122-b3a1e56eeb16') in Site 'http://server:port'. Exception: Invalid field name. {ca8f9dc8-8ccc-485a-adcc-b0e99c7f5e41} http://server:port
    CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.
    Exception: The system cannot find the path specified.

    When I attempt to run the Wizard again, it completes successfully this time, but only running 8 steps this time instead of the original 10.

    When I run:
     Stsadm –o localupgradestatus, I see this in the return:

      <object>
        <name>http://server:port</name>
        <type>Microsoft.SharePoint.SPSite</type>
        <level>6</level>
        <status>Needs Upgrade</status>
      </object>
      <object

    So in attempt to address the original error I run:
     Stsadm -o installfeature -name PWSFields -force

    Followed by:
     psconfig.exe -cmd upgrade -inplace b2b -force

    Command line errors returned:
     Performing configuration task 3 of 4
     Upgrading SharePoint Products...
     Failed to upgrade SharePoint Products.

    Some notable logs entries:

    PCDiagnostics:
     Task upgrade has failed with an unknown exception
    02/03/2011 15:39:44  8  ERR            Exception: Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20110203-153915-607 was updated by ENT\mspfarmadmin, in the PSCONFIG (6328) process, on machine PWN401AV141.  View the tracing log for more information about the conflict.
       at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)
       at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Microsoft.SharePoint.Administration.ISPPersistedStoreProvider.PutObject(SPPersistedObject persistedObject, Boolean ensure)
       at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()
       at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Update()
       at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ContinueOnLocalThread(Guid id, Boolean consoleOutput)
       at Microsoft.SharePoint.Upgrade.SPManager.ContinueSessionOnLocalThread(Guid id, Boolean consoleOutput)
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

    ServerName-date.log:
    File system cache monitor encoutered error, flushing in memory cache: System.IO.InternalBufferOverflowException: Too many changes at once in directory:C:\ProgramData\Microsoft\SharePoint\Config\dfd50c03-42a7-4b6a-839f-1cc6d084434e\. 
    .
    .
    .
    The configuration database was queried for a non-existent object with the id 4822bb5b-077f-4304-a983-79c090b8e4b4. Most commonly, this is caused by removing an SPFeatureDefinition without writing upgrade code to remove references to the feature from each site. 

    UpdatedConcurrencyException: The object SPUpgradeSession Name=Upgrade-20110203-153915-607 was updated by another user.  Determine if these changes will conflict, resolve any differences, and reapply the second change.  This error may also indicate a programming error caused by obtaining two copies of the same object in a single thread. Previous update information: User: ENT\mspfarmadmin Process:PSCONFIG (6328) Machine:PWN401AV141 Time:February 03, 2011 03:39:44.0000  Current update information: User: ENT\mspfarmadmin Process:PSCONFIG (6328) Machine:PWN401AV141 Time:February 03, 2011 03:39:44.3420   

    ConcurrencyException: Old Version : 146167 New Version : 146169 

    Upgrade-Date.log
    No notable errors

    SharePoint Central Admin Upgrade Status:
    This upgrade session has been stopped. Possible causes include the process being terminated abruptly or the OS has rebooted. Please restart the upgrade again.

    My sites are up, but my upgrade just won't complete successfully.  I've been googling these errors for two days and haven't found anything of substance.  Can anyone point me in the right direction?

    Thanks.
    Jason

    Friday, February 4, 2011 4:29 PM

Answers

  • Thanks Dharm for the FeatureAdmin tip.  The tool actually found a bad farm feature that I uninstalled, however it did not help with my upgrade issues.  Since this is a dev environment, I'm going to kick off a SharePoint uninstall / reinstall and see if that makes a difference.
    Monday, February 7, 2011 2:56 PM

All replies

  • I have seen a similar error with SharePoint, the issue for that case was that a feature was not deployed fully.  So the admin needed to remove the feature and re-deploy....

    Have a look at the following to help manage features - http://featureadmin.codeplex.com/

    Hope this help to begin with.....


    Best Regards, Dharmesh Patel Microsoft Technology Specialist Project Server / SharePoint / BI Reporting http://www.DharmeshPatel.co.uk
    • Proposed as answer by Dharm Patel Tuesday, February 8, 2011 6:58 AM
    Monday, February 7, 2011 9:46 AM
  • Thanks Dharm for the FeatureAdmin tip.  The tool actually found a bad farm feature that I uninstalled, however it did not help with my upgrade issues.  Since this is a dev environment, I'm going to kick off a SharePoint uninstall / reinstall and see if that makes a difference.
    Monday, February 7, 2011 2:56 PM
  • Did you ever find a solution?  A reinstall didn't help me.

    Monday, April 11, 2011 10:38 PM
  • No real solution yet.  My workaround is still to very meticulously uninstall and reinstall everything, making sure that I complete each step before moving onto the next one.  The order in which I complete them is:

    Uninstall:

    1. Backup the MSP and SharePoint databases
    2. Manually stop the IIS SharePoint websites on all servers from IIS Manager
    3. Disable the SharePoint and Project Server services on all servers from Server Manager
    4. Add/Remove Programs (1) Project Server (2) SharePoint Server on the web servers first, then the app server (not sure if order matters here)
    5. Delete all SharePoint databases (you can keep your MSP databases)
    6. Delete all SharePoint websites and App Pools from all servers

    Reinstall:

    1. Install SharePoint Server 2010 on all web and app servers, running the Configuration Wizard on the app server, then all web servers before proceeding to step 2.
    2. Install Project Server 2010 on all web and app servers, running the Configuration Wizard on the app server, then all web servers before proceeding to step 3.
    3. Run SharePoint Server 2010 Dec CU on the app server.
    4. Run the Project Server 2010 Dec CU on the app server.
    5. Complete steps 3-4 on all web servers, one at a time.
    6. Run the Configuration Wizard on the app server, then all web servers.
    7. Reconfigure the SharePoint instance, creating your web app and attaching the existing MSP databases.

    Note that I still receive the error in the original post every single time I attempt to apply a hotfix to my farm.  I have to follow the steps above (which takes several hours) to apply even the smallest hotfix.  I plan on opening a support case with Microsoft the next time I'm ready to patch my farm to get to the bottom of this issue.

    Good luck.
    Jason

    Tuesday, April 12, 2011 11:59 AM
  • I'm getting a similar issue. Though I've single server with 2 web apps. One for PWA and one for Project Workspaces.

    http://social.technet.microsoft.com/Forums/en-US/projectserver2010general/thread/e94e3f51-e1ba-4aac-bc41-3d3c4a95c5be

    Thursday, April 14, 2011 5:42 PM
  • I was able to fix my issue. Go to other thread link for details.

     

    Thursday, April 14, 2011 7:43 PM