none
SharePoint Update stuck at same step in all version

    Question

  • I am running psconfig after the July monthly security patches and they have now been running on 8 different farms for 6 hours.They all seem to be spinning their wheels at the same place and in all versions of SP including 2010, 2013 and 2016.

    Has anyone else seen extremely long configuration times after the patches? It's concerning that I am seeing this happen in all farms on all versions. I'm hoping it's not something going on with out internal architecture.

    The are all stuck at this step for 2013 and 2016:

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

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

    This is using the following command to update:

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

    For the 2010 farms, I am stuck at the following step:

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

    For these older systems we just use the following command to update:

    PSCONFIG.EXE -cmd upgrade -inplace b2b -wait

    Here is a snipit of the last few lines of the update log file. The last entry is only a few minutes after starting the update:

    07/12/2018 08:31:36.21 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPManager ajxot DEBUG calling Prejoined farm level actions. 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:36.21 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPUpgradeSession aloop DEBUG Entering upgrade for [SPPrejoinedFarm] 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:36.22 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPDelegateManager ajyys DEBUG Delegate [Microsoft.SharePoint.Search.Upgrade.SPSearchServiceSequence2] returned not applicable for [SPPrejoinedFarm]. 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:36.24 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPDelegateManager ajyys DEBUG Delegate [Microsoft.Office.Server.Search.Upgrade.SearchServiceSequence2] returned not applicable for [SPPrejoinedFarm]. 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:36.24 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPUpgradeSession ajxmf DEBUG CanUpgrade [SPPrejoinedFarm] returned: True. 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:36.24 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPHierarchyManager ajyw6 DEBUG [SPTree Value=SPPrejoinedFarm] added to dependency cache by lookup 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:36.24 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPUpgradeSession ajxnh DEBUG [SPPrejoinedFarm] IsGrown=False IsRoot=True IsLeaf=True. 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:36.24 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [SPPrejoinedFarm] returned: False. 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:36.24 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPUpgradeSession ajxno DEBUG Skip upgrading [SPPrejoinedFarm]. 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:36.24 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPUpgradeSession alooy DEBUG Exiting upgrade for [SPPrejoinedFarm].  Elapsed Time=[00:00:00] 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:36.24 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPManager ajxow DEBUG Using local farm SPFarm Name=SharePoint_Config. 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:53.19 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPUpgradeSession ajxmc DEBUG Upgrade session is committed to the farm SPFarm Name=SharePoint_Config 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:53.19 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPUpgradeSession ajxn2 DEBUG UPGRADE PERCENTAGE: 5.00000000% done, Total Elapsed Time 00:01:44.0359496. 00000000-0000-0000-0000-000000000000
    07/12/2018 08:31:53.19 PSCONFIG (0x25AC) 0x1450 SharePoint Foundation Upgrade SPManager aj0ul INFO psconfig: Successfully bootstrapped the upgrade sequence by calling SPManager.Initialized() with flags [ConsoleOutput]. 00000000-0000-0000-0000-000000000000


    ULS logs have the same repeating lines over and over again:

    07/12/2018 15:13:36.71 DistributedCacheService.exe (0x0530) 0x1F68 SharePoint Foundation DistributedCache ahlcq Medium Calling... SPDistributedCacheClusterCustomProvider:: BeginTransaction
    07/12/2018 15:13:36.71 DistributedCacheService.exe (0x0530) 0x1F68 SharePoint Foundation DistributedCache ahlcr Medium Successfully executed... SPDistributedCacheClusterCustomProvider:: BeginTransaction
    07/12/2018 15:13:36.71 DistributedCacheService.exe (0x0530) 0x1F68 SharePoint Foundation DistributedCache ahlc2 Medium Calling... SPDistributedCacheClusterCustomProvider:: GetValue(object transactionContext, string type, string key).
    07/12/2018 15:13:36.71 DistributedCacheService.exe (0x0530) 0x1F68 SharePoint Foundation DistributedCache ahlc3 Medium Successfully executed... SPDistributedCacheClusterCustomProvider:: GetValue(object transactionContext, string type, string key).
    07/12/2018 15:13:36.71 DistributedCacheService.exe (0x0530) 0x1F68 SharePoint Foundation DistributedCache ahlc0 Medium Calling... SPDistributedCacheClusterCustomProvider:: GetStoreUtcTime.
    07/12/2018 15:13:36.71 DistributedCacheService.exe (0x0530) 0x1F68 SharePoint Foundation DistributedCache ahlc1 Medium Successfully executed... SPDistributedCacheClusterCustomProvider:: GetStoreUtcTime
    07/12/2018 15:13:36.71 DistributedCacheService.exe (0x0530) 0x1F68 SharePoint Foundation DistributedCache ahldb Medium Calling... SPDistributedCacheClusterCustomProvider:: Update(object transactionContext, string type, string key, byte[] data, long oldVersion).
    07/12/2018 15:13:36.71 DistributedCacheService.exe (0x0530) 0x1F68 SharePoint Foundation DistributedCache ahldc Medium Successfully executed... SPDistributedCacheClusterCustomProvider:: Update(object transactionContext, string type, string key, byte[] data, long oldVersion).
    07/12/2018 15:13:48.29 PSCONFIG.EXE (0x25AC) 0x1D50 SharePoint Foundation Topology aae1 Medium Updating server locks.
    07/12/2018 15:13:48.31 PSCONFIG.EXE (0x25AC) 0x1D50 SharePoint Foundation Topology aae2 Medium Successfully updated [1] server locks. pid=[9644]
    07/12/2018 15:14:03.40 PSCONFIG.EXE (0x25AC) 0x1D50 SharePoint Foundation Topology aae1 Medium Updating server locks.
    07/12/2018 15:14:03.40 PSCONFIG.EXE (0x25AC) 0x1D50 SharePoint Foundation Topology aae2 Medium Successfully updated [1] server locks. pid=[9644]
    07/12/2018 15:14:18.52 PSCONFIG.EXE (0x25AC) 0x1D50 SharePoint Foundation Topology aae1 Medium Updating server locks.
    07/12/2018 15:14:18.52 PSCONFIG.EXE (0x25AC) 0x1D50 SharePoint Foundation Topology aae2 Medium Successfully updated [1] server locks. pid=[9644]


     

    jeudi 12 juillet 2018 19:18

Toutes les réponses

  • You can't run Config wizard or PSConfig command in all servers simultaneously. It's one at a timer per server. 
    jeudi 12 juillet 2018 19:50
  • You are correct. While each farm is multi tier with various server roles, only the server with Central Admin on it is running psconfig per each farm. It is stuck on the first server running the configuration on every farm.
    jeudi 12 juillet 2018 21:36
  • I have used the script(see below link) several times on a SharePoint 2013 farm and it always works without a hitch. It has saved me countless hours.

    https://blogs.msdn.microsoft.com/russmax/2013/04/01/why-sharepoint-2013-cumulative-update-takes-5-hours-to-install/


    nme

    jeudi 12 juillet 2018 21:44
  • I appreciate the script and may use it the next CU that comes along.

    However, I don't think it will help in this instance as this is just a normal monthly security update and it would appear that it's not the amount of time that it is taking, but the fact that NOTHING is happening after the configuration gets to a certain step.

    I would try to back out the updates but, as they have already partially run on one server in the farm, it would probably result in a version mismatch. Nobody wants that.

    jeudi 12 juillet 2018 22:27
  • Hi David, 

    Which update did you installed?

    You can check whether this cumulative update must have Microsoft SharePoint Server 2013 Service Pack 1 installed.

    Try to run the Configuration wizard again by selecting configuration wizard as "Run as Administration".

    Best Regards, 

    Lisa Chen 



    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    vendredi 13 juillet 2018 08:45
    Modérateur