Sharepoint 2013 Updates Error

Question

Sharepoint 2013 Updates Error

Dave Nordin 1

Hi

While trying to run Sharepoint 2013 Updates using the powershell script:

Apply server upgrades

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

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

Got errors for the first time in years on updated Windows Server (On Prem) 2012 R2:

10/07/2021 07:15:07 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.

Follow this link for more information about how to troubleshoot upgrade failures:
https://go.microsoft.com/fwlink/?LinkId=259653

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()

1 answer

Your answer

Answer 1

Allen Xu_MSFT 13,866

Hi @Dave Nordin ,

Please have a try to the below solution to this issue(Note: run all PowerShell (PS) commands as an administrator in an elevated PowerShell window – need 2 pre-opened windows):

Turn off all the following services (you can do this in your first PowerShell window). net stop SPTraceV4; net stop SPWriterV4; net stop SPAdminV4; net stop SPTimerV4; net stop w3svc
Manually stop both search services (in the services GUI on the SP server). Then run the following command in your second PowerShell window. stsadm -o setproperty -pn command-line-upgrade-running -pv No
Flush the Config Cache follow this blog post and run the following PowerShell in your second PowerShell window. PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
As soon as it reaches the step where the error appeared before in the upgrade process, in the first elevated PS window, run the following PS. net start SPTraceV4; net start SPWriterV4; net start SPAdminV4; net start SPTimerV4; net start w3svc
Quickly and manually start the two search services (in the Services GUI on the SP Server). The upgrade process should complete successfully after this.

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Dave Nordin 1 Reputation point

2021-10-08T13:14:21.3+00:00

Allen,

I was able to run this procedure and SP updates ran successfully as a result on our dev server (a 1 server farm.)

However, a subsequent straight-up run of the updates fifteen minutes later failed with the original error again.
Dave Nordin 1 Reputation point

2021-10-08T13:23:15.897+00:00
Allen,

We are also experiencing other issues on both our dev and production instances:

A certain document library cannot not receive drag-drop file uploads without hanging (prod and dev.)

At least one of our workflows is failing to update status columns in its related list. I have been updating these manually.

There have been no changes to these instances for years.

My approach to diagnosing these was to first restart the dev server & services and then to run SP Updates.

This is the reason I first reported only the updates issue as it made sense to get that working to see if the other
problems might be fixed as a result.
Allen Xu_MSFT 13,866 Reputation points

2021-10-11T07:39:03.263+00:00

@Dave Nordin

Do you mean that after following the steps above, the cmdlet "PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures" has been executed successfully on your dev server? Have you installed the CU before executing the cmdlet on all your SharePoint servers?
Dave Nordin 1 Reputation point

2021-10-11T12:19:46.08+00:00

I have only run the prescribed steps on the dev Sharepoint instance, which consists of only one server.

After following the steps, the cmdlet ran though 100% successfully. The logs indicate Sharepoint dev is at 15.0.5363.1000.

This looks like a pretty recent release looking at this list:

https://learn.microsoft.com/en-us/officeupdates/sharepoint-updates?redirectedfrom=MSDN

If I run the cmdlet again, without all the steps, it fails with the problem I originally reported.

Other problems I described with the document libraries and workflows persist as well.

I will try to download and install the September CU on the dev instance:

https://support.microsoft.com/en-us/topic/september-14-2021-cumulative-update-for-sharepoint-enterprise-server-2013-kb5002023-e1e2e7e4-3eb4-41c3-9c12-c331a86b9be2
Allen Xu_MSFT 13,866 Reputation points

2021-10-12T01:41:29.003+00:00

@Dave Nordin ,

You have to install the CU on all servers in your SharePoint farm before using PSConfig.exe.
Dave Nordin 1 Reputation point

2021-10-12T17:45:10.327+00:00

Yes the CU was installed and the subsequent run with the extra steps activated it successfully in dev. The dev instance was upgraded from 15.0.5363.1000 to 15.0.5379.1000.

September 14, 2021, cumulative update for SharePoint Enterprise Server 2013 (KB5002023)

https://support.microsoft.com/en-us/topic/september-14-2021-cumulative-update-for-sharepoint-enterprise-server-2013-kb5002023-e1e2e7e4-3eb4-41c3-9c12-c331a86b9be2
Dave Nordin 1 Reputation point

2021-10-12T17:49:12.543+00:00

This upgrade does not appear to have fixed our problems with document libraries and workflows as described in earlier posts.

These are mission critical objects in our production instance.

As a result, I would like to set up a remote session with someone on your end so I can demonstrate these issues and get them fixed.

Please let me know a good time.

Thanks
Allen Xu_MSFT 13,866 Reputation points

2021-10-13T01:27:37.247+00:00

@Dave Nordin ,

Forum technical support on Microsoft Q&A does not support seeting up a remote session with you. If the issue is urgent to your business, it is recommended that you contact Microsoft Customer Support Services (CSS) via telephone so that a dedicated Support Professional can assist you in a more efficient manner. Please be advised that you might be charged for phone support service. Please go to the website (https://support.microsoft.com/en-sg/help/4051701/global-customer-service-phone-numbers) to find related number and call it to create a new Phone Service Request to Microsoft Phone Support team.
Allen Xu_MSFT 13,866 Reputation points

2021-10-18T06:00:25.147+00:00

@Dave Nordin ,

You can share here if you get any solution from CSS phone support. It will be beneficial to others who meet similar issues to yours.

Share via

Sharepoint 2013 Updates Error

While trying to run Sharepoint 2013 Updates using the powershell script:

Apply server upgrades

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

1 answer

Your answer