locked
PSConfig fails - "Failed to upgrade SharePoint Products" RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am stumped on this one and I can't seem to find anything similar posted.

     

    When I run the PSCONFIG I get the following:

     

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>PSCo
    nfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd
    installfeatures
    SharePoint Products Configuration Wizard version 14.0.6009.1000. Copyright (C) M
    icrosoft Corporation 2010. All rights reserved.

    Performing configuration task 1 of 6
    Initializing SharePoint Products upgrade...

    Waiting to get a lock to upgrade the farm.

    Successfully initialized SharePoint Products upgrade.

    Performing configuration task 2 of 6
    Initiating the upgrade sequence...

    Successfully initiated the upgrade sequence.

    Performing configuration task 3 of 6
    Registering SharePoint features...

    Successfully installed feature C:\Program Files\Common Files\Microsoft Shared\We
    b Server Extensions\14\Template\Features\ReportServerStapling\Feature.xml.

    Successfully registered SharePoint features.

    Performing configuration task 4 of 6
    Installing the application content files...

    Installing the SharePoint Central Administration Web Application content files..
    .

    Installing the SharePoint Web Application content files...

    Successfully installed the application content files.

    Performing configuration task 5 of 6
    Upgrading SharePoint Products...

    10.00%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_21_2011_17_9_26_952_800986324.log and the application ev
    ent log.

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>

     

     

    Any ideas?

    SBS 2011 Standard, Single server

     

    Thanks,

    Saturday, September 24, 2011 1:21 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    Don't rebuild.  I think that's a red herring.  Ping me at susan-at-msmvps.com and I'll set up a case because I'd like to know why it's saying this.
    • Marked as answer by Sean Zhu - Friday, September 30, 2011 3:30 AM
    Tuesday, September 27, 2011 2:07 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\1
    4\LOGS\PSCDiagnostics_9_21_2011_17_9_26_952_800986324.log
     
    What's in there?
     
    Saturday, September 24, 2011 1:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This is the warning and errors that I am getting. 

     

     

     

    09/21/2011 17:10:10  5  WRN            Failed to add the service connection point for this farm
    09/21/2011 17:10:10  5  INF            Entering function StringResourceManager.GetResourceString
    09/21/2011 17:10:10  5  INF              Resource id to be retrieved is ServiceConnectionPointNotCreatedEventLog for language English (United States)
    09/21/2011 17:10:10  5  INF              Resource retrieved id ServiceConnectionPointNotCreatedEventLog is Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
    09/21/2011 17:10:10  5  INF            Leaving function StringResourceManager.GetResourceString
    09/21/2011 17:10:10  5  WRN            Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
    Microsoft.SharePoint.SPException: The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=XXXX,DC=local doesn't exist in the directory.
       at Microsoft.SharePoint.Administration.SPServiceConnectionPoint.Ensure(String serviceBindingInformation)
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()

    09/21/2011 17:10:29  5  ERR            The exclusive inplace upgrader timer job failed.

    09/21/2011 17:10:29  5  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.
    09/21/2011 17:10:29  5  INF            Entering function Common.BuildExceptionInformation
    09/21/2011 17:10:29  5  INF              Entering function Common.BuildExceptionMessage
    09/21/2011 17:10:29  5  INF                Entering function StringResourceManager.GetResourceString
    09/21/2011 17:10:29  5  INF                  Resource id to be retrieved is ExceptionInfo for language English (United States)
    09/21/2011 17:10:29  5  INF                  Resource retrieved id ExceptionInfo is An exception of type {0} was thrown.  Additional exception information: {1}
    09/21/2011 17:10:29  5  INF                Leaving function StringResourceManager.GetResourceString
    09/21/2011 17:10:29  5  INF              Leaving function Common.BuildExceptionMessage
    09/21/2011 17:10:29  5  INF            Leaving function Common.BuildExceptionInformation
    09/21/2011 17:10:29  5  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()


    09/21/2011 17:10:29  1  ERR          Task upgrade SharePoint Products failed, so stopping execution of the engine

    09/21/2011 17:10:29  1  ERR          Failed to upgrade SharePoint Products.
    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()

     

    Background - this server was running fine and when the last round of updates were installed we got the backup fail problem reported in many otherthreads.  PSCONFIG was run and it fails with these errors.

    Thank you for looking at this.

    Saturday, September 24, 2011 1:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Backups will fail until this psconfig runs.

    http://www.jonthenerd.com/2011/06/30/sharepoint-2010-sp1-upgrade-error-unable-to-create-a-service-connection-point-in-the-current-active-directory-domain/

    Can you see if ensuring timer service is working?  I'm also asking around to see for more guidance, but since a security patch caused this it's a free call to Microsoft.  Ultimately I would recommend a call to support.  Since it's a security patch it will be a free call and if you have any issues please email me at susan-at-msmvps.com to get a case open.

     

     

     

    Saturday, September 24, 2011 2:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The timer service is running, just checked it again to be sure.

    I will keep trouble shooting and call support if I cant sort it out.

    Thank you Susan for your assistance. 

    I will post back here if/when I get this fixed.

    Thank You,

    CP

    Saturday, September 24, 2011 2:25 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    SharePoint 2010 June 2010 Cumulative Update installation failed:
    http://www.wictorwilen.se/Post/SharePoint-2010-June-2010-Cumulative-Update-installation-failed.aspx

    Turn off uac and try that command again.

    • Proposed as answer by Atli Þ Monday, September 26, 2011 10:30 AM
    Saturday, September 24, 2011 2:31 AM
  • Question
    Sign in to vote
    2
    Sign in to vote
    And you are run-as-admin on that command prompt yes?
    • Proposed as answer by steve-areeno Monday, August 17, 2015 12:02 PM
    Sunday, September 25, 2011 2:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We tried truning off the UAC and we are opening command prompt with run-as-admin.

    It appears we have a bigger problen then just this, it apprears we have a sharpoint problem (Sharepoint container missing from AD).

    I may have to resort to doing a repair install or a re-build. 

    It is odd as everything on this server runs perfect except backup.

    Tuesday, September 27, 2011 1:56 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Don't rebuild.  I think that's a red herring.  Ping me at susan-at-msmvps.com and I'll set up a case because I'd like to know why it's saying this.
    • Marked as answer by Sean Zhu - Friday, September 30, 2011 3:30 AM
    Tuesday, September 27, 2011 2:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello, I have the exact same problem, I know how you solved?
    Thank you.
    Monday, October 3, 2011 6:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    What is the answer to this question?  It's shown as an answer but there is no answer listed.

    Thursday, October 20, 2011 12:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    There's no one answer fix all.

    What does the error log say, post up that log file it points to.  Start a new thread, if you don't have a technet cases (as they will comp you back due to the fact it's a security patch issue) ping me for help opening up a case.

    Thursday, October 20, 2011 12:55 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello, I have also the same problem. I postet my LOG on http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/03479288-abac-4c3c-9dc8-dd9bae7f8979 . I also try to run-as-admin on that command prompt and clear the cache but the problem still exist.

    Wednesday, November 9, 2011 11:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Same Problem! Really infuriating that this happens! I Did a SBS 2003 to SBS 2011 upgrade last week and this happened. (Still unresolved) Doing another SBS 2003 to SBS 2011 Upgrade this week and AGAIN Same problem! No resolution anywhere! WTF! Microsoft needs to get their act together and post a fix or pull this bad update!

    I NEED AN ANSWER!

    Wednesday, November 9, 2011 2:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    They are not pulling it.

    Can you post up the contents of the log file and please start a new thread?

    If it doesn't work (and it does) your situation may be different than another so sometimes there isn't a single answer that works.

    Wednesday, November 9, 2011 3:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I found a workaround to fix the problem. Please wait I will test it again.
    Wednesday, November 9, 2011 3:24 PM
  • Question
    Sign in to vote
    24
    Sign in to vote

    I think I've found a workaround to fix the problem.

    I have the problem only on SBS 2011 systems that have been migrated.

    The SharePoint Foundation 2010 SP1 Update and psconfig upgrade works without problems with new installed SBS2011 systems.

    So I have compared the PSCDiagnostic Logs and found the following differences:

     

    PSCDiagnostic Log of a migrated SBS 2011:

    11/09/2011 15:39:57  13  INF                    Detected that this is a build to build upgrade. Re-provision the SPTracingServiceInstance service

    11/09/2011 15:39:58  13  INF                    Starting Service SPAdministrationServiceInstance

    11/09/2011 15:39:58  13  INF                    Detected that this is a build to build upgrade. Re-provision the SPAdministrationServiceInstance service

    11/09/2011 15:39:58  13  INF                    Starting Service SPSearchServiceInstance

    11/09/2011 15:39:58  13  INF                    Detected that this is a build to build upgrade. Re-provision the SPSearchServiceInstance service

    11/09/2011 15:40:04  13  INF                  Leaving function UpgradeTask.StartAllServices

    11/09/2011 15:40:04  13  INF                  SyncUpgradeTimerJob: sleeping for 10 seconds

    11/09/2011 15:40:14  13  INF                  SyncUpgradeTimerJob: SPTIMERV4 is not running anymore. Return -1.

    11/09/2011 15:40:14  13  ERR                  The exclusive inplace upgrader timer job failed.

    11/09/2011 15:40:14  13  INF                  Entering function StringResourceManager.GetResourceString

    11/09/2011 15:40:14  13  INF                    Resource id to be retrieved is UpgradeTaskFailConfigSyncDisplayLabel for language German (Germany)

    11/09/2011 15:40:14  13  INF                    Resource retrieved id UpgradeTaskFailConfigSyncDisplayLabel is Fehler beim Ausführen des Upgrades für SharePoint-Produkte.

    11/09/2011 15:40:14  13  INF                  Leaving function StringResourceManager.GetResourceString

    11/09/2011 15:40:14  13  INF                  Entering function Common.BuildExceptionMessage

    11/09/2011 15:40:14  13  INF                    Entering function StringResourceManager.GetResourceString

    11/09/2011 15:40:14  13  INF                      Resource id to be retrieved is ExceptionInfo for language German (Germany)

    11/09/2011 15:40:14  13  INF                      Resource retrieved id ExceptionInfo is Eine Ausnahme vom Typ '{0}' wurde ausgelöst. Weitere Ausnahmeinformationen: {1}

     

     PSCDiagnostic Log of a newly installed SBS2011:

    11/03/2011 09:04:40  8  INF              Detected that this is a build to build upgrade. Re-provision the SPTracingServiceInstance service

    11/03/2011 09:04:40  8  INF              Starting Service SPWriterServiceInstance

    11/03/2011 09:04:40  8  INF              Detected that this is a build to build upgrade. Re-provision the SPWriterServiceInstance service

    11/03/2011 09:04:41  8  INF              Starting Service SPAdministrationServiceInstance

    11/03/2011 09:04:41  8  INF              Detected that this is a build to build upgrade. Re-provision the SPAdministrationServiceInstance service

    11/03/2011 09:04:42  8  INF              Starting Service SPSearchServiceInstance

    11/03/2011 09:04:42  8  INF              Detected that this is a build to build upgrade. Re-provision the SPSearchServiceInstance service

    11/03/2011 09:04:45  8  INF              Starting Service SPTimerServiceInstance

    11/03/2011 09:04:45  8  INF              Detected that this is a build to build upgrade. Re-provision the SPTimerServiceInstance service

    11/03/2011 09:04:46  8  INF            Leaving function UpgradeTask.StartAllServices

    11/03/2011 09:04:46  8  INF            SyncUpgradeTimerJob: sleeping for 10 seconds

    11/03/2011 09:04:56  8  INF            Entering function StringResourceManager.GetResourceString

    11/03/2011 09:04:56  8  INF              Resource id to be retrieved is UpgradeTimerJobStatus for language German (Germany)

    11/03/2011 09:04:56  8  INF              Resource retrieved id UpgradeTimerJobStatus is Im Prozess des Timerdiensts wird ein Upgrade der Farm ausgeführt. Der Task ist zu {0:F2} % abgeschlossen.

    11/03/2011 09:04:56  8  INF            Leaving function StringResourceManager.GetResourceString

    11/03/2011 09:04:56  8  INF            Entering function TaskBase.OnTaskNotify

    11/03/2011 09:04:56  8  INF              Creating the OnTaskNotify event for task upgrade

    11/03/2011 09:04:56  8  INF              Entering function TaskBase.FireTaskNotify

    11/03/2011 09:04:56  8  INF                Firing the OnTaskNotify event for task upgrade

    11/03/2011 09:04:56  8  INF                Entering function CommandLine.TaskNotifyEventHandler

    11/03/2011 09:04:56  8  INF                Leaving function CommandLine.TaskNotifyEventHandler

    11/03/2011 09:04:56  8  INF              Leaving function TaskBase.FireTaskNotify

    11/03/2011 09:04:56  8  INF            Leaving function TaskBase.OnTaskNotify

     

    On the migrated SBS2011 PSCDiagnostic Log I found no entry to detect or start the services SPWriterServiceInstance and SPTimerServiceInstance.

     

    My workaround:

    I run once again the command „PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures“  in the “Bin” Folder as an administrator console session.

    In the moment I saw the staus “Configurationtask 5 of 6 is executed” I start to run the command “net start SPTraceV4 & net start SPWriterV4 & net start SPAdminV4 & net start SPSearch4 & net start SPTimerV4” in a parallel administrator console session and after that the configuration task finished successfully.


    • Edited by streamo Thursday, November 10, 2011 8:51 AM
    • Proposed as answer by Jacob Dybala Tuesday, January 3, 2012 5:01 AM
    Wednesday, November 9, 2011 4:13 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    The workaround worked for me. The backup work again after that. No more errors in the logs. The services are running again all

    Can someone else please test and confirm the workaround?
    Thursday, November 10, 2011 10:00 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    It Works!

    A bit strange, but the result was perfect!!!

     

    Thks Stremo!

    Sunday, November 27, 2011 8:03 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    How you figured this out is beyond me but thank you for sharing this with us!  This worked for me.  One thing worth mentioning is that when I copied the code from the website and created a batch file it did not work, I had to copy the same code and paste it into a command line instance.  That's probably doesn't matter for most but I figured it may help someone out there! 
    Tuesday, January 3, 2012 5:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    here is my psconfig error:

    Microsoft Windows [Version 6.1.7601]

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

     

    C:\Windows\system32>cd\

     

    C:\>cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\B

    IN

     

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN> PSC

    onfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd

     installfeatures

    SharePoint Products Configuration Wizard version 14.0.6009.1000. Copyright (C) M

    icrosoft Corporation 2010. All rights reserved.

     

    Performing configuration task 1 of 6

    Initializing SharePoint Products upgrade...

     

    Waiting to get a lock to upgrade the farm.

     

    Successfully initialized SharePoint Products upgrade.

     

    Performing configuration task 2 of 6

    Initiating the upgrade sequence...

     

    Successfully initiated the upgrade sequence.

     

    Performing configuration task 3 of 6

    Registering SharePoint features...

     

    Successfully installed feature C:\Program Files\Common Files\Microsoft Shared\We

    b Server Extensions\14\Template\Features\ReportServerStapling\Feature.xml.

     

    Successfully registered SharePoint features.

     

    Performing configuration task 4 of 6

    Installing the application content files...

     

    Installing the SharePoint Central Administration Web Application content files..

    .

     

    Installing the SharePoint Web Application content files...

     

    Failed to install the application content files.

     

    An exception of type System.IO.FileNotFoundException was thrown.  Additional exc

    eption information: Could not find file 'C:\inetpub\wwwroot\web.config'.

     

    Total number of configuration settings run: 4

    Total number of successful configuration settings: 3

    Total number of unsuccessful configuration settings: 2

    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_1_10_2012_14_23_47_210_1294875675.log and the application

    event log.

     

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN> PSC

    onfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd

     installfeatures

    SharePoint Products Configuration Wizard version 14.0.6009.1000. Copyright (C) M

    icrosoft Corporation 2010. All rights reserved.

     

    Performing configuration task 1 of 6

    Initializing SharePoint Products upgrade...

     

    Waiting to get a lock to upgrade the farm.

     

    Successfully initialized SharePoint Products upgrade.

     

    Performing configuration task 2 of 6

    Initiating the upgrade sequence...

     

    Successfully initiated the upgrade sequence.

     

    Performing configuration task 3 of 6

    Registering SharePoint features...

     

    Successfully installed feature C:\Program Files\Common Files\Microsoft Shared\We

    b Server Extensions\14\Template\Features\ReportServerStapling\Feature.xml.

     

    Successfully registered SharePoint features.

     

    Performing configuration task 4 of 6

    Installing the application content files...

     

    Installing the SharePoint Central Administration Web Application content files..

    .

     

    Installing the SharePoint Web Application content files...

     

    Successfully installed the application content files.

     

    Performing configuration task 5 of 6

    Upgrading SharePoint Products...

     

    10.00%The farm is being upgraded in the timer service process. The task is 26.32

    % completed.

     

    The farm is being upgraded in the timer service process. The task is 26.83% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 27.06% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 27.29% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 27.29% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 27.29% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 27.29% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 27.29% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 28.49% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 29.09% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 36.77% comp

    leted.

     

    The farm is being upgraded in the timer service process. The task is 36.78% comp

    leted.

     

    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_1_10_2012_14_53_20_743_1044296164.log and the application

    event log.

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>

     

    any suggestions ? 

    Abdul Rahman.Y
    Tuesday, January 10, 2012 7:20 AM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Worked for me. I think that the significant portion of those logs is:

    11/09/2011 15:40:14  13  INF                  SyncUpgradeTimerJob: SPTIMERV4 is not running anymore. Return -1.

    11/09/2011 15:40:14  13  ERR                  The exclusive inplace upgrader timer job failed.


    Wednesday, March 14, 2012 1:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Streamo's workaround did the trick for me.  Thank you for sharing.

    Regards,

    John Babbitt
    Systems Administrator
    Ashland Support Group

    Wednesday, March 21, 2012 5:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Steamo, thank you 1,000,000.  The work-around solved the same issue for me today, after several hours of failures, reboots, log reviews, and research.  For the record, this was also a migrated SBS 2003 installation.

    I also agree and empathize with everybody on this thread (as well as several other that eventually led me to here) that this was an incredibly messy patch by itself, and a complete (restrains himself from all-caps) disaster as regards the breaking of SBS backup.  My client, who is generally consumed with his 'day job' duties and uses my services infrequently, was running for several weeks without any backups, and then had to spend hundreds of dollars (and lost time on the other tasks I'm here to accomplish) to have me diagnose, research, and finally find this brilliant yet ridiculously arcane workaround. MS can and should do much better, especially considering how SBS is positioned and sold to end-users.

    Nuff-said,

    Janmon

    • Edited by Jsoar Thursday, April 19, 2012 5:09 AM
    Thursday, April 19, 2012 5:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    wow great it worked for me 2 thanks man
    Sunday, June 24, 2012 11:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Worked for me. Thx a lot already got grey hair from this s....

    Tuesday, July 31, 2012 8:43 AM
  • Question
    Sign in to vote
    3
    Sign in to vote

    I had the same issue and called Microsoft support.  Here is the fix:

    • Stop the "SharePoint 2010 Timer" service
    • Delete ONLY the xml files from C:\ProgramData\Microsoft\SharePoint\Config\216f8013-b78b-4e5b-8631-3a5f4c7277e8
    • Note: Do NOT delete the cache.ini file in this folder
    • Edit cache.ini and change to "1"
    • Start "SharePoint 2010 Timer" service
    • Run psconfig again:  PSConfig.exe -cmd upgrade -inplace b2b -wait -force
    Wednesday, August 1, 2012 7:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In my case trying to upgrade SharePoint 2010 Foundation with the command:

    PS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -
cmd installfeatures
    I initially received the same error. But then I simply ran the command a second time and was successful. For what its worth I did stop and restart the Timer Service in the Windows Server Manager. Don't know if that had anything to do with it.

    Wednesday, August 1, 2012 10:56 PM
  • Question
    Sign in to vote
    3
    Sign in to vote

    I had the same issue and called Microsoft support.  Here is the fix:

    • Stop the "SharePoint 2010 Timer" service
    • Delete ONLY the xml files from C:\ProgramData\Microsoft\SharePoint\Config\216f8013-b78b-4e5b-8631-3a5f4c7277e8
    • Note: Do NOT delete the cache.ini file in this folder
    • Edit cache.ini and change to "1"
    • Start "SharePoint 2010 Timer" service
    • Run psconfig again:  PSConfig.exe -cmd upgrade -inplace b2b -wait -force

    Thanks for posting this Ben, it worked for me.

    Had been getting the PSConfig error after applying Windows Updates on an SBS2011 Standard server installed in migration mode.

    • Proposed as answer by HorNet505 Friday, May 17, 2013 12:41 AM
    Thursday, December 6, 2012 9:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    1. Initially I tried http://support.microsoft.com/kb/2009272 but it did not help (I re-implemented later).
    2. I re-registered the DLL’s as per http://social.technet.microsoft.com/Forums/da/winservergen/thread/b4bd0deb-45d0-4661-8c50-a2b45db41103 from NareshD.  I do not believe this is necessary unless there is a corruption in the system but I am noting here just in case.
    3. I tried to run The PSConfig but it was failing:  I had to do the following in order to make it finish successfully:
      1. (from same page at http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/94a8bb64-e0ea-493f-8e29-01347b1fc6c7/) :
        On the migrated SBS2011 PSCDiagnostic Log I found no entry to detect or start the services SPWriterServiceInstance and SPTimerServiceInstance.
      2. I run once again the command „PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures“ in the “Bin” Folder as an administrator console session.
      3. In the moment I saw the status “Configuration task 5 of 6 is executed” I start to run the command “net start SPTraceV4 & net start SPWriterV4 & net start SPAdminV4 & net start SPSearch4 & net start SPTimerV4” in a parallel administrator console session and after that, the configuration task finished successfully.  (I just opened another cmd window and copy/paste the sequence below when I saw the status “Configuration Task x of y” on the screen:
        net start SPTraceV4
        net start SPWriterV4
        net start SPAdminV4
        net start SPSearch4
        net start SPTimerV4
        -Note SPSearch4 is disabled in our system…
        Very awkward but it worked…
    4. I implemented http://support.microsoft.com/kb/2009272 again.
    5. Backup started working with no errors.

    Constantine

    Saturday, December 15, 2012 4:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Getting similar problems and gone through loads of documents and got nowhere.  Hoping someone can shed some light on this please.

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>PSConfig.exe -cmd upgrade -inplace b2b -wait -force
    SharePoint Products Configuration Wizard version 14.0.6009.1000. Copyright (C) Microsoft Corporation 2010. All rights reserved.

    Performing configuration task 1 of 4
    Initializing SharePoint Products upgrade...

    Waiting to get a lock to upgrade the farm.

    Successfully initialized SharePoint Products upgrade.

    Performing configuration task 2 of 4
    Initiating the upgrade sequence...

    Successfully initiated the upgrade sequence.

    Performing configuration task 3 of 4
    Upgrading SharePoint Products...

    100.00%

    Failed to upgrade SharePoint Products.

    An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
      Additional exception information: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Se
    rver Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.

    Total number of configuration settings run: 3
    Total number of successful configuration settings: 2
    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 located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\1
    4\LOGS\PSCDiagnostics_1_20_2013_23_53_35_708_63478246.log and the application event log.


    -----

    Begin trace logging for SharePoint 2010 Products Configuration Wizard.  Version 14.0.6009.1000

    01/20/2013 23:54:05  9  WRN            Failed to add the service connection point for this farm
    01/20/2013 23:54:05  9  WRN            Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
    Microsoft.SharePoint.SPException: The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=johnmhayes,DC=local doesn't exist in the directory.
       at Microsoft.SharePoint.Administration.SPServiceConnectionPoint.Ensure(String serviceBindingInformation)
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()

    01/20/2013 23:54:33  9  ERR            Task upgrade has failed with an unknown exception
    01/20/2013 23:54:33  9  ERR            Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
       at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
       at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
    tion
    01/20/2013 23:54:33  9  ERR            An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
    Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
       at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
       at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

    01/20/2013 23:54:33  9  ERR              Task upgrade has failed
    01/20/2013 23:54:33  9  INF              friendlyMessage for task upgrade is An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
    01/20/2013 23:54:33  9  INF              debugMessage for task upgrade is An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
    Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
       at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
       at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

    01/20/2013 23:54:33  1  ERR          Task upgrade SharePoint Products failed, so stopping execution of the engine

    01/20/2013 23:54:33  1  ERR          Failed to upgrade SharePoint Products.
    An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
    Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
       at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
       at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

    01/20/2013 23:54:33  1  ERR          One or more configuration tasks has failed or some tasks were not run

    01/20/2013 23:54:33  1  ERR        One or more configuration tasks has failed to execute

    01/20/2013 23:54:33  1  ERR          Configuration of SharePoint Products failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\PSCDiagnostics_1_20_2013_23_53_35_708_63478246.log, fix the problem, and run this configuration wizard again.

    01/20/2013 23:54:33  1  ERR      Post setup configuration was not run successfully when using the command line task driver module







    Monday, January 21, 2013 12:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Can you link the entire log as I can't read anything in that snippit.  The service connection point is a red herring.

    Alternatively call support as issues with a security patch are a free call (they will comp it back at the end)

    Monday, January 21, 2013 12:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    try: http://sharepoint.stackexchange.com/questions/36064/service-connection-point-and-sp1

    If no luck, I would suggest to "repair" SP from add/remove programs and then re-run PSConfig.

    Good Luck!  I know how painfull it can be...

    Constantine

    Monday, January 21, 2013 12:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I wouldn't rip out sharepoint on a SBS box.  it's not as easy as add/remove (and on SBS 2011 it's in programs and features anyway)

    Please post up the entire log file first.

    Monday, January 21, 2013 1:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Susan, full log attached
    Friday, January 25, 2013 10:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Read lots of Forums and although some have worked in the past especially PSCONFIG this time it fails even to try.

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>PSCo
    nfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd
    installfeatures
    SharePoint Products Configuration Wizard version 14.0.6009.1000. Copyright (C) M
    icrosoft Corporation 2010. All rights reserved.

    then it comes back and says it failed to initialize............

    Backups have failed which is expected with the error.
    I am also unable to open sharepoint management shell as well as Central administration admin tried both running as administrator.
    The configuration wizard also fails.

    I don't really care about sharepoint it's the backups that i need to get running again.

    Everything went wrong after security updates .

    Any help would be gratetfully appreciated

     

    Sunday, February 10, 2013 3:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Do you have any relation to David Coperfield dude? The trick just worked for me as well!

    Dimitris Papadimitriou, Software Development Professional

    Friday, March 8, 2013 10:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In my case trying to upgrade SharePoint 2010 Foundation with the command:

    PS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -
cmd installfeatures
    I initially received the same error. But then I simply ran the command a second time and was successful. For what its worth I did stop and restart the Timer Service in the Windows Server Manager. Don't know if that had anything to do with it.

    I had the same problem while installing MS Project Server 2010 with April 2013 CU

    Base version: MS Project Server 2010 Service Pack 1 with June 2011 CU

    Installed Upgrade: April 9, 2013 CU KB2775426

    Installation was successful and SharePoint Configuration Wizard failed at the end. Just referred this thread out and did what Raja Afrija suggested ("restarted SharePoint Timer Service" and re-ran the config wizard with run as administrator"). This fixed the problem and all set to work.

    Thank you so much for this discussion thread.

    Thank you, Ravi.

    Saturday, May 11, 2013 8:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The workaround of starting the services works here!
    Tuesday, May 14, 2013 12:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Susan

    When I go to Control Panel: "Uninstall or change a program" I can see "Microsoft SharePoint Foundation 2010"!  This is an SBS 2011 installation.  Am I not supposed to be able to see it there? 

    We hired a company to do some work on the SharePoint: is it possible that they reinstalled SharePoint individually (not through the SBS2011 disk" and this is why I am having problems after each and any MS update on the server not being able to backup?

    Thanks

    CG

    Constantine

    Sunday, May 19, 2013 2:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You are supposed to see it in there.  It's possible that there was an update installed and no one psconfig'd.

    Can you start a new thread please?

    Sunday, May 19, 2013 4:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for the reply Susan.  There are several threads open for my problem:

    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/9166eda7-d702-4b5e-b04c-142b7e73b971

    http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/d5daada2-b78b-4935-bd9e-80726c26c4a8

    http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/920bf71e-be19-49eb-9f2b-ebcf70ad8177

    (and some more...) but none of them has fixed my backup problem.  Backup used to work fine.  Now, every time I install the monthly security updates, unless I manage to get psconfig to work (problem in this thread) the backups do not happen.  I follow the procedure I posted at http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/9166eda7-d702-4b5e-b04c-142b7e73b971 and then everything starts working fine.

    Thanks again

    Constantine

    Monday, May 20, 2013 12:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As I vaguely recall windows search is supposed to be enabled.

    Monday, May 20, 2013 12:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I just double checked and Windows Search service "WSearch" is enabled.  The only difference from the standard SBS2011 SharePoint installation is that the new Adobe iFilter is installed. 

    When I follow the procedure I posted at http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/9166eda7-d702-4b5e-b04c-142b7e73b971 and then everything starts working fine.

    THANKS!

     

    Constantine

    Monday, May 20, 2013 12:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks, it's work so good...

    Tuesday, July 16, 2013 2:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    plz help me on this case:

    http://social.technet.microsoft.com/Forums/sharepoint/en-US/8071f02f-2220-4405-9cc9-de9c19838805/cant-view-excel-files-in-browser-unable-to-proess-the-request-wait-a-few-minutes-and-try

    Tuesday, July 16, 2013 2:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    For me the fix worked as well, but although the SharePoint sites (companyweb) are running normally, the central administration site still fails to launch with a 503 error. The SharepointAministrationPool in IIS stops working. Any thoughts on that? Do I need to clear the config cache once more?

    SBS2011 standard, (fresh install, no upgrade from 2003), with all patches and updates running. Windows backup is running fine.

    Monday, July 29, 2013 8:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In my situation, I was running SP2010 SP2 upgrade and getting a failure on Task 3 of 4 after executing psconfig.exe -cmd upgrade -inplace b2b. The failure occured at 10.00% and displayed this message:

    10.00%Failed to upgrade SharePoint Products.

    Following streamo's suggestion, I set up the netstart command in a new cmd window and executed it when I saw the 10.00% notification first appear. The process completed. I then ran the PSConfig GUI tool from the start menu to finish off the upgrade.

    Many thanks to streamo!

    

    Kevin Scott

    • Proposed as answer by CoachBill1 Tuesday, December 29, 2015 7:25 PM
    Wednesday, August 14, 2013 3:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    use this command and every things work fine: psconfig.exe -cmd upgrade -b2b -wait -force its work for me.

    VA SharePoint MCTS

    Friday, August 16, 2013 1:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    it works for me. use -wait psconfig.exe -cmd upgrade -inplace b2b -wait -force I hope that's useful.

    VA SharePoint MCTS

    Friday, August 16, 2013 1:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Turning off UAC worked!! Well, I also rebooted my WFE servers also, but it Configuration Wizard was able to complete after that.
    Friday, August 30, 2013 5:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    it worked like magic...thanks a lot!!!!
    • Proposed as answer by paromita4u Wednesday, October 9, 2013 10:35 AM
    Wednesday, October 9, 2013 10:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This worked for me

    PSConfig.exe -cmd upgrade -inplace b2b -wait -force -cmd applicationcontent -install -cmd installfeatures

    I just took the original command and added "-wait"

    Thanks to all in this thread that helped

    Mark

    Crash-2000.com

    I also did this too

    I had the same issue and called Microsoft support.  Here is the fix:

    • Stop the "SharePoint 2010 Timer" service
    • Delete ONLY the xml files from C:\ProgramData\Microsoft\SharePoint\Config\216f8013-b78b-4e5b-8631-3a5f4c7277e8
    • Note: Do NOT delete the cache.ini file in this folder
    • Edit cache.ini and change to "1"
    • Start "SharePoint 2010 Timer" service
    • Run psconfig again:  PSConfig.exe -cmd upgrade -inplace b2b -wait -force

    Mark Bale


    • Edited by Crash2000 Tuesday, December 3, 2013 6:53 PM
    Tuesday, December 3, 2013 6:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Clear the SharePoint configuration cache:
    • Log into each server in the farm if more than single server deploy
    • On each server stop the SP timer service
    • On each server go to C:\ProgramData\Microsoft\SharePoint\Config\GUID and make a copy of the folder that contains the cache.ini file.
    • Sort by file type, delete all files accept the cache.ini (.xml, .tmp)
    • Edit the cache.ini file and select all and delete.  Enter the numeral 1 and save on each server.
    • Start the SharePoint Timer service on all servers

      Make sure all SharePoint services are running on each server then try running PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures again.  This has fixed the problem for me many times.
    Wednesday, January 8, 2014 5:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Guys

    I thought I'd add our experience with this issue. Hopefully it will help somebody out there.

    We'd been having the same problems as reported here. This all started because SBS2011 Windows Server backup failed due to SPSearch VSS writer failure and turned out that we needed to complete the SharePoint upgrade using psconfig.exe and failed as above. We tried all the fixes suggested above without success and eventually turned to Microsoft support for help.

    Our problem turned out to be a corrupt SPSearch SQL database - the Ms tech deleted and recreated it and then ran psconfig successfully. I'm afraid I can't give you the diagnostic trail that lead to the diagnosis but bear this in mind if you are struggling.

    Tuesday, January 28, 2014 10:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I think I've found a workaround to fix the problem.

    I have the problem only on SBS 2011 systems that have been migrated.

    The SharePoint Foundation 2010 SP1 Update and psconfig upgrade works without problems with new installed SBS2011 systems.

    So I have compared the PSCDiagnostic Logs and found the following differences:

     

    PSCDiagnostic Log of a migrated SBS 2011:

    11/09/2011 15:39:57  13  INF                    Detected that this is a build to build upgrade. Re-provision the SPTracingServiceInstance service

    11/09/2011 15:39:58  13  INF                    Starting Service SPAdministrationServiceInstance

    11/09/2011 15:39:58  13  INF                    Detected that this is a build to build upgrade. Re-provision the SPAdministrationServiceInstance service

    11/09/2011 15:39:58  13  INF                    Starting Service SPSearchServiceInstance

    11/09/2011 15:39:58  13  INF                    Detected that this is a build to build upgrade. Re-provision the SPSearchServiceInstance service

    11/09/2011 15:40:04  13  INF                  Leaving function UpgradeTask.StartAllServices

    11/09/2011 15:40:04  13  INF                  SyncUpgradeTimerJob: sleeping for 10 seconds

    11/09/2011 15:40:14  13  INF                  SyncUpgradeTimerJob: SPTIMERV4 is not running anymore. Return -1.

    11/09/2011 15:40:14  13  ERR                  The exclusive inplace upgrader timer job failed.

    11/09/2011 15:40:14  13  INF                  Entering function StringResourceManager.GetResourceString

    11/09/2011 15:40:14  13  INF                    Resource id to be retrieved is UpgradeTaskFailConfigSyncDisplayLabel for language German (Germany)

    11/09/2011 15:40:14  13  INF                    Resource retrieved id UpgradeTaskFailConfigSyncDisplayLabel is Fehler beim Ausführen des Upgrades für SharePoint-Produkte.

    11/09/2011 15:40:14  13  INF                  Leaving function StringResourceManager.GetResourceString

    11/09/2011 15:40:14  13  INF                  Entering function Common.BuildExceptionMessage

    11/09/2011 15:40:14  13  INF                    Entering function StringResourceManager.GetResourceString

    11/09/2011 15:40:14  13  INF                      Resource id to be retrieved is ExceptionInfo for language German (Germany)

    11/09/2011 15:40:14  13  INF                      Resource retrieved id ExceptionInfo is Eine Ausnahme vom Typ '{0}' wurde ausgelöst. Weitere Ausnahmeinformationen: {1}

     

     PSCDiagnostic Log of a newly installed SBS2011:

    11/03/2011 09:04:40  8  INF              Detected that this is a build to build upgrade. Re-provision the SPTracingServiceInstance service

    11/03/2011 09:04:40  8  INF              Starting Service SPWriterServiceInstance

    11/03/2011 09:04:40  8  INF              Detected that this is a build to build upgrade. Re-provision the SPWriterServiceInstance service

    11/03/2011 09:04:41  8  INF              Starting Service SPAdministrationServiceInstance

    11/03/2011 09:04:41  8  INF              Detected that this is a build to build upgrade. Re-provision the SPAdministrationServiceInstance service

    11/03/2011 09:04:42  8  INF              Starting Service SPSearchServiceInstance

    11/03/2011 09:04:42  8  INF              Detected that this is a build to build upgrade. Re-provision the SPSearchServiceInstance service

    11/03/2011 09:04:45  8  INF              Starting Service SPTimerServiceInstance

    11/03/2011 09:04:45  8  INF              Detected that this is a build to build upgrade. Re-provision the SPTimerServiceInstance service

    11/03/2011 09:04:46  8  INF            Leaving function UpgradeTask.StartAllServices

    11/03/2011 09:04:46  8  INF            SyncUpgradeTimerJob: sleeping for 10 seconds

    11/03/2011 09:04:56  8  INF            Entering function StringResourceManager.GetResourceString

    11/03/2011 09:04:56  8  INF              Resource id to be retrieved is UpgradeTimerJobStatus for language German (Germany)

    11/03/2011 09:04:56  8  INF              Resource retrieved id UpgradeTimerJobStatus is Im Prozess des Timerdiensts wird ein Upgrade der Farm ausgeführt. Der Task ist zu {0:F2} % abgeschlossen.

    11/03/2011 09:04:56  8  INF            Leaving function StringResourceManager.GetResourceString

    11/03/2011 09:04:56  8  INF            Entering function TaskBase.OnTaskNotify

    11/03/2011 09:04:56  8  INF              Creating the OnTaskNotify event for task upgrade

    11/03/2011 09:04:56  8  INF              Entering function TaskBase.FireTaskNotify

    11/03/2011 09:04:56  8  INF                Firing the OnTaskNotify event for task upgrade

    11/03/2011 09:04:56  8  INF                Entering function CommandLine.TaskNotifyEventHandler

    11/03/2011 09:04:56  8  INF                Leaving function CommandLine.TaskNotifyEventHandler

    11/03/2011 09:04:56  8  INF              Leaving function TaskBase.FireTaskNotify

    11/03/2011 09:04:56  8  INF            Leaving function TaskBase.OnTaskNotify

     

    On the migrated SBS2011 PSCDiagnostic Log I found no entry to detect or start the services SPWriterServiceInstance and SPTimerServiceInstance.

     

    My workaround:

    I run once again the command „PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures“  in the “Bin” Folder as an administrator console session.

    In the moment I saw the staus “Configurationtask 5 of 6 is executed” I start to run the command “net start SPTraceV4 & net start SPWriterV4 & net start SPAdminV4 & net start SPSearch4 & net start SPTimerV4” in a parallel administrator console session and after that the configuration task finished successfully.


    Helped me out to find out that one of the services was disabled.

    So before running config wizard, check all of your SHP services and if they are running (mine SPSearchV4 was disabled ==> update failed)

    Wednesday, February 19, 2014 8:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Very Much for this, slightly odd, but very effective solution. Saved me much time.

    Cheers

    Tuesday, June 17, 2014 9:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Does these commands need to be ran on every server in the farm?  Thanks!
    Wednesday, June 18, 2014 2:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Workaround worked for me also, thanks !
    Thursday, July 17, 2014 4:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you soooo much. This worked a treat. Cant believe Microsoft released a update that doesn't work with migrated servers. Well spotted

    Friday, August 15, 2014 6:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the workaround, Streamo. Worked perfectly. Appreciated.
    Thursday, September 11, 2014 7:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I fixed. you need to double check that account you are using to install, have the owner permissions on all content databases on the SQL. You can check on the error file generated on the ULS logs "Upgrade-20140911-161053-772-error" if you use the command

    PSConfig.exe -cmd upgrade -inplace b2b -force

    Thursday, September 11, 2014 9:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Streamo, thank you, this also worked on a SharePoint 2013 SP1 server - Chad
    Wednesday, April 1, 2015 7:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It worked for me too Thankyou
    Tuesday, May 26, 2015 8:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I had the same problem and found the answer somewhere else (what is currently marked as answer here is useless).

    Found it here: http://blogs.technet.com/b/sharepointwarrior/archive/2012/12/07/sp-2010-psconfig-fails-with-missing-security-updates-that-are-actually-installed.aspx

    • run psconfig –cmd upgrade –inplace b2b –force –cmd installcheck –noinstallcheck
    • as soon as stsadm says ‘upgrading sharepoint products” (step 4 of 5) open a command prompt and force start the SharePoint timer service “net start SPTimerV4”
    • PSCONFIG succeeds!!!

    As for the reasons why this happens...if someone finds out, thank you for sharing.

    Patrick

    Patrick Beauperin

    Monday, July 13, 2015 8:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This was my issue. Thanks.
    Monday, August 17, 2015 12:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Another workaround is to run the PS Command:

    get-spproduct -local   If you get any error relating to missing updates you know that are installed.  This command actually "reindexes the installed updates" so that they show up in CA.

    I ALWAYS check the "Manage Servers...." link in CA.  This is where your first alert for missing updates can be seen.

    Monday, September 14, 2015 1:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    More total BS,,,,!!!!!!!!!!!!!!!!  F*,  Do yo want to sell SharePoint 2013?  OR NOT?   I cant get around this total lazy jacked up total bs crap that Microsft has created... thanks for wastring over a week of my time,,, and I still cant get sharepoint 2013 to install????  I guess I will spend millions with unix, Linux systems?   since you want me to pay for your support for me to evaluate your Applications?  Are you f**** High?   how do expect to sell any product if we cant even get it to install?    Ass Hats
    Friday, December 11, 2015 10:50 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    After trying most of the suggestions above, what worked for me was to break the process into two parts. Restarting the SharePoint Timer Service was not necessary.

    First executing:

    PS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN> .\psconfig.exe -cmd upgrade -inplace b2b -wait -force

    SharePoint Products Configuration Wizard version 15.0.4569.1503. Copyright (C) Microsoft Corporation 2012. All rights rese

    Performing configuration task 1 of 4
    Initializing SharePoint Products upgrade...

    Waiting to get a lock to upgrade the farm.

    Successfully initialized the SharePoint Products configuration.

    Performing configuration task 2 of 4
    Initiating the upgrade sequence...

    Successfully initiated the upgrade sequence.

    Performing configuration task 3 of 4
    Upgrading SharePoint Products...

    100.00% :
    Successfully upgraded SharePoint Products.

    Performing configuration task 4 of 4
    Finalizing the SharePoint Products configuration...

    Successfully completed the SharePoint Products configuration.

    Total number of configuration settings run: 4
    Total number of successful configuration settings: 4
    Total number of unsuccessful configuration settings: 0
    Successfully stopped the configuration of SharePoint Products.

    Then a second run with: ( This will process configuration steps 5-9 )

    PS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN> .\psconfigui.exe -cmd upgrade -inplace b2b -wait -force

    • Proposed as answer by Thomasd.rosa Thursday, April 28, 2016 5:35 PM
    Tuesday, December 29, 2015 7:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This command solve my problem, SharePoint 2013 Foundation.

    I have to clear the cache too

    psconfigui.exe -cmd upgrade -inplace b2b -wait -force

    Thursday, April 28, 2016 5:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you, this helped me, and backup works also :)
    Tuesday, August 23, 2016 1:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    High everyone. We ran into this problem and error as well, but mine was a little different in case the above workarounds do not work for everyone. Some databases cannot be updated when they are in a HA failover or mirroring configuration. We utilize SQL 2012 and Always on. I had to remove all the databases from the availability groups, then run psconfig, then it worked. Figured this out a while back, but was training a colleague on how to update SharePoint 2013 and he ran across this post.
    Thursday, September 22, 2016 4:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the same issue.  What was the resolution?

    Kindest regards,

    Thursday, January 26, 2017 5:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Wow! after 20+ hours of work and trying everything found on Google, THIS worked for me.
    Thank you so much!
    Friday, February 24, 2017 1:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Before doing any step,first try the below steps

    1.Change UAC to low

    2.Run As Administrator "sharepoint products and configuration wizard"

    Tuesday, November 14, 2017 7:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I can confirm this workaround worked for me

    Thanks

    Wednesday, November 15, 2017 8:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This worked for me as it shown the exact content db name which was causing error

    Please Mark it as answer if this reply helps you in resolving the issue,It will help other users facing similar problem

    Friday, February 9, 2018 8:19 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It may be worth adding -wait to the command.

    i.e.

    PSConfig.exe -cmd upgrade -inplace b2b -wait -force -cmd applicationcontent -install -cmd installfeatures

    This worked for me after trawling through all of the similar posts.


    • Edited by JABOLTON Thursday, January 10, 2019 4:55 PM Paste issue
    Thursday, January 10, 2019 4:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Everyone.

    We found when you start the upgrade process the upgrade stops the SharePoint 2010 Timer.  As soon as you start the upgrade and once the Timer is stopped, restart the Timer.  The upgrade completed without issue.

    Greg

    Thursday, May 14, 2020 2:09 PM