none
Manually running PSCONFIG is required after installing SharePoint Foundation 2010 Updates

    Question

  • Microsoft SharePoint Foundation 2010 Service Pack 1 (SP1) was recently released through Microsoft Update. On a default installation, Windows SBS 2011 Standard administrators should be able to see it in the SBS Console and would need to approve it for installation before it is offered for installation on the server.

    Since SharePoint Foundation 2010, patching SharePoint is a two-step process. The updated binaries are first installed and then PSCONFIG must be completed to update the SharePoint databases.
    Without completing PSCONFIG, you might experience unexpected SharePoint search failures and all backups may stop working on the affected server.

    The Following errors may be found in the server application log:

    Log Name: Application
    Source: Microsoft-SharePoint Products-SharePoint Foundation Search
    Event ID: 70
    Task Category: Gatherer
    Level: Error
    User: CONTOSO\spsearch
    Computer: CONTOSO-SERVER.contoso.local
    Description:
    The mount operation for the gatherer application 37ad8233-57f1-47b1-873e-6a91d0f1bc36 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.

    Log Name: Application
    Source: Microsoft-Windows-Backup
    Event ID: 521
    Level: Error
    User: SYSTEM
    Description:
    The backup operation that started at '?2011?-?07?-?06T02:12:07.198000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    You can also run the following commands to determine if you need to complete the update process with PSCONFIG:

    • Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
    • Once the shell opens, type the following command followed by enter:
      (get-spserver $env:computername).NeedsUpgrade

    image

    If the result of this command is True, then you need to complete the steps below. If the result is False then no further action is needed, if you are encountering similar events the cause will most likely not be resolved by the following steps.

    To complete the SharePoint service pack process you need to follow the same steps that were previously posted on the Official SBS Blog regarding the necessity to complete PSCONFIG after a SharePoint update. Here are the steps from the article:

    In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:

    1. Open an Administrative command prompt.
    2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
    3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

    Note: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.

    For additional information on SharePoint Foundation 2010 patching mechanism, please see the following TechNet article:

    http://technet.microsoft.com/en-us/library/ff806326.aspx


    Wednesday, July 06, 2011 7:12 AM

Answers

  • Script required after update to sharpoint otherwise backup fails -completely unacceptable and must be fixed | Microsoft Connect:
    https://connect.microsoft.com/SBS/feedback/details/733648/script-required-after-update-to-sharpoint-otherwise-backup-fails-completely-unacceptable-and-must-be-fixed

    This is a "connect" bug.  If you feel that the above solution is not good enough sign into the SBS connect site and vote up that bug.

    "there is much discussion on this topic and Microsoft need to take serious note of the severity of the numerous complaints - an update to sharepoint stops backups?! And you must manually run a corrective script ?!
    this is a small business product that was meant to need less hand holding, and yes it requires more.
    I see that Microsoft is not making fixing this a priority - I suggest a look around the various  forums where frustrated and angry people are venting. windows updates must be painless and automatic - please fix this and make communicating with your customers a priority - this is serious enough for a product recall with some country's consumer laws."

    Bugged by NMichaels           


    Friday, March 30, 2012 6:36 PM
    Moderator

All replies

  • Hi

    The backup was working fine but has now stopped.

    I have checked the error message and it is as follows

    The backup operation that started at '‎2011‎-‎06‎-‎30T11:05:23.109000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    I also ran the following tool and these are the results

    Microsoft Windows [Version 6.1.7601]

    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\cnewton2k>vssadmin list writers

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

    (C) Copyright 2001-2005 Microsoft Corp.

     

    Writer name: 'Task Scheduler Writer'

       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'VSS Metadata Store Writer'

       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'Performance Counters Writer'

       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'System Writer'

       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

       Writer Instance Id: {9e802f79-be66-4a56-bde5-a6ce04e10329}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'SqlServerWriter'

       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

       Writer Instance Id: {6373b52d-713b-42fd-a779-b145bec85071}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'SharePoint Services Writer'

       Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}

       Writer Instance Id: {104ff654-a380-4424-b573-75b2c201bade}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'ASR Writer'

       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

       Writer Instance Id: {64061a9c-5e9a-42c3-8775-ef18b770a953}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'FSRM Writer'

       Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}

       Writer Instance Id: {3c0f0952-99ae-41d9-8d0d-d228daf52ba7}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'NPS VSS Writer'

       Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}

       Writer Instance Id: {18089b6e-2ffe-46a9-8022-bcad58447297}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'WMI Writer'

       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

       Writer Instance Id: {e6f5c9f8-ec92-49ab-b11a-10884c4c9dc4}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'MSSearch Service Writer'

       Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}

       Writer Instance Id: {23f2983a-19e3-4d53-a68a-198350700e9f}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'Registry Writer'

       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

       Writer Instance Id: {f255c165-6faf-446e-a533-087c1ca90d95}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'IIS Config Writer'

       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

       Writer Instance Id: {28200e1f-0f5c-4fb4-ac5e-5b6948c681e7}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'WDS VSS Writer'

       Writer Id: {82cb5521-68db-4626-83a4-7fc6f88853e9}

       Writer Instance Id: {756a7cd2-abbe-45f3-810b-450bb4a6b659}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'TS Gateway Writer'

       Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}

       Writer Instance Id: {4f134585-b221-48fb-90a8-e710c4380ec4}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'SPSearch4 VSS Writer'

       Writer Id: {35500004-0201-0000-0000-000000000000}

       Writer Instance Id: {34a1fd6e-667d-4671-a551-2d4689c4e508}

       State: [8] Failed

       Last error: Inconsistent shadow copy

     

    Writer name: 'Dhcp Jet Writer'

       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}

       Writer Instance Id: {dc06d792-c61b-48b7-a1a6-a2ac2eaca32b}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'BITS Writer'

       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

       Writer Instance Id: {c58c550d-09ac-4a5b-9bc5-286c82bf351e}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'COM+ REGDB Writer'

       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

       Writer Instance Id: {15c4fd92-25b2-436a-a11d-7ee8b8b6f9d6}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'Microsoft Exchange Writer'

       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

       Writer Instance Id: {ee1f3ce4-1519-4a34-83fb-4af250204e7f}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'IIS Metabase Writer'

       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

       Writer Instance Id: {cc2f3cac-d32d-4dc8-ae0b-1e47cb5a7bd0}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'NTDS'

       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

       Writer Instance Id: {97bc19c0-483e-4ec1-857b-50c0d50123b5}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'Shadow Copy Optimization Writer'

       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

       Writer Instance Id: {70332f39-bdeb-41cb-9155-b6e828c69d60}

       State: [1] Stable

       Last error: No error

     

    Writer name: 'Certificate Authority'

       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}

       Writer Instance Id: {a5db7495-ddc5-4c5a-b96b-c1f76cf6d794}

       State: [5] Waiting for completion

       Last error: No error

     

    Writer name: 'FRS Writer'

       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}

       Writer Instance Id: {35d03d75-5522-489f-9616-9c67655d2e42}

       State: [5] Waiting for completion

       Last error: No error

    I have disbaled backup and then i tired to restart it but it fails every time.

    Anyone have any advice?

    Thanks in advance 

    Cheers Carl

    Thursday, June 30, 2011 11:53 AM
  • Your SharePoint services writer is waiting for completion.  Did you install any SharePoint updates lately?  (Susan edit - specifically the trigger is SharePoint Service pack 1) If you did, then you need to fix SharePoint before your backup will work.

    1. Open an Administrative command prompt.
    2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
    3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

    Try to run a backup after running this command.


    Jeff
    Thursday, June 30, 2011 1:16 PM
  • Hi Jeff

     

    Same issue as Carl, Your solution worked for me.

     

    Thank You

    Roberto

    Thursday, June 30, 2011 3:13 PM
  • I have exactly the same issue after last installing Microsoft Updates.  Backup now fails and my writer is the same status.

    Unfortunately Jeff, I have run the command and it was successful, but backup still fails.  Does it require a reboot after this?  If I don't get this fixed soon I'm going to uninstall the SharePoint updates and see what happens.

    Also there is an event log error and I remember seeing "memeber" (member being spelt wrong) so I wonder if this has anything to do with it.  I'm running out the door now but I will be back and will give more info on this stuff later.

    Thursday, June 30, 2011 7:05 PM
  • You have to run the psconfig.  You can't uninstall the SharePoint service pack.  Reboot the box and see if that fixes it and manually try the psconfig again.
     

    Thursday, June 30, 2011 8:38 PM
    Moderator
  • OK well I literally have been onsite all day, 6am start and just got back to the office 6pm... yuck.  Not even home yet.  But I quickly remoted into my server and the 12pm auto backup (lunchtime) had been successful.

    So perhaps the fix is correct, it just needs more than one minute before the backup is ready to work after completing the command?

    Either way this needs to be fixed.  Having a SharePoint update break backups until a manual command is run doesn't go down well with me or the clients who are running SBS 2011.  Hopefully the update gets fixed properly and released ASAP.

    Thanks to all.

    Friday, July 01, 2011 8:13 AM
  • Thanks a lot, this was the solution i was looking for!! not funny those sharepointupdates!!
    Kind Regards Roland Berger - MXP
    Friday, July 01, 2011 11:08 AM
  • Here's the scoop Premium.  The manual running of the command of psconfig is the expected manner in which SharePoint updates are done.  It's how SharePoint 2010 does things.

    I don't expect a "fix" here because SharePoint doesn't automatically run this command for anyone.

    Friday, July 01, 2011 2:06 PM
    Moderator
  • hi susan,

     

    i have the same problem with my sbs 2011 after the update sharepoint sp1.

    when i type  C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

    in the cmd.exe result is denied access. cmd is running as administrator.

    what can i do?

    thanks and best regards from germany

     

    uwe

     

    Friday, July 01, 2011 7:47 PM
  • Click on start, then find the command icon in the program menu, right mouse click and then click on run as administrator.

    What happens exactly?  As you should be able to run this without issues.

    Friday, July 01, 2011 7:55 PM
    Moderator
  • Good Morning,

     

    my mistake... there was a wrong command in the cmd.exe. but now everything is ok. the server works good and backup is in function.

     

    Thanks and a nice weekend.

    • Proposed as answer by FortEight Sunday, July 03, 2011 2:50 PM
    • Unproposed as answer by FortEight Sunday, July 03, 2011 2:50 PM
    Saturday, July 02, 2011 10:25 AM
  • The solution i found was similar to the one BigRedFan posted.

    Under search i typed in sharepoint, Then i right clicked on SharePoint 2010 Management Shell and ran it as Administrator.

    Then all i did was type psconfig.exe -cmd upgrade

    and everything is back to normal now.

    Sunday, July 03, 2011 3:07 PM
  • Thanks a lot. It took me some time to find out that this also applies to SearchServer Express.

     

    Wednesday, July 06, 2011 2:26 PM
  • all good until psconfig fail at last step. getting this message from upgrade log:

    [OWSTIMER] [SPUpgradeSession] [ERROR] [7/14/2011 10:49:42 AM]: Upgrade [SPContentDatabase Name=WSS_Content] failed.
    [OWSTIMER] [SPUpgradeSession] [ERROR] [7/14/2011 10:49:42 AM]: Exception: Object reference not set to an instance of an object.
    [OWSTIMER] [SPUpgradeSession] [ERROR] [7/14/2011 10:49:42 AM]:    at Microsoft.SharePoint.ApplicationRuntime.SafeControls.GetTypeFromGuid(Guid guid, Guid solutionId, String assemblyFullName, String typeFullName, Boolean throwIfNotFound)
       at
    Microsoft.SharePoint.Upgrade.SPContentDatabaseIntegrity.CheckWebParts()
       at
    Microsoft.SharePoint.Upgrade.SPContentDatabaseIntegrity.Check(Boolean calledFromHealthRule)
       at
    Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.ContentDatabaseDataIntegrityCheck()
       at
    Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.PreUpgrade()
       at
    Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

    any tips?

    Friday, July 15, 2011 2:14 PM
  • Susan

    I cannot believe that you are seriously suggesting that it is not possible for Microsoft to release a Service Pack for Sharepoint that is not fully automated and doesn't require manual command lines and a ton of hair-pulling.

    I also don't expect a Windows update, or Service Pack will break my SBS 2011 server functionality either! If a Windows Update or Service Pack runs, you don't expect it will break functionality- let alone kill the backup. Windows Updates and Service packs should be fully tested prior to release. Hotfixes on the other hand could be excused, as they have not been fully tested. However, if a dodgy Windows Update is released it is implied that it will do NO harm (since Microsoft tells us they are good for us - many sites may choose to run them -  WITHOUT any instructions! 

    I've been testing this in a Hyper-V VM with dozens of snapshots, trying to determine which new update breaks what. I started with a fresh mint SBS 2011 and still there are a few 'benign' unexplained ERRORS in the logs. So Microsoft releases an article about these 'benign' ERRORs. If they were benign, why not just make them 'WARNINGS"?

    Take any path: - install 60+ Windows updates and things only get worse, or install Win 2008 R2 Service Pack 1 on a freshly minted SBS 2011 and whoah see how many new 'benign ERRORS' we now get. Ohh and did I mention the backup is now broken along with a few other non important features like Sharepoint, etc.. C'mon for heaven's sake - give me a break! 

    A service pack release generally comes with a list of gotcha's but in all honesty, try installing SP1 against a freshly minted SBS 2011 standard and see how many problems you get. Geez- this is simply NOT good enough for a production environment. Killing Sharepoint search functionality is one thing, but killing the backup is NOT funny, and completely unacceptable for a production server. Plus now there a a truckload of so called 'benign' errors in the event logs- how the hell is an ERROR benign anyway?

    Plus it makes me look bad in the eyes of my clients, but I just blame Microsoft for it and send the CEO an email with dozens of links to this site to illuminate the sad and long list of current woes caused by Windows updates - along with the BILL!

    Brilliant stuff!

     

    Monday, July 18, 2011 9:15 AM
  • Though I hear where you are coming from the general principle of 'updates have been installed, you must now restart' has been broken, not only in respect of sharepoint but several other update targets, for some time.

    The Malicious Software Removal Tool, which has been around for quite a while, performs a scan of the system after installation. If you restart, as prompted by other updates, you interrupt this process.

    The thing that gets me is: there is a method already implemented in Windows for such tasks to be performed after restart at patch completion, automatically. It just doesn't get used.

    Tuesday, July 19, 2011 2:25 AM
  • "The Malicious Software Removal Tool, which has been around for quite a while, performs a scan of the system after installation. If you restart, as prompted by other updates, you interrupt this process."

    This illustrates my concern.  SBS Updates should be smart enough to follow rules of deployment and provide a "Novice Admin" some clue about what it does and what to expect.- ie: like this MSRT which should run on its own (with a warning to run outside production hours) and it should display scan progress so you don't reboot and interrupt the scan.

    The SBS 2011 has a very pretty GUI console with lots of animations and lights which illuminates GREEN for good, or RED to tell you the server has CRITICAL ERRORS. What is the point if the thing is permanently RED after you do an update? Makes a slick idea so useless in reality. Remember the SBS Console is aimed at giving a not-so-techy admin (read Business owner) an assist in administrating their server (I'm sure its part of the sales pitch to reduce IT admin costs??)  Microsoft SBS Team makes a point of putting lots of tiddly wizards and feedback using lights in the console exactly for that reason. I suggest that just reading this post (let alone understanding how to run PS command line tools)  would scare away 90% of the intended 'budding IT admins' audience that the SBS Team is trying to appeal to.


    Tuesday, July 19, 2011 10:43 AM
  • I'm seriously suggesting this becasue SharePoint itself releases ALL updates without automation for ANY platform they are on.

    1TB - here's the reality.  SharePoint doesn't code for SBS.  They code for themselves.  They have decided in their infinite wisdom that it's better for them that their admins run psconfig all by themselves.

    Do you ... think about this now.... really want to be the ONLY platform out here running SharePoint kicking psconfig automatically given that -no one else- will be doing this?  Remember how hit and miss that psconfig has been in the past?  Sometimes it runs, sometimes it doesn't.

    You MUST run psconfig after Service Pack 1.  Period.  The reality of SBS is that we get how the rest of Microsoft codes this stuff.  All updates, all service packs for SharePoint do not manually run a psconfig command in the 2010 era. 

    I agree with you about the "ignore these errors" and we're trying to get these revisited.  But this - asking Microsoft to automatically run psconfig - ain't gonna happen.  They won't code a SharePoint service pack just for SBS for one, for two after realizing that SharePoint doesn't do this automatically anymore as they feel the risk of automatically doing it is too great and want their admins to do it, I feel it's too high of risk for us.

    I do agree that SharePoint really needs to post somewhere how these updates should work becasue I'm still of the opinion that they take it for granted that their admins know this stuff.

     

    Tuesday, July 19, 2011 1:57 PM
    Moderator
  • The real problem here is that once I tell my clients "your backups didn't run because Microsoft's update interfered with it" the client tells me "OK, from now on, before applying any updates at all, you must get the CEO's personal sign-off". As a result, servers no longer get patched, and slowly get brittle and insecure.

     

    Tuesday, July 19, 2011 2:57 PM
  • Yeah, I hear you, but I think SBS *is* a different platform even it it is running the same underlying OS. It has a dozen tiddly little wizards like 'Fix my network' for god's sake! So obviously to keep in line with your belief that Sharepoint has to have an IT guru just to kick off PSConfig, then the answer seems to be obvious - eg, that the SBS team needs to write a "Fix my Companyweb" wizard for the target audience for which SBS is aimed at.

    I don't quiet understand your concern about "the risk of automatically doing it is too great... I feel it's too high of a risk for us." Please illuminate me- this article TELLS me I just have to run this because a Windows Update broke it and our backup, and if I don't run this our SP Search functionality and our backups are ALL broken... The risk of NOT running it is I get my backside kicked- there is NO uninstall of Sharepoint as you point out- so there is NO alternative to fix it? Unless I am missing something? It seems to me the risk is in NOT running this script! What does it matter if PSConfig is so flaky it might fail- if it doesn't work, I have no choice then but to do a full reinstall from a backup or VM snapshot.

    Bottom line: Sharepoint team should't release updates that break critical server functions like backup, without CLEAR documentation on how to fix it, and/or for SBS audience SBS Team needs to write a "Fix My Companyweb" - while the Sharepoint team continues to want everyone to be a Sharepoint/PSConfig guru".

    Sorry I don't buy it. What do other people here think? 


    Tuesday, July 19, 2011 3:38 PM
  • Any SharePoint update needs a manual psconfig.  This is the new norm of SharePoint 2010. 

    This was a service pack.  There was no immediate need to install this.   I'm an advocate that most patches do not have to be immediately installed on a well maintained server.  You should have other mitigations in place that patches are not your first defense.

    They should be tested, you should know the expected behavior and then they get installed.

     

    Tuesday, July 19, 2011 3:46 PM
    Moderator
  • SBS 2008.  SharePoint updates on that platform attempt to run psconfig and there's a measurable percent of the time that they fail.  Thus the SharePoint folks made every platform in the 2010 to do manual psconfigs.  No 2010 SharePoint kicks an automatic psconfig.

    If they, the coders of SharePoint, deemed that they can't code up a psconfig command that will 100% complete, and thus deemed it better to require the SharePoint admins do it manually - I'm not comfortable asking the SBS team to put in their code base something that kicks an automatic psconfig given our past history of it not completing successfully.

    It appears to me that the best results occur when psconfig it run manually and not from a script. 

    YOU -the admin - must manually run it.  You need to look at SharePoint updates - any updates - as a database update and thus you do not install them as a normal Microsoft update, treat it as a deployment that you do after you backup the server, do it manually - and THEN run the psconfig command.  SBS is not a diy box.  It needs a SBS admin.  You as the partner need to not automatically install any SharePoint update.  The minute you see a SharePoint update, service pack, stop.  Deploy it after a backup.  Manually run the psconfig command. 

    SharePoint needs patching TLC.  That's the reality.

    I'm asking for better documentation from SharePoint.  I do not believe that they clearly state that manual psconfig-ing is now required.  It's buried in technet content that discusses server farms.

    Tuesday, July 19, 2011 3:53 PM
    Moderator
  • Would that it were true.  Last I checked this was an SBS forum- not Sharepoint. In building a new SBS 2011 server, there is nothing to suggest that one should NOT install Service Pack 1 (or any Service Packs) in order to skip the need to do 60+ updates out of the box (I remind you that even the install wants to AUTOMATICALLY go online and do updates during the install). As I pointed out the logs have errors in them from day 1. Well maintained servers shouldn't have ERRORS in them, let alone from Day 1, or post Service Pack on a fresh install! I didn't apply any Sharepoint service packs to my knowledge- just windows6.1-KB976932-X64. Backup and and SPSearch are broken. 

    One assumes that this very clean scenario would have been rigorously 'Tested' already by Microsoft before the Service pack was released. If a Windows 2008R2 service pack breaks stuff in SBS- then the SBS team should FLAG this as NOT FOR SBS 2011- they didn't.  We're not even in a production environment yet so mitigation and lines of defense are still in the future.

    I'm still not buying it. Soz



    Tuesday, July 19, 2011 3:59 PM
  • So then manually run psconfig.  KJ is testing a script that will look at events for Sharepoint and kick a psconfig.

    I know the reality of Microsoft - especially in this day and age.  They will not release a SBS specific SharePoint update, I just don't expect that out of them. 

    What I do expect (and am asking for) is better documentation.  Right now I'm still of the strong believe that SharePoint's patching documentation sucks (to put it bluntly).

    Tuesday, July 19, 2011 4:08 PM
    Moderator
  • From the link http://www.microsoft.com/sbs/en/us/editions-overview.aspx

    Benefits of Windows Small Business Server 2011 Standard include:

    • Automatic backup of business data and simple recovery features

    • Affordable and easy to deploy, use and maintain

    • Enterprise quality functionality and productivity capabilities

    • Organize and access files from virtually anywhere

    In the light of your current observations about the *reality of Microsoft - especially in this day and age.*  I have to rethink my sales pitch.

    Tuesday, July 19, 2011 4:27 PM
  • I'm not marketing.  This hasn't been a DIY box in years.

    They'd argue your customers need to go hosted SharePoint where they do the psconfig.

    I see this as the price tag of premise.  I control, I patch.

    Tuesday, July 19, 2011 4:31 PM
    Moderator
  • I would also like to ask for better error handling in this scenario.

    There are two real problems here.

    First of all, it broke a completely unrelated component - Windows Backup.

    Second of all, the event log entries are very cryptic.

    In our situation, my client isn't actually using Sharepoint, it is just installed as part of SBS.

    The only error message in the event log showed 

    The backup operation that started at '‎2011‎-‎07‎-‎06T19:00:38.745000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

     

    It took several failed backup attempts to correlate that the Sharepoint errors are even related. That's easily a week of missed backups - not good at all.

    And then, of all the error messages, the only one that even remotely indicates what is wrong said this: "The mount operation for the gatherer application e513e507-99e8-49ce-93e6-89996b8cd3e9 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded."

    What I would also expect is that the WSUS/WUAU includes some kind of alert "manual intervention required". In WSUS I can already see exactly which machines have installed updates but not been rebooted. Why not add a mechanism that similarly says "manual intervention required" with a link to the correct Web page?

    What we have here is an automatic update that silently completes and says "everything is perfectly fine" - and then things start falling apart, simply because the "automatic" update isn't all that automatic.

     

    Tuesday, July 19, 2011 4:48 PM
  • I hear you.  The WSUS KB goes not to a SharePoint kb but to an office sp1 landing page kb which has zilch info.

    SBS doesn't control WSUS (lord knows we don't).  WSUS doesn't control what content gets published up in it's KBs, but definitely I'll bug it and ask as communication is SEVERELY lacking in these SharePoint updates.

    Tuesday, July 19, 2011 4:58 PM
    Moderator
  • I'm glad I found this post when I did.  Over a weeks worth of failed backups.  After running the PSconfig i'm back to normal. 
    Tuesday, July 19, 2011 6:25 PM
  • Can anyone confirm or deny whether SP1 will be installed automatically during an SBS2003 to SBS2011 migration, when the install wizard asks to go online to download updates?

    Forewarned is forearmed, as they say, and I'll be doing my first SBS2003 to SBS2011 migration next weekend.

    I'm assuming the guidance *is* to allow the SBS2011 installer to go online and get updates???

     

    Many thanks,

     

    Jim

    Wednesday, July 20, 2011 11:41 AM
  • Many prefer not to apply updates until the system is fully installed and configured. Get the base install working, get your data across, get rid of the old server, update.
    Wednesday, July 20, 2011 11:44 AM
  • It will not.

    (it slows down your migration when you say yes to updates)

    Wednesday, July 20, 2011 1:23 PM
    Moderator
  • I'm getting the same message.  PSConfig runs fine until the last moment and then it says configuration has failed and gives me the same exact error.  Have you had any luck in fixing the issue?
    Thursday, July 21, 2011 12:53 AM
  • I wanted to add one more item. As it turns out, the update requires a second manual step after successfully running PSCONFIG. You also need to manually create the stored procedure 'proc_UpdateStatisticsNVP'. in the Sharepoint configuration database.

    The details are described here: http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/9a7a260e-8d2d-4dc5-a9ba-f6c57e6a3659

    Fortunately, forgetting this step doesn't have as dramatic consequences as forgetting PSCONFIG. The main symptom is an event log entry from Source SharePoint Foundation, event ID 5586.

     

    Saturday, July 30, 2011 8:44 AM
  • This is getting ridiculous. SBS is sold as a solution for businesses that do not have a permanent IT staff to maintain the infrastructure and Microsoft recommend that for security and stability updates should be applied as soon as possible. Now we are effectively being told that certain updates (for that is how this is being presented whatever you call it) requires technical intervention as soon as they are applied. Why do the Sharepoint team assume that PSCONFIG will be manually run each time? Now KKeane has identified yet another task that has to be manually run.

    It is perfectly true that they don't want to code specifically for SBS but surely this applies to all levels.


    25 years of loving (and too often hating) everything Microsoft.
    Friday, August 05, 2011 10:46 PM
  • Thank you, this resolved my problem.  Would never have been able to figure this out on my own.
    Sunday, September 04, 2011 10:13 AM
  • Just a note... this fix solved my problem but I am not getting the expected result from the following upon a test run this morning

    Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.

    Once the shell opens, type the following command followed by enter:


    (get-spserver $env:computername).NeedsUpgrade

    Instead of the word TRUE (as seen from cmdline sharepoint mgmt shell)... the line comes up blank.


    R, J

    • Edited by Crakdkorn Sunday, September 11, 2011 1:20 PM
    Sunday, September 11, 2011 1:17 PM
  • I have read these comments in this thread, as I too have a broken production SBS 2011 server with no backup functionality any more. I had been under the false impression that SBS2011 was suitable for production, my understanding has now been adjusted!

    Life is too short to become a Sharepoint developer with "in depth" understanding just to run an SBS server. Frankly since earlier problems, Sharepoint isn't used any more in this system, but it is totally unacceptable that the Backup function should be rendered useless too.

     

    If anyone can guide me I'd appreciate at least getting backup to work again, I'm not bothered about Sharepoint. I get these errors in the log file from the manual PS part of the process...

    09/19/2011 07:19:30  14  ERR            The exclusive inplace upgrader timer job failed.

    and

    09/19/2011 07:19:30  14  ERR            Task upgrade has failed with a PostSetupConfigurationTaskException An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: The upgrade command is invalid or a failure has been encountered.
    Failed to upgrade SharePoint Products.

    and

    09/19/2011 07:19:30  14  ERR            An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: The upgrade command is invalid or a failure has been encountered.
    Failed to upgrade SharePoint Products.
    Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

    and

    09/19/2011 07:19:30  14  ERR              Task upgrade has failed

     

    Apologies for my tone in this post, and forgive my ranting. This process is exasperating.

    So what to do? Is there a way of fixing this? Suggestions including alternative backup tools most welcome.

    Thanks

    Ken

     

     

    Monday, September 19, 2011 3:05 PM
  • First off baby steps, let's get that backup working.

    Did you already attempt to run the psconfig command? 

    Monday, September 19, 2011 4:05 PM
    Moderator
  • Yes I have run the psconfig step. Those error messages came from the log file.

    While I was writing my previous post I was running a test backup, that completed successfully. So the mail issue is now fixed.

    Sharepoint is also happens to be working now that I have restarted IIS.

    Interestingly I get this result

    PS C:\Users\root> (get-spserver $env:computername).NeedsUpgrade
    False

     

    Any thoughts

    Ken

    Monday, September 19, 2011 6:46 PM
  • Thoughts about? Sorry not quite understanding the question.
    Monday, September 19, 2011 6:48 PM
    Moderator
  • The following was the result of the psupdate command

    "Failed to upgrade SharePoint Products.

    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfig
    urationTaskException was thrown.  Additional exception information: The upgrade
    command is invalid or a failure has been encountered.
    Failed to upgrade SharePoint Products.

    Total number of configuration settings run: 5
    Total number of successful configuration settings: 4
    Total number of unsuccessful configuration settings: 1
    Successfully stopped the configuration of SharePoint Products.
    Configuration of SharePoint Products failed.  Configuration must be performed be
    fore you use SharePoint Products.  For further details, see the diagnostic log l
    ocated at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\1
    4\LOGS\PSCDiagnostics_9_19_2011_7_9_12_896_214747051.log and the application eve
    nt log."

    The errors from the log are posted further up this thread.

    Thanks

    Ken

    Monday, September 19, 2011 7:03 PM
  • Monday, September 19, 2011 7:44 PM
    Moderator
  • I'll delete the entries here, to keep this thread tidy, and move them over to a new thread

    Thanks

    Ken

    Monday, September 19, 2011 8:30 PM
  • Thanks for this solution. I had this issue and ran the fix. I am now able to run backup.

     

    I have to agree with everyone else about this being a problem... A warning would have been nice. I've been chasing error logs and doing research to find this answer for well over a day.

    Monday, October 03, 2011 3:56 PM
  • I'm still receiving the message updating my psconfig databases when logging in to my terminal server with same policies...

    Have updated the sharepoint manually:

    1. Open an Administrative command prompt.
    2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
    3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

    This step has succeeded!

     

    After that I restart all services sharepoint e.d. / IIS and readed the blog;'

    http://blogs.technet.com/b/sbs/  says it has to do with manual scheduler task:

    Note: this message will only be cleared after the issue is resolved and the schedule task runs again that night. If needed, you can re-run the scheduled task in Task Manager, under Microsoft\Windows\Windows Small Business Server 2011 Standard.

    The task writes a log called WSSPsconfigurationNotification.log in C:\Program Files\Windows Small Business Server\logs.

    We also have the more traditional console alert, if configured, an email will be sent when this alert is detected.

    clip_image005

     

    Have run the task manually, still exist the same message error when logging in to my network!  Anyone experience the same problems?

    Thanks in advantage,

    Array01

     

     

    Tuesday, October 04, 2011 6:23 PM
  • i have been struggling with the sharepoint security up date on SBS 2008.  I have run the psconfig as shown in KB944267.  The psconfig on 2008 is run from the %\12\bin instead of what the %14\bin for 2010.  There is no 14 folder.  I am having a terrible time with this and wondered if I need to use the longer command line that has been stated in here, and whether it will work from the %\12\bin folder.  The command I am running is:

    psconfig -cmd upgrade -inplace b2b -wait -force

    results are as follows:

    Friday, October 07, 2011 12:29 AM
  • in SBS 2008 you are to also do the following before the psconfig:

     

    net stop MSSQL$MICROSOFT##SSEE

    net start MSSQL$MICROSOFT##SSEE

    Then the psconfig listed in my last post.  After that to rerun the Sharepoint Products and Technologies Configuration Wizard.  After doing all of this I get the following Errors:

    Friday, October 07, 2011 12:33 AM
  • My application event log shows the following errors:

    Friday, October 07, 2011 12:34 AM
  • See that log file referred to?

    dig it out and post in a new thread please since this is a SBS 2008 box.

    Friday, October 07, 2011 12:41 AM
    Moderator
  • that log is 1.3 mb.  here are the items from today:

     

    [SPManager] [DEBUG] [10/6/2011 6:30:39 PM]: Logging enabled Thursday, October 06, 2011 at 6:30:39 PM.
    [SPManager] [INFO] [10/6/2011 6:30:39 PM]: psconfig: Creating the upgrade manager and setting properties prior to bootstrapping upgrade
    [SPManager] [INFO] [10/6/2011 6:30:39 PM]: psconfig: Setting the upgrade mode to inplace
    [SPManager] [INFO] [10/6/2011 6:30:39 PM]: psconfig: Bootstrapping upgrade by calling SPManager.Initialized()
    [SPManager] [INFO] [10/6/2011 6:30:39 PM]: Upgrade Boot Strap starts. Initialized in Mode: InPlace, as MachineAdmin: True.
    [SPManager] [ERROR] [10/6/2011 6:30:39 PM]: No connection string to a WSS configuration database detected.
    [SPManager] [ERROR] [10/6/2011 6:30:39 PM]: SPManager.Initialize failed.
    [SPManager] [ERROR] [10/6/2011 6:30:39 PM]: No connection string to a WSS configuration database detected.
    [SPManager] [ERROR] [10/6/2011 6:30:39 PM]:    at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
    [SPManager] [INFO] [10/6/2011 6:30:39 PM]: Upgrade Boot Strap finishes. 2 errors and 0 warnings encountered.
    [SPManager] [DEBUG] [10/6/2011 7:36:52 PM]: Logging enabled Thursday, October 06, 2011 at 7:36:52 PM.
    [SPManager] [INFO] [10/6/2011 7:36:52 PM]: psconfig: Creating the upgrade manager and setting properties prior to bootstrapping upgrade
    [SPManager] [INFO] [10/6/2011 7:36:52 PM]: psconfig: Setting the upgrade mode to inplace
    [SPManager] [INFO] [10/6/2011 7:36:52 PM]: psconfig: Bootstrapping upgrade by calling SPManager.Initialized()
    [SPManager] [INFO] [10/6/2011 7:36:52 PM]: Upgrade Boot Strap starts. Initialized in Mode: InPlace, as MachineAdmin: True.
    [SPManager] [ERROR] [10/6/2011 7:36:52 PM]: No connection string to a WSS configuration database detected.
    [SPManager] [ERROR] [10/6/2011 7:36:52 PM]: SPManager.Initialize failed.
    [SPManager] [ERROR] [10/6/2011 7:36:52 PM]: No connection string to a WSS configuration database detected.
    [SPManager] [ERROR] [10/6/2011 7:36:52 PM]:    at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
    [SPManager] [INFO] [10/6/2011 7:36:52 PM]: Upgrade Boot Strap finishes. 2 errors and 0 warnings encountered.

     

    my company web has been down since 10/3.  do you want to see the log entries from when the update was originally done?

    Friday, October 07, 2011 12:48 AM
  •  

    I've spend a fortune in hours cleaning up after updates to Sharepoint including two complete restores from backup.  And it irks me that the next day, after the full restore, and serious angst from the client, there was SBS urging me to install these updates again.

    My SBS installation have more failures due to updates than any other cause.  Is that reasonable?

    Automatic updates is being turned off until Microsoft gets their head on straight.

     


    Ian 'Skip' Guyer
    Monday, October 10, 2011 5:55 AM
  • Hello,

    thanks.

    this working fine.


    • Edited by rmoro Wednesday, October 26, 2011 8:19 AM
    Wednesday, October 26, 2011 8:19 AM
  • Unable to finish psconfig upgrade after Update SBS2011 (German) to SharePoint Foundation Service Pack 1. Pleas have a look on my threat http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/03479288-abac-4c3c-9dc8-dd9bae7f8979 and help me please.

    It seems to be the same problem which has user kens999 posted further up

    Tuesday, November 08, 2011 7:46 AM
  • You hit the nail on the head. I couldn't agree with you more. It is ridiculous to be honest.
    Armel Washington, DC
    Thursday, November 10, 2011 4:23 PM
  • Very true. I have seen customers who have completely disable Windows Update to avoid having bad surprises when updates get push down their systems. Pretty scary stuff but it's common out there because people simply don't want to have to deal with the constant pain that comes with patching things with Windows Updates. I'm sure Redmond can do a better job.
    Armel Washington, DC
    Thursday, November 10, 2011 4:27 PM
  • Its tempting to do that. Surely its not beyond the wit of a Windows Update programmer to build the appropriate commands into a script that runs at the end of the update process. Or is that too complicated??? :-( Ken
    Thursday, November 10, 2011 4:33 PM
  • I am just installing Home Server 2011, and have installed Sharepoint 2010 on it. Then I went thru the updates process and lo and behold Home Server backups then didn't work, exactly as described above. I applied the magic command line fix advised above, and backups now seem to be working again. I would like to add my voice to the concern about updates which can break a system like this. Sharepoint is a pretty significant product for Microsoft's future and my opinion is that it shouldn't be possible for a Microsoft update to cripple a system like this. Don't forget that Home Server 2010 is in the retail channel, and some users are likely to struggle if they come up against a problem like this. But anyway, well done folks for getting me out of a hole.
    • Edited by KazMax Sunday, November 20, 2011 3:02 PM
    Sunday, November 20, 2011 2:59 PM
  • If you havent already enable the administrator account then log in as that. Should work fine after that
    Monday, November 21, 2011 3:59 AM
  • If you select install latest updates during install, SP1 for Sharepoint will be installed.
    Monday, November 21, 2011 10:06 PM
  • Two things.

    a. don't say yes to updates during an install, it will slow down the install

    and

    b. I've done several tests of saying yes, and I've never seen it install sp1 if you do say yes. 

    Bottom line, one should patch newly built servers -AFTER- you have installed them and made a backup.

    Monday, November 21, 2011 10:13 PM
    Moderator
  • Susan

    I cannot believe that you are seriously suggesting that it is not possible for Microsoft to release a Service Pack for Sharepoint that is not fully automated and doesn't require manual command lines and a ton of hair-pulling.

    I also don't expect a Windows update, or Service Pack will break my SBS 2011 server functionality either! If a Windows Update or Service Pack runs, you don't expect it will break functionality- let alone kill the backup. Windows Updates and Service packs should be fully tested prior to release. Hotfixes on the other hand could be excused, as they have not been fully tested. However, if a dodgy Windows Update is released it is implied that it will do NO harm (since Microsoft tells us they are good for us - many sites may choose to run them -  WITHOUT any instructions! 

    I've been testing this in a Hyper-V VM with dozens of snapshots, trying to determine which new update breaks what. I started with a fresh mint SBS 2011 and still there are a few 'benign' unexplained ERRORS in the logs. So Microsoft releases an article about these 'benign' ERRORs. If they were benign, why not just make them 'WARNINGS"?

    Take any path: - install 60+ Windows updates and things only get worse, or install Win 2008 R2 Service Pack 1 on a freshly minted SBS 2011 and whoah see how many new 'benign ERRORS' we now get. Ohh and did I mention the backup is now broken along with a few other non important features like Sharepoint, etc.. C'mon for heaven's sake - give me a break! 

    A service pack release generally comes with a list of gotcha's but in all honesty, try installing SP1 against a freshly minted SBS 2011 standard and see how many problems you get. Geez- this is simply NOT good enough for a production environment. Killing Sharepoint search functionality is one thing, but killing the backup is NOT funny, and completely unacceptable for a production server. Plus now there a a truckload of so called 'benign' errors in the event logs- how the hell is an ERROR benign anyway?

    Plus it makes me look bad in the eyes of my clients, but I just blame Microsoft for it and send the CEO an email with dozens of links to this site to illuminate the sad and long list of current woes caused by Windows updates - along with the BILL!

    Brilliant stuff!

     


    a f***** men, what a disaster. Resorting to third reformat there will be no installing sharepoint update this time. All of my clients have given up on updates they just let it crash.
    Monday, November 28, 2011 1:09 AM
  • 'continuing updates' is not at question. The question is more about 'installing updates during installation' and _just what_ updates get installed at such time. There is a known procedure (ie. not a problem but a required procedure) for the installation of sharepoint updates but it is not expected that should one decide to install updates during initial install that such updates be applied.

    We have it on reasonable authority, and by observation, that, in fact, such 'additional updates' do not get installed. You seem to be suggesting otherwise. But hang there just a sec, you are not the only one to suggest that maybe more than 'required updates' are applied should one choose to download updates during install. We don't however need 'reactionary response' to such but logs proving it so.

    Should one in fact both apply updates that get installed during installation and then apply further updates, post-installation? sounds like madness to me, until I have a basic backup of my 'base install'.

    There seems to also be a further complication as the age of 'install media' increases. Update xyz has now been replaced by update mno, in turn replaced by klm. The update logic has also been updated but that relies on update qrs having been applied to the system.

    We all agree that MS 'continuing updates' needs work, with certain components being 'more problematic' (.net and sharepoint, fer instance) than others.

    Take an easier path, install from DVD with any problems being confined to that DVD 'space', no updates. Configure the system, take a backup, and then suck down MSUpdate. (My [not so] Humble Opinion)

    Monday, November 28, 2011 1:42 AM
  • Two things.

    a. don't say yes to updates during an install, it will slow down the install

    and

    b. I've done several tests of saying yes, and I've never seen it install sp1 if you do say yes. 

    Bottom line, one should patch newly built servers -AFTER- you have installed them and made a backup.

    FWIIW: I agree. That is how I did the install and now, after installing updates, I am getting the Small Business Server health message about sharepoint needing the psconfig utility, whenever anyone with Admin privileges logs on to any machine in the domain. Running the PS cmdlet to see if an update is needed, I get false. I ran the recommended psconfig command anyway and it ran to completion. I even ran the config utility. No joy. It seems as though Sharepoint is working OK, I can run backups and my sites seem OK. I have spent a bunch of time copying profiles manually but I guess I am going to have to go back to the image I made prior to running the updates and try to get along without Sharepoint SP-1. I can't believe all the errors in the event logs versus the times I have installed Server 2008R2, I guess SBS 2011 makes for IT job security <smile>

    Lou

     


    Lou
    Thursday, December 01, 2011 2:38 AM
  • Two things.

    a. don't say yes to updates during an install, it will slow down the install

    and

    b. I've done several tests of saying yes, and I've never seen it install sp1 if you do say yes. 

    Bottom line, one should patch newly built servers -AFTER- you have installed them and made a backup.

    Normally I wouldn't, but I did this as a test. Feature shouldn't be there really.
    Monday, December 12, 2011 2:07 AM
  • I've lost two whole working days thanks to Sharepoint getting in a pickle on a customer's server. Suitable for a small business my arse. We will not be supporting this corck of shite until it's repaired.

     

    Angry? You wouldn't believe how furios I am right now.

     

    Oh, and as for the documentation? Woeful.

    Monday, December 12, 2011 1:50 PM
  • Make sure you have installed update rollup 1 for SBS 2011 because there is now an alert that tells you want to do.
    Monday, December 12, 2011 3:19 PM
    Moderator
  • Did the psconfig work?  Can you start a new thread to track the issue.
    Monday, December 12, 2011 3:21 PM
    Moderator
  • Lou?  Please start a new thread.  By any chance do you have a box with a large amount of RAM?
    Monday, December 12, 2011 3:22 PM
    Moderator
  • >>Lou?  Please start a new thread. 

    No need for this situation. The "problem" sort of went away over time. Working on a nit kind of problem that I am going to open a new  thread about.

    >> By any chance do you have a box with a large amount of RAM?

    No, only 12GB of RAM. My test system has about 6GB allocated in the VM and that seems minimal. 

    Thanks for all your helpful posts, you have the patience of a saint (New Orleans Saint) :)

     




    Lou
    Monday, December 12, 2011 5:17 PM
  • Susan, it's time to stop making excuses or blaming us guys in the field. Some of us remember Slammer and Code Red. The first rule is patch, patch then patch again. I won't even begin to  troubleshoot until I'm up to the base patch level.

    What's being said here goes against best practice as learned over years of installing and maintaining MS products.

    If we can't install an SBS box, let it fully automatically update to the latest patch revision level at the time then I'm afraid it's simply not fit for purpose.

    Please concentrate on getting the feedback to the Sharepoint team or we, the poor sods who have to support this rubbish will create solutions using different vendors products.

    I have now spent a week losing face in a customer facing environment but it looks like this prima donna is finally alive again. Do you really think I'm going to recommend using Sharepoint next time?

    Posted from my MacBook because Vista was so utterly rubbish.

     

     

    Tuesday, December 13, 2011 7:40 PM
  • I'm not making excuses, I'm stating facts and reality.  The SharePoint team will not make an automatic psconfig command on farm installed SharePoints.  I have given feedback until I'm blue in the face. 

    You either have to decide that manually running psconfig each time a SharePoint update gets installed is tattooeed on your forehead or you don't install SBS Standard and instead install SBS essentials and go for hosted SharePoint right now or as you say install something else.  SBS Standard is not a diy box.  And updating it is not automated.  I cannot get anything more than the alert in update rollup 1 where it flags you if you haven't run it.

    There's another issue with SharePoint that I'm tracking (an ugly error that some (not all) get after sp1) and their response is that they are looking to fix it in the next version (which a service pack or truly the next version) and to ignore it.  Lovely.

    I am one voice that they don't listen to.  If you feel this is important I need your voices too.

    Sign up to http://connect.microsoft.com/sbs (it takes a liveID you'll have to find a windows box to log into).  File a bug in there.  State exactly what you expect as a behavior.

    One person is not enough to give feedback.  I need you to give it too.

    Tuesday, December 13, 2011 7:52 PM
    Moderator
  • Ms. Bradley is not a Microsoft employee. But in any case, I found an easy solution to this problem: Control Panel - Programs & Features - Uninstall. Thankfully, Sharepoint uninstalls without ill effects on SBS (although the VSS writers remain behind, it doesn't seem to cause problems).
    Tuesday, December 13, 2011 11:06 PM
  • Thank you a million! I tried this (with slight modification) and it worked like a charm. (The issue was SBS2011 backup failure afer service pack update.)
    Wednesday, December 14, 2011 5:20 AM
  • Happy New Year!

    Thank you for posting this, saved me a lot of time. The backup error was very important to me and I just had to sort it out real fast.

     


    I am not a vegetarian because I love animals; I am a vegetarian because I hate plants.
    Tuesday, January 03, 2012 10:58 AM
  • Hi,

    After installing SP1 in server Configuration DB version is not updated and not able to restore the backup of site having higher version, after following above commands Configuration DB version got updated and site got restored.

    Thank you for the post.


    Wednesday, February 29, 2012 11:11 AM
  • Microsoft SharePoint Foundation 2010 Service Pack 1 (SP1) was recently released through Microsoft Update. On a default installation, Windows SBS 2011 Standard administrators should be able to see it in the SBS Console and would need to approve it for installation before it is offered for installation on the server.

    Since SharePoint Foundation 2010, patching SharePoint is a two-step process. The updated binaries are first installed and then PSCONFIG must be completed to update the SharePoint databases.
    Without completing PSCONFIG, you might experience unexpected SharePoint search failures and all backups may stop working on the affected server.

    The Following errors may be found in the server application log:

    Log Name: Application
    Source: Microsoft-SharePoint Products-SharePoint Foundation Search
    Event ID: 70
    Task Category: Gatherer
    Level: Error
    User: CONTOSO\spsearch
    Computer: CONTOSO-SERVER.contoso.local
    Description:
    The mount operation for the gatherer application 37ad8233-57f1-47b1-873e-6a91d0f1bc36 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.

    Log Name: Application
    Source: Microsoft-Windows-Backup
    Event ID: 521
    Level: Error
    User: SYSTEM
    Description:
    The backup operation that started at '?2011?-?07?-?06T02:12:07.198000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    You can also run the following commands to determine if you need to complete the update process with PSCONFIG:

    • Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
    • Once the shell opens, type the following command followed by enter:
      (get-spserver $env:computername).NeedsUpgrade

    image

    If the result of this command is True, then you need to complete the steps below. If the result is False then no further action is needed, if you are encountering similar events the cause will most likely not be resolved by the following steps.

    To complete the SharePoint service pack process you need to follow the same steps that were previously posted on the Official SBS Blog regarding the necessity to complete PSCONFIG after a SharePoint update. Here are the steps from the article:

    In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:

    1. Open an Administrative command prompt.
    2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
    3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

    Note: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.

    For additional information on SharePoint Foundation 2010 patching mechanism, please see the following TechNet article:

    http://technet.microsoft.com/en-us/library/ff806326.aspx

    Thank's a lot for this article!

    Martin

    Friday, March 02, 2012 9:25 PM
  • Hello everyone,

    I just want to weigh in on this thread, I'm going to try to keep it short as I can... but it's likely going to go long.

    18 years. 18 years of promoting, selling, and servicing MS. DOS then Win for Workgroups then NT 3.1 all through 2008. Exchange the whole way. SQL Server, IIS. Many 1000's of licensing dollars sent to Redmond, thanks to me. I was an MCP before Y2K. I started "cloud" computing through SPLA in 2004. Now I am getting out. Done with SPLA, been selling off customers for the past 2 years, and now moving my last customer - my best friend's business - to SBS2011 so I can shovel cow pies or make hamburgers or something more rewarding and less stressful.

    Today I had to go in and physically get on the SBS server console because Remote Admin quit working. Service Pack 1 installed last night, broke something with RPC. I don't know how it got fixed, 2 reboots didn't work, disabling IP6 didn't work... yeah unrelated to this thread but bear with me. I installed 5 more Updates: 4 were .NET related, 1 was for time zones or DST. Rebooted and magically my RPC related Remote Admin problem was fixed. I can only suspect that MS hides bug fixes in other updates from time to time to save face. This is not the first time I've seen this in my 18 years. Disgust level rising again.

    Moved on to the Sharepoint update PSCONFIG alert that brought me to this thread. Reading through this furthers my disgust with Microsoft, and reassures me that ending my career is the right thing to do. Garbage. Pure garbage. Yeah the thread helped me fix it, although I still get a warning dialog when logging in. Hope it goes away overnight, because tomorrow I fear as I continue to build this new system more baloney will arise.

    How am I supposed to feel confident that this customer, these people that are good friends I've known for nearly 30 years, are going to come away with a reliable business system? Like so many big tech companies, MS has gotten big and smug and now puts out crap. Like Digital Equipment eventually did. Like IBM did with the Sys36/AS400 platform. Like Novell did with Netware. Well... DEC is ancient history, the AS/400 market is nearly dead, and who even talks about Novell nowadays? 

    I am so angry I dedicated my best years, age 21-39, to Microsoft. Wish I had a criminal mind, should have pirated every one of those apps. Microsoft will either die, like DEC and like Novell, or they will remain as a legacy support business like IBM has become, selling to those who can't afford to migrate their data to something else.

    The crummy code behind SBS2011 is the beginning of the end. And surely someone will reply "MS is here to stay, bud". And I will read that and remember the DEC guy working on that corrupted VAX back in '94: "Digital Equipment is here to stay, bud".

    All for now, done ranting. Mod will probably delete this anyway, cant hurt sales you know. Cant let the "marks" in on the "con". 

    Sent from my 2 month old Mac Pro on Safari. Laughing Out Loud. Goodbye Microsoft and your fanboys (and fangirls - Susan).

    Nate Erb

    Friday, March 23, 2012 10:22 PM
  • ...and no the post won't be deleted, and yes the alert will go (or should) go away in 24 hours.
    Friday, March 23, 2012 10:26 PM
    Moderator
  • Script required after update to sharpoint otherwise backup fails -completely unacceptable and must be fixed | Microsoft Connect:
    https://connect.microsoft.com/SBS/feedback/details/733648/script-required-after-update-to-sharpoint-otherwise-backup-fails-completely-unacceptable-and-must-be-fixed

    This is a "connect" bug.  If you feel that the above solution is not good enough sign into the SBS connect site and vote up that bug.

    "there is much discussion on this topic and Microsoft need to take serious note of the severity of the numerous complaints - an update to sharepoint stops backups?! And you must manually run a corrective script ?!
    this is a small business product that was meant to need less hand holding, and yes it requires more.
    I see that Microsoft is not making fixing this a priority - I suggest a look around the various  forums where frustrated and angry people are venting. windows updates must be painless and automatic - please fix this and make communicating with your customers a priority - this is serious enough for a product recall with some country's consumer laws."

    Bugged by NMichaels           


    Friday, March 30, 2012 6:36 PM
    Moderator
  • After spending several weeks trying to achieve a stable installation (after applying updates) of SBS 2011 server either virtually or physically suddenly I have come to realise why Microsoft are plugging online cloud solutions so heavily these days. In my opinion SBS2011 is so seriously flawed that small businesses will have no choice but to convert to online cloud solutions. SBS 2011 critical errors are so common it makes server administration for small businesses completely impossible as they would require at least one full time server administrator just to deal with the constant critical errors that are produced.

    I may be the exception but i've yet to come across a small business that knows what Sharepoint is let alone uses the product. It is a shame Microsoft didn't leave the option of adding it as a server role that could be installed only if required. Many applications installed on SBS 2011 by default are never going to be needed so why include them in the first place. Microsoft Server exams always stipulate not adding unnecessary programs, roles, features etc on a Domain Controller, however the SBS development team were to busy adding junk to SBS 2011 instead of reading the Microsoft server books on how it's supposed to be done.

    Perhaps this is another reason why Microsoft Partners dealing with small businesses will now require the administrating office 365 exam to qualify for the new Microsoft small business competency. We shall wait to see if Microsoft’s big gamble of putting all their eggs into one basket "THE CLOUD" will pay off in the not too distant future.


    • Edited by back2work Monday, June 11, 2012 3:04 PM
    Thursday, June 07, 2012 1:41 AM
  • I got a reply from Microsoft regarding the Sharepoint and multiple critical (ok to ignore) errors.

    They gave me the usual "run PSCONFIG" line but I replied that it was simply not good enough and did not match the 'ease of use and maintainabilty' promoted in their advertising. Didn't Microsoft test SBS 2011 before it shipped ??!? They would have seen these problems and at the very least put an erratta sheet in with the product - or better yet, removed Sharepoint if it caused problems.

    To ship a combination of products in SBS 2011 that cause multiple critical errors - THAT YOU WONT FIX is costing us thousands of dollars in time and headaches. Trying to explain to business owners who see these errors, that Microsoft's development team are not good enough to produce an error free product from day one, is costing us even more time/money and makes us look like liars !

    THIS IS MEANT TO BE AN EASY TO USE PRODUCT FOR SMALL BUSINESS as you advertise.

    This is, frankly, false advertising and deceptive - Illegal business behavior in most countries.

    I would really like to send Microsoft a bill for this - class actions have been done for less - and yes IM ANGRY !

    Just the PSCONFIG issue alone needs a global warning (it's not even mentioned in any SBS books !) - or better yet a product recall - Im not joking, it's THAT serious - to break your backup program is unforgivable.

    We are not all going cloud ! The cloud is not the be all and end all - ask Sony about that ;)

    There are thousands of us loyal administrators waiting for you to fix your broken product !

    PLEASE FIX it SOON, I remember a time when MS cared.....



    • Edited by Nmichaels Monday, June 11, 2012 12:00 PM spelling
    Monday, June 11, 2012 11:55 AM
  • Hello,

    I'm running SBS 2011 on top of VMWARE ESXi 5.0 U1 (HP custom image installed).

    I ran PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures  in my SBS 2011 environment and then I did a reboot of the server. After restart guess what: BOOTMGR is missing; Press CTRL+ALT+DEL to restart. So, be very carefully what you run.


    Monday, June 25, 2012 6:50 PM
  • This command would ABSOLUTELY not cause a bootmgr failure.

    You have hardware issues that dropped data on you .  This command only upgrades SharePoint.

    Monday, June 25, 2012 7:04 PM
    Moderator
  • Dear Susan,

    The hardware from the host is ok. The server is newly installed (brand new HP DL380 G7 - 1 week in test environment and 3 days in production).

    I did many restarts before PSConfig.exe and nothing happened. But after this command the server went down.

    Please have in mind that:

    - SBS 2011 is running in virtual environment (maybe this is in conflict with PSConfig)

    - The IP address of the SBS 2011 server has changed from test VLAN to production VLAN

    Ionut

    Tuesday, June 26, 2012 9:36 AM
  • No.  Running as a guest in a virtual machine is supported.

    I have psconfig'd many a box and the failure of bootmgr is a very specific failure that psconfig would not cause.

    Psconifig only runs a script to update SharePoint.

    It would also not change the IP address of the box.  I know what this script does.  I've done it tons of time successfully.  I know SBS boxes.  It would not cause your symptoms.

    A newly installed box is right at the point in time when "stuff happens".

    http://pcsupport.about.com/od/findbyerrormessage/a/bootmgr-is-missing.htm

    By any chance did you have some usb device or some other virtual boot item in a position where the server booted from that and not the harddrive it's supposed to?

    Tuesday, June 26, 2012 1:44 PM
    Moderator
  • Susan;

    Reading thru this thread....we are going to replace our 6 Servers and were going to go to Server 2008.  Seeing that Microsoft isn't interested in supporting the small business community what OS other than Microsoft might you recommend?  Thanks

    Tuesday, June 26, 2012 1:46 PM
  • Greg, firstly this has nothing to do with pscoinfig, so I'd start a new thread.

    Secondly why do you think that Microsoft isn't interested in supporting the Small biz community?

    SharePoint 2010 needs a manual psconfig command (fact).  Normal SharePoint does not get it done for them.  Microsoft has a blog, a sticky post, a BPA rule, a reminder all stuck inside of SBS to tell you to do this command, none of which are in the normal SharePoint standalone product.

    Furthermore, there's a second product called SBS Essentials which does not include SharePoint as an alternative.

    Tuesday, June 26, 2012 2:01 PM
    Moderator
  • Because MS won't fix a known problem? My Apple stuff 'just works', SBS needs to be the same. Running scripts is a massive no-no for SBS. 

    What is MS's Mantra? Always use the wizards, SBS needs to adhere to this...

    Tuesday, June 26, 2012 3:57 PM
  • Let me ask you this...

    SharePoint 2010 as a product does not get updated via Microsoft update when installed in farm mode.  Microsoft changed it so that SBS will get offered security updates otherwise we'd not even be offered them via MU or WSUS.

    Would you prefer that SBS be the ONLY product that attempts to run psconfig knowing that on the SBS 2008 platform it's not 100% successful when it attempts to do so, or would you as a Microsoft partner rather be in charge of patching SharePoint on your schedule?  That's your request here.  You are asking SBS Standard to be the only platform that runs this psconfig command automatically.

    Truly is that what you want?

    Vote up the connect bug or install SBS Essentials that does not include SharePoint.  SBS standard (and even SBS 2008) needs an admin otherwise your clients wouldn't need you.

    Tuesday, June 26, 2012 4:06 PM
    Moderator
  • IMO Most Small Businesses opt for SBS 2011 Standard over Essentials due to Exchange 2010 being included. I would guess that the percentage of small businesses purchasing SBS 2011 Standard because SharePoint is included is fairly small. Hosted Exchange is great for built up urban areas with fast broadband connections but for Small Business in rural and less built up areas the cloud and SBS Essentials can be problematic. SBS 2003 had a box to tick if you wanted to install internal sites so why not have this on 2011. Also with SBS 2003 you're asked if you want to install DHCP server so saying no and using your own VPN or hardware firewall for DHCP was a breeze. Server 2008R2 requires vastly more hands on than SBS 2011 so that's not a good solution for most small businesses.  Regarding the Critical Errors that should be ignored I've learnt that this is great advice as trying to remove them only breeds more of them and eventually a complete re-install from backup is required. Overall I think SBS 2011 Standard is a good product but I question how much experience the development team actually have within small business environments.

    Tuesday, June 26, 2012 5:16 PM
  • Susan, I think that's a good question. There is a third option - and that's what I did for my clients. My Small Business Clients don't buy SBS for Sharepoint. Most don't even know what it is or what to use it for. So I simply remove Sharepoint from the SBS Server. Problem solved.

    I think in the next version, if they can't fix this issue, Microsoft should look into removing Sharepoint from SBS Standard altogether or offering it as an optional add-on.

    Tuesday, June 26, 2012 6:20 PM
  • Let me ask you this...

    SharePoint 2010 as a product does not get updated via Microsoft update when installed in farm mode.  Microsoft changed it so that SBS will get offered security updates otherwise we'd not even be offered them via MU or WSUS.

    Would you prefer that SBS be the ONLY product that attempts to run psconfig knowing that on the SBS 2008 platform it's not 100% successful when it attempts to do so, or would you as a Microsoft partner rather be in charge of patching SharePoint on your schedule?  That's your request here.  You are asking SBS Standard to be the only platform that runs this psconfig command automatically.

    Truly is that what you want?

    Vote up the connect bug or install SBS Essentials that does not include SharePoint.  SBS standard (and even SBS 2008) needs an admin otherwise your clients wouldn't need you.

    Susan,

    How much would you expect  us to charge our customers to fix a known MS fault when WE recommended the product in the first place?

    In *the real world* the conversation ends with the phrase "I'm not bloody paying for that" so the reseller has to take a four hour hit on the chin the first time they encounter the fault. 

    This is what irks me about MS, they leave known faults out in the wild and expect us to fathom out what's wrong. If we need to learn MS's scripting language it probably makes more sense to learn *Nix and take them down another path.

    SBS is designed as a Wizard driven GUI product, it needs to work as such. 

    As has been said, Sharepoint is a niche product and has very little use in a small business environment.

    Wednesday, June 27, 2012 8:21 AM
  • Hello,

    I must agree with kkeane: Microsoft must allow us not to install Sharepoint by default. If the client wants it then put the DVD in the server and install it. Most clients want Windows 2008 server and Exchange.

    Susan,

    I have checked the virtual machine settings and the only thing that attracted my attention was that the host DVD drive is connected to the virtual machine (but no DVD in the unit). I have done several reboots of the virtual machine before PSConfig and all went ok (with the host dvd device connected and nothing happened).

    In this week-end I will do again a full backup of the virtual machine and then I will try again the PSConfig command with the DVD device disconnected.

    Thank you,

    Ionut

    Thursday, June 28, 2012 7:42 AM
  • Dear Susan,

    You are right: PSConfig does not make your system unbootable. But marking C: drive as ACTIVE does. So, that is why I got bootmgr missing message.

    I have ran PSConfig and followed by "stsadm -o registerwsswriter" and now I can use Windows Server Backup.

    My apologies to you all.

    Thanks,

    Ionut

    Sunday, July 01, 2012 6:27 PM
  • The latest SharePoint updates would not take continually failing at step 5 out of 6. I'm using SBS2011 Premium with SQL2008 and SharePoint DB installed on a seperate server. To resolve I added -wait to the PSConfig.exe line. PSConfig completed successfully after 6 failed attempts.

    I followed the steps as described in order to update the SharePoint databases;

    1. Open an Administrative command prompt.
    2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
    3. Run PSConfig.exe -cmd upgrade -inplace b2b -wait -force -cmd applicationcontent -install -cmd installfeatures

     
    • Proposed as answer by TonyMac Friday, August 03, 2012 1:17 AM
    Friday, August 03, 2012 1:16 AM
  • Can I firstly say a massive 'THANK YOU!' to Susan and all the others here who provided information.

    Ran the script and now the only SBS2011 server we have seems happy. We'll see if the backups (which have failed for a month) are working later...

    Needless to say I wasn't popular when I installed updates on a server which had only been updated once since install (60+ Updates) only to break the backup! (The speed increase was the only sweetener!)

    Unfortunately that's the way it goes in SME's - often the person administrating isn't involved in the purchase side. If I were they'd definately not have SBS2011 with Exchange, Sharepoint, IIS and a huge Database program on a poor (ie heavily struggling)  Xeon E5506 with only 12GB of RAM... For 3 users!

    Now if only there was an easy way to uninstall Sharepoint (it's unused) without breaking further updates...

    Thursday, August 09, 2012 2:32 PM
  • Microsoft SharePoint Foundation 2010 Service Pack 1 (SP1) was recently released through Microsoft Update. On a default installation, Windows SBS 2011 Standard administrators should be able to see it in the SBS Console and would need to approve it for installation before it is offered for installation on the server.

    Since SharePoint Foundation 2010, patching SharePoint is a two-step process. The updated binaries are first installed and then PSCONFIG must be completed to update the SharePoint databases.
    Without completing PSCONFIG, you might experience unexpected SharePoint search failures and all backups may stop working on the affected server.

    The Following errors may be found in the server application log:

    Log Name: Application
    Source: Microsoft-SharePoint Products-SharePoint Foundation Search
    Event ID: 70
    Task Category: Gatherer
    Level: Error
    User: CONTOSO\spsearch
    Computer: CONTOSO-SERVER.contoso.local
    Description:
    The mount operation for the gatherer application 37ad8233-57f1-47b1-873e-6a91d0f1bc36 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.

    Log Name: Application
    Source: Microsoft-Windows-Backup
    Event ID: 521
    Level: Error
    User: SYSTEM
    Description:
    The backup operation that started at '?2011?-?07?-?06T02:12:07.198000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    You can also run the following commands to determine if you need to complete the update process with PSCONFIG:

    • Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
    • Once the shell opens, type the following command followed by enter:
      (get-spserver $env:computername).NeedsUpgrade

    image

    If the result of this command is True, then you need to complete the steps below. If the result is False then no further action is needed, if you are encountering similar events the cause will most likely not be resolved by the following steps.

    To complete the SharePoint service pack process you need to follow the same steps that were previously posted on the Official SBS Blog regarding the necessity to complete PSCONFIG after a SharePoint update. Here are the steps from the article:

    In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:

    1. Open an Administrative command prompt.
    2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
    3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

    Note: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.

    For additional information on SharePoint Foundation 2010 patching mechanism, please see the following TechNet article:

    http://technet.microsoft.com/en-us/library/ff806326.aspx


    After SP1 installation I face similar problems (before everything was fine).

    Now Exchangeserver is not running anymore and remote acces is not possible.

    (get-spserver $env:computername).NeedsUpgrade  not working because my server name is "name-server" .  Returning argument  no server with the name "-server"

    PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures. Not working. Returning error IIS must be installed and running. I checked, and it is.

    These errors cost me two day's allready. Software is running on a brand new HP-350P Gen8 server.

    Hope anybody can be of assistance.

    Thursday, September 13, 2012 7:27 PM
  • Can you start a new post as I really hate posting on these forum threads that are so long and it takes the page so long to get posted.

    I started your thread over there: http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/0b503434-f2a2-47e6-882e-4255b0843935

    Friday, September 14, 2012 12:50 AM
    Moderator
  • Very useful thanks, have just rolled this fix out across our SBS 2011 base. I find it difficult to understand however this cannot have been fixed automatically....
    Wednesday, September 26, 2012 2:10 PM
  • I did another action to the failiure of PsConfig.

    I just ran it again, and no error :)

    Not very scientific or smart, but it works .

    Wednesday, November 07, 2012 9:40 AM
  • Out of the 5 Servers we had failing this worked for 3 of them!

    Thankyou so much!

    Thursday, December 27, 2012 12:15 PM
  • I have exactly the same problem as you had, how did you resolve the issue. PSConfig ran fine, but the Error Message keeps appearing.

    Friday, January 11, 2013 8:57 PM
  • Thanks for posting this, fixed my issues and I wrote about my experience on my blog.
    Friday, May 31, 2013 1:36 PM
  • Same here. Running SP Foundation 2010 with backend SQLServ 2008 R2 Express. The hyperlink suggests it's looking for an upgrade to non-Express MSSQL. Annoying. But the site loads and seems to function. Haven't tried backup yet.
    Saturday, July 20, 2013 3:52 PM
  • I remember when America and Microsoft sold the best and where the best. Now America and Microsoft sell complete dog shit. Good luck selling dog shit and ruling the world cos your going to need it!
    Sunday, July 21, 2013 2:57 AM
  • I remember when servers were only run by IT admins, when they were only in data centers and we didn't deal with all of this.  We're going back to that model.  SharePoint since 2010 ... and still does even in the server farms - needs to have this command done by the IT admin when the server is ready to have the patch deployed. 

    If you are still running SBS 2011, put psconfig on your todo list after a sharepoint update.  BTW what patch are you referring to as there wasn't a SharePoint patch out this month?


    Don't Retire TechNet

    Sunday, July 21, 2013 6:52 AM
    Moderator
  • OK, so I threw caution to the wind and used the SQL Server install to update my 2008 R2 Express to 2012 Express. Surprisingly, it worked like a charm, and Sharepoint responded well. I had a client PC logged in to Sharepoint and it refreshed without requiring a re-login. It's not asking me to update the database any longer. (It is nowasking me to not use the same account for the SP-80 service as for the Central Admin, though). So, to me it seems it doesn't like SQL Server 2008, at least the Express version.
    Sunday, July 21, 2013 12:23 PM
  • Same here.  I did the PSConfig update on my SBS 2011 server in late May, and the PSConfig update command completed without errors.  I then ran “(get-spserver $env:computername).NeedsUpgrade” from SharePoint powershell and got a ‘false’ response, indicating that the SharePoint updates have been completed.  This should make the message go away, I found an article regarding the message popup and running a manual task in the task scheduler on the server to update WSSconfiglogs, so I did this.  All is good with SharePoint, but the message is still popping up 2 months after the update was completed.  Whenever the administrator account logs on to the server or ANY PC on the domain, it receives the psconfig message.  Something is broken with the SBS Console Health Alert notification, because the update has already been done and confirmed, this message was supposed to go away 24 hours after the update.  This has not happened.
    Friday, September 06, 2013 5:07 PM
  • I ran the PSConfig script and now most of the event 8230 status 1376 are gone except for the warnings that occur every hour at precisly x:00:01 .


    MWebjorn

    Saturday, October 05, 2013 8:06 AM
  • I found I had to run iisreset after this as well otherwise Activesync was failing.

    Wednesday, October 23, 2013 9:22 PM
  • I have exactly the same problem as you had, how did you resolve the issue. PSConfig ran fine, but the Error Message keeps appearing.


    Does the error messages appear at random times, or is there some regularity in when they appear?

    MWebjorn

    Thursday, October 24, 2013 5:43 AM